Description of problem: Version-Release number of selected component (if applicable): host rhel5.6.z: # uname -r 2.6.18-238.14.1.el5 # rpm -q kvm kvm-83-224.el5_6.1 host rhel5.7: # uname -r 2.6.18-266.el5 # rpm -q kvm kvm-83-237.el5 How reproducible: always. Steps to Reproduce: 1.start guest with floppy on RHEL5.7.0 host eg:/usr/libexec/qemu-kvm -no-hpet -no-kvm-pit-reinjection -rtc-td-hack -startdate now -usbdevice tablet -k en-us -smp 2,cores=1 -cpu qemu64,+sse2 -m 4G -balloon none -boot dc -net nic,vlan=1,macaddr=00:1a:4a:42:49:00,model=virtio -net tap,vlan=1,script=/etc/qemu-ifup,downscript=no -drive file=/opt/rhel5.6.0/rhel6u1_5.6.0,if=virtio,format=raw,werror=stop,cache=none,boot=on -vnc :1 -M rhel5.6.0 -monitor stdio -drive file=/opt/virtio-drivers.vfd,if=floppy,format=raw 2.in the guest #modprobe floppy 3.start listenning port on RHEL5.6.z host 4.do live migration. Actual results: (qemu) Unknown savevm section or instance 'fdc/media_changed' 0 load of migration failed Expected results: migration should be successful. Additional info: Tried on kvm-83-236.el5 ,does not hit this issue.
Hi,Dor it's seems that kvm-floppy-save-and-restore-DIR-register.patch applied in kvm-83-237.el5 result in this regression,if developer need to fix this in rhel5.6.z,please raise rhel‑5.6.z falg
do migrate for windows7 guest from rhel5.7 host to rhel5.6.z host, guest will crash. steps to reproduce: 1. src (rhel5.6.z) /usr/libexec/qemu-kvm -M rhel5.6.0 -rtc-td-hack -startdate now -name win7 -smp 4 -m 4G -uuid `uuidgen` -boot c -drive file=/dev/vg0/data4,media=disk,if=ide,cache=none,boot=on,format=qcow2,werror=stop -net nic,vlan=1,macaddr=52:87:78:D4:b3:9f,model=rtl8139 -net tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio -spice disable-ticketing,port=5911 -qxl 1 2.des (rhel5.7) /usr/libexec/qemu-kvm -M rhel5.6.0 -rtc-td-hack -startdate now -name win7 -smp 4 -m 4G -uuid `uuidgen` -boot c -drive file=/dev/vg0/data4,media=disk,if=ide,cache=none,boot=on,format=qcow2,werror=stop -net nic,vlan=1,macaddr=52:87:78:D4:b3:9f,model=rtl8139 -net tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio -spice disable-ticketing,port=5911 -qxl 1 -incoming tcp:0:5555 3. do migrate from src to des 4. do migrate from des to src monitor will show below fail message Unknown savevm section or instance 'fdc/media_changed' 0 load of migration failed 5. check guest
We probably need to add a -M rhel5.7 for the fix.
(In reply to comment #2) > do migrate for windows7 guest from rhel5.7 host to rhel5.6.z host, guest will > crash. ^^^^^ [snip] > 4. do migrate from des to src > monitor will show below fail message > Unknown savevm section or instance 'fdc/media_changed' 0 > load of migration failed > > 5. check guest Did the guest actually crash or did the migration fail and the guest continued running on "des"?
sorry, my description is not accurate, guest is not crash, it will be in a stopped state.
Patch(es) included on kvm-83-238.el5
Reproduced this issue on kvm-83-237.el5 Verified it on kvm-83-238.el5 with the steps of comment #0. Actual Results: migration could finish successfully.After migration complete, guest could be used on dst host. Based on above ,this issue has been fixed ald. Move status to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When a host with a floppy drive attached and Red Hat Enterprise Linux 5.7 installed was being migrated to another host with kernel version 2.6.18-238.14.1 installed, the migration process failed and the host was left in a stopped state. A patch has been provided to address this issue and the migration now finishes successfully in the described scenario.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1068.html