Public bug reported:
Issuing a `vagrant up` on the notebook I use results in a kernel panic,
when I use libvirt as provider for Vagrant.
Changing the CPU model from 'qemu64' (default) to 'kvm64' works, but has
to be configured in the Vagrantfile manually. The same problem occurs if
I start the VM using the virt-manager and without using Vagrant.
I don't have the same problem on another machine. It might be related to
the hardware I use on my notebook.
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "vagrant-libvirt-qemu-causes-kernel-panic.png"
https://bugs.launchpad.net/bugs/1650593/+attachment/4792388/+files/vagrant-libvirt-qemu-causes-kernel-panic.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650593
Title:
Kernel panic on `vagrant up` using `qemu64` CPU model
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1650593/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
