Hi there, first of all I must say i''m a little noobish at Linux and Xen. Currently I''m using Debian Etch x86_64, and I''d like to virtualize WindowsXP. The machine is a Intel Xeon which supports VT instructions. I''ve followed thousands of tutorials, guides and forums. (I think) I''ve successfully created the domain, and the thing is the console freezes when I execute xm console win. Just no error output, the key cursor wont even move. The only solution to this is opening a new terminal and destroying the domain. The thing is I''m accessing to the server through ssh, and I could guess is something about the graphical output. Tried SDL but I get quite a lot of errors on the log. Using VNC, this is the log: domid: 47 qemu: the number of cpus is 1 shared page at pfn:1ffff, mfn: 435da buffered io page at pfn:1fffd, mfn: 435dc char device redirected to /dev/pts/3 False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 -- View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14332639.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
davefury wrote:> Hi there, first of all I must say i''m a little noobish at Linux and Xen. > Currently I''m using Debian Etch x86_64, and I''d like to virtualize > WindowsXP. > > The machine is a Intel Xeon which supports VT instructions. > > I''ve followed thousands of tutorials, guides and forums. (I think) I''ve > successfully created the domain, and the thing is the console freezes when I > execute xm console win. Just no error output, the key cursor wont even move. >When you do "xm console win" - where win is a windows machine - from an ssh session from dom0, what do you expect as the output? If I am running the same command against a linux machine, I would expect a log in prompt, but what for windows? I don''t think it''s possible to get what you expect. --Sadique> The only solution to this is opening a new terminal and destroying the > domain. > > The thing is I''m accessing to the server through ssh, and I could guess is > something about the graphical output. Tried SDL but I get quite a lot of > errors on the log. Using VNC, this is the log: > > domid: 47 > qemu: the number of cpus is 1 > shared page at pfn:1ffff, mfn: 435da > buffered io page at pfn:1fffd, mfn: 435dc > char device redirected to /dev/pts/3 > False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, > count: 0, size: 0 > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I was expecting a Windows installation window or something, like the windows installation cd booting. Other tutorials i''ve followed about installing windows on xen doesnt mention anything in particular... Just create the domain and "console" it. I''ve got the ssh addition that could mess the thing. Thank you very much for the reply! Sadique Puthen wrote:> > davefury wrote: >> Hi there, first of all I must say i''m a little noobish at Linux and Xen. >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize >> WindowsXP. >> >> The machine is a Intel Xeon which supports VT instructions. >> >> I''ve followed thousands of tutorials, guides and forums. (I think) I''ve >> successfully created the domain, and the thing is the console freezes >> when I >> execute xm console win. Just no error output, the key cursor wont even >> move. >> > > When you do "xm console win" - where win is a windows machine - from an > ssh session from dom0, what do you expect as the output? If I am > running the same command against a linux machine, I would expect a log > in prompt, but what for windows? I don''t think it''s possible to get > what you expect. > > --Sadique > >> The only solution to this is opening a new terminal and destroying the >> domain. >> >> The thing is I''m accessing to the server through ssh, and I could guess >> is >> something about the graphical output. Tried SDL but I get quite a lot of >> errors on the log. Using VNC, this is the log: >> >> domid: 47 >> qemu: the number of cpus is 1 >> shared page at pfn:1ffff, mfn: 435da >> buffered io page at pfn:1fffd, mfn: 435dc >> char device redirected to /dev/pts/3 >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, >> count: 0, size: 0 >> >> >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fr, Dez 14, 2007 at 02:34:47 -0800, davefury wrote:> > I was expecting a Windows installation window or something, like the windows > installation cd booting. Other tutorials i''ve followed about installing > windows on xen dont mention anything in particular... Just create the domain > and "console" it. I''ve got the ssh addition that could mess the thing. > > Thank you very much for the reply! >Let us concentrate on VNC. Enable vnc usage in the domain config file. And after you have started the domain xm create win try to attach to vnc session using vncviewer: vncviewer localhost:0> > > Sadique Puthen wrote: > > > > davefury wrote: > >> Hi there, first of all I must say i''m a little noobish at Linux and Xen. > >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize > >> WindowsXP. > >> > >> The machine is a Intel Xeon which supports VT instructions. > >> > >> I''ve followed thousands of tutorials, guides and forums. (I think) I''ve > >> successfully created the domain, and the thing is the console freezes > >> when I > >> execute xm console win. Just no error output, the key cursor wont even > >> move. > >> > > > > When you do "xm console win" - where win is a windows machine - from an > > ssh session from dom0, what do you expect as the output? If I am > > running the same command against a linux machine, I would expect a log > > in prompt, but what for windows? I don''t think it''s possible to get > > what you expect. > > > > --Sadique > > > >> The only solution to this is opening a new terminal and destroying the > >> domain. > >> > >> The thing is I''m accessing to the server through ssh, and I could guess > >> is > >> something about the graphical output. Tried SDL but I get quite a lot of > >> errors on the log. Using VNC, this is the log: > >> > >> domid: 47 > >> qemu: the number of cpus is 1 > >> shared page at pfn:1ffff, mfn: 435da > >> buffered io page at pfn:1fffd, mfn: 435dc > >> char device redirected to /dev/pts/3 > >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, > >> count: 0, size: 0 > >> > >> > >> > >> > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html > Sent from the Xen - User mailing list archive at Nabble.com. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- WBR, i.m.chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the reply again! Sadly, vncviewer localhost:0 gives me a "Error: Can''t open display:" :( Igor Chubin wrote:> > On Fr, Dez 14, 2007 at 02:34:47 -0800, davefury wrote: >> >> I was expecting a Windows installation window or something, like the >> windows >> installation cd booting. Other tutorials i''ve followed about installing >> windows on xen dont mention anything in particular... Just create the >> domain >> and "console" it. I''ve got the ssh addition that could mess the thing. >> >> Thank you very much for the reply! >> > > > Let us concentrate on VNC. > > Enable vnc usage in the domain config file. > And after you have started the domain > > xm create win > > try to attach to vnc session using vncviewer: > > vncviewer localhost:0 > > >> >> >> Sadique Puthen wrote: >> > >> > davefury wrote: >> >> Hi there, first of all I must say i''m a little noobish at Linux and >> Xen. >> >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize >> >> WindowsXP. >> >> >> >> The machine is a Intel Xeon which supports VT instructions. >> >> >> >> I''ve followed thousands of tutorials, guides and forums. (I think) >> I''ve >> >> successfully created the domain, and the thing is the console freezes >> >> when I >> >> execute xm console win. Just no error output, the key cursor wont even >> >> move. >> >> >> > >> > When you do "xm console win" - where win is a windows machine - from an >> > ssh session from dom0, what do you expect as the output? If I am >> > running the same command against a linux machine, I would expect a log >> > in prompt, but what for windows? I don''t think it''s possible to get >> > what you expect. >> > >> > --Sadique >> > >> >> The only solution to this is opening a new terminal and destroying the >> >> domain. >> >> >> >> The thing is I''m accessing to the server through ssh, and I could >> guess >> >> is >> >> something about the graphical output. Tried SDL but I get quite a lot >> of >> >> errors on the log. Using VNC, this is the log: >> >> >> >> domid: 47 >> >> qemu: the number of cpus is 1 >> >> shared page at pfn:1ffff, mfn: 435da >> >> buffered io page at pfn:1fffd, mfn: 435dc >> >> char device redirected to /dev/pts/3 >> >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: >> 0, >> >> count: 0, size: 0 >> >> >> >> >> >> >> >> >> > >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html >> Sent from the Xen - User mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > -- > WBR, i.m.chubin > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333766.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok, here''s what I did: ssh -X root@ip xterm After login vncviewer localhost:0 I got a new window screen showing what appears to be the initial check of the HVMAssist Bios. Ata0 Master: Unknown Device Ata0 Slave: QEMU Harddisk ata-7 hard-disk (4096 Mbytes) Ata1 Master: QEMU CD-ROM ATAPI-4 Cd-Rom/Dvd-Rom Ata1 Slave: Unknown Device Boot from hard disk 0 failed FATAL: Not a bootable disk. How should I change my .cfg so It boots from the .iso I stored in file:/home/david/win.iso ? Think I almost got it :) Thanks! davefury wrote:> > Thanks for the reply again! > > Sadly, > > vncviewer localhost:0 > > gives me a > > "Error: Can''t open display:" > > :( > > Btw, forgot to paste my win.cfg, just in case it needs a review. > > kernel = ''/usr/lib64/xen-3.0.3-1/boot/hvmloader'' > builder = ''hvm'' > memory = ''512'' > device_model=''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'' > > # Disks > disk = [ ''file:/home/xen/domains/win/disk.img,ioemu:hdb,w'', > ''file:/home/david/win.iso,ioemu:hdc:cdrom,r'' ] > > > # Hostname > name = ''win'' > > # Networking > vif = [''type=ioemu, bridge=xenbr0''] > > # Behaviour > acpi=1 > boot=''c'' > vnc=1 > vncviewer=1 > #sdl=1 > serial=''pty'' > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > > Igor Chubin wrote: >> >> On Fr, Dez 14, 2007 at 02:34:47 -0800, davefury wrote: >>> >>> I was expecting a Windows installation window or something, like the >>> windows >>> installation cd booting. Other tutorials i''ve followed about installing >>> windows on xen dont mention anything in particular... Just create the >>> domain >>> and "console" it. I''ve got the ssh addition that could mess the thing. >>> >>> Thank you very much for the reply! >>> >> >> >> Let us concentrate on VNC. >> >> Enable vnc usage in the domain config file. >> And after you have started the domain >> >> xm create win >> >> try to attach to vnc session using vncviewer: >> >> vncviewer localhost:0 >> >> >>> >>> >>> Sadique Puthen wrote: >>> > >>> > davefury wrote: >>> >> Hi there, first of all I must say i''m a little noobish at Linux and >>> Xen. >>> >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize >>> >> WindowsXP. >>> >> >>> >> The machine is a Intel Xeon which supports VT instructions. >>> >> >>> >> I''ve followed thousands of tutorials, guides and forums. (I think) >>> I''ve >>> >> successfully created the domain, and the thing is the console freezes >>> >> when I >>> >> execute xm console win. Just no error output, the key cursor wont >>> even >>> >> move. >>> >> >>> > >>> > When you do "xm console win" - where win is a windows machine - from >>> an >>> > ssh session from dom0, what do you expect as the output? If I am >>> > running the same command against a linux machine, I would expect a log >>> > in prompt, but what for windows? I don''t think it''s possible to get >>> > what you expect. >>> > >>> > --Sadique >>> > >>> >> The only solution to this is opening a new terminal and destroying >>> the >>> >> domain. >>> >> >>> >> The thing is I''m accessing to the server through ssh, and I could >>> guess >>> >> is >>> >> something about the graphical output. Tried SDL but I get quite a lot >>> of >>> >> errors on the log. Using VNC, this is the log: >>> >> >>> >> domid: 47 >>> >> qemu: the number of cpus is 1 >>> >> shared page at pfn:1ffff, mfn: 435da >>> >> buffered io page at pfn:1fffd, mfn: 435dc >>> >> char device redirected to /dev/pts/3 >>> >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, >>> data: 0, >>> >> count: 0, size: 0 >>> >> >>> >> >>> >> >>> >> >>> > >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xensource.com >>> > http://lists.xensource.com/xen-users >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html >>> Sent from the Xen - User mailing list archive at Nabble.com. >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> >> -- >> WBR, i.m.chubin >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > >-- View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333912.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Solved: Modified disk = [ ''file:/home/xen/domains/win/disk.img,ioemu:hdb,w'', ''file:/home/david/win.iso,ioemu:hda:cdrom,r'' ] and added the line: cdrom=''/home/david/win.iso'' pointing where the installation cdimage is stored. Now the domu runs for 3 or 4 seconds (I can see the the Windows setup loading bar) and after that it autodestroys. Some progress here, hope you dont mind the excesive posting, but hope this helps to newcomers to this world like me. Thanks. davefury wrote:> > Ok, here''s what I did: > > ssh -X root@ip xterm > > After login > > vncviewer localhost:0 > > I got a new window screen showing what appears to be the initial check of > the HVMAssist Bios. > > > Ata0 Master: Unknown Device > Ata0 Slave: QEMU Harddisk ata-7 hard-disk (4096 Mbytes) > Ata1 Master: QEMU CD-ROM ATAPI-4 Cd-Rom/Dvd-Rom > Ata1 Slave: Unknown Device > > Boot from hard disk 0 failed > FATAL: Not a bootable disk. > > How should I change my .cfg so It boots from the .iso I stored in > file:/home/david/win.iso ? > > Think I almost got it :) > > Thanks! > > > > Btw, forgot to paste my win.cfg, just in case it needs a review. > > kernel = ''/usr/lib64/xen-3.0.3-1/boot/hvmloader'' > builder = ''hvm'' > memory = ''512'' > device_model=''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'' > > # Disks > disk = [ ''file:/home/xen/domains/win/disk.img,ioemu:hdb,w'', > ''file:/home/david/win.iso,ioemu:hdc:cdrom,r'' ] > > > # Hostname > name = ''win'' > > # Networking > vif = [''type=ioemu, bridge=xenbr0''] > > # Behaviour > acpi=1 > boot=''c'' > vnc=1 > vncviewer=1 > #sdl=1 > serial=''pty'' > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > > Igor Chubin wrote: >> >> On Fr, Dez 14, 2007 at 02:34:47 -0800, davefury wrote: >>> >>> I was expecting a Windows installation window or something, like the >>> windows >>> installation cd booting. Other tutorials i''ve followed about installing >>> windows on xen dont mention anything in particular... Just create the >>> domain >>> and "console" it. I''ve got the ssh addition that could mess the thing. >>> >>> Thank you very much for the reply! >>> >> >> >> Let us concentrate on VNC. >> >> Enable vnc usage in the domain config file. >> And after you have started the domain >> >> xm create win >> >> try to attach to vnc session using vncviewer: >> >> vncviewer localhost:0 >> >> >>> >>> >>> Sadique Puthen wrote: >>> > >>> > davefury wrote: >>> >> Hi there, first of all I must say i''m a little noobish at Linux and >>> Xen. >>> >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize >>> >> WindowsXP. >>> >> >>> >> The machine is a Intel Xeon which supports VT instructions. >>> >> >>> >> I''ve followed thousands of tutorials, guides and forums. (I think) >>> I''ve >>> >> successfully created the domain, and the thing is the console freezes >>> >> when I >>> >> execute xm console win. Just no error output, the key cursor wont >>> even >>> >> move. >>> >> >>> > >>> > When you do "xm console win" - where win is a windows machine - from >>> an >>> > ssh session from dom0, what do you expect as the output? If I am >>> > running the same command against a linux machine, I would expect a log >>> > in prompt, but what for windows? I don''t think it''s possible to get >>> > what you expect. >>> > >>> > --Sadique >>> > >>> >> The only solution to this is opening a new terminal and destroying >>> the >>> >> domain. >>> >> >>> >> The thing is I''m accessing to the server through ssh, and I could >>> guess >>> >> is >>> >> something about the graphical output. Tried SDL but I get quite a lot >>> of >>> >> errors on the log. Using VNC, this is the log: >>> >> >>> >> domid: 47 >>> >> qemu: the number of cpus is 1 >>> >> shared page at pfn:1ffff, mfn: 435da >>> >> buffered io page at pfn:1fffd, mfn: 435dc >>> >> char device redirected to /dev/pts/3 >>> >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, >>> data: 0, >>> >> count: 0, size: 0 >>> >> >>> >> >>> >> >>> >> >>> > >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xensource.com >>> > http://lists.xensource.com/xen-users >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html >>> Sent from the Xen - User mailing list archive at Nabble.com. >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> >> -- >> WBR, i.m.chubin >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > > >-- View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14334397.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fr, Dez 14, 2007 at 03:43:52 -0800, davefury wrote:> > Solved: > > Modified > disk = [ ''file:/home/xen/domains/win/disk.img,ioemu:hdb,w'', > ''file:/home/david/win.iso,ioemu:hda:cdrom,r'' ] >Better change this line to : disk = [ ''file:/home/xen/domains/win/disk.img,hda,w'', ''file:/home/david/win.iso,hdb:cdrom,r'' ] and add the line with the ''boot'' parameter: boot = ''d'' and try again.> and added the line: > cdrom=''/home/david/win.iso'' > pointing where the installation cdimage is stored. > > Now the domu runs for 3 or 4 seconds (I can see the the Windows setup > loading bar) and after that it autodestroys. > > Some progress here, hope you dont mind the excesive posting, but hope this > helps to newcomers to this world like me. Thanks. > > > davefury wrote: > > > > Ok, here''s what I did: > > > > ssh -X root@ip xterm > > > > After login > > > > vncviewer localhost:0 > > > > I got a new window screen showing what appears to be the initial check of > > the HVMAssist Bios. > > > > > > Ata0 Master: Unknown Device > > Ata0 Slave: QEMU Harddisk ata-7 hard-disk (4096 Mbytes) > > Ata1 Master: QEMU CD-ROM ATAPI-4 Cd-Rom/Dvd-Rom > > Ata1 Slave: Unknown Device > > > > Boot from hard disk 0 failed > > FATAL: Not a bootable disk. > > > > How should I change my .cfg so It boots from the .iso I stored in > > file:/home/david/win.iso ? > > > > Think I almost got it :) > > > > Thanks! > > > > > > > > Btw, forgot to paste my win.cfg, just in case it needs a review. > > > > kernel = ''/usr/lib64/xen-3.0.3-1/boot/hvmloader'' > > builder = ''hvm'' > > memory = ''512'' > > device_model=''/usr/lib64/xen-3.0.3-1/bin/qemu-dm'' > > > > # Disks > > disk = [ ''file:/home/xen/domains/win/disk.img,ioemu:hdb,w'', > > ''file:/home/david/win.iso,ioemu:hdc:cdrom,r'' ] > > > > > > # Hostname > > name = ''win'' > > > > # Networking > > vif = [''type=ioemu, bridge=xenbr0''] > > > > # Behaviour > > acpi=1 > > boot=''c'' > > vnc=1 > > vncviewer=1 > > #sdl=1 > > serial=''pty'' > > on_poweroff = ''destroy'' > > on_reboot = ''restart'' > > on_crash = ''restart'' > > > > > > Igor Chubin wrote: > >> > >> On Fr, Dez 14, 2007 at 02:34:47 -0800, davefury wrote: > >>> > >>> I was expecting a Windows installation window or something, like the > >>> windows > >>> installation cd booting. Other tutorials i''ve followed about installing > >>> windows on xen dont mention anything in particular... Just create the > >>> domain > >>> and "console" it. I''ve got the ssh addition that could mess the thing. > >>> > >>> Thank you very much for the reply! > >>> > >> > >> > >> Let us concentrate on VNC. > >> > >> Enable vnc usage in the domain config file. > >> And after you have started the domain > >> > >> xm create win > >> > >> try to attach to vnc session using vncviewer: > >> > >> vncviewer localhost:0 > >> > >> > >>> > >>> > >>> Sadique Puthen wrote: > >>> > > >>> > davefury wrote: > >>> >> Hi there, first of all I must say i''m a little noobish at Linux and > >>> Xen. > >>> >> Currently I''m using Debian Etch x86_64, and I''d like to virtualize > >>> >> WindowsXP. > >>> >> > >>> >> The machine is a Intel Xeon which supports VT instructions. > >>> >> > >>> >> I''ve followed thousands of tutorials, guides and forums. (I think) > >>> I''ve > >>> >> successfully created the domain, and the thing is the console freezes > >>> >> when I > >>> >> execute xm console win. Just no error output, the key cursor wont > >>> even > >>> >> move. > >>> >> > >>> > > >>> > When you do "xm console win" - where win is a windows machine - from > >>> an > >>> > ssh session from dom0, what do you expect as the output? If I am > >>> > running the same command against a linux machine, I would expect a log > >>> > in prompt, but what for windows? I don''t think it''s possible to get > >>> > what you expect. > >>> > > >>> > --Sadique > >>> > > >>> >> The only solution to this is opening a new terminal and destroying > >>> the > >>> >> domain. > >>> >> > >>> >> The thing is I''m accessing to the server through ssh, and I could > >>> guess > >>> >> is > >>> >> something about the graphical output. Tried SDL but I get quite a lot > >>> of > >>> >> errors on the log. Using VNC, this is the log: > >>> >> > >>> >> domid: 47 > >>> >> qemu: the number of cpus is 1 > >>> >> shared page at pfn:1ffff, mfn: 435da > >>> >> buffered io page at pfn:1fffd, mfn: 435dc > >>> >> char device redirected to /dev/pts/3 > >>> >> False I/O request ... in-service already: 0, pvalid: 0, port: 0, > >>> data: 0, > >>> >> count: 0, size: 0 > >>> >> > >>> >> > >>> >> > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Xen-users mailing list > >>> > Xen-users@lists.xensource.com > >>> > http://lists.xensource.com/xen-users > >>> > > >>> > > >>> > >>> -- > >>> View this message in context: > >>> http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14333271.html > >>> Sent from the Xen - User mailing list archive at Nabble.com. > >>> > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> Xen-users@lists.xensource.com > >>> http://lists.xensource.com/xen-users > >> > >> -- > >> WBR, i.m.chubin > >> > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > >> > >> > > > > > > > > > > -- > View this message in context: http://www.nabble.com/Problem%3A-Windows-on-Xen-tp14332639p14334397.html > Sent from the Xen - User mailing list archive at Nabble.com. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- WBR, i.m.chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just noticed your mail - I''ve spent most of the day installing a Win2K
domU, which works. I started with the "How to Install Windows on Xen
3.0" technical note, which is nearly correct. Note that the sample
config file uses sdl, not vnc.
The problem in the appnote is that the config file says:
disk = [ ''phy:/dev/VG_Guests/w2k3-001,ioemu:hda,w'' ]
cdrom = "/tmp/WINDOWS_2003_STANMDARD.ISO"
This won''t work on Xen 3; mine now says
disk = [ ''phy:/dev/VG_Guests/w2k-001,ioemu:hda,w'' ,
''file:/tmp/WINDOWS_2000.ISO,hdc:cdrom,r''];
note no cdrom line, as Igor says. And, to expand on the boot line, you
need to change
boot="d"
to boot="cd" # or just "c"
as soon as installation completes.
Next problem: the DomU runs, but it starts life in a 640x480 window. The
full-screen config option doesn''t work, and I can''t find any
documentation on how to get a bigger window. I can change the window
size by using Windoze properties to increase resolution up to 1Kx768,
but it won''t go any higher than that. And the mouse is almost unusably
slow. I''ll try giving the domU a whole core, but I''m not
optimistic. If
you can work out how to fix that lot, I''d be very grateful... :)
Evan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> Next problem: the DomU runs, but it starts life in a 640x480 window. > The full-screen config option doesn''t work, and I can''t find any > documentation on how to get a bigger window. I can change the window > size by using Windoze properties to increase resolution up to 1Kx768, > but it won''t go any higher than that. And the mouse is almost unusably > slow. I''ll try giving the domU a whole core, but I''m not optimistic. If > you can work out how to fix that lot, I''d be very grateful... :) >Evan, my experience is that is much nicer to work with a windows vm connecting via rdesktop. Cheers frank _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Frank Mueller wrote:>> Next problem: the DomU runs, but it starts life in a 640x480 window. >> The full-screen config option doesn''t work, and I can''t find any >> documentation on how to get a bigger window. I can change the window >> size by using Windoze properties to increase resolution up to 1Kx768, >> but it won''t go any higher than that. And the mouse is almost unusably >> slow. I''ll try giving the domU a whole core, but I''m not optimistic. If >> you can work out how to fix that lot, I''d be very grateful... :) >> > > Evan, my experience is that is much nicer to work with a windows vm > connecting via > rdesktop.I think you''re right, but - 1 - my terminal is a Windows box, and I think rdesktop is Unix-only, and 2 - I''m running Win2K, which I don''t think has any built-in terminal services stuff. Given that, I''m now running vncserver on the Win2K domU, and a vnc client on the Win2K terminal. This actually works pretty well. I can get full screen, and the mouse works properly. There is a problem, which is that the pixel block update in vnc is *very* slow, so you can''t move windows around too much. However, it''s a *lot* better than using SDL on the Dom0. I don''t suppose you know of anything like rdesktop for Win2K? Without paying for it? :) Evan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri December 14 2007 1:29:07 pm Evan Lavelle wrote:> Next problem: the DomU runs, but it starts life in a 640x480 window. The > full-screen config option doesn''t work, and I can''t find any > documentation on how to get a bigger window. I can change the window > size by using Windoze properties to increase resolution up to 1Kx768, > but it won''t go any higher than that. And the mouse is almost unusably > slow. I''ll try giving the domU a whole core, but I''m not optimistic. If > you can work out how to fix that lot, I''d be very grateful... :)The video card that xen''s qemu-dm emulates only goes up that far. Sorry. As for the mouse, add the following line to your win2k .cfg: usbdevice="tablet"> Given that, I''m now running vncserver on the Win2K domU, and a vnc > client on the Win2K terminal. This actually works pretty well. I can get > full screen, and the mouse works properly. There is a problem, which is > that the pixel block update in vnc is *very* slow, so you can''t move > windows around too much. However, it''s a *lot* better than using SDL on > the Dom0.You can play with the ''-encodings'' flag to vncviewer, but I find this gets tedious. qemu-dm gets the vnc setup right for you. To use this, add the lines below to your .cfg, and use ''vncviewer dom0-name'', instead of domu-name. # more documentation on these options is in your example scripts: # /etc/xen/xmexample.hvm (/etc/xen/examples/xmexample.hvm on SuSE) sdl=0 vnc=1 # the default is only localhost access: #vnclisten="127.0.0.1" # uncomment the following to execute vncviewer from any station #vnclisten="0.0.0.0" # set VNC display number, default = domid #vncdisplay=1 # try to find an unused port for the VNC server, default = 1 #vncunused=1 vncconsole=1 vncpasswd="" # the following is to enable ctrl-alt-1 and ctrl-alt-2 switching # between the windows session and the qemu monitor monitor=1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users