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@xxxxxxxxxxxxxxxxxxx
> >>> > 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@xxxxxxxxxxxxxxxxxxx
> >>> http://lists.xensource.com/xen-users
> >>
> >> --
> >> WBR, i.m.chubin
> >>
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
--
WBR, i.m.chubin
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home