This bug was fixed in the package libvirt - 1.0.0-0ubuntu4
---
libvirt (1.0.0-0ubuntu4) raring; urgency=low
* debian/patches/apparmor-allow-hugepages: update apparmor policies to
allow use of hugepages. (LP: #646468)
* debian/patches/vnc-socket.patch: If a vnc socket is in us
** Branch linked: lp:ubuntu/raring-proposed/libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069534
Title:
libvirt doesn't include *.vnc files with apparmor profiles
To manage notifications a
** Changed in: libvirt (Ubuntu)
Status: Triaged => In Progress
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069534
Title:
libvirt doesn't include *.vnc files with apparmor profiles
To manag
Per irc discussion, this should be done with a domain-specific rule
added through virt-aa-helper.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069534
Title:
libvirt doesn't include *.vnc files wit
After checking again, the XML file (/etc/libvirt/qemu/laranja.fritz.box.xml)
contains (snipped):
a virsh dumpxml produces after the vm is started (snipped):
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I will try to investigate what happened that the socket path was used
instead of listen (maybe in one of the debugging attempts, I did not
supply the listen parameter ?). I'm sorry to not be able to provide an
immediate answer on this one since I can't reach my test system at the
moment since I'm c
Thanks for that info.
Your dumpxml output shows
but when I reproduce your command exactly I get the normal
Do you know how you ended up with the vnc socket defined?
If it was done by hand, then I'd prefer to say that you should also add
the socket file to the apparmor profile by hand.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069534
Title:
libvirt doesn't include *.vnc files with apparmor profiles
To manage no
The command line used was :
virt-install -n laranja.fritz.box -r 512 --os-variant=ubuntuprecise --disk
/home/vms/disk_laranja_root.img,device=disk,bus=virtio,size=8,sparse=true,format=raw
-w bridge=vms,model=virtio --graphics vnc,listen=0.0.0.0,password=qwerty
--location=http://de.archive.ubun
Thanks for reproring this bug.
Could you please give the full exact vmbuildder command you are using?
I'll try to reproduce.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
11 matches
Mail list logo
