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/
Home Products Support Community News


[Xen-users] Re: xm create error - Unable to allocate memory

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: xm create error - Unable to allocate memory
From: Glen Eustace <geustace@xxxxxxxxxxxxxx>
Date: Mon, 12 May 2008 11:51:39 +1200
Delivery-date: Sun, 11 May 2008 16:52:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080226)
An alternative to VNC is to use sdl, just set sdl=1 in your config (instead
of vnc=1).

The Xen host has no graphical capability, i.e. no monitor and X not installed.

I have been trying to get VNC going. It is kind of weird. If I include a 'boot 
=' in the config file, I can't get a connection, virt-viewer displays 'unable 
to find vnc graphics for agree-20'

If I take the boot parameter out, I can connect but the BIOS tries to load from 
the HD which hasn't even been formatted yet.

PS: It would seem that the memory allocation issue, was more to do with not 
having a vfb defined.  as I have now had to put the kernel parameter back in.

Xen-users mailing list

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