Xen users - Jan 2009 - Windows 2K3 HVM constantly crashing on install (Etch, Xen 3.0.3)

Hi All,
I''m having a problem getting this HVM to stay up after boot, if anyone
can
offer assistance it''d be great.
It will start ok, then boot off the CD to install windows but once the
Windows install loads its setup drivers and gets to the partition selection,
the domU crashes and reboots.

Here is the config;
kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
device_model = "/usr/lib/xen-3.0.3-1/bin/qemu-dm"
builder=''hvm''
name = "prod-com-04"
vif = [ ''mac=00:50:56:0F:C2:25'' ]
memory = 1024
shadow_memory = 8
disk = [ ''phy:/dev/eddie/com-04,hda,w'' ,
''file:/mnt/archive/win_2k3.iso,hdc:cdrom,r'' ]
boot="d"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''''
serial=''pty''
usbdevice=''tablet''
acpi = 1
apic = 1

I''ve tried using a local disk image as well as the LV setup above but
with
no luck. Same again with sda instead of hda.

I''m not sure if it matters, but the LV is setup over iSCSI, I have some
other Etch based hosts that work fine and the Dom0 is not having any issues
with the iSCSI setup.

Thanks,
Mark


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I tried to run up a WinXP install to see if that would help and it does to a
degree.
I can partition the disk fine and setup copies files, but as soon as the
install reboots it won''t continue into Windows to finalise the install
procedure.

All I am seeing in the logs is this from xend-debug.log;
Traceback (most recent call last):
  File "SocketServer.py", line 463, in process_request_thread
    self.finish_request(request, client_address)
  File "SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "SocketServer.py", line 521, in __init__
    self.handle()
  File "BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "BaseHTTPServer.py", line 310, in handle_one_request
    method()
  File "/usr/lib/xen-3.0.3-1/lib/python/xen/util/xmlrpclib2.py", line
66, in
do_POST
    self.send_response(200)
  File "BaseHTTPServer.py", line 367, in send_response
    self.wfile.write("%s %d %s\r\n" %
  File "socket.py", line 248, in write
    self.flush()
  File "socket.py", line 235, in flush
    self._sock.sendall(buffer)
error: (32, ''Broken pipe'')

And this from xend.log;
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) Waiting for devices
vif.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) Waiting for 0.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vif/31/0/hotplug-status.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vif/31/0/hotplug-status.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) Waiting for devices
usb.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) Waiting for devices
vbd.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) Waiting for 768.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/31/768/hotplug-status.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/31/768/hotplug-status.
[2009-01-07 15:07:20 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for 5632.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/31/5632/hotplug-status.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
/local/domain/0/backend/vbd/31/5632/hotplug-status.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) hotplugStatusCallback
1.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for devices
irq.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for devices
pci.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for devices
ioports.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for devices
tap.
[2009-01-07 15:07:21 xend 4170] DEBUG (__init__:1072) Waiting for devices
vtpm.
[2009-01-07 15:07:21 xend 4170] INFO (__init__:1072) Domain winxp (31)
unpaused.

I think my next option is to try backports and move to 3.2.1.

2009/1/5 Mark Walkom <markwalkom@gmail.com>
> Hi All,
> I''m having a problem getting this HVM to stay up after boot, if
anyone can
> offer assistance it''d be great.
> It will start ok, then boot off the CD to install windows but once the
> Windows install loads its setup drivers and gets to the partition
selection,
> the domU crashes and reboots.
>
> Here is the config;
> kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
> device_model = "/usr/lib/xen-3.0.3-1/bin/qemu-dm"
> builder=''hvm''
> name = "prod-com-04"
> vif = [ ''mac=00:50:56:0F:C2:25'' ]
> memory = 1024
> shadow_memory = 8
> disk = [ ''phy:/dev/eddie/com-04,hda,w'' ,
> ''file:/mnt/archive/win_2k3.iso,hdc:cdrom,r'' ]
> boot="d"
> sdl=0
> vnc=1
> vncconsole=1
> vncpasswd=''''
> serial=''pty''
> usbdevice=''tablet''
> acpi = 1
> apic = 1
>
> I''ve tried using a local disk image as well as the LV setup above
but with
> no luck. Same again with sda instead of hda.
>
> I''m not sure if it matters, but the LV is setup over iSCSI, I have
some
> other Etch based hosts that work fine and the Dom0 is not having any issues
> with the iSCSI setup.
>
> Thanks,
> Mark
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users