[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] VM crashed after migration.

From: Ma, Stephen B.
Subject: [Qemu-devel] VM crashed after migration.
Date: Fri, 13 Jul 2012 18:34:47 +0000


Sometimes I am seeing my VM crash immediately after it has been migrated to a 
new host.  The VM is running RHEL6.2 with the following devices:

The VM has the following devices:
address@hidden ~]# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] 
(rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:04.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
High Definition Audio Controller (rev 01)
00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device
00:06.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
00:07.0 SCSI storage controller: Red Hat, Inc Virtio block device
00:08.0 Ethernet controller: Red Hat, Inc Virtio network device

Here is the backtrace from crash:

This GDB was configured as "x86_64-unknown-linux-gnu"...

      KERNEL: /usr/lib/debug/lib/modules/2.6.32-220.el6.x86_64/vmlinux
        CPUS: 8
        DATE: Fri Jul 13 09:13:10 2012
      UPTIME: 00:02:41
LOAD AVERAGE: 2.25, 0.75, 0.27
       TASKS: 362
    NODENAME: vmdev51.cup.hp.com
     RELEASE: 2.6.32-220.el6.x86_64
     VERSION: #1 SMP Wed Nov 9 08:03:13 EST 2011
     MACHINE: x86_64  (2266 Mhz)
      MEMORY: 32 GB
       PANIC: "kernel BUG at drivers/ata/libata-sff.c:1453!"
         PID: 73
     COMMAND: "ata/4"
        TASK: ffff88080c2feb00  [THREAD_INFO: ffff88080c302000]
         CPU: 4

crash> bt
PID: 73     TASK: ffff88080c2feb00  CPU: 4   COMMAND: "ata/4"
 #0 [ffff88080c303a60] machine_kexec at ffffffff81031fcb
 #1 [ffff88080c303ac0] crash_kexec at ffffffff810b8f72
 #2 [ffff88080c303b90] oops_end at ffffffff814f04b0
 #3 [ffff88080c303bc0] die at ffffffff8100f26b
 #4 [ffff88080c303bf0] do_trap at ffffffff814efda4
 #5 [ffff88080c303c50] do_invalid_op at ffffffff8100ce35
 #6 [ffff88080c303cf0] invalid_op at ffffffff8100bedb
    [exception RIP: ata_sff_hsm_move+317]
    RIP: ffffffff8138009d  RSP: ffff88080c303da0  RFLAGS: 00010297
    RAX: 0000000000000000  RBX: ffff8808073c80d0  RCX: 0000000000000000
    RDX: ffff8808073c8180  RSI: 0000000000000046  RDI: 0000000000000009
    RBP: ffff88080c303e00   R8: 0000000000008d87   R9: 0000000000000000
    R10: 000000000000000f  R11: 0000000000000007  R12: ffff8808073c8000
    R13: 0000000000000004  R14: 0000000000000058  R15: ffff8808073c9d08
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #7 [ffff88080c303e08] ata_pio_task at ffffffff81380a83
 #8 [ffff88080c303e38] worker_thread at ffffffff8108b2b0
 #9 [ffff88080c303ee8] kthread at ffffffff81090886
#10 [ffff88080c303f48] kernel_thread at ffffffff8100c14a

The VM has an active-backup bond bond0 with a virtio device as the active port. 
 If the bonding interface hasn't been created, the migration of the VM succeeds 
with no panic afterwards.  Anyone know what the problem is?

Here is more information about the systems:

KVM and OS (on both src and target hosts): 3.4.0-rc4
OS on the VM: RHEL6.2
Qemu: qemu 1.1

reply via email to

[Prev in Thread] Current Thread [Next in Thread]