WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Windows 2003 DomU reboots sentire erver on create

I was using the Gentoo version which is 3.0.2.  I did realize it looks
like XWindows is required for installing Windows, so I am installing
that now.  I didn't realize that, I was trying to run it from a console.

You could probably run without X if you exported the Windows guest's display over VNC.

It still seems odd it would reboot the server as opposed to failing with
an error, however.

Indeed. That's definitely a bug, no question about it. However, it's quite possibly been fixed in a later Xen release. The version of Xen you're running is fairly old and there have been fixes to the HVM code since then. I really would recommend you download 3.0.4 and try that in place of the stock Gentoo version - you'd have a better chance of it working.

I was planning on 32 bit Windows.  I had read you could still run 32bit
versions of DomU on a 64bit Dom0.  I'd like to keep Dom0 at 64bit for
options with memory for the future.

That's fine. You can run 32-bit, or 32-bit with PAE guests on a 64-bit Xen/dom0.

Cheers,
Mark


-----Original Message-----
From: M.A. Williamson [mailto:maw48@xxxxxxxxxxxxxxxx] On Behalf Of M.A.
Williamson
Sent: Wednesday, December 27, 2006 6:35 PM
To: Kriz, Mike
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Windows 2003 DomU reboots sentire erver on
create

I'm trying to get a Windows 2003 domu running, and I'm having
difficulties.  Any help would be much appreciated!  About the server:
It's an IBM x series running AMD64, x64 install of Gentoo Linux.

I have it up and running with a pretty standard Xen 3.0 install, and
the
Linux domUs work perfectly.

When I try to start Windows 2003, the whole server completely reboots.
I am following the Xen Windows Howto PDF.

This is definitely some kind of bug in your version of Xen.

What point release are you installing? i.e. 3.0.[01234] or -unstable?
I'd recommend upgrading to the latest release (which is 3.0.4) to test whether your problem still occurs.

Also, you're presumably installing 64-bit Win 2k3? If you were to try a 32-bit install I have a hunch it'd work OK. I realise that probably doesn't solve your problem though... Last I remember, 64-bit support for Windows

was a bit less mature than 32-bit support, so presumably there may still
be some kinks.

We may want to take this to the xen-devel list as a bug, if we can't
work out some other solution. Good luck in the meantime!

Cheers,
Mark


Here's a basic config I am using that is based on the howto, other then
that I am using a file as the filesystem rather then an LVM:

kernel = '/usr/lib64/xen/boot/hvmloader'
builder='hvm'
memory = 512
name = 'winxendefault'
vif = [ ' ' ]
disk = [ 'file:/xen_fs/win2k3_1,hda,w' ]
cdrom='/xen_images/win2k3_cd.iso'
boot='d'
sdl=1
vnc=0
vncviewer=0
device_model = '/usr/lib64/xen/bin/qemu-dm'

Here is some debug output from the crash in xend.log:

