Bug 591410 - BSOD occurred after live migration without shared storage
BSOD occurred after live migration without shared storage
Status: CLOSED NEXTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.0
All Linux
medium Severity medium
: rc
: ---
Assigned To: Virtualization Maintenance
Virtualization Bugs
:
Depends On:
Blocks: 580953
  Show dependency treegraph
 
Reported: 2010-05-12 04:04 EDT by Mike Cao
Modified: 2013-01-09 17:34 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-12 06:44:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
BSOD (16.82 KB, image/png)
2010-05-12 04:06 EDT, Mike Cao
no flags Details
MEMORY DUMP (4.70 KB, text/plain)
2010-05-12 05:03 EDT, Mike Cao
no flags Details
Minidump dump analyzed by Windbg (6.29 KB, text/plain)
2010-05-12 05:04 EDT, Mike Cao
no flags Details

  None (edit)
Description Mike Cao 2010-05-12 04:04:07 EDT
Description of problem:
 BSOD occurred after live migration without shared storage 

Version-Release number of selected component (if applicable):
Host:
# uname -r
2.6.32-23.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.48.el6.x86_64
Guest:
Windows 2008 r2

How reproducible:
test 2 times,100% reproduced.

Steps to Reproduce:
1.start a vm with in source host with:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -drive file=/home/win2k8_r2,if=virtio,format=raw,boot=on -net nic,macaddr=20:10:43:23:23:12,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -uuid `uuidgen` -vnc :7 -boot dc -cpu qemu64,+sse2 -smp 2 -balloon none -startdate now -monitor stdio
2.start another with in dest host with:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -drive file=/home/test2.raw,if=virtio,format=raw,boot=on -net nic,macaddr=20:10:43:23:23:12,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -uuid `uuidgen` -vnc :8 -boot dc -cpu qemu64,+sse2 -smp 2 -balloon none -startdate now -monitor stdio -incoming tcp:0:5888
Noticed that the image is not the same image in step1.
3.in the source host qemu monior type:(qemu) migrate -b tcp:<ip>:5888
  
Actual results:
after step 3 ,the guest is BOSD.

Expected results:
after migration ,the guest can be used normally.

Additional info:
When BOSD ,reboot it ,the guest can be used normally.
Comment 1 Mike Cao 2010-05-12 04:06:16 EDT
Created attachment 413344 [details]
BSOD
Comment 3 Mike Cao 2010-05-12 05:03:14 EDT
Created attachment 413365 [details]
MEMORY DUMP

in the attach is memory dump analyzed by Windbg.
Comment 4 Mike Cao 2010-05-12 05:04:51 EDT
Created attachment 413367 [details]
Minidump dump analyzed by Windbg
Comment 5 RHEL Product and Program Management 2010-05-12 05:32:49 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 6 Amit Shah 2010-05-12 06:06:19 EDT
It's expected for the migration to work for the storage images be the same. Can't really say this is a bug.

Note You need to log in before you can comment on or make changes to this bug.