[Bug 1848497] Re: virtio-balloon change breaks migration from qemu prior to 4.0

[Christian Ehrhardt ]

With a migration Bionic to Eoan with a balloon device I can confirm
this.

Guestconfig:
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>

root at testkvm-bionic-from:~# virsh migrate --unsafe --live testguest qemu+ssh://10.192.69.27/system
error: internal error: qemu unexpectedly closed the monitor: 2019-10-21T13:44:16.155100Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
2019-10-21T13:44:18.530641Z qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x10 read: e1 device: 1 cmask: ff wmask: c0 w1cmask:0
2019-10-21T13:44:18.530657Z qemu-system-x86_64: Failed to load PCIDevice:config
2019-10-21T13:44:18.530660Z qemu-system-x86_64: Failed to load virtio-balloon:virtio
2019-10-21T13:44:18.530663Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:06.0/virtio-balloon'
2019-10-21T13:44:18.530839Z qemu-system-x86_64: load of migration failed: Invalid argument

** Changed in: qemu (Ubuntu)
       Status: New => Confirmed

** Changed in: qemu (Ubuntu)
   Importance: Undecided => High

** Changed in: qemu (Ubuntu)
     Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1848497

Title:
  virtio-balloon change breaks migration from qemu prior to 4.0

Status in Ubuntu Cloud Archive:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Related but not the same as bug 1838569 which had two error signatures.
  The first being covered there and the second handled here.

  --- ---
  Quote from https://bugs.launchpad.net/cloud-archive/+bug/1838569/comments/4
  Daniel 'f0o' Preussker (dpreussker) wrote 1 hour ago:	#4
  With recent release of OpenStack Train this issue reappears...

  Upgrading from Stein to Train will require all VMs to be hard-rebooted
  to be migrated as a final step because Live Migration fails with:

  Oct 17 10:28:43 h2.1.openstack.r0cket.net libvirtd[1545]: Unable to read from monitor: Connection reset by peer
  Oct 17 10:28:43 h2.1.openstack.r0cket.net libvirtd[1545]: internal error: qemu unexpectedly closed the monitor: 2019-10-17T10:28:42.981201Z qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x10 read: a1 device: 1 cmask: ff wmask: c0 w1cmask:0
                                                            2019-10-17T10:28:42.981250Z qemu-system-x86_64: Failed to load PCIDevice:config
                                                            2019-10-17T10:28:42.981263Z qemu-system-x86_64: Failed to load virtio-balloon:virtio
                                                            2019-10-17T10:28:42.981272Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:05.0/virtio-balloon'
                                                            2019-10-17T10:28:42.981391Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2532609 kHz) and host (2532608 kHz), and TSC scaling unavailable
                                                            2019-10-17T10:28:42.983157Z qemu-system-x86_64: warning: TSC frequency mismatch between VM (2532609 kHz) and host (2532608 kHz), and TSC scaling unavailable
                                                            2019-10-17T10:28:42.983672Z qemu-system-x86_64: load of migration failed: Invalid argument

  
  --- ---

  
  Identified as:
  Dr. David Alan Gilbert (dgilbert-h) wrote 1 hour ago:	#5
  Dnaiel: That's a different problem; 'Bad config data: i=0x10 read: a1 device: 1 cmask: ff wmask: c0 w1cmask:0'; so should probably be a separate bug.

  I'd bet on this being the one fixed by
  2bbadb08ce272d65e1f78621002008b07d1e0f03

  
  --- ---

  And that is a fix that only is in qemu 4.1 and would be an open bug
  for Ubuntu and Cloud Archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1848497/+subscriptions