From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Mon, 7 Jun 2010 12:12:51 -0400 Message-ID: <20100607161251.GF8487@phenom.dumpdata.com> References: <4C08C96F.2080400@redhat.com> <20100604104250.GL17817@reaktio.net> <4C0CD631.4030006@redhat.com> <20100607114538.GC17817@reaktio.net> <4C0CEFC0.5040506@redhat.com> <4C0CF0C0.8070607@redhat.com> <20100607131936.GF17817@reaktio.net> <4C0CF24D.3060507@redhat.com> <4C0CF35C.2030909@redhat.com> <4C0CF5EC.8040905@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4C0CF5EC.8040905@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michal Novotny Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.