Ok, I know what is failing, but I don't know why.
On amd64 things are ok:
$ cat /proc/cpuinfo | grep model
model : 37
model name : Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz
... repeated 4 times ...
$ dpkg --print-architecture
amd64
$ uname -m
x86_64
$ cat ./628055.xml |
Ok, I am able to reproduce this on a pure i386 machine using the disk as
setup by eucalyptus. My tests before were not identical. Here are the
results:
== amd64 ==
$ ./628055.sh
$ cat /proc/cpuinfo | grep model
model : 37
model name : Intel(R) Core(TM) i7 CPU L 640 @
Here is the problem: stat() is returning with error in virFileExists()
on 32 bit when we use it on the disk image. Ie:
$ ls -l /home/jamie/tmp/628055/disk
-rw-r--r-- 1 jamie jamie 2179989504 2010-09-22 08:57 /home/jamie/tmp/628055/disk
== amd64 ==
$ a.out /home/jamie/tmp/628055/disk
Turns out this was a missing #include in virt-aa-helper.c. In previous
releases we did not need '#include sys/stat.h', but in libvirt 0.8.3
(presumably because of its embedded gnulib, which has functions for
stat()) and the toolchain in maverick, we do.
Specifically, virt-aa-helper.c has in its
On a i386 test upgrade from 10.04 to Maverick I also got this error. All
instances fail to start. Full logs at lp:~hggdh2/+junk/uec-qa, revision
61.
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this
Disabled apparmor, I don't get the error message anymore. But I fall on
another bug (VM doesn't seem to boot correctly) afterwards, so difficult
to say everything works just fine. I'll try to test livirt/qemu/kvm
outside eucalyptus to debug this.
--
Instances don't start correctly: Security
That is what I thought might be the case. If the VM dies a horrible
death then apparmor has no process to attach to when changing profile. I
am going to unassign this from me until is is determined the AppArmor
security driver is the problem.
** Changed in: libvirt (Ubuntu Maverick)
Hi. Sorry but currently I'm not able to provide my domain.xml (however
will do as soon as I find the time). But I would like to say that I'm
not using eucalyptus and all my VMs work fine without apparmor.
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
I can reproduce it again on a daily UEC/i386:
- grep DENIED /var/log/kern.log doesn't yield anything
- See attached virsh capabilities output on the NC
** Attachment added: capabilities
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/628055/+attachment/1588196/+files/capabilities
--
@Andrea, are you running on i386 or amd64 ?
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
Thierry, what type of CPU did you use to reproduce this? Can you post
the domain xml for the affected guest?
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because you are a member
It's an Intel(R) Core(TM)2 Duo CPU T6670, running an i386 server
install, trying to run an i386 instance.
I don't have a domain.xml, euca must be destroying it on error, or it
never gets created. Same machine running an amd64 server install, trying
to run an i386 instance, works perfectly. That's
Can you disable the AppArmor driver and see if it works there? This can be done
by adjusting /etc/libvirt/qemu.conf to have:
security_driver = none
Then restart libvirt-bin with:
$ sudo stop libvirt-bin
$ sudo start libvirt-bin
Verify the AppArmor driver is disabled with (don't worry if it
This error is a generic error that is unfortunately not informative and not
necessarily indicative of an AppArmor problem. Can you post the output of:
$ virsh capabilities
$ grep DENIED /var/log/kern.log
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
Also, the restart of libvirt could have been enough to 'fix' the issue,
and not be a problem with AppArmor. That said, I need the kern.log
output to determine if it is AppArmor or not.
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
Andrea, the virsh capabilities output does not list apparmor as a
capability. Are you saying that it doesn't work with apparmor disabled
as well?
** Changed in: libvirt (Ubuntu Maverick)
Status: Confirmed = Incomplete
** Changed in: libvirt (Ubuntu Maverick)
Status: Incomplete =
Oops, sorry! I ran virsh capabilities after disabling apparmor.
So, to clarify: with AppArmor, every attempt to use a virtual machine
fails; without it, everything works perfectly.
** Attachment added: virsh-capabilities-with-apparmor
I can't reproduce this with libvirt (I don't have eucalyptus available
for testing). That said, looking at the capabilities, I see in the
guest:
domain type='qemu'
/domain
domain type='kvm'
emulator/usr/bin/kvm/emulator
machinepc-0.12/machine
machine
Actually, the two domains in the virsh capabilties seems to be normal (I
see it here). Please still post the domain xml for the affected guest
however.
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received
Tentatively assigned to Jamie, so that he can check if this is a recent
profile confinement issue...
** Changed in: libvirt (Ubuntu Maverick)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: libvirt (Ubuntu Maverick)
Probably not eucalyptus-specific.
** Changed in: eucalyptus (Ubuntu Maverick)
Status: New = Invalid
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because you are a member
I see this bug too, but I don't think the problem is in eucalyptus: I'm
using qemu+kvm+libvirt.
Whenever I try to start any of my virtual machines (that just some days
ago in Lucid worked fine) I get this error:
# virsh -c qemu:///system start abc
error: Failed to start domain abc
error:
** Summary changed:
- Instances don't go to running state: Security Labeling error running
aa_change_profile()
+ Instances don't start correctly: Security Labeling error running
aa_change_profile()
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: New
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because you are a member of Ubuntu
Server Team,
@Thierry: When you were able to reproduce this, was it encountered
shortly after boot? I noticed eucalyptus-cloud being a resource hog,
that tends to settle down. This could indicate why it's inconsistent?
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
** Tags added: server-mrs
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) = Dave Walker (davewalker)
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because
That was not shortly, but like 15min after boot.
--
Instances don't start correctly: Security Labeling error running
aa_change_profile()
https://bugs.launchpad.net/bugs/628055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
27 matches
Mail list logo
