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 <rajesh.batt...@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:shadow...@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" <rajesh.batt...@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:t...@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 >> > >> >
