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@lists.xensource.com http://lists.xensource.com/xen-users
Okay so I did 2)... Windows not runs stably and fine on Xen. But really really slow though. I tried 3) but no help speeding the system up. I could really do with a few hints on how to speed up VMX domains though... Quoting John Wilson <j.wilson@student.manchester.ac.uk>:> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Wilson <j.wilson@student.manchester.ac.uk> writes:> To all you guys who have managed to get Windows up on Xen...I haven''t. Haven''t even tried.> 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.Hm, I thought VT is a hardware technology in next generations CPUs which aren''t available yet. Am I wrong? urs _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> John Wilson <j.wilson@student.manchester.ac.uk> writes: > > To all you guys who have managed to get Windows up on Xen... > > I haven''t. Haven''t even tried. > > > 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. > > Hm, I thought VT is a hardware technology in next generations CPUs > which aren''t available yet. Am I wrong?It depends who you are ;-) You can''t buy them in stores but various academic and commercial users have them already... We have them here in Cambridge and you can bet that other players in the virtualisation game have access to them too. Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Okay so I did 2)... Windows not runs stably and fine on Xen. But really > really slow though. I tried 3) but no help speeding the system up. I could > really do with a few hints on how to speed up VMX domains though...I''m not sure if it''s known to be very fast - it''s not going to fully optimised in the 3.0 release, AFAIK. Are benchmarks running slower than expected on it? (I know you can''t publish them but they might be interesting to look at). Bear in mind that the QEmu display device we''re using is sluggish even under QEmu. Cheers, Mark> Quoting John Wilson <j.wilson@student.manchester.ac.uk>: > > 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@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:>>Okay so I did 2)... Windows not runs stably and fine on Xen. But really >>really slow though. I tried 3) but no help speeding the system up. I could >>really do with a few hints on how to speed up VMX domains though... >> >> > >I''m not sure if it''s known to be very fast - it''s not going to fully optimised >in the 3.0 release, AFAIK. > >Are benchmarks running slower than expected on it? (I know you can''t publish >them but they might be interesting to look at). Bear in mind that the QEmu >display device we''re using is sluggish even under QEmu. > >The current VT architecture is a proof-of-concept. Every IO operation takes a bunch of context switches. There are a bunch of people working on a new architecture that won''t suffer from this problem. Regards, Anthony Liguori>Cheers, >Mark > > > >>Quoting John Wilson <j.wilson@student.manchester.ac.uk>: >> >> >>>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@lists.xensource.com >>>http://lists.xensource.com/xen-users >>> >>> >>_______________________________________________ >>Xen-users mailing list >>Xen-users@lists.xensource.com >>http://lists.xensource.com/xen-users >> >> > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Quoting Mark Williamson <mark.williamson@cl.cam.ac.uk>:> I''m not sure if it''s known to be very fast - it''s not going to fully > optimised > in the 3.0 release, AFAIK. > > Are benchmarks running slower than expected on it? (I know you can''t publish > them but they might be interesting to look at). Bear in mind that the QEmu > display device we''re using is sluggish even under QEmu. > > Cheers, > MarkHey, Well it''s stable enough to be left on for hours without failure, but its very sluggish indeed (takes a good few seconds to open a window). It may well be the display, but I don''t know... The process viewer reported taskmgr.exe consuming a sustained 96-98% of the cpu resources. Device manager shows the CPU speed and memory correct... I''m only currently using one logical processor (i.e. 1/2 a core) at the mo though so I''ll have a look at it after disabling hyperthreading, I might try giving it a few more vcpus too, although I don''t know what it''ll make of smp... John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@student.manchester.ac.uk] >> Sent: Wednesday, September 14, 2005 3:55 PM >> To: xen-users@lists.xensource.com >> 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@lists.xensource.com http://lists.xensource.com/xen-users
John, When I did an "xm create", I got the following error... Using config file "vmx1". VNC= 1 (-2, ''Name or service not known'') Error: Error connecting to xend, is xend running? xen-vt:~/xen/vm # vncviewer-log -listen: Listening on port 11001 (flash port 10901) vncviewer-log -listen: Command line errors are not reported until a connection comes in. And xend is running. I am able to create a VMX domain using SDL. Any ideas? Thanks Aravindh> -----Original Message----- > From: John Wilson [mailto:j.wilson@student.manchester.ac.uk] > Sent: Thursday, September 15, 2005 2:54 PM > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] Windows on Xen+VT > > 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 forthe> 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 itswonderful> 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 onlyget> > SDL. Could you please tell me what steps you followed? It would alsobe> > 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@student.manchester.ac.uk] > >> Sent: Wednesday, September 14, 2005 3:55 PM > >> To: xen-users@lists.xensource.com > >> 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 Iwonder> > if > >> anyone has any experience on ''best practices'' and such whencreating> > WinXP > >> virtual machines. > >> > >> I''m currently using an image that boots to windows setup I madeusing> >> QEMU, > >> and it boots fine, tells me its resuming setup, then blue screenswith> > a > >> reference to an infinite loop being detected in the framebufdriver.> >> (Although I think it might just be detecting extreme slowness asthis> >> 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, asopposed> > 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... Isuppose I> >> could test this in the lab really:-) > >> 5) Anything else I should know? > >> > >> > >> John > >> > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@student.manchester.ac.uk] > >> Sent: Wednesday, September 14, 2005 3:55 PM > >> To: xen-users@lists.xensource.com > >> 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey, I had serious speed issues using the vnc options... BUT... If you put ''stdvga=1'' into the config file and disable vnc, it opens up the viewer window automatically and provides a significant performance boost to windows...:) John Quoting Mark Williamson <mark.williamson@cl.cam.ac.uk>:> 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@student.manchester.ac.uk] >> >> Sent: Wednesday, September 14, 2005 3:55 PM >> >> To: xen-users@lists.xensource.com >> >> 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@lists.xensource.com >> http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I had serious speed issues using the vnc options... > BUT... > If you put ''stdvga=1'' into the config file and disable vnc, > it opens up the viewer window automatically and provides a > significant performance boost to > windows...:)It sounds like you''re running without the memory mapped Cirrus Logic driver patches. I thought these were in mainline, but maybe not. The patch speeds graphics up by 3-4 decimal orders of magnitude! (Without the patch, drawing each pixel involves 10''s of thousands of cycles) There''s still work to do on Windows performance on Xen, but the primary objective has to be to make it rock solid stable. We can then worry about tuning and turning off debuging etc. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark, I have vnc=1 and vncviewer=1. I am getting the following error message when I do an "xm create -f" Using config file "vmx1". VNC= 1 (-2, ''Name or service not known'') Error: Error connecting to xend, is xend running? xen-vt:~/xen/vm # vncviewer-log -listen: Listening on port 11001 (flash port 10901) vncviewer-log -listen: Command line errors are not reported until a connection comes in. And xend is running. I am able to create a VMX domain using SDL. BTW I have installed libvncserver. Any idea why this is happening? Aravindh> -----Original Message----- > From: Mark Williamson [mailto:mark.williamson@cl.cam.ac.uk] > Sent: Thursday, September 15, 2005 8:33 PM > To: xen-users@lists.xensource.com > Cc: John Wilson; Puthiyaparambil, Aravindh > Subject: Re: [Xen-users] Windows on Xen+VT > > You should be able to spawn the vncviewer automatically from xm (andhave> 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 canprobably> 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 forthe> > 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 onlyget> > > SDL. Could you please tell me what steps you followed? It wouldalso> 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@student.manchester.ac.uk] > > >> Sent: Wednesday, September 14, 2005 3:55 PM > > >> To: xen-users@lists.xensource.com > > >> 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 Iwonder> > > > > > if > > > > > >> anyone has any experience on ''best practices'' and such whencreating> > > > > > WinXP > > > > > >> virtual machines. > > >> > > >> I''m currently using an image that boots to windows setup I madeusing> > >> QEMU, > > >> and it boots fine, tells me its resuming setup, then blue screens > with > > > > > > a > > > > > >> reference to an infinite loop being detected in the framebufdriver.> > >> (Although I think it might just be detecting extreme slowness asthis> > >> infinite loop). > > >> > > >> 1) So how to speed it up/why would it be going so slowly? (mylinux> > > > > > 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, asopposed> > > > > > 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 forVT, I> > > > > > don''t > > > > > >> really trust it and it seems a little suspiciously slow... Isuppose> I > > >> could test this in the lab really:-) > > >> 5) Anything else I should know? > > >> > > >> > > >> John > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users