Well, there are some clear indications in your log what might be wrong:
warning: TCG doesn't support requested feature: CPUID.01H:EDX.vme [bit 1]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit
24]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.osxsave [bit 27]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
Try to disable these features in your "-cpu" parameter for example.
If that does not help, please try to start QEMU without libvirt first, to see
whether it is an issue with libvirt (then you should report it to their bug
tracker instead) or QEMU. And please use the latest release of QEMU (currently
v2.8.0), since the bug might have already been fixed in a later version.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1652333
Title:
TCG mode fails to boot Linux kernel with qemu 2.6.0 and libvirt 2.0.0
Status in QEMU:
Incomplete
Bug description:
Trying to boot a Cirros (minimal Linux) VM with qemu 2.6.0 and libvirt
2.0.0 in TCG mode fails for me. The VM gets stuck in "Starting up ..."
and never moves on. The command line used to boot the VM was:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name
guest=instance-00000002,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-instance-00000002
/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=tcg,usb=off -cpu
SandyBridge,+osxsave,+hypervisor,+xsaveopt -m 512 -realtime mlock=off
-smp 1,sockets=1,cores=1,threads=1 -uuid ae38b0e1-b3ae-41ec-
8e50-c89669a2ec1c -smbios 'type=1,manufacturer=Red
Hat,product=OpenStack Compute,version=14.0.2-7.el7ost,serial=edd3a67d-
6ce5-4c36-8f20-085d1097abb7,uuid=ae38b0e1-b3ae-41ec-
8e50-c89669a2ec1c,family=Virtual Machine' -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-instance-00000002/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-
shutdown -boot strict=on -device piix3-usb-
uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/lib/nova/instances/ae38b0e1-b3ae-41ec-
8e50-c89669a2ec1c/disk,format=qcow2,if=none,id=drive-virtio-
disk0,cache=none -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -netdev tap,fd=28,id=hostnet0 -device virtio-net-
pci,netdev=hostnet0,id=net0,mac=fa:16:3e:c1:27:73,bus=pci.0,addr=0x3
-add-fd set=1,fd=31 -chardev
file,id=charserial0,path=/dev/fdset/1,append=on -device isa-
serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1
-device isa-serial,chardev=charserial1,id=serial1 -device usb-
tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0 -k en-us -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
A qcow2 image can be downloaded from http://download.cirros-
cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img to reproduce the issue.
I've seen a similar failure with a CentOS 7.2 image.
I am also attaching the libvirt log from the failed VM.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1652333/+subscriptions
