Control: tags -1 + moreinfo
On Fri, 26 Oct 2018 Antoine Beaupre <[email protected]> wrote:
> It looks like the way autopkgtest calls qemu is suboptimal:
>
> gnupg2-2.1.1816$ autopkgtest . -- qemu
> /var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
> autopkgtest [15:26:43]: version 5.6
> autopkgtest [15:26:43]: host curie; command line: /usr/bin/autopkgtest . --
> qemu /var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
> qemu-system-x86_64: warning: host doesn't support requested feature:
> CPUID.01H:ECX.vmx [bit 5]
> autopkgtest [15:26:54]: testbed dpkg architecture: amd64
> autopkgtest [15:26:57]: testbed running kernel: Linux 4.9.0-7-amd64 #1 SMP
> Debian 4.9.110-1 (2018-07-05)
> autopkgtest [15:26:57]: @@@@@@@@@@@@@@@@@@@@ unbuilt-tree .
> [...]
>
> From there on the build proceeds on fine, but I suspect it's not using
> the hardware support for virtualization.
Hi, are you still experiencing this? In my understanding, autopkgtest
tries to automatically detect whether the cpu supports vmx, and
opportunistically enables some qemu flags:
with open('/proc/cpuinfo', 'r') as f:
for line in f:
if line.startswith('flags'):
words = line.split()
if 'vmx' in words:
adtlog.debug(
'Detected KVM capable Intel host CPU, '
'enabling nested KVM'
)
return ['-cpu', 'kvm64,+vmx,+lahf_lm']
What happens if you manually try those?
Could it be that when you tried you had the virtualization extensions
disabled from the BIOS? I am not sure if vmx would still show up in
cpuinfo in this case, but this may be the case.
Cheers,
Paride
