Workaround: https://github.com/virtio-win/kvm-guest-drivers-
windows/issues/177#issuecomment-717318013
** Bug watch added: github.com/virtio-win/kvm-guest-drivers-windows/issues #177
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/177
--
You received this bug notification
** Changed in: libvirt (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: virt-manager (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) =>
I can also reproduce this. I'm using Khadas VIM3 with amologic CPUs.
Ubuntu 20.04, kernel 5.7 and libvirt 6.0.0, qemu 4.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832395
Title:
"kvm_init_vcpu
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: virt-manager (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco
Below is content of /var/log/libvirt/qemu/instance-0007.log
Source of instance-0007 is second link in this comment:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/comments/9
(network device was removed, img file name was changed, everything else
is untouched)
2019-06-11
Below is content of /var/log/libvirt/qemu/instance-0007.log
Source of instance-0007 is second link in this comment:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/comments/9
(network device was removed, img file name was changed, everything else
is untouched)
2019-06-11
