As soon as the cd-rom kicks in, the machine reboots! Any clues on what I need to be doing next (I tried both windows XP and 2k3)? 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue Mar 14 16:23:33 EST 2006 i686 i686 i386 GNU/Linux 2. xen modules: kernel-xen0-2.6.15-1.2054_FC5 xen-3.0.1-4 3. My config file: kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 512 name = "winxp" vcpus=1 pae=0 acpi=0 apic=0 cpus = "" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''file:/root/windisk/windisk.img,ioemu:hda,w'' ] on_poweroff = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' device_model = ''/usr/lib/xen/bin/qemu-dm'' cdrom=''/dev/cdrom'' boot=''d'' sdl=0 vnc=1 vncviewer=0 stdvga=0 serial=''pty'' ne2000=0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
BTW, this happens only when trying to launch native Windows, but I could install FC4, FC5 w/o any problems (and yes, VMXON is done, i.e. the platform does support hvm). Any ideas? -- On 6/24/06, pv <vishnubhatt@gmail.com> wrote:> > As soon as the cd-rom kicks in, the machine reboots! Any clues on what I > need to be doing next (I tried both windows XP and 2k3)? > > > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue Mar 14 > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux > 2. xen modules: > kernel-xen0-2.6.15-1.2054_FC5 > xen-3.0.1-4 > 3. My config file: > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 512 > name = "winxp" > vcpus=1 > pae=0 > acpi=0 > apic=0 > cpus = "" > vif = [ ''type=ioemu, bridge=xenbr0'' ] > disk = [ ''file:/root/windisk/windisk.img,ioemu:hda,w'' ] > on_poweroff = ''destroy'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > device_model = ''/usr/lib/xen/bin/qemu-dm'' > cdrom=''/dev/cdrom'' > boot=''d'' > sdl=0 > vnc=1 > vncviewer=0 > stdvga=0 > serial=''pty'' > ne2000=0 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Just a thought but, have you tried using an ISO file instead of /dev/cdrom? Marcus pv wrote:> BTW, this happens only when trying to launch native Windows, but I > could install FC4, FC5 w/o any problems (and yes, VMXON is done, i.e. > the platform does support hvm). Any ideas? > -- > > > On 6/24/06, *pv* <vishnubhatt@gmail.com > <mailto:vishnubhatt@gmail.com>> wrote: > > As soon as the cd-rom kicks in, the machine reboots! Any clues on > what I need to be doing next (I tried both windows XP and 2k3)? > > > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue Mar 14 > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux > 2. xen modules: > kernel-xen0-2.6.15-1.2054_FC5 > xen-3.0.1-4 > 3. My config file: > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 512 > name = "winxp" > vcpus=1 > pae=0 > acpi=0 > apic=0 > cpus = "" > vif = [ ''type=ioemu, bridge=xenbr0'' ] > disk = [ ''file:/root/windisk/windisk.img,ioemu:hda,w'' ] > on_poweroff = ''destroy'' > on_reboot = ''destroy'' > on_crash = ''destroy'' > device_model = ''/usr/lib/xen/bin/qemu-dm'' > cdrom=''/dev/cdrom'' > boot=''d'' > sdl=0 > vnc=1 > vncviewer=0 > stdvga=0 > serial=''pty'' > ne2000=0 > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
Tried that - same results, next is to go to xen-unstable and try it there
but when I do that, I''m getting into other/maybe-unrelated startup
issues
(excerpt from the xend.log):
[2006-06-25 12:57:20 xend] INFO (SrvDaemon:185) Xend exited with status 1.
[2006-06-25 12:58:03 xend] INFO (SrvDaemon:285) Xend Daemon started
[2006-06-25 12:58:03 xend] ERROR (SrvDaemon:299) Exception starting xend
((22, ''Invalid argument''))
Traceback (most recent call last):
File
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line
288, in run
xinfo = xc.xeninfo()
error: (22, ''Invalid argument'')
[2006-06-25 12:58:03 xend] INFO (SrvDaemon:185) Xend exited with status 1.
--
On 6/25/06, Marcus Carlson <marcus@mejlamej.nu>
wrote:>
> Hi,
>
> Just a thought but, have you tried using an ISO file instead of
> /dev/cdrom?
>
> Marcus
>
> pv wrote:
> > BTW, this happens only when trying to launch native Windows, but I
> > could install FC4, FC5 w/o any problems (and yes, VMXON is done, i.e.
> > the platform does support hvm). Any ideas?
> > --
> >
> >
> > On 6/24/06, *pv* <vishnubhatt@gmail.com
> > <mailto:vishnubhatt@gmail.com>> wrote:
> >
> > As soon as the cd-rom kicks in, the machine reboots! Any clues on
> > what I need to be doing next (I tried both windows XP and 2k3)?
> >
> >
> > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue Mar 14
> > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux
> > 2. xen modules:
> > kernel-xen0-2.6.15-1.2054_FC5
> > xen-3.0.1-4
> > 3. My config file:
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder=''hvm''
> > memory = 512
> > name = "winxp"
> > vcpus=1
> > pae=0
> > acpi=0
> > apic=0
> > cpus = ""
> > vif = [ ''type=ioemu, bridge=xenbr0'' ]
> > disk = [
''file:/root/windisk/windisk.img,ioemu:hda,w'' ]
> > on_poweroff = ''destroy''
> > on_reboot = ''destroy''
> > on_crash = ''destroy''
> > device_model = ''/usr/lib/xen/bin/qemu-dm''
> > cdrom=''/dev/cdrom''
> > boot=''d''
> > sdl=0
> > vnc=1
> > vncviewer=0
> > stdvga=0
> > serial=''pty''
> > ne2000=0
> >
> >
> >
------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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
Sachiko Yoshihama
2006-Jun-26 11:24 UTC
Re: [Xen-users] Re: Trying to install Windows in Xen
Hi, I had the same problem that the machine reboots at Windows installation, when I was using 2.6.16-1.2133_FC5xen0. The problem does not happen on the latest 2.6.17-1.2139_FC5xen0. Perhaps you can update "kernel-xen0" and "xen" to the latest version. The following mail archive is also very helpful. http://lists.xensource.com/archives/html/xen-users/2006-06/msg00452.html Sachiko On 6/26/06, pv <vishnubhatt@gmail.com> wrote:> > Tried that - same results, next is to go to xen-unstable and try it there > but when I do that, I''m getting into other/maybe-unrelated startup issues > (excerpt from the xend.log): > > > [2006-06-25 12:57:20 xend] INFO (SrvDaemon:185) Xend exited with status 1. > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:285) Xend Daemon started > [2006-06-25 12:58:03 xend] ERROR (SrvDaemon:299) Exception starting xend > ((22, ''Invalid argument'')) > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", > line 288, in run > xinfo = xc.xeninfo() > error: (22, ''Invalid argument'') > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:185) Xend exited with status 1. > > > -- > > On 6/25/06, Marcus Carlson <marcus@mejlamej.nu> wrote: > > > > Hi, > > > > Just a thought but, have you tried using an ISO file instead of > > /dev/cdrom? > > > > Marcus > > > > pv wrote: > > > BTW, this happens only when trying to launch native Windows, but I > > > could install FC4, FC5 w/o any problems (and yes, VMXON is done, i.e. > > > the platform does support hvm). Any ideas? > > > -- > > > > > > > > > On 6/24/06, *pv* <vishnubhatt@gmail.com > > > <mailto:vishnubhatt@gmail.com>> wrote: > > > > > > As soon as the cd-rom kicks in, the machine reboots! Any clues on > > > what I need to be doing next (I tried both windows XP and 2k3)? > > > > > > > > > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue Mar 14 > > > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux > > > 2. xen modules: > > > kernel-xen0-2.6.15-1.2054_FC5 > > > xen-3.0.1-4 > > > 3. My config file: > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > builder=''hvm'' > > > memory = 512 > > > name = "winxp" > > > vcpus=1 > > > pae=0 > > > acpi=0 > > > apic=0 > > > cpus = "" > > > vif = [ ''type=ioemu, bridge=xenbr0'' ] > > > disk = [ ''file:/root/windisk/windisk.img,ioemu:hda,w'' ] > > > on_poweroff = ''destroy'' > > > on_reboot = ''destroy'' > > > on_crash = ''destroy'' > > > device_model = ''/usr/lib/xen/bin/qemu-dm'' > > > cdrom=''/dev/cdrom'' > > > boot=''d'' > > > sdl=0 > > > vnc=1 > > > vncviewer=0 > > > stdvga=0 > > > serial=''pty'' > > > ne2000=0 > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > 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
thx SY, i saw the same link and was encouraged to keep pushing, Marcus
recommended to create an iso file instead of a cd-rom, which I tried, but
here''s my test results so far:
1. even the iso file - would reboot my server/box.
2. i created two iso files one for winxp and one for win2k3.
3. but i had another iso file w/ FC5 which worked fine.
4. now, heres a wierd one that i happened to come across
1. when i did the fc5 iso and then the winxp - it went to a
stage that i''m going to describe below.
2. when i did the fc5 iso and then the win2k3, it did not work -
i.e it rebooted my h/w.
5. so, based on 4.1 - i was able to make some progress and able to hit
F5 and I was able to select ''Standard PC''. And, as the note
in the link
suggested that it''ll be about 20mins to do its deed - I waited as
long. I
tried this a few times, and the last time I waited overnite, but it was
still stuck at the message the bottom left corner "Starting windows
system"
and did not make any progress i.e reboot as the note suggested it
would....
--
On 6/26/06, Sachiko Yoshihama <sachiko.yoshihama@gmail.com> wrote:
> Hi,
>
> I had the same problem that the machine reboots at Windows installation,
> when I was using 2.6.16-1.2133_FC5xen0.
> The problem does not happen on the latest 2.6.17-1.2139_FC5xen0.
> Perhaps you can update "kernel-xen0" and "xen" to the
latest version.
>
> The following mail archive is also very helpful.
> http://lists.xensource.com/archives/html/xen-users/2006-06/msg00452.html
>
>
> Sachiko
>
>
> On 6/26/06, pv <vishnubhatt@gmail.com> wrote:
> >
> > Tried that - same results, next is to go to xen-unstable and try it
> > there but when I do that, I''m getting into
other/maybe-unrelated startup
> > issues (excerpt from the xend.log):
> >
> >
> > [2006-06-25 12:57:20 xend] INFO (SrvDaemon:185) Xend exited with
status
> > 1.
> > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:285) Xend Daemon started
> > [2006-06-25 12:58:03 xend] ERROR (SrvDaemon:299) Exception starting
xend
> > ((22, ''Invalid argument''))
> > Traceback (most recent call last):
> > File
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py",
> > line 288, in run
> > xinfo = xc.xeninfo()
> > error: (22, ''Invalid argument'')
> > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:185) Xend exited with
status
> > 1.
> >
> > --
> >
> > On 6/25/06, Marcus Carlson <marcus@mejlamej.nu > wrote:
> > >
> > > Hi,
> > >
> > > Just a thought but, have you tried using an ISO file instead of
> > > /dev/cdrom?
> > >
> > > Marcus
> > >
> > > pv wrote:
> > > > BTW, this happens only when trying to launch native Windows,
but I
> > > > could install FC4, FC5 w/o any problems (and yes, VMXON is
done, i.e
> > > .
> > > > the platform does support hvm). Any ideas?
> > > > --
> > > >
> > > >
> > > > On 6/24/06, *pv* <vishnubhatt@gmail.com
> > > > <mailto: vishnubhatt@gmail.com>> wrote:
> > > >
> > > > As soon as the cd-rom kicks in, the machine reboots! Any
clues
> > > on
> > > > what I need to be doing next (I tried both windows XP
and 2k3)?
> > > >
> > > >
> > > > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP
Tue Mar
> > > 14
> > > > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux
> > > > 2. xen modules:
> > > > kernel-xen0-2.6.15-1.2054_FC5
> > > > xen-3.0.1-4
> > > > 3. My config file:
> > > > kernel = "/usr/lib/xen/boot/hvmloader"
> > > > builder=''hvm''
> > > > memory = 512
> > > > name = "winxp"
> > > > vcpus=1
> > > > pae=0
> > > > acpi=0
> > > > apic=0
> > > > cpus = ""
> > > > vif = [ ''type=ioemu,
bridge=xenbr0'' ]
> > > > disk = [
''file:/root/windisk/windisk.img,ioemu:hda,w'' ]
> > > > on_poweroff = ''destroy''
> > > > on_reboot = ''destroy''
> > > > on_crash = ''destroy''
> > > > device_model =
''/usr/lib/xen/bin/qemu-dm''
> > > > cdrom=''/dev/cdrom''
> > > > boot=''d''
> > > > sdl=0
> > > > vnc=1
> > > > vncviewer=0
> > > > stdvga=0
> > > > serial=''pty''
> > > > ne2000=0
> > > >
> > > >
> > > >
> > >
------------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > 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
Ok a reprise: The link from Marcus is great! I built my own xen-unstable (i had to change some of the install.sh to make sure that the python library is loaded correctly in the xend script) and it works! now to test out other wierdness + win2k3. but at least i was able to bring up a winxp system i.e. reach the other end of the tunnel so-to-speak. Thx everyone whoever chimed in to help and esply to Marcus and Sachiko for getting me to thru to the final pieces, -- On 6/26/06, pv <vishnubhatt@gmail.com> wrote:> > thx SY, i saw the same link and was encouraged to keep pushing, Marcus > recommended to create an iso file instead of a cd-rom, which I tried, but > here''s my test results so far: > > > 1. even the iso file - would reboot my server/box. > 2. i created two iso files one for winxp and one for win2k3. > 3. but i had another iso file w/ FC5 which worked fine. > 4. now, heres a wierd one that i happened to come across > 1. when i did the fc5 iso and then the winxp - it went to a > stage that i''m going to describe below. > 2. when i did the fc5 iso and then the win2k3, it did not work > - i.e it rebooted my h/w. > 5. so, based on 4.1 - i was able to make some progress and able to > hit F5 and I was able to select ''Standard PC''. And, as the note in the link > suggested that it''ll be about 20mins to do its deed - I waited as long. I > tried this a few times, and the last time I waited overnite, but it was > still stuck at the message the bottom left corner "Starting windows system" > and did not make any progress i.e reboot as the note suggested it > would.... > > -- > > On 6/26/06, Sachiko Yoshihama <sachiko.yoshihama@gmail.com> wrote: > > > Hi, > > > > I had the same problem that the machine reboots at Windows installation, > > when I was using 2.6.16-1.2133_FC5xen0. > > The problem does not happen on the latest 2.6.17-1.2139_FC5xen0. > > Perhaps you can update "kernel-xen0" and "xen" to the latest version. > > > > The following mail archive is also very helpful. > > http://lists.xensource.com/archives/html/xen-users/2006-06/msg00452.html > > > > > > > > Sachiko > > > > > > On 6/26/06, pv <vishnubhatt@gmail.com> wrote: > > > > > > Tried that - same results, next is to go to xen-unstable and try it > > > there but when I do that, I''m getting into other/maybe-unrelated startup > > > issues (excerpt from the xend.log): > > > > > > > > > [2006-06-25 12:57:20 xend] INFO (SrvDaemon:185) Xend exited with > > > status 1. > > > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:285) Xend Daemon started > > > [2006-06-25 12:58:03 xend] ERROR (SrvDaemon:299) Exception starting > > > xend ((22, ''Invalid argument'')) > > > Traceback (most recent call last): > > > File > > > "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, > > > in run > > > xinfo = xc.xeninfo() > > > error: (22, ''Invalid argument'') > > > [2006-06-25 12:58:03 xend] INFO (SrvDaemon:185) Xend exited with > > > status 1. > > > > > > -- > > > > > > On 6/25/06, Marcus Carlson <marcus@mejlamej.nu > wrote: > > > > > > > > Hi, > > > > > > > > Just a thought but, have you tried using an ISO file instead of > > > > /dev/cdrom? > > > > > > > > Marcus > > > > > > > > pv wrote: > > > > > BTW, this happens only when trying to launch native Windows, but I > > > > > could install FC4, FC5 w/o any problems (and yes, VMXON is done, > > > > i.e. > > > > > the platform does support hvm). Any ideas? > > > > > -- > > > > > > > > > > > > > > > On 6/24/06, *pv* <vishnubhatt@gmail.com > > > > > <mailto: vishnubhatt@gmail.com>> wrote: > > > > > > > > > > As soon as the cd-rom kicks in, the machine reboots! Any clues > > > > on > > > > > what I need to be doing next (I tried both windows XP and > > > > 2k3)? > > > > > > > > > > > > > > > 1. uname -a : Linux fc4 2.6.15-1.2054_FC5xen0 #1 SMP Tue > > > > Mar 14 > > > > > 16:23:33 EST 2006 i686 i686 i386 GNU/Linux > > > > > 2. xen modules: > > > > > kernel-xen0-2.6.15-1.2054_FC5 > > > > > xen-3.0.1-4 > > > > > 3. My config file: > > > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > > > builder=''hvm'' > > > > > memory = 512 > > > > > name = "winxp" > > > > > vcpus=1 > > > > > pae=0 > > > > > acpi=0 > > > > > apic=0 > > > > > cpus = "" > > > > > vif = [ ''type=ioemu, bridge=xenbr0'' ] > > > > > disk = [ ''file:/root/windisk/windisk.img,ioemu:hda,w'' ] > > > > > on_poweroff = ''destroy'' > > > > > on_reboot = ''destroy'' > > > > > on_crash = ''destroy'' > > > > > device_model = ''/usr/lib/xen/bin/qemu-dm'' > > > > > cdrom=''/dev/cdrom'' > > > > > boot=''d'' > > > > > sdl=0 > > > > > vnc=1 > > > > > vncviewer=0 > > > > > stdvga=0 > > > > > serial=''pty'' > > > > > ne2000=0 > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > _______________________________________________ > > > > > 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