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

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Problem with starting guest (para_virt dom0)
From: "Adam Wendt" <thelsdj@xxxxxxxxx>
Date: Wed, 14 Jan 2009 23:56:58 -0800
Delivery-date: Wed, 14 Jan 2009 23:57:36 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=vVKYL6KzuQ1GA9iGNP+DJG/YZnbMDFz8sLp4xDM6ZyI=; b=X6zPeULHTb7YfJv1p0IhoHTa3cKF2UwxJ+P1wW2j+KQ49ccnDdFRlPqXZFgmIlLy2a Izm45Zq0e8lFXovTsq7wD8sbSzfi13MWfAsSZ1mMrPtkjPzD8GHMCSiecVu05rv/ZiJa RGmbRHB66LSHhiyH2IishklkGidrLlBzBFiDc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=EcQCMK19YLxY5rwozlmsymIxlpNLiY1qxmuIozDklUhGFl86IAw3uJsgAV6+7aplNC lTDaTkPMhOak9fom4Wa+xlEBTGf1K/t/USmiw/g/REFrTOf+o5U+JTWmMozsct3dyKs0 KNy3PBOvCSuoq3nxPodbwHkWAsYw1IzHVnvr8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

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?

Thanks,

Adam
Adam Wendt Consulting
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>