WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem with starting guest (para_virt dom0)

To: Adam Wendt <thelsdj@xxxxxxxxx>
Subject: Re: [Xen-devel] Problem with starting guest (para_virt dom0)
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Thu, 15 Jan 2009 08:04:49 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Jan 2009 00:05:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7385ecaf0901142356l5fc58aabx4f525d5a453287d7@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <7385ecaf0901142356l5fc58aabx4f525d5a453287d7@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2009-01-14 at 23:56 -0800, Adam Wendt wrote:
> Hi,
> 
> I've managed to get a para_virt dom0 running on my x86_64 system but
> having problems starting a guest.  First problem was that xenstore
> client programs weren't able to communicate over xenbus (xs_write_all
> hitting its return false branch) still not sure why this is happening.
> I was able to at least get xenstore working by hacking the client to
> use the normal socket by default.

Perhaps you need to enable xenfs in your kernel build and mount it
on /proc/xen in order to gain access to /proc/xen/xsd*?

> But now I'm getting:
> Error: [Errno 2] No such file or directory: '/proc/xen/balloon'
> 
> Google only turned up reports that this is related to trying to give
> the guest too much memory, but xm info shows I have over 3.5G free and
> only trying to give 128M to the guest. Any other ideas what might be
> causing this?

pvops only supports balloon via a sysfs interface not proc. There is a
patch in xen-unstable.hg from Jeremy Fitzhardinge which fixes this but
you'll either need to use xen-unstable or backport it to whatever you
are using (it's pretty simple, IIRC).

Ian.



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

<Prev in Thread] Current Thread [Next in Thread>