I just installed the lucid's kernel.
I've got the following traceback when trying to launch a VM :
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest: open /dev/kvm: Permission
denied
Could not initialize KVM, will disable KVM support
qemu: could not open disk image
/home/fabiena/kvm/libvirt-image/obm23-lenny.qcow2
Then I changed permissions of /dev/kvm from
crw-rw----+ 1 root kvm 10
to
crw-rw----+ 1 root libvirtd 10
and I got the following error :
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest: qemu: could not open disk
image /home/fabiena/kvm/libvirt-image/obm23-lenny.qcow2
$ ls -l /home/fabiena/kvm/libvirt-image/obm23-lenny.qcow2-rw-r--r-- 1
root root 1009516544 2010-01-05 18:01 /home/fabiena/kvm/libvirt-
image/obm23-lenny.qcow2
The owner and group of this file have been changed (by libvirt ?) when I
tried to run the VM.
Then I tried this :
$ sudo /etc/init.d/libvirt-bin restart
And now I can run the VM and it uses VT !
Thanks for your information !
----
So it seems that there are 2 troubles :
- the group of /dev/kvm : I have to check how this group is set (maybe it's one
of my script)
- the restart of libvirt-bin daemon : does everyone have to do this or is it a
trouble of my environment ?
--
[PPA] VT is not used with libvirt 0.7.5
https://bugs.launchpad.net/bugs/503376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
