Re: [Xen-devel] [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling

[Michal Novotny <minovotn@xxxxxxxxxx>]

On 06/07/2010 06:12 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 07, 2010 at 03:36:44PM +0200, Michal Novotny wrote:
>    
> > Well,
> > it doesn't seem to be that easy because I can't boot any of the guests.
> > No matter whether HVM or PV.
> >
> > For PV it's connected with the hotplugging:
> >
> > # xm create rhel5-32pv
> > Using config file "./rhel5-32pv".
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> >      
> Make sure you have your tun module loaded (yeah, no need for it, but the
> qemu-ifup might be touch it). Also you can take a look at
> /var/log/xen/xen-hotplug to see what the error is.
>
>    
> > For HVM guests it's:
> >      
> .. snip..
>    
> > # xm create rhel5-32fv
> > Using config file "./rhel5-32fv".
> > Error: Not enough memory is available, and dom0 cannot be shrunk any further
> >      
> Try xm mem-set 0 2048 before the start and see if that makes it work.
>    
Well, now it changed to:

# xenstored
 FATAL: Failed to initialize dom0 state: Invalid argument

what does it mean and how to fix it?

Michal

--
Michal Novotny<minovotn@xxxxxxxxxx>, RHCE
Virtualization Team (xen userspace), Red Hat


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel