migrate failed invalid cpu feature invtsc

[Laz Peterson]

Description: Ubuntu 15.04
Release: 15.04

libvirt-bin:
  Installed: 1.2.12-0ubuntu12
  Candidate: 1.2.12-0ubuntu13
  Version table:
     1.2.12-0ubuntu13 0
        500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages
 *** 1.2.12-0ubuntu12 0
        500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

Very similar to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386503

I have only tried on Ubuntu 15.04 using SandyBridge CPU features. I actually have Haswell CPUs in the host servers, but the TSX issue is preventing me from using that CPU feature set. (Would love to see that fix come downstream!)

Live migration does not work. Suspend does work.

Issue exists in both 1.2.12-0ubuntu12 and 1.2.12-0ubuntu13.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: libvirt-bin 1.2.12-0ubuntu12
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sun May 24 10:31:55 2015
InstallationDate: Installed on 2015-05-24 (0 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.qemu.networks.default.xml: [deleted]

[Laz Peterson (laz-v)]

I stand corrected ... This is something to be addressed within virt-manager and not libvirt. Using "Copy host CPU configuration" adds +invtsc (among other things). I mistakenly thought that directive simply does "-cpu host".

My apologies! Thank you and keep up the good work.

[Nigel Jones (nigel-7)]

Just raising the same issue.. if believed different please say & I'll open new. Again ubuntu 15.04 with upstream, cannot suspend - cause located to "invtsc" being added to the command line "+invtsc" after using the "copy host configuration" in virt-manager. I did also try changing policy to "disable" in the xml file but this appeared to have no effect. Impact - cannot suspend guest with an arguably default logical configuration