*** This bug is a duplicate of bug 1342083 ***
https://bugs.launchpad.net/bugs/1342083
Marking this as a dup of #1342083 (because this bug is probably both
valid, and due to the same cause).
** This bug has been marked a duplicate of bug 1342083
Failed to create chardev due to apparmor
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Oneiric)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Oneiric)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had a similar problem, but the cause turned out to be different for
me.
I had changed the GID of group tty from 5 to 11. I later found out that
this contravenes the Ubuntu standard GID policy.
The symptom was similar to the above
chardev: opening backend pty failed: Exec format error
It turns
I also had this behaviour on 12.10 (upgraded from 12.04)
virt-install was repeatedly not working
sudo virt-install --name=lin01 --ram 1024 --disk
path=/var/lib/libvirt/images/disk1.img,format=raw,bus=virtio,cache=none,size=2
--disk
This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached
end-of-life and is no longer supported, so I am closing the bug task for
Maverick. Please upgrade to a newer version of Ubuntu.
More information here:
https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html
Not only Maverik, Ubuntu 10.10, also later versions, as 11.04, 11.10, and
partly 12.04.
It is a variety of things triggering this bug:
- Apparmor
- Kernel-Version, kernel-release (maybe it is triggered by compiling modules in
different ways)
- libvirtd-version
- maybe even filesystem dependent
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Oneiric)
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
Serge,
sorry for the late answer, I wasn't subscribed to this bug before, I'll
answer more quickly in the future.
As for NFS - no NFS on this machine, and no console.log either. It seems
I was confusingly brief in my comment, I wasn't replying to Mandar
really, but to the original bug report.
Having the same issue in Ubuntu 11.10. What I don't get is that I still
see apparmor=DENIED errors in my kern.log even after doing
/etc/init.d/apparmor restart ; /etc/init.d/apparmor teardown
Maybe I'm missing something about how apparmor works, but I don't have
the time to find out right now. So
Hanno,
thanks for that info.
So booting with 'apparmor=0' stops the failure for you. Do you have the
console.log location as nfs mounted as Mandar did?
Can either Hanno or Mandar confirm that you have seen this on 12.04
precise?
** Also affects: libvirt (Ubuntu Oneiric)
Importance:
I'm facing similar problem in openstack/nova-compute context
We are using libvirt as default KVM to spawn the instances.
I faced the problem ONLY when the directory where it creates the console.log
was nfs mounted (Not local disk path)
Indeed I too have serial in the XML file -which is where the
** Tags added: apparmor
--
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
To manage notifications about this bug go to:
Seeing this in Oneiric stock, as well as Oneiric with libvirt etc. from
Precise.
Even tried ln -s /etc/apparmor.d/usr.sbin.libvirtd
/etc/apparmor.d/disabled to no avail.
Seems to focus on opening a fd and pt_chown'ing it:
Mar 19 16:03:51 jekaterina kernel: [ 2029.039478] type=1400
This bug seems to have slipped into libvirt-bin 0.9.2-4ubuntu15.2 for
Ubuntu 11.10 :-(
--
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
@Andrea,
were you saying that you've seen this happen on Precise?
--
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
To manage
The problem seems gone with libvirt-bin 0.9.2-4ubuntu15.1 (Ubuntu
11.10).
--
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
To manage
I've just encountered this bug today for the first time. The symptoms
are exactly the same: serial and console in the domain xml,
apparmor=DENIED messages in kern.log and a reboot fixed the problem.
I'd like to nominate this bug for Oneiric and Precise, however Launchpad
is OOPSing.
--
You
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
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start
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
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
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM
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
** Tags removed: apparmor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with serial or console
To manage notifications about this bug go
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
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
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
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
** Tags removed: apparmor
--
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
To manage notifications about this bug go to:
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
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
@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
Server Team, which is subscribed to libvirt in
@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.
** Changed in: libvirt (Ubuntu Maverick)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM with serial or console
** 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
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt
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
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
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
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
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'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'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
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
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)
** 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
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs
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
Server Team, which is subscribed to libvirt in ubuntu.
--
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:
[
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 {
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 -
** 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
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
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:
[
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 {
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 -
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
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
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 didn't
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
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
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
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 didn't
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
** 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
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
** 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
67 matches
Mail list logo
