Re: Missing hvm output - really vnc hvm experience

[John Hayward <John.C.Hayward%wheaton.edu@localhost>]

Hello all,
    When I started windows xp with vnc via the config file I notice that 
my mouse does not track well when I leave the vncviewer - that is when I
come back in the dot is off from where the cursor mouse would expected to 
be.  This makes it difficult to get to edges of the window since once the
dot leaves the window the cursor does not move.
    If I install vncserver on the dom_u and run from there things are 
happier.

    Is this an windows XP issue (several have reported that windows XP did
not work as well as windows server) or a problem with using vnc from xen?

johnh...

    FWIW SDL seemed to work just fine (except I could not access it 
remotly via ssh - which might be expected).

NetBSD-4.0 xen 3.1.2

On Thu, 1 May 2008, Manuel Bouyer wrote:

> Date: Thu, 1 May 2008 13:41:36 +0200
> From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
> To: Michael Dexter <dexter%ambidexter.com@localhost>
> Cc: port-xen%NetBSD.org@localhost
> Subject: Re: Missing hvm output
>
> On Thu, May 01, 2008 at 01:47:21PM +0300, Michael Dexter wrote:
> > Hello all,
> >
> > I am experimenting with HVM support under NetBSD 4.0 Xen 3 and various install 
> > CD's and upon using a slightly modified included hvm configuration file, I get:
> >
> > # xm create hvmtest.cfg
> > Using config file "./hvmtest.cfg".
> > Started domain hvm
> > #
> >
> > The configuration file suggests that this should should bring up an xwindow.
> >
> > I have tried this from within X, the console and with -c for what it's worth.
> >
> > I can however see the DomU running with 'xm list'
> >
> > /var/log/xen/qemu-dm.2148.log ends with:
> >
> > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> > Triggered log-dirty buffer switch
> >
> > All dependencies for xentools3-hvm appear to be resolved.
> >
> > Any suggestions?
>
> Can you show your config file ? I've not used SDL support for a
> long time; vnc support works nicely. But if using vnc, you have to start
> vncviewer yourself :)
> You can see if it's listening for vnc connections with netstat -a -f inet
> (look for port 5900 and above)
>
> --
> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>     NetBSD: 26 ans d'experience feront toujours la difference
> --

johnh...