Hi all,
I've been trying to install Windows Server 2008 R2 under Xen 3.1 on
Red Hat, but it keeps blue screening after the first reboot during the
install. It seems to only affect 2008 R2. Windows Server 2008
installs fine, rebooting a couple of times along the way.
With R2, it will go through the initial unpack and install, and then
it reboots. I'm installing it with virt-manager and I can watch it
try to restart the guest, but unsuccessfully. xend-debug reports this
(a lot):
Exception in thread Thread-50540:
Traceback (most recent call last):
File "/usr/lib64/python2.4/threading.py", line 442, in __bootstrap
self.run()
File "/usr/lib64/python2.4/threading.py", line 422, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendDomainInfo.py", line 1295, in maybeRestart
{"destroy" : self.destroy,
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendDomainInfo.py", line 2557, in restart
config = self.sxpr()
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendDomainInfo.py", line 1660, in sxpr
self.getDiskConfigurations()))
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendDomainInfo.py", line 1630, in getDiskConfigurations
config = vbd.configuration(disk)
File "/usr/lib64/python2.4/site-packages/xen/xend/server/blkif.py",
line 119, in configuration
result = DevController.configuration(self, devid)
File "/usr/lib64/python2.4/site-packages/xen/xend/server/
DevController.py", line 251, in configuration
raise VmError("Device %s not connected" % devid)
VmError: Device 768 not connected
I'm wondering if anyone has had similar issues... I'd probably be
okay with going with just 2008, but there was a big security patch
release with R2 and I'd prefer to use it.
Many thanks in advance,
...adam
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home