* map all the bios at the top of memory */ RHEL-7 maps the BIOS in PCI address space just below 4GB (pc.bios): RHEL-6 maps the BIOS in PCI address space directly at 896 KB (pc.bios). In both RHEL-6 and RHEL-7 qemu, the PAM registers start out as "pam-pci" I think I have an extremely convoluted theory about what happens. The alias doesn't show the contents of the aliased memory range. For some reason it doesn't have the desired effect in case (2) When a guest is booted on the RHEL-7 host fresh, pc.bios ends up at 4095.875 However its guest-physical mapping changes, from 896 KB to 4095.875 MB. ![]() The migration from the RHEL-6 host to the RHEL-7 host does transfer theĬontents of the "pc.bios" RAMBlock (connected by the "pc.bios" ID string), # /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu Westmere -enable-kvm -m 2048 -realtime mlock=off -smp 4,sockets=2,cores=2,threads=1,maxcpus=160 -drive file=/mnt/win8-64-ide.qcow2,if=none,media=disk,id=drive-ide1-1-0,format=qcow2,werror=stop,rerror=stop,cache=none,boot=on -device ide-drive,drive=drive-ide1-1-0,id=ide-disk0 -vnc :10 -monitor stdio -nodefconfig -net none -incoming tcp:0:5800 # /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu Westmere -enable-kvm -m 2048 -realtime mlock=off -smp 4,sockets=2,cores=2,threads=1,maxcpus=160 -drive file=/mnt/win8-64-ide.qcowne,media=disk,id=drive-ide1-1-0,format=qcow2,werror=stop,rerror=stop,cache=none,boot=on -device ide-drive,drive=drive-ide1-1-0,id=ide-disk0 -vnc :10 -monitor stdio -nodefconfig -net none Version-Release number of selected component (if applicable): I migrate win8-64 guest from RHEL6.5 host to RHEL7.0 host, after migriation, do reboot inside the guest, reboot is failed and the screenshot is as the attachment file. ![]() Please stand by while rebooting the system. and this is the last part of guest console output # /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu Opteron_G2 -enable-kvm -m 2G -smp 4 -name rhel6.5 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=/mnt/2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -net none -vnc :1 -monitor stdio -serial unix:/tmp/monitor2,server,nowait -incoming tcp:0:5555 # /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu Opteron_G2 -enable-kvm -m 2G -smp 4 -name rhel6.5 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=/mnt/2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -net none -vnc :1 -monitor stdio -serial unix:/tmp/monitor2,server,nowaitģ.Boot rhel6.5 guest with listening on rhel7 host Re-tested this issue with nfs, still can reproduce this issue. Important: qemu-kvm security, bug fix, and enhancement update ![]() Proposed patch for the *separate* USB problem (downstream only) Qemu-kvm command line, please search usb device in cliĤ patches for approach #1 (illustration only), mbox formatĬall trace log after migration and system_reset Proposed patch (downstream only), v2 approach #2 Info mtree diff between migrated-from-rhel6 and cold-booted-on-rhel7ĭump ramblocks in stage 1 of the RHEL-6 outgoing migration (debug patch) Proof of concept patch for the analysis in comment 16 The screenshot of shutdown/system_powerdown failed
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |