| 2016-12-16 15:46:21 |
Patrick Nawracay |
bug |
|
|
added bug |
| 2016-12-16 15:46:21 |
Patrick Nawracay |
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 |
|
| 2016-12-16 15:46:56 |
Patrick Nawracay |
attachment added |
|
dmesg.log https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1650593/+attachment/4792389/+files/dmesg.log |
|
| 2016-12-16 15:47:12 |
Patrick Nawracay |
attachment added |
|
proc_cpuinfo.log https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1650593/+attachment/4792390/+files/proc_cpuinfo.log |
|
| 2016-12-16 15:47:25 |
Patrick Nawracay |
attachment added |
|
proc_version_signature.log https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1650593/+attachment/4792391/+files/proc_version_signature.log |
|
| 2016-12-16 15:47:40 |
Patrick Nawracay |
attachment added |
|
uname-a.log https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1650593/+attachment/4792392/+files/uname-a.log |
|
| 2016-12-16 15:49:24 |
Patrick Nawracay |
description |
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. |
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. |
|
