On the eucalyptus NC, when we try to start a VM, the process is unable
to do so with the following error being thrown by libvirt (reported in
nc.log):
libvirt: monitor socket did not show up.: Connection refused (code=38)
[Thu Dec 23 13:08:58 2010][002757][EUCAFATAL ] hypervisor failed to start
Can you thoroughly test libvirt 0.7.0-1ubuntu8 with eucalyptus? I fixed
this bug properly along with attach and detach of devices and disks
(using Jaunty kvm as you mentioned in bug #432154). Please make sure
that the workaround rules in /etc/apparmor.d/abstractions/libvirt-qemu
are no longer
This bug was fixed in the package libvirt - 0.7.0-1ubuntu6
---
libvirt (0.7.0-1ubuntu6) karmic; urgency=low
* debian/apparmor/libvirt-qemu: workaround eucalyptus serial console,
kernel and initrd location. This should be removed after virt-aa-helper is
able to get these
I am going to provide a eucalyptus specific workaround in my next
libvirt upload, to get this the serial, kernel and initrd working.
How are you using attach-disk/detach-disk? I can't seem to get them
working here to test this.
** Package changed: eucalyptus (Ubuntu) = libvirt (Ubuntu)
**
There is another bug, in KVM i suspect, that is preventing
attach/detach of block devices from fully working, however, you can see
some progress (logs indicating activity on the scsi bus in the VM when
you do an attach/detach):
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/432154
--
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
libvirt apparmor profile is preventing libvirt from running
** Changed in: eucalyptus (Ubuntu)
Milestone: None = ubuntu-9.10-beta
--
libvirt apparmor profile is preventing libvirt from running eucalyptus VMs
https://bugs.launchpad.net/bugs/431090
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Daniel, can you please give the output of:
$ dmesg | grep audit
Also, can you give me the paths to the pid file, log file and monitor
file for this virtual machine?
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Incomplete
--
libvirt apparmor profile is preventing libvirt from
Daniel, also can you add the following to /etc/apparmor.d/abstractions
/libvirt-qemu and let me know if it fixes it for you?
/var/lib/eucalyptus/instances/**/console.log w,
--
libvirt apparmor profile is preventing libvirt from running eucalyptus VMs
https://bugs.launchpad.net/bugs/431090
You
Daniel, one last thing (sorry for the multiple requests), can you also give me
the xml for this virtual machine:
$ virsh dumpxml i-4CFC08E8
--
libvirt apparmor profile is preventing libvirt from running eucalyptus VMs
https://bugs.launchpad.net/bugs/431090
You received this bug notification
Jamie, thank you for taking a look here. First, after your response,
I've been able to modify /etc/apparmor.d/abstractions/libvirt-qemu with
the following:
/var/lib/eucalyptus/instances/**/console.log w,
/var/lib/eucalyptus/instances/**/kernel r,
/var/lib/eucalyptus/instances/**/ramdisk
I've found one more runtime issue with the apparmor profile. Eucalyptus
can provide the ability to dynamically attach/detach block devices to
VMs at runtime using libvirt attach-disk/detach-disk. We currently use
AOE for dynamic block devices, and these appear on the node in:
/dev/etherd/e*
12 matches
Mail list logo
