Jamie,
sorry, I thought his latest comment mentioned that as a working
workaround, but I must have seen it in the description.
So yes, removing the tag seems good.
** Description changed:
I get the error:
Error starting domain: internal error Process exited while reading
console log ou
Serge, but comment #25 by Thomas said he is having the problem even with
AppArmor disabled...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with serial or cons
Quoting Jamie Strandboge (ja...@ubuntu.com):
> Based on Thomas' assessment, should the title of this bug be adjusted
> and the apparmor tag removed?
Since disabling apparmor works around the problem, I don't think so.
I'm going to have to install a maverick partition on a physical laptop to test
Based on Thomas' assessment, should the title of this bug be adjusted
and the apparmor tag removed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with serial o
The only real fix is not to use lxc/kvm on one hardware in parallel. As
long as you use *only* kvm/lxc you'll not see this error any more. This
is because most lxc-tools do not use libvirtd for operations.
At least with version 0.8.8-1ubuntu6.5 (available from the mainline
repositories) some othe
@Thomas,
could you tell us which testing ppa version of kvm fixes it? Do you
knwo which upstream commit fixes it? We should be able to push this fix
back into maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: libvirt (Ubuntu Maverick)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with serial or console when apparmor is
Looks like it is fixed with libvirt 0.8.8. Unfortunately this package is
only available from a testing ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with s
After a few further test, I am quite sure:
It is a conflict between lxc/kvm (at least in my case). Could you please
confirm kvm not allocating pty dynamicaly? As lxc not doing it
dynamicaly? Raising conflicts if kvm-guests where started, after them
lxc-guest are started, then kvm-guests are stoped
I see this error since today. Even stopping apparmor, then tearing down
all profiles, trying to start a kvm host gives:
root@vh01:~# service apparmor stop
* Clearing AppArmor profiles cache
[ OK ]
All profi
I've ran into this issue twice now today. I can be creating VMs just
fine and then go to create another one and it fails with this error.
Rebooting fixed the issue the first time and I was able to create VMs
again like normal but then for seemingly no reason I started getting the
error again.
--
I just began running into this after upgrading to Maverick
** Changed in: libvirt (Ubuntu Maverick)
Status: Invalid => New
--
libvirt won't start a VM with serial or console when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
You received this bug notification because you are
I have never been able to reproduce. I've certainly known libvirt to
right itself after a full reboot, so maybe something weird was going on.
Feel free to re-open if you can reproduce.
** Changed in: libvirt (Ubuntu Maverick)
Status: New => Invalid
** Changed in: libvirt (Ubuntu Maverick)
I've not been able to reproduce this since the ninth, so I'd like to mark
it invalid. Jamie, is that ok with you?
--
libvirt won't start a VM with serial or console when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
You received this bug notification because you are a member of Ubun
Quoting Jamie Strandboge (ja...@ubuntu.com):
> We can create a child profile for pt_chown so only it would get
> cap_fowner. Can you try the following in /etc/apparmor.d/abstractions
> /libvirt-qemu:
>
> owner @{PROC}/[0-9]*/fd/ r,
> owner @{PROC}/[0-9]*/fd/3 r,
> /usr/lib/pt_chown cix -> li
We can create a child profile for pt_chown so only it would get
cap_fowner. Can you try the following in /etc/apparmor.d/abstractions
/libvirt-qemu:
owner @{PROC}/[0-9]*/fd/ r,
owner @{PROC}/[0-9]*/fd/3 r,
/usr/lib/pt_chown cix -> libvirt_pt_chown,
profile libvirt_pt_chown {
capabilit
I chowned and chmoded /srv/libvirt-storage-pool-1 to be
se...@sergelap:~/ $ ls -ld /srv/libvirt-storage-pool-1/
drwxr-x--- 2 root kvm 4096 2010-09-03 09:45 /srv/libvirt-storage-pool-1/
and made sure to be in the kvm group, but this still did not suffice. The
errors
in the log are as usual:
[ 2
Fascinating, today the problem is back.
--
libvirt won't start a VM with serial or console when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Tags added: server-mrs
--
libvirt won't start a VM with serial or console when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
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.u
Quoting Jamie Strandboge (ja...@ubuntu.com):
> Serge, do you still have the following in your
> /etc/apparmor.d/abstractions/libvirt-qemu:
> /usr/lib/pt_chown ix,
> owner @{PROC}/[0-9]*/fd/ r,
> owner @{PROC}/[0-9]*/fd/3 r,
Right, I pulled those out since they weren't working anyway.
> I d
Serge, do you still have the following in your
/etc/apparmor.d/abstractions/libvirt-qemu:
/usr/lib/pt_chown ix,
owner @{PROC}/[0-9]*/fd/ r,
owner @{PROC}/[0-9]*/fd/3 r,
I didn't see it in your attached libvirt-qemu file either, so I am
slightly confused. Updating that file will require a fu
Quoting Jamie Strandboge (ja...@ubuntu.com):
> I cannot reproduce with the m2.xml file using qemu:///system on the
> local machine. I used virt-manager to create the /srv/libvirt-storage-
> pool-1/maverick2.img image (but I had to 'chmod 750 /srv/libvirt-
> storage-pool-1 ; chgrp kvm /srv/libvirt-s
I cannot reproduce with the m2.xml file using qemu:///system on the
local machine. I used virt-manager to create the /srv/libvirt-storage-
pool-1/maverick2.img image (but I had to 'chmod 750 /srv/libvirt-
storage-pool-1 ; chgrp kvm /srv/libvirt-storage-pool-1' to make this
work).
Can you provide e
** Attachment added: "libvirt-qemu"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/632696/+attachment/1555814/+files/libvirt-qemu
--
libvirt won't start a VM with serial or console when apparmor is enabled
https://bugs.launchpad.net/bugs/632696
You received this bug notification beca
Can you attach your /etc/apparmor.d/abstractions/libvirt-qemu file?
** Summary changed:
- libvirt won't start a VM when apparmor is enabled
+ libvirt won't start a VM with serial or console when apparmor is enabled
--
libvirt won't start a VM with serial or console when apparmor is enabled
http
25 matches
Mail list logo