[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create(['vm', ['name', 'winxendefault'], ['memory',
512],
['vcpus', 1], ['
image', ['hvm', ['kernel', '/boot/vmlinuz-2.6.16.28-xenU'],
['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['vcpus', 1], ['cdrom',
'/xen_images/win2k3_cd.iso
'], ['boot', 'd'], ['sdl', 1], ['xauthority', '/root/.Xauthority']]],
['device', ['vbd', ['uname', 'file:/xen_fs/win2k3_1'], ['dev', 'hda'],
['mode', 'w']]],
['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:00:00:94'],
['type', 'ioemu']]]])
[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
parseConfig: config is ['vm', ['name', 'winxendefault'], ['memory',
512], ['vcpus', 1], [
'image', ['hvm', ['kernel', '/boot/vmlinuz-2.6.16.28-xenU'],
['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['vcpus', 1], ['cdrom',
'/xen_images/win2k3_cd.is
o'], ['boot', 'd'], ['sdl', 1], ['xauthority', '/root/.Xauthority']]],
['device', ['vbd', ['uname', 'file:/xen_fs/win2k3_1'], ['dev', 'hda'],
['mode', 'w']]],
['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:00:00:94'],
['type', 'ioemu']]]]
[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:380)
parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash':
None,
'on_reboot': Non
e, 'image': ['hvm', ['kernel', '/boot/vmlinuz-2.6.16.28-xenU'],
['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['vcpus', 1], ['cdrom',
'/xen_images/win2k3_cd
.iso'], ['boot', 'd'], ['sdl', 1], ['xauthority',
'/root/.Xauthority']],
'on_poweroff': None, 'cpus': None, 'name': 'winxendefault', 'backend':
[], 'vcpus': 1
, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 512, 'device':
[('vbd', ['vbd', ['uname', 'file:/xen_fs/win2k3_1'], ['dev', 'hda'],
['mode', 'w']]), ('vif
', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:00:00:94'], ['type',
'ioemu']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.construct: None 0
[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
XendDomainInfo.initDomain: 2 1.0
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: cdrom, val:
/xen_images/win2k3_cd.iso
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: boot, val: d
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: fda, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: fdb, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: nic-ne2000, val:
None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: enable-audio, val:
None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: localtime, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: serial, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: std-vga, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: isa, val: None
[2006-12-27 10:53:05 xend] DEBUG (image:266) args: vcpus, val: 1
[2006-12-27 10:53:05 xend] DEBUG (balloon:130) Balloon: free 7; need
513.
[2006-12-27 10:53:05 xend] DEBUG (balloon:139) Balloon: setting dom0
target to 4017.
[2006-12-27 10:53:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:945)
Setting memory target of domain Domain-0 (0) to 4017 MiB.
[2006-12-27 10:53:06 xend] DEBUG (balloon:126) Balloon: free 513; need
513; done.
[2006-12-27 10:53:06 xend] INFO (image:135) buildDomain os=hvm dom=2
vcpus=1
[2006-12-27 10:53:06 xend] DEBUG (image:224) dom            = 2
[2006-12-27 10:53:06 xend] DEBUG (image:225) image          =
/boot/vmlinuz-2.6.16.28-xenU
[2006-12-27 10:53:06 xend] DEBUG (image:226) store_evtchn   = 1
[2006-12-27 10:53:06 xend] DEBUG (image:227) memsize        = 512
[2006-12-27 10:53:06 xend] DEBUG (image:228) vcpus          = 1
[2006-12-27 10:53:06 xend] DEBUG (image:229) pae            = 0
[2006-12-27 10:53:06 xend] DEBUG (image:230) acpi           = 0
[2006-12-27 10:53:06 xend] DEBUG (image:231) apic           = 0
[2006-12-27 10:53:06 xend] DEBUG (image:396) hvm shutdown watch
registered
[2006-12-27 10:53:06 xend.XendDomainInfo] ERROR (XendDomainInfo:190)
Domain construction failed
Traceback (most recent call last):
 File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 183, in create
   vm.initDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1225, in initDomain
   channel_details = self.image.createImage()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
118,
in createImage
   return self.createDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
137,
in createDomain
   result = self.buildDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
242,
in buildDomain
   apic           = self.apic)
error: (0, 'Error')
[2006-12-27 10:53:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
XendDomainInfo.destroy: domid=2
[2006-12-27 10:53:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(2)
[2006-12-27 10:53:06 xend] DEBUG (image:408) hvm shutdown watch
unregistered
[2006-12-27 10:53:06 xend] ERROR (xmlrpclib2:98) (0, 'Error')
Traceback (most recent call last):
 File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py",
line
80, in _marshaled_dispatch
   response = self._dispatch(method, params)
 File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 406, in
_dispatch
   return func(*params)
 File
"/usr/lib64/python2.4/site-packages/xen/xend/server/XMLRPCServer.py",
line 63, in domain_create
   info = XendDomain.instance().domain_create(config)
 File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py",
line
227, in domain_create
   dominfo = XendDomainInfo.create(config)
 File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 183, in create
   vm.initDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1225, in initDomain
   channel_details = self.image.createImage()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
118,
in createImage
   return self.createDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
137,
in createDomain
   result = self.buildDomain()
 File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line
242,
in buildDomain
   apic           = self.apic)
error: (0, 'Error')


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended
recipient
or an authorized representative of the intended recipient, you are
hereby
notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

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



This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.


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