[Users] oVirt 3.1 - VM Migration Issue

Dan Kenigsberg danken at redhat.com
Wed Jan 9 11:20:02 EST 2013


On Wed, Jan 09, 2013 at 09:05:37AM -0500, Simon Grinberg wrote:
> 
> 
> ----- Original Message -----
> > From: "Dan Kenigsberg" <danken at redhat.com>
> > To: "Tom Brown" <tom at ng23.net>
> > Cc: "Simon Grinberg" <sgrinber at redhat.com>, users at ovirt.org
> > Sent: Wednesday, January 9, 2013 2:11:14 PM
> > Subject: Re: [Users] oVirt 3.1 - VM Migration Issue
> > 
> > On Wed, Jan 09, 2013 at 10:06:12AM +0000, Tom Brown wrote:
> > > 
> > > 
> > > >> libvirtError: internal error Process exited while reading
> > > >> console log outpu
> > > > could this be related to selinux? can you try disabling it and
> > > > see if migration succeeds?
> > > 
> > > It was indeed the case! my src node was set to disabled and my
> > > destination node was enforcing, this was due to the destination
> > > being the first HV built and therefore provisioned slightly
> > > differently, my kickstart server is a VM in the pool.
> > > 
> > > Its interesting that a VM can be provisioned onto a node that is
> > > set to enforcing and yet not migrated to.
> > 
> > I have (only a vague) memory of discussing this already...
> > Shouldn't oVirt-Engine be aware of selinux enforcement? If a cluster
> > has
> > disabled hosts, an enforcing host should not be operational (or at
> > least
> > warn the admin about that).
> 
> 
> I recall something like that, but I don't recall we ever converged and can't find the thread

What is your opinion on the subject?

I think that at the least, the scheduler must be aware of selinux
enforcement when it chooses migration destination.


More information about the Users mailing list