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

["Todd Deshane" <deshantm@xxxxxxxxx>]

On Sun, May 11, 2008 at 7:51 PM, Glen Eustace <geustace@xxxxxxxxxxxxxx> wrote:

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.

So vnc is probably your best choice until you can get in and configure remote desktop.
 

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'

are you referring to the bootloader = ...pygrub line?

If so, then pygub might actually be able to run in an ncurses (i.e. console) environment but  you won't be able to use it to boot windows yet probably.

You will want to use the vnc=1 line

You will also need to configure vnc in the /etc/xen/xend-config.sxp file.

add a vnc-listen line:

(vnc-listen '0.0.0.0')

make sure also that you have a vncpasswd line
(vncpasswd '')

Then, after booting the windows guest you should be able to connect to it by using
a vncviewer to the IP of the dom0.

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.

which vfb line are you referring to?


Cheers,
Todd
 

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