RE: [Xen-users] Windows 2003 and 2008

["Dustin Henning" <Dustin.Henning@xxxxxxxxxxx>]

        I didn't see the new thread on the same issue...  The config sent by
Fajar A. Nugraha includes these lines:
sdl=0  # this disables sdl
vnc=1  # this enables vnc
vnclisten="0.0.0.0"  # this tells vnc to allow connections on all IPs
instead of only loopback connections, remember, it is dom0 doing the vnc,
not domU
vncpasswd='' # this allows connections to the appropriate vnc port with no
password, or a password can be entered

There may be another line that binds the machine to a specific vnc port, but
I don't have access to my configs to tell you what it is.  It would be in
the xmexample.hvm in /etc/xen if you have one there.  It MIGHT be vncport=
where 0 means automatic and 1+ tells which port (590x where 1+=x), but I am
not certain, as the vncport part was just a guess.  I have also seen
instances where the whole port has to be entered (5901 or whatever), but I
don't know whether that was in the xml configs or something totally
different.
        Dustin


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dustin Henning
Sent: Wednesday, July 02, 2008 08:55
To: 'Steffen Heil'; 'Jeroen Torrekens'; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Windows 2003 and 2008

        I'm not a native to Linux and haven't really used it that much, but
I never had any luck with X forwarding.  Also, I believe SDL is resource
intensive.  I recommend you set up your HVM DomU to use VNC instead of SDL.
At that point, the vncserver in your Dom0 will function similar to the way
an IPvM functions and you will be able to access your server through there.
This obviously will require the vncserver to exist and be properly
configured (I use F8 with xen from F8 repos and this is all automatic, so I
can't help you with custom configuration for that).  It will also require
you to have the appropriate port open on the Dom0 network to the machine you
want to connect through vnc from.  I think you want to set the tablet
usbdevice up as well, because otherwise the mouse will be a pain.
Regardless, once you can get in through VNC, you can enable remote desktop,
then you can close vnc back up and connect directly to the domu that way.
However, you will still need to use vnc if you need to access the boot menu
because of the GPLPV drivers orto try to get at safe mode or something.
Hope this helps,
        Dustin

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Steffen Heil
Sent: Wednesday, July 02, 2008 08:44
To: 'Jeroen Torrekens'; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Windows 2003 and 2008

Hi

> > It opens a SDL window. That does require a GUI, doesn't it?
> > 
> > Regards,
> >   Steffen
> 
> You can use X forwarding for that. If you are running windows, check 
> Xming. If you are running linux, you'll have all the tools you need 
> (look at ssh -X).

I tried. However I get the following in the logs.
Any idea how to solve that?

Reagrds,
  Steffen



Strip off blktap sub-type prefix to /root/w2k3.iso Watching
/local/domain/0/device-model/49/logdirty/next-active
Watching /local/domain/0/device-model/49/command
bridge xenbr100 does not exist!

     =======================|  DirectFB 1.0.1  |=======================
          (c) 2001-2007  The DirectFB Organization (directfb.org)
          (c) 2000-2004  Convergence (integrated media) GmbH
        ------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-04-08 15:15)
(*) Direct/Memcpy: Using Generic 64bit memcpy()
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
variable.
(!) DirectFB/Core: Could not initialize 'system' core!
    --> Initialization error!
Could not initialize SDL - exiting


For the following configuration:

kernel  = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory  = '512'
device_model='/usr/lib/xen/bin/qemu-dm'
disk    = [
'phy:/dev/raid/windows,ioemu:hda,w','tap:aio:/root/w2k3.iso,ioemu:hdc:cdrom,
r' ]
#disk    = [ 'phy:/dev/raid/windows,ioemu:hda,w' ]
#cdrom   = '/root/w2k3.iso'
name    = 'windows'
vif = ['type=ioemu,mac=00:16:3e:00:00:08,ip=78.46.250.160/32']
boot='d'
vnc=0
sdl=1
stdvga=1




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



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