> Hi,
> if no cpu model is set the default is qemu64 which is rather
> conservative for
> - maximum migratability
> - guaranteeing the same feature set will be available wherever you
> start your KVM
>
> But I thought svm/vmx would be part of that set.
>
> A short test at least on Xenial proved my assumption that for me that
> is flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl
> pni vmx cx16 x2apic popcnt hypervisor lahf_lm abm tpr_shadow vnmi
> flexpriority ept vpid Which contains vmx and kvm-ok is happy.
>
> Could you provide a "cat /proc/cpuinfo" of host and guest as well as
> the full commandline that libvirt generated for you?
Here is the output of cpuinfo (see attachment). And the qemu command
line generated is:
On Tue, 12 Apr 2016 16:49:39 -0000
ChristianEhrhardt <email address hidden> wrote:
> Hi,
> if no cpu model is set the default is qemu64 which is rather
> conservative for
> - maximum migratability
> - guaranteeing the same feature set will be available wherever you
> start your KVM
>
> But I thought svm/vmx would be part of that set.
>
> A short test at least on Xenial proved my assumption that for me that
> is flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl
> pni vmx cx16 x2apic popcnt hypervisor lahf_lm abm tpr_shadow vnmi
> flexpriority ept vpid Which contains vmx and kvm-ok is happy.
>
> Could you provide a "cat /proc/cpuinfo" of host and guest as well as
> the full commandline that libvirt generated for you?
Here is the output of cpuinfo (see attachment). And the qemu command
line generated is:
qemu-system-x86_64 -enable-kvm -name lp1561019 -S -machine \ vivid,accel= kvm,usb= off -m 2048 -realtime \ 2,cores= 1,threads= 1 \ ff3d-4e37- b2f0-93b47b029e 56 \ id=charmonitor, path=/var/ lib/libvirt/ qemu/lp1561019. monitor, server, nowait \ charmonitor, id=monitor, mode=control \ uhci,id= usb,bus= pci.0,addr= 0x1.0x2 -drive \ /var/lib/ uvtool/ libvirt/ images/ lp1561019. qcow,if= none,id= drive-virtio- disk0,format= qcow2 \ blk-pci, scsi=off, bus=pci. 0,addr= 0x4,drive= drive-virtio- disk0,id= virtio- disk0,bootindex =1 \ /var/lib/ uvtool/ libvirt/ images/ lp1561019- ds.qcow, if=none, id=drive- virtio- disk1,format= raw \ blk-pci, scsi=off, bus=pci. 0,addr= 0x5,drive= drive-virtio- disk1,id= virtio- disk1 \ 27,id=hostnet0, vhost=on, vhostfd= 28 -device \ net-pci, netdev= hostnet0, id=net0, mac=52: 54:00:74: 40:d0,bus= pci.0,addr= 0x3 \ serial, chardev= charserial0, id=serial0 -vnc 127.0.0.1:1 \ vga,id= video0, bus=pci. 0,addr= 0x2 -device \ balloon- pci,id= balloon0, bus=pci. 0,addr= 0x6 -msg timestamp=on
pc-i440fx-
mlock=off -smp 2,sockets=
-uuid 464aa942-
-no-user-config -nodefaults -chardev \
socket,
-mon chardev=
-rtc base=utc -no-shutdown -boot strict=on \
-device piix3-usb-
file=
-device \
virtio-
-drive \
file=
-device \
virtio-
-netdev tap,fd=
virtio-
-chardev pty,id=charserial0 -device \
isa-
-device cirrus-
virtio-
Also here is the xml generated by libvirt can be found at http:// paste.ubuntu. com/15856773/
The command line I used to create this vm was:
$ uvt-kvm create --memory 2048 --cpu 2 lp1561019 release=trusty arch=amd64
Using virt-manager for the bootstrap of the VM doesn't produce different results.
Best,
--
Felipe Reyes
Software Sustaining Engineer @ Canonical
STS Engineering Team
# Email: <email address hidden> (GPG:0x9B1FFF39)
# Phone: +56 9 7640 7887
# Launchpad: ~freyes | IRC: freyes