[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Windows on Xen+VT
You should be able to spawn the vncviewer automatically from xm (and have the device emulation automatically connect to it). Try setting: vnc=1 to start the server and vncviewer='yes' in the config to spawn a VNC viewer It should work - otherwise the code in create.py and image.py can probably be hacked to fix it without too much difficulty. Cheers, Mark On Thursday 15 September 2005 19:53, John Wilson wrote: > How I managed to get VMX up and running: > > 1) Perform a Xen 3.0 source build with libvncserver installed > 2) Modify the VMX config file and 'xm create -f vmx.img' > 3) After confirmation of domain creation, 'netstat -nat' to look for the > vnc server (on port 590X)... mine was located at ip 0.0.0.0:5901 > 4) vncviewer 0.0.0.0:5901 > > And the VNC window opens up displaying the VMX domain in all its wonderful > glory:-) > > My config file was just the vmx example with the image file changed. > > John > > Quoting "Puthiyaparambil, Aravindh" > > > John, > > > > I have been trying to get VNC to work with VMX domains. I have the > > libvnc library installed. I have been able to get it working only get > > SDL. Could you please tell me what steps you followed? It would also be > > helpful if you could get me a copy of your Windows VMX domain's xm > > config file. > > > > Thanks, > > Aravindh > > > >> -----Original Message----- > >> From: John Wilson [mailto:j.wilson@xxxxxxxxxxxxxxxxxxxxxxxx] > >> Sent: Wednesday, September 14, 2005 3:55 PM > >> To: xen-users@xxxxxxxxxxxxxxxxxxx > >> Subject: [Xen-users] Windows on Xen+VT > >> > >> To all you guys who have managed to get Windows up on Xen... > >> > >> Its early days for me as I only figured out how to get it up and > > > > running > > > >> through vnc today, but basically it runs rather slowly, and I wonder > > > > if > > > >> anyone has any experience on 'best practices' and such when creating > > > > WinXP > > > >> virtual machines. > >> > >> I'm currently using an image that boots to windows setup I made using > >> QEMU, > >> and it boots fine, tells me its resuming setup, then blue screens with > > > > a > > > >> reference to an infinite loop being detected in the framebuf driver. > >> (Although I think it might just be detecting extreme slowness as this > >> infinite loop). > >> > >> 1) So how to speed it up/why would it be going so slowly? (my linux > > > > VMX > > > >> machines don't exactly burn rubber either) > >> 2) Should I fully install windows onto the image with QEMU first? > >> 3) Should the video output be configured for full screen, as opposed > > > > to > > > >> windowed as it is currently? > >> 4)Is there any possibility at all that a VMX domain (especially > > > > windows) > > > >> could be run on a non-VT machine? (Beacause its a very new > > > > pre-production > > > >> bios and platform, and even though it's set up in the bios for VT, I > > > > don't > > > >> really trust it and it seems a little suspiciously slow... I suppose I > >> could test this in the lab really:-) > >> 5) Anything else I should know? > >> > >> > >> John > > _______________________________________________ > 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |