[Qemu-devel] [Bug 1603970] [NEW] KVM freezes after live migration (AMD 4184 -> 4234)

[Kilian Ries]

Public bug reported:

Hi,

i have two host systems with different CPU types:

Host A:
AMD Opteron(tm) Processor 4234

Host B:
AMD Opteron(tm) Processor 4184

Live migration from B -> A works as expected, migration from A -> B
always ends in a freezed KVM. If the KVM is frozen, VNC output is still
present, however, you can't type anything. CPU usage is always at 100%
for one core (so if i set two cores, one is at 100% the other one at 0%
usage).

My command to launch the KVM is the following:

/usr/bin/kvm -id 104 -chardev socket,id=qmp,path=/var/run/qemu-
server/104.qmp,server,nowait -mon chardev=qmp,mode=control -pidfile
/var/run/qemu-server/104.pid -daemonize -smbios
type=1,uuid=26dd83a9-b9bd-4641-8016-c55f255f1bdf -name kilian-test -smp
1,sockets=1,cores=1,maxcpus=1 -nodefaults -boot menu=on,strict=on
,reboot-timeout=1000 -vga cirrus -vnc unix:/var/run/qemu-
server/104.vnc,x509,password -cpu
kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 512 -object
memory-backend-ram,id=ram-node0,size=512M -numa
node,nodeid=0,cpus=0,memdev=ram-node0 -k de -device pci-
bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-
bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-
uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-
tablet,id=tablet,bus=uhci.0,port=1 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-
name=iqn.1993-08.org.debian:01:5ca1e9d334b2 -drive
file=/mnt/pve/nfs_synology/images/104/vm-104-disk-2.qcow2,if=none,id
=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on
-device virtio-blk-pci,drive=drive-
virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -netdev
type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-
bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device
virtio-net-
pci,mac=66:33:31:36:35:36,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300


KVM / QEMU version: QEMU emulator version 2.5.1.1

I have tried to set different CPU types, but no one works (qemu64, vm64,
Opteron_G1, ...).


I have found an email from 2014 where another user reports exactly the same 
problem:

http://lists.gnu.org/archive/html/qemu-discuss/2014-02/msg00002.html

Greets
Kilian

** 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/1603970

Title:
  KVM freezes after live migration (AMD 4184 -> 4234)

Status in QEMU:
  New

Bug description:
  Hi,

  i have two host systems with different CPU types:

  Host A:
  AMD Opteron(tm) Processor 4234

  Host B:
  AMD Opteron(tm) Processor 4184

  Live migration from B -> A works as expected, migration from A -> B
  always ends in a freezed KVM. If the KVM is frozen, VNC output is
  still present, however, you can't type anything. CPU usage is always
  at 100% for one core (so if i set two cores, one is at 100% the other
  one at 0% usage).

  My command to launch the KVM is the following:

  /usr/bin/kvm -id 104 -chardev socket,id=qmp,path=/var/run/qemu-
  server/104.qmp,server,nowait -mon chardev=qmp,mode=control -pidfile
  /var/run/qemu-server/104.pid -daemonize -smbios
  type=1,uuid=26dd83a9-b9bd-4641-8016-c55f255f1bdf -name kilian-test
  -smp 1,sockets=1,cores=1,maxcpus=1 -nodefaults -boot menu=on,strict=on
  ,reboot-timeout=1000 -vga cirrus -vnc unix:/var/run/qemu-
  server/104.vnc,x509,password -cpu
  kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 512 -object
  memory-backend-ram,id=ram-node0,size=512M -numa
  node,nodeid=0,cpus=0,memdev=ram-node0 -k de -device pci-
  bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-
  bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-
  uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-
  tablet,id=tablet,bus=uhci.0,port=1 -device virtio-balloon-
  pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-
  name=iqn.1993-08.org.debian:01:5ca1e9d334b2 -drive
  file=/mnt/pve/nfs_synology/images/104/vm-104-disk-2.qcow2,if=none,id
  =drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on
  -device virtio-blk-pci,drive=drive-
  virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -netdev
  type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-
  bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device
  virtio-net-
  
pci,mac=66:33:31:36:35:36,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300

  
  KVM / QEMU version: QEMU emulator version 2.5.1.1

  I have tried to set different CPU types, but no one works (qemu64,
  vm64, Opteron_G1, ...).

  
  I have found an email from 2014 where another user reports exactly the same 
problem:

  http://lists.gnu.org/archive/html/qemu-discuss/2014-02/msg00002.html

  Greets
  Kilian

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1603970/+subscriptions