You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Rajesh Battala <ra...@citrix.com> on 2013/05/21 10:22:54 UTC
Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Hi All,
When SystemVM's are coming up in KVM, they are getting shutoff with error.
What could be reason to mark the VM as tainted.
Libvirt.log:
=====
2013-05-04 07:03:54.035+0000: 26209: warning : qemuDomainObjTaint:1297 : Domain id=2 name='r-6-VM' uuid=5b34a307-7433-3ae8-b172-87a5668e193b is tainted: high-privileges
r-6-vm.log: (guest log)
==================
2013-05-04 07:03:54.034+0000: starting up
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.3.0 -enable-kvm -m 128 -smp 1,sockets=1,cores=1,threads=1 -name r-6-VM -uuid 5b34a307-7433-3ae8-b172-87a5668e193b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/r-6-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/5b1702c1-ddb8-4ed3-b24b-ed1bea5ec300,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:4c:23:00:02,bus=pci.0,addr=0x3 -netdev tap,fd=30,id=hostnet1,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=0e:00:a9:fe:01:04,bus=pci.0,addr=0x4 -netdev tap,fd=32,id=hostnet2,vhost=on,vhostfd=33 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:c5:2c:00:00:3f,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-6-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-6-VM.vport -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
Domain id=2 is tainted: high-privileges
char device redirected to /dev/pts/1
qemu: terminating on signal 15 from pid 26206
2013-05-04 13:57:11.189+0000: shutting down
Cloudstackagent err:
libvir: QEMU error : Domain not found: no domain with matching uuid '5b34a307-7433-3ae8-b172-87a5668e193b'
Thanks
Rajesh Battala
Re: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Marcus Sorensen <sh...@gmail.com>.
Actually, the issue is right here. Sorry, I was on my phone earlier
and didn't parse the whole log.
qemu: terminating on signal 15 from pid 26206
2013-05-04 13:57:11.189+0000: shutting down
So the reason it won't start is most likely because cloudstack is
starting it and shutting it down.
On Tue, May 21, 2013 at 5:43 AM, Marcus Sorensen <sh...@gmail.com> wrote:
> Those were just examples of things it could say. My point was that the
> individual VM log will tell why it didn't start.
>
> On Tue, May 21, 2013 at 5:24 AM, Rajesh Battala
> <ra...@citrix.com> wrote:
>> Apparmor is not installed . Selinux is in permissive mode. I think it's not the problem with Selinux
>>
>>> -----Original Message-----
>>> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>>> Sent: Tuesday, May 21, 2013 4:15 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: Unable to start System VM's in KVM Failing with error Domain is
>>> Tainted with high-privilages
>>>
>>> The tainted message means nothing. Look at /var/log/libvirtd/qemu/v-2-
>>> VM.log. it might say permission denied to the VM image, vm image missing,
>>> or that apparmor/selinux is blocking access to the virtio serial socket, or
>>> something else.
>>> On May 21, 2013 3:31 AM, "Rajesh Battala" <ra...@citrix.com>
>>> wrote:
>>>
>>> > From the log,
>>> >
>>> > libvirt version: 0.9.10 and it's is from package: 21.el6
>>> > x86-003.build.bos.redhat.com)
>>> >
>>> > Thanks
>>> > Rajesh Battala
>>> > > -----Original Message-----
>>> > > From: Prasanna Santhanam [mailto:tsp@apache.org]
>>> > > Sent: Tuesday, May 21, 2013 2:56 PM
>>> > > To: dev@cloudstack.apache.org
>>> > > Subject: Re: Unable to start System VM's in KVM Failing with error
>>> > Domain is
>>> > > Tainted with high-privilages
>>> > >
>>> > > On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
>>> > > > This issue I saw while looking at the logs for the issue
>>> > > https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation]
>>> > > Failed to deploy VR in KVM].
>>> > > >
>>> > > > Build/Code is from the latest master branch. Latest system
>>> > > > templates
>>> > are
>>> > > used.
>>> > > All the domains are failing on these hosts. So it seems like an
>>> > environment
>>> > > problem because my KVM hosts are able to spin up VMs fine on master.
>>> > >
>>> > > 2013-05-04 07:12:02.584+0000: 26210: warning :
>>> qemuDomainObjTaint:1297 :
>>> > > Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-
>>> 9bbff40e0d14
>>> > > is tainted: high-privileges
>>> > > 2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 :
>>> > > internal error End of file from monitor
>>> > >
>>> > > ^ The real error is the monitor EOF.
>>> > >
>>> > > More googling reveals this is a possible race condition in libvirt:
>>> > > https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
>>> > >
>>> > > But I'm not sure if that's what's happening here. Someone with more
>>> > > libvirt/qemu expertise will have to look at this. :(
>>> > >
>>> > > Can the bug report be updated with the version of libvirt? The line
>>> > numbers
>>> > > don't match up for the qemuMonitorIO method in the error log.
>>> > >
>>> > > I'd follow up on the #virt channel too to see if there's anyone who
>>> > knows.
>>> > >
>>> > > ------------------------
>>> > > Powered by BigRock.com
>>> >
>>> >
Re: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Marcus Sorensen <sh...@gmail.com>.
Those were just examples of things it could say. My point was that the
individual VM log will tell why it didn't start.
On Tue, May 21, 2013 at 5:24 AM, Rajesh Battala
<ra...@citrix.com> wrote:
> Apparmor is not installed . Selinux is in permissive mode. I think it's not the problem with Selinux
>
>> -----Original Message-----
>> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>> Sent: Tuesday, May 21, 2013 4:15 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: Unable to start System VM's in KVM Failing with error Domain is
>> Tainted with high-privilages
>>
>> The tainted message means nothing. Look at /var/log/libvirtd/qemu/v-2-
>> VM.log. it might say permission denied to the VM image, vm image missing,
>> or that apparmor/selinux is blocking access to the virtio serial socket, or
>> something else.
>> On May 21, 2013 3:31 AM, "Rajesh Battala" <ra...@citrix.com>
>> wrote:
>>
>> > From the log,
>> >
>> > libvirt version: 0.9.10 and it's is from package: 21.el6
>> > x86-003.build.bos.redhat.com)
>> >
>> > Thanks
>> > Rajesh Battala
>> > > -----Original Message-----
>> > > From: Prasanna Santhanam [mailto:tsp@apache.org]
>> > > Sent: Tuesday, May 21, 2013 2:56 PM
>> > > To: dev@cloudstack.apache.org
>> > > Subject: Re: Unable to start System VM's in KVM Failing with error
>> > Domain is
>> > > Tainted with high-privilages
>> > >
>> > > On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
>> > > > This issue I saw while looking at the logs for the issue
>> > > https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation]
>> > > Failed to deploy VR in KVM].
>> > > >
>> > > > Build/Code is from the latest master branch. Latest system
>> > > > templates
>> > are
>> > > used.
>> > > All the domains are failing on these hosts. So it seems like an
>> > environment
>> > > problem because my KVM hosts are able to spin up VMs fine on master.
>> > >
>> > > 2013-05-04 07:12:02.584+0000: 26210: warning :
>> qemuDomainObjTaint:1297 :
>> > > Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-
>> 9bbff40e0d14
>> > > is tainted: high-privileges
>> > > 2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 :
>> > > internal error End of file from monitor
>> > >
>> > > ^ The real error is the monitor EOF.
>> > >
>> > > More googling reveals this is a possible race condition in libvirt:
>> > > https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
>> > >
>> > > But I'm not sure if that's what's happening here. Someone with more
>> > > libvirt/qemu expertise will have to look at this. :(
>> > >
>> > > Can the bug report be updated with the version of libvirt? The line
>> > numbers
>> > > don't match up for the qemuMonitorIO method in the error log.
>> > >
>> > > I'd follow up on the #virt channel too to see if there's anyone who
>> > knows.
>> > >
>> > > ------------------------
>> > > Powered by BigRock.com
>> >
>> >
RE: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Rajesh Battala <ra...@citrix.com>.
Apparmor is not installed . Selinux is in permissive mode. I think it's not the problem with Selinux
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Tuesday, May 21, 2013 4:15 PM
> To: dev@cloudstack.apache.org
> Subject: RE: Unable to start System VM's in KVM Failing with error Domain is
> Tainted with high-privilages
>
> The tainted message means nothing. Look at /var/log/libvirtd/qemu/v-2-
> VM.log. it might say permission denied to the VM image, vm image missing,
> or that apparmor/selinux is blocking access to the virtio serial socket, or
> something else.
> On May 21, 2013 3:31 AM, "Rajesh Battala" <ra...@citrix.com>
> wrote:
>
> > From the log,
> >
> > libvirt version: 0.9.10 and it's is from package: 21.el6
> > x86-003.build.bos.redhat.com)
> >
> > Thanks
> > Rajesh Battala
> > > -----Original Message-----
> > > From: Prasanna Santhanam [mailto:tsp@apache.org]
> > > Sent: Tuesday, May 21, 2013 2:56 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Unable to start System VM's in KVM Failing with error
> > Domain is
> > > Tainted with high-privilages
> > >
> > > On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
> > > > This issue I saw while looking at the logs for the issue
> > > https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation]
> > > Failed to deploy VR in KVM].
> > > >
> > > > Build/Code is from the latest master branch. Latest system
> > > > templates
> > are
> > > used.
> > > All the domains are failing on these hosts. So it seems like an
> > environment
> > > problem because my KVM hosts are able to spin up VMs fine on master.
> > >
> > > 2013-05-04 07:12:02.584+0000: 26210: warning :
> qemuDomainObjTaint:1297 :
> > > Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-
> 9bbff40e0d14
> > > is tainted: high-privileges
> > > 2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 :
> > > internal error End of file from monitor
> > >
> > > ^ The real error is the monitor EOF.
> > >
> > > More googling reveals this is a possible race condition in libvirt:
> > > https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
> > >
> > > But I'm not sure if that's what's happening here. Someone with more
> > > libvirt/qemu expertise will have to look at this. :(
> > >
> > > Can the bug report be updated with the version of libvirt? The line
> > numbers
> > > don't match up for the qemuMonitorIO method in the error log.
> > >
> > > I'd follow up on the #virt channel too to see if there's anyone who
> > knows.
> > >
> > > ------------------------
> > > Powered by BigRock.com
> >
> >
RE: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Marcus Sorensen <sh...@gmail.com>.
The tainted message means nothing. Look at
/var/log/libvirtd/qemu/v-2-VM.log. it might say permission denied to the VM
image, vm image missing, or that apparmor/selinux is blocking access to the
virtio serial socket, or something else.
On May 21, 2013 3:31 AM, "Rajesh Battala" <ra...@citrix.com> wrote:
> From the log,
>
> libvirt version: 0.9.10 and it's is from package: 21.el6
> x86-003.build.bos.redhat.com)
>
> Thanks
> Rajesh Battala
> > -----Original Message-----
> > From: Prasanna Santhanam [mailto:tsp@apache.org]
> > Sent: Tuesday, May 21, 2013 2:56 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Unable to start System VM's in KVM Failing with error
> Domain is
> > Tainted with high-privilages
> >
> > On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
> > > This issue I saw while looking at the logs for the issue
> > https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation]
> > Failed to deploy VR in KVM].
> > >
> > > Build/Code is from the latest master branch. Latest system templates
> are
> > used.
> > All the domains are failing on these hosts. So it seems like an
> environment
> > problem because my KVM hosts are able to spin up VMs fine on master.
> >
> > 2013-05-04 07:12:02.584+0000: 26210: warning : qemuDomainObjTaint:1297 :
> > Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-9bbff40e0d14
> > is tainted: high-privileges
> > 2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 : internal
> > error End of file from monitor
> >
> > ^ The real error is the monitor EOF.
> >
> > More googling reveals this is a possible race condition in libvirt:
> > https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
> >
> > But I'm not sure if that's what's happening here. Someone with more
> > libvirt/qemu expertise will have to look at this. :(
> >
> > Can the bug report be updated with the version of libvirt? The line
> numbers
> > don't match up for the qemuMonitorIO method in the error log.
> >
> > I'd follow up on the #virt channel too to see if there's anyone who
> knows.
> >
> > ------------------------
> > Powered by BigRock.com
>
>
RE: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Rajesh Battala <ra...@citrix.com>.
>From the log,
libvirt version: 0.9.10 and it's is from package: 21.el6 x86-003.build.bos.redhat.com)
Thanks
Rajesh Battala
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: Tuesday, May 21, 2013 2:56 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Unable to start System VM's in KVM Failing with error Domain is
> Tainted with high-privilages
>
> On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
> > This issue I saw while looking at the logs for the issue
> https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation]
> Failed to deploy VR in KVM].
> >
> > Build/Code is from the latest master branch. Latest system templates are
> used.
> All the domains are failing on these hosts. So it seems like an environment
> problem because my KVM hosts are able to spin up VMs fine on master.
>
> 2013-05-04 07:12:02.584+0000: 26210: warning : qemuDomainObjTaint:1297 :
> Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-9bbff40e0d14
> is tainted: high-privileges
> 2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 : internal
> error End of file from monitor
>
> ^ The real error is the monitor EOF.
>
> More googling reveals this is a possible race condition in libvirt:
> https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
>
> But I'm not sure if that's what's happening here. Someone with more
> libvirt/qemu expertise will have to look at this. :(
>
> Can the bug report be updated with the version of libvirt? The line numbers
> don't match up for the qemuMonitorIO method in the error log.
>
> I'd follow up on the #virt channel too to see if there's anyone who knows.
>
> ------------------------
> Powered by BigRock.com
Re: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Prasanna Santhanam <ts...@apache.org>.
On Tue, May 21, 2013 at 08:55:23AM +0000, Rajesh Battala wrote:
> This issue I saw while looking at the logs for the issue https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation] Failed to deploy VR in KVM].
>
> Build/Code is from the latest master branch. Latest system templates are used.
All the domains are failing on these hosts. So it seems like an
environment problem because my KVM hosts are able to spin up VMs fine
on master.
2013-05-04 07:12:02.584+0000: 26210: warning : qemuDomainObjTaint:1297 : Domain id=7 name='v-2-VM' uuid=1422832d-be18-352a-a08a-9bbff40e0d14 is tainted: high-privileges
2013-05-04 07:13:36.851+0000: 26206: error : qemuMonitorIO:574 : internal error End of file from monitor
^ The real error is the monitor EOF.
More googling reveals this is a possible race condition in libvirt:
https://www.redhat.com/archives/libvir-list/2013-March/msg00051.html
But I'm not sure if that's what's happening here. Someone with more
libvirt/qemu expertise will have to look at this. :(
Can the bug report be updated with the version of libvirt? The line
numbers don't match up for the qemuMonitorIO method in the error log.
I'd follow up on the #virt channel too to see if there's anyone who
knows.
------------------------
Powered by BigRock.com
RE: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Rajesh Battala <ra...@citrix.com>.
This issue I saw while looking at the logs for the issue https://issues.apache.org/jira/browse/CLOUDSTACK-2330 [[Automation] Failed to deploy VR in KVM].
Build/Code is from the latest master branch. Latest system templates are used.
Thanks
Rajesh Battala
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: Tuesday, May 21, 2013 2:10 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Unable to start System VM's in KVM Failing with error Domain is
> Tainted with high-privilages
>
> On Tue, May 21, 2013 at 08:22:54AM +0000, Rajesh Battala wrote:
> > Hi All,
> >
> > When SystemVM's are coming up in KVM, they are getting shutoff with
> > error.
> >
> > What could be reason to mark the VM as tainted.
> If we do custom qemu options, apparently -
> https://www.berrange.com/tags/tainting/
>
>
> > Libvirt.log:
> > =====
> > 2013-05-04 07:03:54.035+0000: 26209: warning :
> > qemuDomainObjTaint:1297 : Domain id=2 name='r-6-VM'
> > uuid=5b34a307-7433-3ae8-b172-87a5668e193b is tainted:
> > high-privileges
>
> What's in the libvirt log below these warnings?
>
> >
> >
> > r-6-vm.log: (guest log)
> > ==================
> > 2013-05-04 07:03:54.034+0000: starting up
> > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none
> /usr/libexec/qemu-kvm -S -M rhel6.3.0 -enable-kvm -m 128 -smp
> 1,sockets=1,cores=1,threads=1 -name r-6-VM -uuid 5b34a307-7433-3ae8-
> b172-87a5668e193b -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/r-6-
> VM.monitor,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-
> pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/fff90cb5-06dd-33b3-
> 8815-d78c08ca01d9/5b1702c1-ddb8-4ed3-b24b-
> ed1bea5ec300,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -
> device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-
> disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-
> common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-
> 0,readonly=on,format=raw,cache=none -device ide-
> drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev
> tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-
> pci,netdev=hostnet0,id=net0,mac=02:00:4c:23:00:02,bus=pci.0,addr=0x3 -
> netdev tap,fd=30,id=hostnet1,vhost=on,vhostfd=31 -device virtio-net-
> pci,netdev=hostnet1,id=net1,mac=0e:00:a9:fe:01:04,bus=pci.0,addr=0x4 -
> netdev tap,fd=32,id=hostnet2,vhost=on,vhostfd=33 -device virtio-net-
> pci,netdev=hostnet2,id=net2,mac=06:c5:2c:00:00:3f,bus=pci.0,addr=0x5 -
> chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -
> chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-6-
> VM.agent,server,nowait -device virtserialport,bus=virtio-
> serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-6-VM.vport -device
> usb-tablet,id=input0 -vnc 0.0.0.0:1 -vga cirrus -device virtio-balloon-
> pci,id=balloon0,bus=pci.0,addr=0x8
> > Domain id=2 is tainted: high-privileges
> > char device redirected to /dev/pts/1
> > qemu: terminating on signal 15 from pid 26206
> > 2013-05-04 13:57:11.189+0000: shutting down
> >
> Does it happen only with routers?
>
> Sounds like you should file a bug with details like:
> 1. are you using the latest systemvm templates?
> 2. which branch you are facing this on? master?
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
Re: Unable to start System VM's in KVM Failing with error Domain is
Tainted with high-privilages
Posted by Prasanna Santhanam <ts...@apache.org>.
On Tue, May 21, 2013 at 08:22:54AM +0000, Rajesh Battala wrote:
> Hi All,
>
> When SystemVM's are coming up in KVM, they are getting shutoff with
> error.
>
> What could be reason to mark the VM as tainted.
If we do custom qemu options, apparently -
https://www.berrange.com/tags/tainting/
> Libvirt.log:
> =====
> 2013-05-04 07:03:54.035+0000: 26209: warning :
> qemuDomainObjTaint:1297 : Domain id=2 name='r-6-VM'
> uuid=5b34a307-7433-3ae8-b172-87a5668e193b is tainted:
> high-privileges
What's in the libvirt log below these warnings?
>
>
> r-6-vm.log: (guest log)
> ==================
> 2013-05-04 07:03:54.034+0000: starting up
> LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.3.0 -enable-kvm -m 128 -smp 1,sockets=1,cores=1,threads=1 -name r-6-VM -uuid 5b34a307-7433-3ae8-b172-87a5668e193b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/r-6-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/5b1702c1-ddb8-4ed3-b24b-ed1bea5ec300,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:4c:23:00:02,bus=pci.0,addr=0x3 -netdev tap,fd=30,id=hostnet1,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=0e:00:a9:fe:01:04,bus=pci.0,addr=0x4 -netdev tap,fd=32,id=hostnet2,vhost=on,vhostfd=33 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:c5:2c:00:00:3f,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-6-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-6-VM.vport -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
> Domain id=2 is tainted: high-privileges
> char device redirected to /dev/pts/1
> qemu: terminating on signal 15 from pid 26206
> 2013-05-04 13:57:11.189+0000: shutting down
>
Does it happen only with routers?
Sounds like you should file a bug with details like:
1. are you using the latest systemvm templates?
2. which branch you are facing this on? master?
--
Prasanna.,
------------------------
Powered by BigRock.com