[Qemu-devel] [Bug 1213797] [NEW] Guest hang after live migration
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d qemu-kvm uq/master Commit:ca916d3729564d0eb3c2374a96903f7e8aced8a7 Host Kernel Version:3.11.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- after guest live migration, the guest will hang, and ping IP fail note: 1. after guest save/restore, the guest will hang, and ping IP fail 2. This should be a qemu-kvm bug. kvm + qemu-kvm = result 205befd9 + ca916d37 = bad 205befd9 + f03d07d4 = good Reproduce steps: 1.Start a TCP daemon for migration qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow -incoming tcp:localhost: 2. create guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow 3. migrate tcp:localhost: Current result: guest hang Expected result: after live/migration or save/restore, the guest works fine ** Affects: qemu Importance: Undecided Status: New ** Attachment added: "guest serial log" https://bugs.launchpad.net/bugs/1213797/+attachment/3777611/+files/guest_serial.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1213797 Title: Guest hang after live migration Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d qemu-kvm uq/master Commit:ca916d3729564d0eb3c2374a96903f7e8aced8a7 Host Kernel Version:3.11.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- after guest live migration, the guest will hang, and ping IP fail note: 1. after guest save/restore, the guest will hang, and ping IP fail 2. This should be a qemu-kvm bug. kvm + qemu-kvm = result 205befd9 + ca916d37 = bad 205befd9 + f03d07d4 = good Reproduce steps: 1.Start a TCP daemon for migration qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow -incoming tcp:localhost: 2. create guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow 3. migrate tcp:localhost: Current result: guest hang Expected result: after live/migration or save/restore, the guest works fine To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1213797/+subscriptions
[Qemu-devel] [Bug 1213797] Re: Guest hang after live migration
Jinsong Liu (@Intel) 's patch "qemu-kvm bugfix for IA32_FEATURE_CONTROL" will fix this bug. That patch will also fix the following bug. 10. 64bit RHEL6.4 guest crashes and reboots continuously https://bugs.launchpad.net/qemu-kvm/+bug/1207623 So you suggent we should use qemu instead of qemu-kvm, right? Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1213797 Title: Guest hang after live migration Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d qemu-kvm uq/master Commit:ca916d3729564d0eb3c2374a96903f7e8aced8a7 Host Kernel Version:3.11.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- after guest live migration, the guest will hang, and ping IP fail note: 1. after guest save/restore, the guest will hang, and ping IP fail 2. This should be a qemu-kvm bug. kvm + qemu-kvm = result 205befd9 + ca916d37 = bad 205befd9 + f03d07d4 = good Reproduce steps: 1.Start a TCP daemon for migration qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow -incoming tcp:localhost: 2. create guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow 3. migrate tcp:localhost: Current result: guest hang Expected result: after live/migration or save/restore, the guest works fine To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1213797/+subscriptions
[Qemu-devel] [Bug 1213797] Re: Guest hang after live migration
OK. Thanks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1213797 Title: Guest hang after live migration Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d qemu-kvm uq/master Commit:ca916d3729564d0eb3c2374a96903f7e8aced8a7 Host Kernel Version:3.11.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- after guest live migration, the guest will hang, and ping IP fail note: 1. after guest save/restore, the guest will hang, and ping IP fail 2. This should be a qemu-kvm bug. kvm + qemu-kvm = result 205befd9 + ca916d37 = bad 205befd9 + f03d07d4 = good Reproduce steps: 1.Start a TCP daemon for migration qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow -incoming tcp:localhost: 2. create guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow 3. migrate tcp:localhost: Current result: guest hang Expected result: after live/migration or save/restore, the guest works fine To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1213797/+subscriptions
[Qemu-devel] [Bug 1213797] Re: Guest hang after live migration
The bug has been fixed by the following commit: commit df67696e97d3edd0cb1683bf2eb3b3236bd9a5ed Author: Liu Jinsong Date: Mon Aug 19 09:33:30 2013 +0800 kvm: x86: fix setting IA32_FEATURE_CONTROL with nested VMX disabled This patch is to fix the bug https://bugs.launchpad.net/qemu- kvm/+bug/120762 IA32_FEATURE_CONTROL is pointless if not expose VMX or SMX bits to cpuid.1.ecx of vcpu. Current qemu-kvm will error return when kvm_put_msrs or kvm_get_msrs. Signed-off-by: Liu Jinsong Signed-off-by: Paolo Bonzini -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1213797 Title: Guest hang after live migration Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d qemu-kvm uq/master Commit:ca916d3729564d0eb3c2374a96903f7e8aced8a7 Host Kernel Version:3.11.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- after guest live migration, the guest will hang, and ping IP fail note: 1. after guest save/restore, the guest will hang, and ping IP fail 2. This should be a qemu-kvm bug. kvm + qemu-kvm = result 205befd9 + ca916d37 = bad 205befd9 + f03d07d4 = good Reproduce steps: 1.Start a TCP daemon for migration qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow -incoming tcp:localhost: 2. create guest qemu-system-x86_64 -enable-kvm -m 2G -smp 2 -net nic,macaddr=00:12:34:56:13:45 -net tap,script=/etc/kvm/qemu-ifup rhel6u2.qcow 3. migrate tcp:localhost: Current result: guest hang Expected result: after live/migration or save/restore, the guest works fine To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1213797/+subscriptions
[Qemu-devel] [Bug 1354279] Re: The guest will be destroyed after hot remove the VF from the guest.
test on Ivytown_EP kvm.git + qemu.git: c77dcacb_0e4a7737 kernel version: 3.16.0 after hot remove the VF from the guest, the guest works fine. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1354279 Title: The guest will be destroyed after hot remove the VF from the guest. Status in QEMU: Fix Committed Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23 qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a Host Kernel Version:3.16.0-rc1 Hardware:Romley_EP, Ivytown_EP,Haswell_EP Bug detailed description: -- hot add the VF to the guest, then hot remove the VF from the guest, the guest will be destroyed. note: 1. when hot add the VF with vfio, the hot remove the VF from the guest, the guest works fine. 2. this shoule be a qemu bug: kvm + qemu= result 9f6226a7 + 5a734804 = bad 9f6226a7 + 9f862687 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -net none rhel6u5.qcow -monitor pty 2. hot add the vf to guest echo "device_add pci-assign,host=05:10.0,id=nic" >/dev/pts/x cat /dev/pts/x 3. hot remove the VF froem guest echo "device_del nic" >/dev/pts/x Current result: the guest willl be destroyed after hot remove the VF from the guest Expected result: the guest works fine after hot remove the VF from the guest Basic root-causing log: -- [root@vt-snb9 qemu.git]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none rhel6u5.qcow -monitor pty VNC server running on `::1:5900' ** ERROR:qom/object.c:725:object_unref: assertion failed: (obj->ref > 0) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1354279/+subscriptions
[Qemu-devel] [Bug 1364249] Re: guest can't get ip when create guest with bridge using virtio driver.
kvm.git + qemu.git:da01e614_b6011bd8 test on Ivytown_EP kernel version: 3.17.0 when create guest with bridge, and the bridge network driver is virtio, the guest can get ip. the bug cannot reproduce. ** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1364249 Title: guest can't get ip when create guest with bridge using virtio driver. Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:c77dcacb397519b6ade8f08201a4a90a7f4f751e qemu.git Commit:f2c85a2f36f57f155cda7bc9f7c42b44f1a2439e Host Kernel Version:3.16.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, and the bridge network driver is virtio, the guest can not get ip. note: 1. this is a qemu bug: kvm + qemu-kvm = result c77dcacb + f2c85a2f= bad c77dcacb + 2d591ce2 = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=00:12:41:34:51:14 -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get ip with bridge using virtio driver. Expected result: guest get ip with bridge using virtio driver. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1364249/+subscriptions
[Qemu-devel] [Bug 1364249] [NEW] guest can't get ip when create guest with bridge using virtio driver.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:c77dcacb397519b6ade8f08201a4a90a7f4f751e qemu.git Commit:f2c85a2f36f57f155cda7bc9f7c42b44f1a2439e Host Kernel Version:3.16.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, and the bridge network driver is virtio, the guest can not get ip. note: 1. this is a qemu bug: kvm + qemu-kvm = result c77dcacb + f2c85a2f= bad c77dcacb + 2d591ce2 = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=00:12:41:34:51:14 -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get ip with bridge using virtio driver. Expected result: guest get ip with bridge using virtio driver. Basic root-causing log: -- ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1364249 Title: guest can't get ip when create guest with bridge using virtio driver. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:c77dcacb397519b6ade8f08201a4a90a7f4f751e qemu.git Commit:f2c85a2f36f57f155cda7bc9f7c42b44f1a2439e Host Kernel Version:3.16.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, and the bridge network driver is virtio, the guest can not get ip. note: 1. this is a qemu bug: kvm + qemu-kvm = result c77dcacb + f2c85a2f= bad c77dcacb + 2d591ce2 = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=00:12:41:34:51:14 -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get ip with bridge using virtio driver. Expected result: guest get ip with bridge using virtio driver. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1364249/+subscriptions
[Qemu-devel] [Bug 1364249] Re: guest can't get ip when create guest with bridge using virtio driver.
kvm.git+ qemu.git:fd275235_8b303011 kernel version:3.17.0_rc1 test on Ivytown_EP the bug can reproduce -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1364249 Title: guest can't get ip when create guest with bridge using virtio driver. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:c77dcacb397519b6ade8f08201a4a90a7f4f751e qemu.git Commit:f2c85a2f36f57f155cda7bc9f7c42b44f1a2439e Host Kernel Version:3.16.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, and the bridge network driver is virtio, the guest can not get ip. note: 1. this is a qemu bug: kvm + qemu-kvm = result c77dcacb + f2c85a2f= bad c77dcacb + 2d591ce2 = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=00:12:41:34:51:14 -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get ip with bridge using virtio driver. Expected result: guest get ip with bridge using virtio driver. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1364249/+subscriptions
[Qemu-devel] [Bug 1364249] Re: guest can't get ip when create guest with bridge using virtio driver.
the first bad commit is commit cc943c36faa192cd4b32af8fe5edb31894017d35 Author: Jan Kiszka Date: Sun Jul 27 09:08:29 2014 +0200 pci: Use bus master address space for delivering MSI/MSI-X messages The spec says (and real HW confirms this) that, if the bus master bit is 0, the device will not generate any PCI accesses. MSI and MSI-X messages fall among these, so we should use the corresponding address space to deliver them. This will prevent delivery if bus master support is disabled. Cc: qemu-sta...@nongnu.org Signed-off-by: Jan Kiszka Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1364249 Title: guest can't get ip when create guest with bridge using virtio driver. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:c77dcacb397519b6ade8f08201a4a90a7f4f751e qemu.git Commit:f2c85a2f36f57f155cda7bc9f7c42b44f1a2439e Host Kernel Version:3.16.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, and the bridge network driver is virtio, the guest can not get ip. note: 1. this is a qemu bug: kvm + qemu-kvm = result c77dcacb + f2c85a2f= bad c77dcacb + 2d591ce2 = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=00:12:41:34:51:14 -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get ip with bridge using virtio driver. Expected result: guest get ip with bridge using virtio driver. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1364249/+subscriptions
[Qemu-devel] [Bug 994378] Re: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line.
this patch fixed the bug: commit 338b522ca43cfd32d11a370f4203bcd089c6c877 Author: Kan Liang Date: Mon Jul 14 12:25:56 2014 -0700 perf/x86/intel: Protect LBR and extra_regs against KVM lying With -cpu host, KVM reports LBR and extra_regs support, if the host has support. When the guest perf driver tries to access LBR or extra_regs MSR, it #GPs all MSR accesses,since KVM doesn't handle LBR and extra_regs support. So check the related MSRs access right once at initialization time to avoid the error access at runtime. For reproducing the issue, please build the kernel with CONFIG_KVM_INTEL = y (for host kernel). And CONFIG_PARAVIRT = n and CONFIG_KVM_GUEST = n (for guest kernel). Start the guest with -cpu host. Run perf record with --branch-any or --branch-filter in guest to trigger LBR Run perf stat offcore events (E.g. LLC-loads/LLC-load-misses ...) in guest to trigger offcore_rsp #GP Signed-off-by: Kan Liang Signed-off-by: Peter Zijlstra Cc: Andi Kleen Cc: Arnaldo Carvalho de Melo Cc: Linus Torvalds Cc: Maria Dimakopoulou Cc: Mark Davies Cc: Paul Mackerras Cc: Stephane Eranian Cc: Yan, Zheng Link: http://lkml.kernel.org/r/1405365957-20202-1-git-send-email-kan.li...@intel.com Signed-off-by: Ingo Molnar -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/994378 Title: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/994378/+subscriptions
[Qemu-devel] [Bug 994378] Re: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line.
when L1 guest kernel: 3.16.0(kvm.git+ qemu.git: c77dcacb..-69f87f71) create L1 guest: qemu-system-x86_64 -enable-kvm -m 6G -smp 4 -net nic,macaddr=00:12:31:45:56:13 -net tap,script=/etc/kvm/qemu-ifup ia32e_nested-kvm.img -cpu host the L1 guest boot up fine -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/994378 Title: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/994378/+subscriptions
[Qemu-devel] [Bug 994378] Re: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line.
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/994378 Title: Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in qemu command line. Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9 qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231 Host Kernel Version:3.4.0-rc3 Hardware:WSM-EP, Romley-EP Bug detailed description: -- (KVM on KVM) L1 guest panic when starting the L1 guest with “-cpu host” parameter in qemu command line. Note: 1. when creating guest with “-cpu qemu64,+vmx”, L1 guest and L2 guest can boot up. 2. This should be a qemu-kvm bug. using '-cpu host' parameter, the following is the result. Kvm+ qemu-kvm =result 19853301 + 69abebf2 = bad 19853301 + 44755ea3 = good 3. when booting up the guest with the good commit of 19853301 + 44755ea3, you can see some error info, but nested virt works fine. (L1 and L2 guest can boot up.) “error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall]” some logs [root@vt-snb9 x86_64-softmmu]# ./qemu-system-x86_64 -m 2048 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /root/nested-kvm.qcow -cpu host error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 xd syscall] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] error: feature "i64" not available in set error: bad option value [extfeature_edx = i64 syscall xd] VNC server running on `::1:5900' Reproduce steps: 1.start up a host with kvm (commit: 19853301) 2.rmmod kvm_intel 3.modprobe kvm_intel nested=1 4.qemu-system-x86_64 -m 2048 -hda L1-kvm.img -cpu host Current result: L1 guest panic. Expected result: L1 guest and L2 guest boot up correctly. Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/994378/+subscriptions
[Qemu-devel] [Bug 1354279] [NEW] The guest will be destroyed after hot remove the VF from the guest.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23 qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a Host Kernel Version:3.16.0-rc1 Hardware:Romley_EP, Ivytown_EP,Haswell_EP Bug detailed description: -- hot add the VF to the guest, then hot remove the VF from the guest, the guest will be destroyed. note: 1. when hot add the VF with vfio, the hot remove the VF from the guest, the guest works fine. 2. this shoule be a qemu bug: kvm + qemu= result 9f6226a7 + 5a734804 = bad 9f6226a7 + 9f862687 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -net none rhel6u5.qcow -monitor pty 2. hot add the vf to guest echo "device_add pci-assign,host=05:10.0,id=nic" >/dev/pts/x cat /dev/pts/x 3. hot remove the VF froem guest echo "device_del nic" >/dev/pts/x Current result: the guest willl be destroyed after hot remove the VF from the guest Expected result: the guest works fine after hot remove the VF from the guest Basic root-causing log: -- [root@vt-snb9 qemu.git]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none rhel6u5.qcow -monitor pty VNC server running on `::1:5900' ** ERROR:qom/object.c:725:object_unref: assertion failed: (obj->ref > 0) Aborted (core dumped) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1354279 Title: The guest will be destroyed after hot remove the VF from the guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23 qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a Host Kernel Version:3.16.0-rc1 Hardware:Romley_EP, Ivytown_EP,Haswell_EP Bug detailed description: -- hot add the VF to the guest, then hot remove the VF from the guest, the guest will be destroyed. note: 1. when hot add the VF with vfio, the hot remove the VF from the guest, the guest works fine. 2. this shoule be a qemu bug: kvm + qemu= result 9f6226a7 + 5a734804 = bad 9f6226a7 + 9f862687 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -net none rhel6u5.qcow -monitor pty 2. hot add the vf to guest echo "device_add pci-assign,host=05:10.0,id=nic" >/dev/pts/x cat /dev/pts/x 3. hot remove the VF froem guest echo "device_del nic" >/dev/pts/x Current result: the guest willl be destroyed after hot remove the VF from the guest Expected result: the guest works fine after hot remove the VF from the guest Basic root-causing log: -- [root@vt-snb9 qemu.git]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none rhel6u5.qcow -monitor pty VNC server running on `::1:5900' ** ERROR:qom/object.c:725:object_unref: assertion failed: (obj->ref > 0) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1354279/+subscriptions
[Qemu-devel] [Bug 1354279] Re: The guest will be destroyed after hot remove the VF from the guest.
the first bad commit is: commit 22a893e4f55344f96e1aafc66f5fedc491a5ca97 Author: Paolo Bonzini Date: Wed Jun 11 10:58:06 2014 +0200 memory: MemoryRegion: replace owner field with QOM parent The two are now the same. Reviewed-by: Peter Crosthwaite Signed-off-by: Paolo Bonzini -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1354279 Title: The guest will be destroyed after hot remove the VF from the guest. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23 qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a Host Kernel Version:3.16.0-rc1 Hardware:Romley_EP, Ivytown_EP,Haswell_EP Bug detailed description: -- hot add the VF to the guest, then hot remove the VF from the guest, the guest will be destroyed. note: 1. when hot add the VF with vfio, the hot remove the VF from the guest, the guest works fine. 2. this shoule be a qemu bug: kvm + qemu= result 9f6226a7 + 5a734804 = bad 9f6226a7 + 9f862687 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -net none rhel6u5.qcow -monitor pty 2. hot add the vf to guest echo "device_add pci-assign,host=05:10.0,id=nic" >/dev/pts/x cat /dev/pts/x 3. hot remove the VF froem guest echo "device_del nic" >/dev/pts/x Current result: the guest willl be destroyed after hot remove the VF from the guest Expected result: the guest works fine after hot remove the VF from the guest Basic root-causing log: -- [root@vt-snb9 qemu.git]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none rhel6u5.qcow -monitor pty VNC server running on `::1:5900' ** ERROR:qom/object.c:725:object_unref: assertion failed: (obj->ref > 0) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1354279/+subscriptions
[Qemu-devel] [Bug 979714] Re: Guest timer interrupt isn't switched off when local timer is enabled
** Attachment added: "dmesg in guest" https://bugs.launchpad.net/bugs/979714/+attachment/3051557/+files/timerdmesg.log -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/979714 Title: Guest timer interrupt isn't switched off when local timer is enabled Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:4f324a1b qemu-kvm Commit: b5ed4b6f Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Start a guest and check into /proc/interrupts, the timer interrupt will constantly increase while local timer interrups are already increasing. qemu-kvm commit: 9d636ae7 doesn't have this issue. The dmesg of the guest shows: APIC calibration not consistent with PM-Timer: 191ms instead of 100ms This should be a qemu-kvm bug. kvm + qemu-kvm = result 4f324a1b + b5ed4b6f = bad 4f324a1b + 9d636ae7 = good Reproduce steps: 1. start up a host with kvm kernel 2. qemu-system-x86_64 –m 1024 –smp 2 –net none –hda /root/rhel6u1.img 3. cat /proc/interrupts Current result: interrupt 0 keeps increasing Expected result: interrupt 0 stops at some value and doesn't increase To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/979714/+subscriptions
[Qemu-devel] [Bug 979714] [NEW] Guest timer interrupt isn't switched off when local timer is enabled
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:4f324a1b qemu-kvm Commit: b5ed4b6f Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Start a guest and check into /proc/interrupts, the timer interrupt will constantly increase while local timer interrups are already increasing. qemu-kvm commit: 9d636ae7 doesn't have this issue. The dmesg of the guest shows: APIC calibration not consistent with PM-Timer: 191ms instead of 100ms This should be a qemu-kvm bug. kvm + qemu-kvm = result 4f324a1b + b5ed4b6f = bad 4f324a1b + 9d636ae7 = good Reproduce steps: 1. start up a host with kvm kernel 2. qemu-system-x86_64 –m 1024 –smp 2 –net none –hda /root/rhel6u1.img 3. cat /proc/interrupts Current result: interrupt 0 keeps increasing Expected result: interrupt 0 stops at some value and doesn't increase ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/979714 Title: Guest timer interrupt isn't switched off when local timer is enabled Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:4f324a1b qemu-kvm Commit: b5ed4b6f Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Start a guest and check into /proc/interrupts, the timer interrupt will constantly increase while local timer interrups are already increasing. qemu-kvm commit: 9d636ae7 doesn't have this issue. The dmesg of the guest shows: APIC calibration not consistent with PM-Timer: 191ms instead of 100ms This should be a qemu-kvm bug. kvm + qemu-kvm = result 4f324a1b + b5ed4b6f = bad 4f324a1b + 9d636ae7 = good Reproduce steps: 1. start up a host with kvm kernel 2. qemu-system-x86_64 –m 1024 –smp 2 –net none –hda /root/rhel6u1.img 3. cat /proc/interrupts Current result: interrupt 0 keeps increasing Expected result: interrupt 0 stops at some value and doesn't increase To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/979714/+subscriptions
[Qemu-devel] [Bug 979714] Re: The pit interrupt still exists even with tickless guest
** Summary changed: - Guest timer interrupt isn't switched off when local timer is enabled + The pit interrupt still exists even with tickless guest -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/979714 Title: The pit interrupt still exists even with tickless guest Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows): Linux(RHEL6u1) kvm.git Commit:4f324a1b qemu-kvm Commit: b5ed4b6f Host Kernel Version:3.3.0-rc5 Hardware: Romley-EP, WSM-EP Bug detailed description: -- Start a guest and check into /proc/interrupts, the timer interrupt will constantly increase while local timer interrups are already increasing. qemu-kvm commit: 9d636ae7 doesn't have this issue. The dmesg of the guest shows: APIC calibration not consistent with PM-Timer: 191ms instead of 100ms This should be a qemu-kvm bug. kvm + qemu-kvm = result 4f324a1b + b5ed4b6f = bad 4f324a1b + 9d636ae7 = good Reproduce steps: 1. start up a host with kvm kernel 2. qemu-system-x86_64 –m 1024 –smp 2 –net none –hda /root/rhel6u1.img 3. cat /proc/interrupts Current result: interrupt 0 keeps increasing Expected result: interrupt 0 stops at some value and doesn't increase To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/979714/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
kvm.git + qemu.git:7cbb39d4_5913815a after use "stop" , then migrate "exec:dd of=test.img", the test.img is about 250M, running time of save guest is less than 450s. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: Invalid Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261265] Re: win7 guest boot up fail.
the first bad commit is: commit 6eefccc0bb9c34051b1e21880fc3a1c1c8686edd Author: Gerd Hoffmann Date: Mon Dec 2 13:01:20 2013 +0100 roms: update vgabios binaries This also switches from lgplvgabios to seavgabios. Signed-off-by: Gerd Hoffmann -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261265 Title: win7 guest boot up fail. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:a1d22a367d5780c9553b2cd5a24f665534ce6ed6 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when create a win7 guest, the guest boot up fail. note: 1. when create win2k3, win2k8 guest, the guest boot up fail. 2. when create win8, win2012 guest, the guest boot up fine. 3. this should be a qemu bug kvm + qemu = result d6d63b51 + a1d22a36 = bad d6d63b51 + 7dc65c02 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/win7.img Current result: win7 guest boot up fail Expected result: win7 guest boot up fine Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261265/+subscriptions
[Qemu-devel] [Bug 1261265] [NEW] win7 guest boot up fail.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:a1d22a367d5780c9553b2cd5a24f665534ce6ed6 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when create a win7 guest, the guest boot up fail. note: 1. when create win2k3, win2k8 guest, the guest boot up fail. 2. when create win8, win2012 guest, the guest boot up fine. 3. this should be a qemu bug kvm + qemu = result d6d63b51 + a1d22a36 = bad d6d63b51 + 7dc65c02 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/win7.img Current result: win7 guest boot up fail Expected result: win7 guest boot up fine Basic root-causing log: -- ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261265 Title: win7 guest boot up fail. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:a1d22a367d5780c9553b2cd5a24f665534ce6ed6 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when create a win7 guest, the guest boot up fail. note: 1. when create win2k3, win2k8 guest, the guest boot up fail. 2. when create win8, win2012 guest, the guest boot up fine. 3. this should be a qemu bug kvm + qemu = result d6d63b51 + a1d22a36 = bad d6d63b51 + 7dc65c02 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/win7.img Current result: win7 guest boot up fail Expected result: win7 guest boot up fine Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261265/+subscriptions
[Qemu-devel] [Bug 1261268] [NEW] save guest running time is more than 450s with AVX running.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
the first bad commit is: commit 6887581728c9eddf858e7458b6eacbfe3ac68302 Author: Gerd Hoffmann Date: Fri Sep 20 15:34:27 2013 +0200 roms: add 'make clean' Signed-off-by: Gerd Hoffmann -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
after re-check , the first bad commit is: commit 3e469dbfe413c25d48321c3a19ddfae0727dc6e5 Author: Andrea Arcangeli Date: Thu Jul 25 12:11:15 2013 +0200 exec: always use MADV_DONTFORK MADV_DONTFORK prevents fork to fail with -ENOMEM if the default overcommit heuristics decides there's too much anonymous virtual memory allocated. If the KVM secondary MMU is synchronized with MMU notifiers or not, doesn't make a difference in that regard. Secondly it's always more efficient to avoid copying the guest physical address space in the fork child (so we avoid to mark all the guest memory readonly in the parent and so we skip the establishment and teardown of lots of pagetables in the child). In the common case we can ignore the error if MADV_DONTFORK is not available. Leave a second invocation that errors out in the KVM path if MMU notifiers are missing and KVM is enabled, to abort in such case. Signed-off-by: Andrea Arcangeli Tested-By: Benoit Canet Acked-by: Paolo Bonzini Signed-off-by: Gleb Natapov -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
after re-check , the first bad commit is: commit 3e469dbfe413c25d48321c3a19ddfae0727dc6e5 Author: Andrea Arcangeli Date: Thu Jul 25 12:11:15 2013 +0200 exec: always use MADV_DONTFORK MADV_DONTFORK prevents fork to fail with -ENOMEM if the default overcommit heuristics decides there's too much anonymous virtual memory allocated. If the KVM secondary MMU is synchronized with MMU notifiers or not, doesn't make a difference in that regard. Secondly it's always more efficient to avoid copying the guest physical address space in the fork child (so we avoid to mark all the guest memory readonly in the parent and so we skip the establishment and teardown of lots of pagetables in the child). In the common case we can ignore the error if MADV_DONTFORK is not available. Leave a second invocation that errors out in the KVM path if MMU notifiers are missing and KVM is enabled, to abort in such case. Signed-off-by: Andrea Arcangeli Tested-By: Benoit Canet Acked-by: Paolo Bonzini Signed-off-by: Gleb Natapov -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
after re-check , the first bad commit is: commit 3e469dbfe413c25d48321c3a19ddfae0727dc6e5 Author: Andrea Arcangeli Date: Thu Jul 25 12:11:15 2013 +0200 exec: always use MADV_DONTFORK MADV_DONTFORK prevents fork to fail with -ENOMEM if the default overcommit heuristics decides there's too much anonymous virtual memory allocated. If the KVM secondary MMU is synchronized with MMU notifiers or not, doesn't make a difference in that regard. Secondly it's always more efficient to avoid copying the guest physical address space in the fork child (so we avoid to mark all the guest memory readonly in the parent and so we skip the establishment and teardown of lots of pagetables in the child). In the common case we can ignore the error if MADV_DONTFORK is not available. Leave a second invocation that errors out in the KVM path if MMU notifiers are missing and KVM is enabled, to abort in such case. Signed-off-by: Andrea Arcangeli Tested-By: Benoit Canet Acked-by: Paolo Bonzini Signed-off-by: Gleb Natapov -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
after re-check , the first bad commit is: commit 3e469dbfe413c25d48321c3a19ddfae0727dc6e5 Author: Andrea Arcangeli Date: Thu Jul 25 12:11:15 2013 +0200 exec: always use MADV_DONTFORK MADV_DONTFORK prevents fork to fail with -ENOMEM if the default overcommit heuristics decides there's too much anonymous virtual memory allocated. If the KVM secondary MMU is synchronized with MMU notifiers or not, doesn't make a difference in that regard. Secondly it's always more efficient to avoid copying the guest physical address space in the fork child (so we avoid to mark all the guest memory readonly in the parent and so we skip the establishment and teardown of lots of pagetables in the child). In the common case we can ignore the error if MADV_DONTFORK is not available. Leave a second invocation that errors out in the KVM path if MMU notifiers are missing and KVM is enabled, to abort in such case. Signed-off-by: Andrea Arcangeli Tested-By: Benoit Canet Acked-by: Paolo Bonzini Signed-off-by: Gleb Natapov -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1261268] Re: save guest running time is more than 450s with AVX running.
after re-check , the first bad commit is: commit 3e469dbfe413c25d48321c3a19ddfae0727dc6e5 Author: Andrea Arcangeli Date: Thu Jul 25 12:11:15 2013 +0200 exec: always use MADV_DONTFORK MADV_DONTFORK prevents fork to fail with -ENOMEM if the default overcommit heuristics decides there's too much anonymous virtual memory allocated. If the KVM secondary MMU is synchronized with MMU notifiers or not, doesn't make a difference in that regard. Secondly it's always more efficient to avoid copying the guest physical address space in the fork child (so we avoid to mark all the guest memory readonly in the parent and so we skip the establishment and teardown of lots of pagetables in the child). In the common case we can ignore the error if MADV_DONTFORK is not available. Leave a second invocation that errors out in the KVM path if MMU notifiers are missing and KVM is enabled, to abort in such case. Signed-off-by: Andrea Arcangeli Tested-By: Benoit Canet Acked-by: Paolo Bonzini Signed-off-by: Gleb Natapov -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261268 Title: save guest running time is more than 450s with AVX running. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:8f84271da83c0e9f92aa7c1c2d0d3875bf0a5cb8 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when guest running avx , then do save /restore, save guest running time is too lomg Note: 1.when save guest (migrate "exec:dd of=test.img")sometimes , the file of test.img is 29G, running time of save guest is about 900s 2. this should be a qemu bug: kvm + qemu = result d6d63b51 + 8f84271d = bad d6d63b51 + b5d54bd4 = good Reproduce steps: 1.qemu-system-x86_64 -enable-kvm -m 1024 -smp 6 -net nic,macaddr=00:12:34:43:14:78 -net tap,script=/etc/kvm/qemu-ifup rhel6u4.qcow 2. scp /usr/tet/XVS/tsets/control_panel/tools/bin/avx.tar.gz $guest_IP:/root 3. tar -zxf avx.tar.gz 4. cd /avx 5. sh chk_avx.sh &>/dev/null & 6. ctrl-alt-2 7. migrate "exec:dd of=test.img" Current result: running time of save guest is more than 450s Expected result: running time of save guest is less than 450s Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261268/+subscriptions
[Qemu-devel] [Bug 1248854] [NEW] The guest cannot boot up with parameter "-no-acpi"
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 qemu.git Commit:a126050a103c924b03388a9a64ce9af8c96b0969 Host Kernel Version:3.12.0-rc5 Hardware:Romley_EP ,Ivytowm_EP Bug detailed description: -- when create guest with parameter "-no-acpi", the guest cannot boot up. note: this should be a qemu bug kvm + qemu = result 81e87e26 + a126050a = bad 81e87e26 + b8616055 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none -no-acpi rhel6u4.qcow Current result: guest cannot boot up Expected result: guest boot up fine. Basic root-causing log: -- [root@vt-snb9 qemu]#qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow -no-acpi VNC server running on `::1:5900' qemu-system-x86_64: /root/qemu/hw/i386/acpi-build.c:135: acpi_get_pm_info: Assertion `obj' failed. Aborted (core dumped) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1248854 Title: The guest cannot boot up with parameter "-no-acpi" Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 qemu.git Commit:a126050a103c924b03388a9a64ce9af8c96b0969 Host Kernel Version:3.12.0-rc5 Hardware:Romley_EP ,Ivytowm_EP Bug detailed description: -- when create guest with parameter "-no-acpi", the guest cannot boot up. note: this should be a qemu bug kvm + qemu = result 81e87e26 + a126050a = bad 81e87e26 + b8616055 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none -no-acpi rhel6u4.qcow Current result: guest cannot boot up Expected result: guest boot up fine. Basic root-causing log: -- [root@vt-snb9 qemu]#qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow -no-acpi VNC server running on `::1:5900' qemu-system-x86_64: /root/qemu/hw/i386/acpi-build.c:135: acpi_get_pm_info: Assertion `obj' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1248854/+subscriptions
[Qemu-devel] [Bug 1248854] Re: The guest cannot boot up with parameter "-no-acpi"
the first bad commit is: commit 72c194f7e75cb64b2558111cb111adb49fbf4097 Author: Michael S. Tsirkin Date: Wed Jul 24 18:56:14 2013 +0300 i386: ACPI table generation code from seabios This adds C code for generating ACPI tables at runtime, imported from seabios git tree commit 51684b7ced75fb76776e8ee84833fcfb6ecf12dd Although ACPI tables come from a system BIOS on real hw, it makes sense that the ACPI tables are coupled with the virtual machine, since they have to abstract the x86 machine to the OS's. This is widely desired as a way to avoid the churn and proliferation of QEMU-specific interfaces associated with ACPI tables in bios code. Notes: As BIOS can reprogram devices prior to loading ACPI tables, we pre-format ACPI tables but defer loading hardware configuration there until tables are loaded. The code structure was intentionally kept as close to the seabios original as possible, to simplify comparison and making sure we didn't lose anything in translation. Minor code duplication results, to help ensure there are no functional regressions, I think it's better to merge it like this and do more code changes in follow-up patches. Cross-version compatibility concerns have been addressed: ACPI tables are exposed to guest as FW_CFG entries. When running with -M 1.5 and older, this patch disables ACPI table generation, and doesn't expose ACPI tables to guest. As table content is likely to change over time, the following measures are taken to simplify cross-version migration: - All tables besides the RSDP are packed in a single FW CFG entry. This entry size is currently 23K. We round it up to 64K to avoid too much churn there. - Tables are placed in special ROM blob (not mapped into guest memory) which is automatically migrated together with the guest, same as BIOS code. - Offsets where hardware configuration is loaded in ACPI tables are also migrated, this is in case future ACPI changes make us rearrange the tables in memory. This patch reuses some code from SeaBIOS, which was originally under LGPLv2 and then relicensed to GPLv3 or LGPLv3, in QEMU under GPLv2+. This relicensing has been acked by all contributors that had contributed to the code since the v2->v3 relicense. ACKs approving the v2+ relicensing are listed below. The list might include ACKs from people not holding copyright on any parts of the reused code, but it's better to err on the side of caution and include them. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1248854 Title: The guest cannot boot up with parameter "-no-acpi" Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 qemu.git Commit:a126050a103c924b03388a9a64ce9af8c96b0969 Host Kernel Version:3.12.0-rc5 Hardware:Romley_EP ,Ivytowm_EP Bug detailed description: -- when create guest with parameter "-no-acpi", the guest cannot boot up. note: this should be a qemu bug kvm + qemu = result 81e87e26 + a126050a = bad 81e87e26 + b8616055 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none -no-acpi rhel6u4.qcow Current result: guest cannot boot up Expected result: guest boot up fine. Basic root-causing log: -- [root@vt-snb9 qemu]#qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow -no-acpi VNC server running on `::1:5900' qemu-system-x86_64: /root/qemu/hw/i386/acpi-build.c:135: acpi_get_pm_info: Assertion `obj' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1248854/+subscriptions
[Qemu-devel] [Bug 1248854] Re: The guest cannot boot up with parameter "-no-acpi"
kvm.git + qemu.git: ede58222_5c5432e7 test on Romley_EP, Ivytown_EP, create guest with parameter "-no-acpi", the guest boot up fine. ** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1248854 Title: The guest cannot boot up with parameter "-no-acpi" Status in QEMU: Confirmed Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 qemu.git Commit:a126050a103c924b03388a9a64ce9af8c96b0969 Host Kernel Version:3.12.0-rc5 Hardware:Romley_EP ,Ivytowm_EP Bug detailed description: -- when create guest with parameter "-no-acpi", the guest cannot boot up. note: this should be a qemu bug kvm + qemu = result 81e87e26 + a126050a = bad 81e87e26 + b8616055 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none -no-acpi rhel6u4.qcow Current result: guest cannot boot up Expected result: guest boot up fine. Basic root-causing log: -- [root@vt-snb9 qemu]#qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow -no-acpi VNC server running on `::1:5900' qemu-system-x86_64: /root/qemu/hw/i386/acpi-build.c:135: acpi_get_pm_info: Assertion `obj' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1248854/+subscriptions
[Qemu-devel] [Bug 1248854] Re: The guest cannot boot up with parameter "-no-acpi"
** Changed in: qemu Status: Confirmed => Fix Committed ** Changed in: qemu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1248854 Title: The guest cannot boot up with parameter "-no-acpi" Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 qemu.git Commit:a126050a103c924b03388a9a64ce9af8c96b0969 Host Kernel Version:3.12.0-rc5 Hardware:Romley_EP ,Ivytowm_EP Bug detailed description: -- when create guest with parameter "-no-acpi", the guest cannot boot up. note: this should be a qemu bug kvm + qemu = result 81e87e26 + a126050a = bad 81e87e26 + b8616055 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none -no-acpi rhel6u4.qcow Current result: guest cannot boot up Expected result: guest boot up fine. Basic root-causing log: -- [root@vt-snb9 qemu]#qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/rhel6u4.qcow -no-acpi VNC server running on `::1:5900' qemu-system-x86_64: /root/qemu/hw/i386/acpi-build.c:135: acpi_get_pm_info: Assertion `obj' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1248854/+subscriptions
[Qemu-devel] [Bug 1261265] Re: win7 guest boot up fail.
kvm.git + qemu.git: d3714010 + d844a7b6 after create win7 guest, the guest boots up fine -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261265 Title: win7 guest boot up fail. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:a1d22a367d5780c9553b2cd5a24f665534ce6ed6 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when create a win7 guest, the guest boot up fail. note: 1. when create win2k3, win2k8 guest, the guest boot up fail. 2. when create win8, win2012 guest, the guest boot up fine. 3. this should be a qemu bug kvm + qemu = result d6d63b51 + a1d22a36 = bad d6d63b51 + 7dc65c02 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/win7.img Current result: win7 guest boot up fail Expected result: win7 guest boot up fine Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261265/+subscriptions
[Qemu-devel] [Bug 1261265] Re: win7 guest boot up fail.
** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1261265 Title: win7 guest boot up fail. Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:d6d63b51fe3bfea0cf596993afa480b0b3b02c32 qemu.git Commit:a1d22a367d5780c9553b2cd5a24f665534ce6ed6 Host Kernel Version:3.13.0-rc1 Hardware:Romley_EP, Ivytown_EP Bug detailed description: -- when create a win7 guest, the guest boot up fail. note: 1. when create win2k3, win2k8 guest, the guest boot up fail. 2. when create win8, win2012 guest, the guest boot up fine. 3. this should be a qemu bug kvm + qemu = result d6d63b51 + a1d22a36 = bad d6d63b51 + 7dc65c02 = good Reproduce steps: 1. create guest qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none /root/win7.img Current result: win7 guest boot up fail Expected result: win7 guest boot up fine Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1261265/+subscriptions
[Qemu-devel] [Bug 1422285] [NEW] The guest will be destroyed when hot plug the VF to guest for the second time.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 Host Kernel Version:3.19.0-rc3 Hardware:Haswell_EP,Ivytown_EP Bug detailed description: -- create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. note: 1. hot plug the device to guest with vfio, the guest works fine 2.this should be a qemu bug: kvm + qemu = result 6557bada + cd2d5541 = bad 6557bada + a805ca54 = good Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow 2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 3. cat /dev/pts/2 & 4. echo "device_del nic" >/dev/pts/2 5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 Current result: guest will be destroyed when hot plug the vf to guest for the second time. Expected result: guest works fine when hot plug the vf to guest for the second time Basic root-causing log: -- [root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow char device redirected to /dev/pts/2 (label compat_monitor0) Segmentation fault (core dumped) some dmesg log: pci-stub :03:10.1: kvm deassign device pci-stub :03:10.1: enabling device ( -> 0002) qemu-system-x86[9894]: segfault at 0 ip (null) sp 7fa73df0cae8 error 14 pci-stub :03:10.1: kvm assign device ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1422285 Title: The guest will be destroyed when hot plug the VF to guest for the second time. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 Host Kernel Version:3.19.0-rc3 Hardware:Haswell_EP,Ivytown_EP Bug detailed description: -- create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. note: 1. hot plug the device to guest with vfio, the guest works fine 2.this should be a qemu bug: kvm + qemu = result 6557bada + cd2d5541 = bad 6557bada + a805ca54 = good Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow 2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 3. cat /dev/pts/2 & 4. echo "device_del nic" >/dev/pts/2 5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 Current result: guest will be destroyed when hot plug the vf to guest for the second time. Expected result: guest works fine when hot plug the vf to guest for the second time Basic root-causing log: -- [root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow char device redirected to /dev/pts/2 (label compat_monitor0) Segmentation fault (core dumped) some dmesg log: pci-stub :03:10.1: kvm deassign device pci-stub :03:10.1: enabling device ( -> 0002) qemu-system-x86[9894]: segfault at 0 ip (null) sp 7fa73df0cae8 error 14 pci-stub :03:10.1: kvm assign device To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422285/+subscriptions
[Qemu-devel] [Bug 1422285] Re: The guest will be destroyed when hot plug the VF to guest for the second time.
the first bad commit is: commit ec6f25e788ef57ce1e9f734984ef8885172fd9e2 Merge: 007c99f 9ef1473 Author: Peter Maydell Date: Tue Feb 3 21:37:16 2015 + Merge remote-tracking branch 'remotes/rth/tags/pull-tg-s390-20150203' into staging s390 translator bug fixes # gpg: Signature made Tue 03 Feb 2015 20:39:15 GMT using RSA key ID 4DD0279B # gpg: Good signature from "Richard Henderson " # gpg: aka "Richard Henderson " # gpg: aka "Richard Henderson " * remotes/rth/tags/pull-tg-s390-20150203: target-s390x: fix and optimize slb* and slbg* computation of carry/borrow flag target-s390x: support OC and NC in the EX instruction disas/s390.c: Remove unused variables target-s390x: Mark check_privileged() as !CONFIG_USER_ONLY target-s390: Implement ECAG target-s390: Implement LURA, LURAG, STURG target-s390: Fix STURA target-s390: Fix STIDP target-s390: Implement EPSW target-s390: Implement SAM specification exception Signed-off-by: Peter Maydell -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1422285 Title: The guest will be destroyed when hot plug the VF to guest for the second time. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 Host Kernel Version:3.19.0-rc3 Hardware:Haswell_EP,Ivytown_EP Bug detailed description: -- create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. note: 1. hot plug the device to guest with vfio, the guest works fine 2.this should be a qemu bug: kvm + qemu = result 6557bada + cd2d5541 = bad 6557bada + a805ca54 = good Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow 2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 3. cat /dev/pts/2 & 4. echo "device_del nic" >/dev/pts/2 5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 Current result: guest will be destroyed when hot plug the vf to guest for the second time. Expected result: guest works fine when hot plug the vf to guest for the second time Basic root-causing log: -- [root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow char device redirected to /dev/pts/2 (label compat_monitor0) Segmentation fault (core dumped) some dmesg log: pci-stub :03:10.1: kvm deassign device pci-stub :03:10.1: enabling device ( -> 0002) qemu-system-x86[9894]: segfault at 0 ip (null) sp 7fa73df0cae8 error 14 pci-stub :03:10.1: kvm assign device To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422285/+subscriptions
[Qemu-devel] [Bug 1422285] Re: The guest will be destroyed when hot plug the VF to guest for the second time.
please ignore comment 1. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1422285 Title: The guest will be destroyed when hot plug the VF to guest for the second time. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 Host Kernel Version:3.19.0-rc3 Hardware:Haswell_EP,Ivytown_EP Bug detailed description: -- create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. note: 1. hot plug the device to guest with vfio, the guest works fine 2.this should be a qemu bug: kvm + qemu = result 6557bada + cd2d5541 = bad 6557bada + a805ca54 = good Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow 2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 3. cat /dev/pts/2 & 4. echo "device_del nic" >/dev/pts/2 5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 Current result: guest will be destroyed when hot plug the vf to guest for the second time. Expected result: guest works fine when hot plug the vf to guest for the second time Basic root-causing log: -- [root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow char device redirected to /dev/pts/2 (label compat_monitor0) Segmentation fault (core dumped) some dmesg log: pci-stub :03:10.1: kvm deassign device pci-stub :03:10.1: enabling device ( -> 0002) qemu-system-x86[9894]: segfault at 0 ip (null) sp 7fa73df0cae8 error 14 pci-stub :03:10.1: kvm assign device To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422285/+subscriptions
[Qemu-devel] [Bug 1422285] Re: The guest will be destroyed when hot plug the VF to guest for the second time.
the first bad commit: commit 374f2981d1f10bc4307f250f24b2a7ddb9b14be0 Author: Paolo Bonzini Date: Fri May 17 12:37:03 2013 +0200 memory: protect current_map by RCU Replace the flat_view_mutex with RCU, avoiding futex contention for dataplane on large systems and many iothreads. Reviewed-by: Fam Zheng Signed-off-by: Paolo Bonzini -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1422285 Title: The guest will be destroyed when hot plug the VF to guest for the second time. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 Host Kernel Version:3.19.0-rc3 Hardware:Haswell_EP,Ivytown_EP Bug detailed description: -- create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. note: 1. hot plug the device to guest with vfio, the guest works fine 2.this should be a qemu bug: kvm + qemu = result 6557bada + cd2d5541 = bad 6557bada + a805ca54 = good Reproduce steps: 1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow 2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 3. cat /dev/pts/2 & 4. echo "device_del nic" >/dev/pts/2 5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 Current result: guest will be destroyed when hot plug the vf to guest for the second time. Expected result: guest works fine when hot plug the vf to guest for the second time Basic root-causing log: -- [root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow char device redirected to /dev/pts/2 (label compat_monitor0) Segmentation fault (core dumped) some dmesg log: pci-stub :03:10.1: kvm deassign device pci-stub :03:10.1: enabling device ( -> 0002) qemu-system-x86[9894]: segfault at 0 ip (null) sp 7fa73df0cae8 error 14 pci-stub :03:10.1: kvm assign device To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422285/+subscriptions
[Qemu-devel] [Bug 1416246] [NEW] create guest fail when compile qemu with parameter "--disable-gtk"
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:8fff5e374a2f6047d1bb52288af7da119bc75765 qemu.kvm Commit:16017c48547960539fcadb1f91d252124f442482 Host Kernel Version:3.19.0-rc3 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- compile the qemu with disable gtk, the create guest , the guest create fail note: 1.qemu.git: 699eae17b841e6784dc3864bf357e26bff1e9dfe when compile the qemu with enable gtk or disable gtk, the guest create pass 2. this should be a qemu bug kvm.git + qemu.git = result 8fff5e37 + 16017c48 = bad 8fff5e37 + 699eae17 = good Reproduce steps: 1. git clone git://vt-sync/qemu.git qemu.git 2. cd qemu.git 3. ./configure --target-list=x86_64-softmmu --disable-sdl --disable-gtk 4. make -j16 5. ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5.qcow Current result: create gust fail when compile qemu with disable gtk Expected result: create guest pass when compile qemu with disable or enable gtk Basic root-causing log: -- [root@vt-ivt2 qemu.git]# ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5-1.qcow qemu-system-x86_64: Invalid parameter 'to' Segmentation fault (core dumped) some dmesg message: qemu-system-x86[96364]: segfault at 24 ip 7fe6d9636a69 sp 7fffc03cf970 error 4 in qemu-system-x86_64[7fe6d933+4ba000] ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1416246 Title: create guest fail when compile qemu with parameter "--disable-gtk" Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux kvm.git Commit:8fff5e374a2f6047d1bb52288af7da119bc75765 qemu.kvm Commit:16017c48547960539fcadb1f91d252124f442482 Host Kernel Version:3.19.0-rc3 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- compile the qemu with disable gtk, the create guest , the guest create fail note: 1.qemu.git: 699eae17b841e6784dc3864bf357e26bff1e9dfe when compile the qemu with enable gtk or disable gtk, the guest create pass 2. this should be a qemu bug kvm.git + qemu.git = result 8fff5e37 + 16017c48 = bad 8fff5e37 + 699eae17 = good Reproduce steps: 1. git clone git://vt-sync/qemu.git qemu.git 2. cd qemu.git 3. ./configure --target-list=x86_64-softmmu --disable-sdl --disable-gtk 4. make -j16 5. ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5.qcow Current result: create gust fail when compile qemu with disable gtk Expected result: create guest pass when compile qemu with disable or enable gtk Basic root-causing log: -- [root@vt-ivt2 qemu.git]# ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5-1.qcow qemu-system-x86_64: Invalid parameter 'to' Segmentation fault (core dumped) some dmesg message: qemu-system-x86[96364]: segfault at 24 ip 7fe6d9636a69 sp 7fffc03cf970 error 4 in qemu-system-x86_64[7fe6d933+4ba000] To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1416246/+subscriptions
[Qemu-devel] [Bug 1406706] [NEW] guest will be destroyed when create guest with parameter "-usbdevice tablet".
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:2c4aa55a6af070262cca425745e8e54310e96b8d qemu.git Commit:ab0302ee764fd702465aef6d88612cdff4302809 Host Kernel Version:3.18.0-rc3 Hardware: Ivytown_EP,Haswell_EP Bug detailed description: -- when create guest with parameter "-usbdevice tablet", then guest will be destroyed. note: this shoule be a qemu bug: kvm + qemu= result 2c4aa55a + ab0302ee = bad 2c4aa55a + 54600752 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 4G smp 2 -net none win8.1.qcow -usbdevice tablet Current result: the guest will be destroyed when create guest with "-usbdevice tablet" Expected result: the guest works fine when create guest with "-usbdevice tablet" Basic root-causing log: -- [root@vt-hsw2 ~]# qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/cathy/win8.1.qcow -usbdevice tablet qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed. Aborted (core dumped) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1406706 Title: guest will be destroyed when create guest with parameter "-usbdevice tablet". Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:2c4aa55a6af070262cca425745e8e54310e96b8d qemu.git Commit:ab0302ee764fd702465aef6d88612cdff4302809 Host Kernel Version:3.18.0-rc3 Hardware: Ivytown_EP,Haswell_EP Bug detailed description: -- when create guest with parameter "-usbdevice tablet", then guest will be destroyed. note: this shoule be a qemu bug: kvm + qemu= result 2c4aa55a + ab0302ee = bad 2c4aa55a + 54600752 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 4G smp 2 -net none win8.1.qcow -usbdevice tablet Current result: the guest will be destroyed when create guest with "-usbdevice tablet" Expected result: the guest works fine when create guest with "-usbdevice tablet" Basic root-causing log: -- [root@vt-hsw2 ~]# qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/cathy/win8.1.qcow -usbdevice tablet qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1406706/+subscriptions
[Qemu-devel] [Bug 1406706] Re: guest will be destroyed when create guest with parameter "-usbdevice tablet".
test the patch with qemu.git commit ab0302ee764fd702465aef6d88612cdff4302809 create guest with parameter "-usbdevice tablet" , the guest works fine. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1406706 Title: guest will be destroyed when create guest with parameter "-usbdevice tablet". Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:2c4aa55a6af070262cca425745e8e54310e96b8d qemu.git Commit:ab0302ee764fd702465aef6d88612cdff4302809 Host Kernel Version:3.18.0-rc3 Hardware: Ivytown_EP,Haswell_EP Bug detailed description: -- when create guest with parameter "-usbdevice tablet", then guest will be destroyed. note: this shoule be a qemu bug: kvm + qemu= result 2c4aa55a + ab0302ee = bad 2c4aa55a + 54600752 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 4G smp 2 -net none win8.1.qcow -usbdevice tablet Current result: the guest will be destroyed when create guest with "-usbdevice tablet" Expected result: the guest works fine when create guest with "-usbdevice tablet" Basic root-causing log: -- [root@vt-hsw2 ~]# qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/cathy/win8.1.qcow -usbdevice tablet qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1406706/+subscriptions
[Qemu-devel] [Bug 1406706] Re: guest will be destroyed when create guest with parameter "-usbdevice tablet".
kvm.git+ qemu.git:bab5bb39_64ea8038 kernel:3.19.0-rc3 create guest with parameter "-usbdevice tablet" , the guest works fine. ** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1406706 Title: guest will be destroyed when create guest with parameter "-usbdevice tablet". Status in QEMU: Fix Released Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):windows kvm.git Commit:2c4aa55a6af070262cca425745e8e54310e96b8d qemu.git Commit:ab0302ee764fd702465aef6d88612cdff4302809 Host Kernel Version:3.18.0-rc3 Hardware: Ivytown_EP,Haswell_EP Bug detailed description: -- when create guest with parameter "-usbdevice tablet", then guest will be destroyed. note: this shoule be a qemu bug: kvm + qemu= result 2c4aa55a + ab0302ee = bad 2c4aa55a + 54600752 = good Reproduce steps: 1. create guest qemu-system-x86_64 --enable-kvm -m 4G smp 2 -net none win8.1.qcow -usbdevice tablet Current result: the guest will be destroyed when create guest with "-usbdevice tablet" Expected result: the guest works fine when create guest with "-usbdevice tablet" Basic root-causing log: -- [root@vt-hsw2 ~]# qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/cathy/win8.1.qcow -usbdevice tablet qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1406706/+subscriptions
[Qemu-devel] [Bug 1096814] Re: Guest hang when doing kernel build and writing date in guest
kvm.git + qemu.git: bab5bb39_74acb997
kernel version:3.19.0-rc3
When write date to remote disk in guest, and compile the kernel, after live
migration, the guest and host work fine.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096814
Title:
Guest hang when doing kernel build and writing date in guest
Status in QEMU:
Fix Released
Bug description:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:e11ae1a102b46f76441e328a2743ae5d6e201423
qemu-kvm Commit:4d9367b76f71c6d938cf8201392abe4bfb1136cb
Host Kernel Version:3.7.0
Hardware:Romley-EP, WSM-EP
Bug detailed description:
--
When writing date to remote filesystem (e.g. NFS) and compiling kernel in a
guest, the guest will hang occasionally.
This can't be reproduced every time.
Reproduce steps:
1. star a guest: qemu-system-x86_64 -m 4096 -smp 4 -drive
file=rhel6u3-b.img,if=virtio -net nic,macaddr=00:16:13:52:24:11 -net tap
2. in guest: mount my-nfs:/temp /mnt
3. do kernel build and write some data in /mnt dir
Current result:
host serial port will print “call trace”message
Expected result:
Guest work fine.
Basic root-causing log:
--
(some log in the host side)
INFO: rcu_sched self-detected stall on CPU { 7} (t=21000 jiffies g=6506
c=6505
q=803)
sending NMI to all CPUs:
NMI backtrace for cpu 7
CPU 7
Pid: 10664, comm: qemu-system-x86 Tainted: P 3.7.0 #2 Intel
Corporation S2600CP/S2600CP
RIP: 0010:[] [] find_next_bit+0x3f/0x9d
RSP: 0018:88043f6e3ce8 EFLAGS: 0006
RAX: ff00fe00 RBX: 88083f20cdd0 RCX: 0009
RDX: 0009 RSI: 00ff RDI: 00ff
RBP: 88043f6e3ce8 R08: R09: 88043f6ecdf0
R10: 0004 R11: R12: 88043f6ecdf0
R13: cdc0 R14: cdd0 R15: 0002
FS: 7fda02753700() GS:88043f6e() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0031db8df760 CR3: 00042c82d000 CR4: 000427e0
DR0: DR1: DR2:
DR3: DR6: 0ff0 DR7: 0400
Process qemu-system-x86 (pid: 10664, threadinfo 88042b31, task
880424d03800)
Stack:
88043f6e3d08 81210366 88043f6ecdf0 0008
88043f6e3d78 81022a57 88043f6e3f48 7fff00020001
0007 0008813fe374 88083f20cdd0 0096
Call Trace:
[] cpumask_next_and+0x2c/0x39
[] __x2apic_send_IPI_mask+0xa9/0x129
[] x2apic_send_IPI_all+0x17/0x19
[] arch_trigger_all_cpu_backtrace+0x52/0x8a
[] print_cpu_stall+0xcc/0x15b
[] __rcu_pending+0x5d/0x166
[] rcu_check_callbacks+0xd0/0x132
[] update_process_times+0x3c/0x72
[] tick_sched_handle+0x45/0x54
[] tick_sched_timer+0x58/0x77
[] __run_hrtimer+0xd6/0x161
[] ? tick_nohz_handler+0xab/0xab
[] ? __do_softirq+0x182/0x1b4
[] hrtimer_interrupt+0xce/0x1b0
[] smp_apic_timer_interrupt+0x81/0x94
[] apic_timer_interrupt+0x6a/0x70
[] ? skb_flow_dissect+0xca/0x33c
[] ? sock_alloc_send_pskb+0x10d/0x337
[] ? skb_copy_datagram_from_iovec+0x58/0x20f
[] __skb_get_rxhash+0x15/0xc0
[] tun_get_user+0x471/0x4e8 [tun]
[] ? tun_sendmsg+0x70/0x70 [tun]
[] tun_chr_aio_write+0x7b/0x93 [tun]
[] do_sync_readv_writev+0x93/0xd1
[] do_readv_writev+0xb6/0x17f
[] ? ret_from_fork+0xb0/0xb0
[] ? do_vfs_ioctl+0x255/0x271
[] vfs_writev+0x3e/0x49
[] sys_writev+0x4f/0x9e
[] system_call_fastpath+0x16/0x1b
Code: 89 d0 48 c1 e9 06 49 83 e0 c0 4c 8d 0c cf 48 89 f7 4c 29 c7 83 e2 3f 74
39 48 83 c8 ff 88 d1 48 d3 e0 49 23 01 48 83 ff 3f 76 3b <48> 85 c0 75 4f 49
83
c1 08 48 83 ef 40 49 83 c0 40 eb 14 49 8b
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1096814/+subscriptions
[Qemu-devel] [Bug 1469946] Re: guest can't get IP when create guest with bridge.
the first bad commit is commit a90a7425cf592a3afeff3eaf32f543b83050ee5c Author: Fam Zheng Date: Thu Jun 4 14:45:17 2015 +0800 tap: Drop tap_can_send This callback is called by main loop before polling s->fd, if it returns false, the fd will not be polled in this iteration. This is redundant with checks inside read callback. After this patch, the data will be sent to peer when it arrives. If the device can't receive, it will be queued to incoming_queue, and when the device status changes, this queue will be flushed. Signed-off-by: Fam Zheng Message-id: 1433400324-7358-7-git-send-email-f...@redhat.com Signed-off-by: Stefan Hajnoczi -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469946 Title: guest can't get IP when create guest with bridge. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 qemu.git Commit:dc1e1350f8061021df765b396295329797d66933 Host Kernel Version:4.1.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, the guest can not get ip. note: 1. fail rate: 3/5 2. this is a qemu bug: kvm + qemu = result aefbef10 + dc1e1350= bad aefbef10 + a4ef02fd = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=$random_mac -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get IP Expected result: guest can get ip Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469946/+subscriptions
[Qemu-devel] [Bug 1469946] [NEW] guest can't get IP when create guest with bridge.
Public bug reported: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 qemu.git Commit:dc1e1350f8061021df765b396295329797d66933 Host Kernel Version:4.1.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, the guest can not get ip. note: 1. fail rate: 3/5 2. this is a qemu bug: kvm + qemu = result aefbef10 + dc1e1350= bad aefbef10 + a4ef02fd = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=$random_mac -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get IP Expected result: guest can get ip Basic root-causing log: -- ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469946 Title: guest can't get IP when create guest with bridge. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 qemu.git Commit:dc1e1350f8061021df765b396295329797d66933 Host Kernel Version:4.1.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, the guest can not get ip. note: 1. fail rate: 3/5 2. this is a qemu bug: kvm + qemu = result aefbef10 + dc1e1350= bad aefbef10 + a4ef02fd = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=$random_mac -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get IP Expected result: guest can get ip Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469946/+subscriptions
[Qemu-devel] [Bug 1469946] Re: guest can't get IP when create guest with bridge.
after try the patch http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg07377.html with qemu.git commit(d2966f804d70a244f5dde395fc5d22a50ed3e74e) the guest can get IP, but after save/retore or live migration, the guest is alive, but ping or ssh guest's IP fail . -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469946 Title: guest can't get IP when create guest with bridge. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 qemu.git Commit:dc1e1350f8061021df765b396295329797d66933 Host Kernel Version:4.1.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, the guest can not get ip. note: 1. fail rate: 3/5 2. this is a qemu bug: kvm + qemu = result aefbef10 + dc1e1350= bad aefbef10 + a4ef02fd = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=$random_mac -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get IP Expected result: guest can get ip Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469946/+subscriptions
[Qemu-devel] [Bug 1469946] Re: guest can't get IP when create guest with bridge.
Since commit 6e99c63 "net/socket: Drop net_socket_can_send" and friends,
net queues need to be explicitly flushed after qemu_can_send_packet()
returns false, because the netdev side will disable the polling of fd.
This fixes the case of "cont" after "stop" (or migration), i.e.
vm_running changes to true, by listening to vm state changes.
Signed-off-by: Fam Zheng
---
include/net/net.h | 2 ++
net/net.c | 14 +-
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/include/net/net.h b/include/net/net.h index 6a6cbef..619a6e1 100644
--- a/include/net/net.h
+++ b/include/net/net.h
@@ -8,6 +8,7 @@
#include "net/queue.h"
#include "migration/vmstate.h"
#include "qapi-types.h"
+#include "sysemu/sysemu.h"
#define MAX_QUEUE_NUM 1024
@@ -92,6 +93,7 @@ struct NetClientState {
NetClientDestructor *destructor;
unsigned int queue_index;
unsigned rxfilter_notify_enabled:1;
+VMChangeStateEntry *vmcse;
};
typedef struct NICState {
diff --git a/net/net.c b/net/net.c
index 6ff7fec..edfa6a0 100644
--- a/net/net.c
+++ b/net/net.c
@@ -43,7 +43,6 @@
#include "qapi-visit.h"
#include "qapi/opts-visitor.h"
#include "qapi/dealloc-visitor.h"
-#include "sysemu/sysemu.h"
/* Net bridge is currently not supported for W32. */ #if !defined(_WIN32) @@
-263,6 +262,16 @@ static void qemu_net_client_destructor(NetClientState *nc)
g_free(nc);
}
+static void qemu_net_client_handle_vmstate(void *opaque,
+ int running,
+ RunState state) {
+NetClientState *nc = opaque;
+if (running && qemu_can_send_packet(nc) && nc->peer) {
+qemu_flush_queued_packets(nc->peer);
+}
+}
+
static void qemu_net_client_setup(NetClientState *nc,
NetClientInfo *info,
NetClientState *peer, @@ -287,6 +296,8 @@
static void qemu_net_client_setup(NetClientState *nc,
nc->incoming_queue = qemu_new_net_queue(nc);
nc->destructor = destructor;
+nc->vmcse =
qemu_add_vm_change_state_handler(qemu_net_client_handle_vmstate,
+ nc);
}
NetClientState *qemu_new_net_client(NetClientInfo *info, @@ -395,6 +406,7 @@
void qemu_del_net_client(NetClientState *nc)
MAX_QUEUE_NUM);
assert(queues != 0);
+qemu_del_vm_change_state_handler(nc->vmcse);
/* If there is a peer NIC, delete and cleanup client, but do not free. */
if (nc->peer && nc->peer->info->type == NET_CLIENT_OPTIONS_KIND_NIC) {
NICState *nic = qemu_get_nic(nc->peer);
--
2.4.3
after try this patch and
http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg07377.html with
qemu.git d2966f804d70a244f5dde395fc5d22a50ed3e74e
after save/retore or live migration, the guest is alive, ping or ssh guest's
IP , it is fine
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1469946
Title:
guest can't get IP when create guest with bridge.
Status in QEMU:
New
Bug description:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):linux
kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66
qemu.git Commit:dc1e1350f8061021df765b396295329797d66933
Host Kernel Version:4.1.0
Hardware:Ivytown_EP, Haswell_EP
Bug detailed description:
--
when create guest with bridge, the guest can not get ip.
note:
1. fail rate: 3/5
2. this is a qemu bug:
kvm + qemu = result
aefbef10 + dc1e1350= bad
aefbef10 + a4ef02fd = good
Reproduce steps:
1. create guest:
qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device
virtio-net-pci,netdev=net0,mac=$random_mac -netdev
tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow
Current result:
guest can't get IP
Expected result:
guest can get ip
Basic root-causing log:
--
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1469946/+subscriptions
[Qemu-devel] [Bug 1007269] Re: Can’t install or boot up 32bit win8 guest.
It's not a KVM bug. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1007269 Title: Can’t install or boot up 32bit win8 guest. Status in QEMU: Invalid Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(rhel6u1) kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6 Host Kernel Version:3.4.0-rc7 Hardware:WSM-EP,Romley-EP Bug detailed description: -- it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. -Win8 Error--- Your computer needs to restart. Please hold down the power button. Error code: 0x005D Parameters: 0x03060D03 0x756E6547 0x49656E69 0x6C65746E -Win8 Error--- "0x005D" code means "UNSUPPORTED_PROCESSOR" in Windows. BTW, you can get 32bit Win8 ISO from the following website. http://windows.microsoft.com/en-US/windows-8/iso Reproduce steps: 1. get 32 bit win8 ISO 2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384 3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso 4. if you have a 32bit win8 image,try to boot it up Current result: 32bit Win8 guest crash Expected result: 32bit win8 guest boot up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1007269/+subscriptions
[Qemu-devel] [Bug 1019179] Re: vCPU hot-add makes the guest abort
qemu-kvm.git has merged to qemu.git, upstream qemu doesn't have cpu_set command. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1019179 Title: vCPU hot-add makes the guest abort Status in QEMU: Invalid Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(RHEL6u1) kvm.git Commit:ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb qemu-kvm Commit:a212f79fc4596570124fb864425b980c157cd001 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, WSM-EP Bug detailed description: -- Hot-add vcpu for a guest in qemu monitor will make the guest abort. (QEMU process is killed.) After Hot-removing vcpu for the guest in qemu monitor, the guest will be still alive but the the number of vCPU in the guest doesn't decrease. Reproduce steps: Hot-add vCPU: 1.start up a host with kvm (commit: ae7a2a3f)and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 5 online Hot-remove vCPU: 1.start up a host with kvm (commit: ae7a2a3f) and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 2 offline 6. ctrl+alt+1 7. ls /sys/devices/system/cpu/(to check CPUs in guest) Current result: vCPU hot-add will cause guest abort. vCPU hot-remove doesn't decrease the number of vCPU in guest. Expected result: The number of the guest’s cpu changes as we expect. Basic root-causing log: -- [root@vt-snb9 ~]# qemu-system-x86_64 -m 1024 -smp 4,maxcpus=10 -hda /root/rhel6u3.qcow VNC server running on `::1:5900' qemu-system-x86_64: hw/qdev.c:84: qdev_set_parent_bus: Assertion `bus->allow_hotplug' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1019179/+subscriptions
[Qemu-devel] [Bug 1019179] Re: vCPU hot-add makes the guest abort
** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1019179 Title: vCPU hot-add makes the guest abort Status in QEMU: Invalid Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):Linux(RHEL6u1) kvm.git Commit:ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb qemu-kvm Commit:a212f79fc4596570124fb864425b980c157cd001 Host Kernel Version:3.5.0-rc1 Hardware:Romley-EP, WSM-EP Bug detailed description: -- Hot-add vcpu for a guest in qemu monitor will make the guest abort. (QEMU process is killed.) After Hot-removing vcpu for the guest in qemu monitor, the guest will be still alive but the the number of vCPU in the guest doesn't decrease. Reproduce steps: Hot-add vCPU: 1.start up a host with kvm (commit: ae7a2a3f)and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 5 online Hot-remove vCPU: 1.start up a host with kvm (commit: ae7a2a3f) and qemu-kvm(commit: a212f79f..) 2.qemu-system-x86_64 -m 1024 -smp 4,maxvcpus=10 –hda /root/rhel6u3.qcow 3. ls /sys/devices/system/cpu/(to check CPUs in guest) 4. ctrl+alt+2 (swith to qemu monitor) 5. cpu_set 2 offline 6. ctrl+alt+1 7. ls /sys/devices/system/cpu/(to check CPUs in guest) Current result: vCPU hot-add will cause guest abort. vCPU hot-remove doesn't decrease the number of vCPU in guest. Expected result: The number of the guest’s cpu changes as we expect. Basic root-causing log: -- [root@vt-snb9 ~]# qemu-system-x86_64 -m 1024 -smp 4,maxcpus=10 -hda /root/rhel6u3.qcow VNC server running on `::1:5900' qemu-system-x86_64: hw/qdev.c:84: qdev_set_parent_bus: Assertion `bus->allow_hotplug' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1019179/+subscriptions
[Qemu-devel] [Bug 1469946] Re: guest can't get IP when create guest with bridge.
Does the bug's patch has merged in qemu.git? I test the latest qemu.git(commit:5b5e8cdd7da7a2214dd062afff5b866234aab228), the bug still can reproduce. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1469946 Title: guest can't get IP when create guest with bridge. Status in QEMU: New Bug description: Environment: Host OS (ia32/ia32e/IA64):ia32e Guest OS (ia32/ia32e/IA64):ia32e Guest OS Type (Linux/Windows):linux kvm.git Commit:aefbef10e3ae6e2c6e3c54f906f10b34c73a2c66 qemu.git Commit:dc1e1350f8061021df765b396295329797d66933 Host Kernel Version:4.1.0 Hardware:Ivytown_EP, Haswell_EP Bug detailed description: -- when create guest with bridge, the guest can not get ip. note: 1. fail rate: 3/5 2. this is a qemu bug: kvm + qemu = result aefbef10 + dc1e1350= bad aefbef10 + a4ef02fd = good Reproduce steps: 1. create guest: qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -device virtio-net-pci,netdev=net0,mac=$random_mac -netdev tap,id=net0,script=/etc/kvm/qemu-ifup rhel6u5.qcow Current result: guest can't get IP Expected result: guest can get ip Basic root-causing log: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1469946/+subscriptions
