Minikube: docker-machine-driver-kvm2 : internal error: CPU IDs in <numa> exceed the <vcpu> count

Created on 4 Nov 2019 · 12Comments · Source: kubernetes/minikube

Hello. I am having an issue with the kvm2 docker-machine driver. It appears that the XML libvirt domain being generated does not have the correct core count set, notice in the XML below that \

I have ebtables 2.0.10, qemu 4.1.0, and libvirt 5.8.0 installed. libvirtd is running.

The exact command to reproduce the issue: docker-machine create -d kvm2 default

The full output of the command that failed:

Running pre-create checks...
Creating machine...
(default) Creating KVM machine...
(default) Setting up store path in /home/david/.docker/machine/machines/default ...
(default) Building disk image from 
(default) Copying /home/david/.docker/machine/cache/boot2docker.iso to /home/david/.docker/machine/machines/default/boot2docker.iso...
(default) Setting executable bit set on /home/david/.docker/machine/machines/default (perms=drwx------)
(default) Setting executable bit set on /home/david/.docker/machine/machines (perms=drwx--x--x)
(default) Setting executable bit set on /home/david/.docker/machine (perms=drwx--x--x)
(default) Setting executable bit set on /home/david/.docker (perms=drwx--x--x)
(default) Setting executable bit set on /home/david (perms=drwx--x--x)
(default) Creating domain...
(default) KVM machine creation complete!
Error creating machine: Error in driver during machine creation: creating domain: error defining domain xml: 
<domain type='kvm'>
  <name>default</name> 
  <memory unit='MB'>0</memory>
  <vcpu>0</vcpu>
  <features>
    <acpi/>
    <apic/>
    <pae/>

  </features>
  <cpu mode='host-passthrough'/>
  <os>
    <type>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <bootmenu enable='no'/>
  </os>
  <devices>
    <disk type='file' device='cdrom'>
      <source file=''/>
      <target dev='hdc' bus='scsi'/>
      <readonly/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='default' io='threads' />
      <source file=''/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <mac address='6c:a0:a0:f3:73:33'/>
      <model type='virtio'/>
    </interface>
    <interface type='network'>
      <source network='minikube-net'/>
      <mac address='f4:34:49:b7:c6:c6'/>
      <model type='virtio'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <rng model='virtio'>
      <backend model='random'>/dev/random</backend>
    </rng>

  </devices>
</domain>
: virError(Code=1, Domain=20, Message='internal error: CPU IDs in <numa> exceed the <vcpu> count')

The output of the minikube logs command: N/A

The operating system version: Manjaro (kernel 5.2.21-1-MANJARO)

My system should be compatible with virtualization. I have VTx enabled, as shown by the output of virt-host-validate below:

  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : PASS
  QEMU: Checking if IOMMU is enabled by kernel                               : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'freezer' controller support                     : PASS
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS

ckvm2 kinbug prioritimportant-longterm

Source

dacruz21

All 12 comments

@josedonizetti any idea?

medyagh on 5 Nov 2019

@dacruz21 are you running docker-machine-driver-kvm2 by itself or through minikube?

medyagh on 6 Nov 2019

Just by itself, with docker-machine create -d kvm2 default

dacruz21 on 6 Nov 2019

It is quite probable that docker-machine-driver-kvm2 does not work well outside of minikube, as it is effectively untested in that configuration. PR's to address this are welcome though!

tstromberg on 6 Nov 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 4 Feb 2020

I'm also seeing this exact error, running latest docker-machine and kvm2 driver on manjaro.

jidar on 7 Feb 2020

👍1

Most likely you want to use the regular libvirt driver (not kvm2) when using docker-machine

https://github.com/dhiltgen/docker-machine-kvm

afbjorklund on 12 Feb 2020

👎2

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 13 Mar 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 12 Apr 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot on 12 Apr 2020

Consider supporting this as there are not other solutions in the community. The repository, https://github.com/dhiltgen/docker-machine-kvm is no longer releasing versions and no longer works.

/remove-lifecycle rotten
/reopen

darkn3rd on 13 Oct 2020

👍1

@darkn3rd: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

Consider supporting this as there are not other solutions in the community. The repository, https://github.com/dhiltgen/docker-machine-kvm is no longer releasing versions and no longer works.

/remove-lifecycle rotten
/reopen