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

[Michal Novotny <minovotn@redhat.com>]

On 06/07/2010 04:56 PM, Pasi Kärkkäinen 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.
>>
>>      
> Do you have correct bridge= specified for the vif? Does the bridge exist?
>
>
>    
Yeah, everything is specified like it was and the bridge exists.

>> For HVM guests it's:
>>
>> # xm create rhel5-32fv
>> Using config file "./rhel5-32fv".
>> Error: Not enough memory is available, and dom0 cannot be shrunk any further
>>
>>      
> Do you have dom0_mem=1024M for xen.gz in grub.conf ?
> You should limit/dedicate some memory for only dom0 and thus prevent the need for ballooning.
>
>
>    

  No, I'm not having dom0_mem here at all.

>> and also the xend.log fragment relevant to the issue:
>>
>>
>> For PV guests there was a change of blktap to blktap2. Couldn't this be
>> related? How could I check I'm using the blktap2 ? Also, my test machine
>> is Intel Xeon X5460 @ 3.16 Ghz, quad-core with 8 GiB RAM running on
>> RHEL-5 with upstream 4.1 xen.
>>
>>      
> Try first using just file:// if using image files, or phy: if using lvm volumes.
>
> -- Pasi
>
>
>    

Ok, I'm using image files. Unfortunately it's not working after reboot 
so it's pretty bad now.

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


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