[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handle

>>> On 02.12.13 at 10:58, "Luke S. Crawford" <lsc@xxxxxxxxx> wrote:
> On 12/02/2013 12:34 AM, Jan Beulich wrote:
>> The thing is that a guest admin may not have access to the VM's
>> config file, i.e. a satisfactory solution ought to involve only guest
>> side actions.
> A service provider who allows customers to run their own kernel would 
> see it the other way around.

And I didn't say that might not also need taking care of, but I'm in
no way convinced that's necessary:

> That is the situation I find myself in.
> I don't have access to my guest's config files.   Something I can do as 
> the manager of the dom0 to ameliorate the problem without requiting the 
> customers to do anything, and without requiring me to break into the 
> guest and figure out how to patch whatever random kernel they might be 
> using would help me a lot.

If you're the manager of the Dom0, how can you not have access
to your guests' config files?

And it surely isn't the responsibility of the Dom0 admin to take care
of broken guest kernels. That's solely the guest admin's job.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.