Created attachment 480173 [details] screen shot Description of problem: when migrating a VM with windoes based OS while the VM is in powering on state, we are getting guest file system corruption (OS will start normally after guest reboot). tested in XP and Win2008. the error for XP is "windows could not start because the following file is missing or corrupt: system32:\DRIVERS\pci.sys Windows2008: Windows failed to start. a recent hardware or software change might be the cause Version-Release number of selected component (if applicable): ic92 rhevm build Source host: 5.6 [root@blond-vdsf ~]# uname -r 2.6.18-238.1.1.el5 [root@blond-vdsf ~]# rpm -qa |grep vds vdsm22-4.5-63.19.el5_6 vdsm22-faqemu-4.5-63.19.el5_6 vdsm22-reg-4.5-63.19.el5_6 vdsm22-cli-4.5-63.19.el5_6 vdsm22-debuginfo-4.5-63.19.el5_6 [root@blond-vdsf ~]# rpm -qa |grep qemu vdsm22-faqemu-4.5-63.19.el5_6 kvm-qemu-img-83-224.el5 destination host: rhevh5 [root@blond-vdsg ~]# uname -r 2.6.18-238.el5 [root@blond-vdsg ~]# rpm -qa |grep vdsm vdsm22-4.5-63.9.el5 vdsm22-cli-4.5-63.9.el5 vdsm22-reg-4.5-63.9.el5 [root@blond-vdsg ~]# rpm -qa |grep qemu kvm-qemu-img-83-224.el5 gpxe-roms-qemu-0.9.7-8.el5 both hosts are AMD How reproducible: 100% Steps to Reproduce: On a two hosts cluster: 1. create a VM with windows OS 2. start the VM 3. Migrate when the VM is in "powering up" state Actual results: the VM will migrate and you will get corruption in the VM's OS Expected results: the VM's OS should not be affected by the migration. Additional info: screen shot attached.
Created attachment 480376 [details] cpuinfo adding information on the hosts: source: [root@blond-vdsf ~]# rpm -qa |grep kvm kvm-83-224.el5 kvm-debuginfo-83-224.el5 kvm-qemu-img-83-224.el5 kvm-tools-83-224.el5 etherboot-zroms-kvm-5.4.4-13.el5 kmod-kvm-83-224.el5 destination: [root@blond-vdsg ~]# rpm -qa |grep kvm etherboot-zroms-kvm-5.4.4-13.el5 kmod-kvm-83-224.el5 kvm-tools-83-224.el5 kvm-qemu-img-83-224.el5 kvm-debuginfo-83-224.el5 kvm-83-224.el5 attached is the cpu info on both hosts.
Hi, Dafna Ron Does it still exists ? FYI ,I think this bug is dup of https://bugzilla.redhat.com/show_bug.cgi?id=693894
*** This bug has been marked as a duplicate of bug 666225 ***