Re: [Xen-users] Windows HVMs No Longer Run

Nick Couchman
2008-05-29T03:22:39Z

Well, the issue actually ended up being some sort of incompatibility between the
version of the GPL PV drivers I had installed and Xen 3.2.  Novell''s
drivers also don''t seem to work, anymore - if I try to use those I get
a BSOD with STOP error 0x00000C2 (BAD_POOL_CALL) or 0x00000007 (some IRQ issue -
only seen this one once or twice).  Without any PV drivers installed, things
seem to work fine, though at a slower pace.  The xenbr108 is a bridge
I''ve explicitly created for one of my VLANs, so I know that is correct.

Thanks,
Nick

>>> On 2008/05/28 at 19:13, jim burns <jim_burn@bellsouth.net>
wrote:
On Thursday May 22 2008 02:41:46 pm Nick Couchman wrote:
> Okay, just upgraded to SLES10 SP2 which has XEN version 3.2.  By and large
> things are working much better, with the exception that I can no longer run
> Windows-based HVMs.  The HVM domUs start, the Windows boot screen loads,
> but when they go to switch to the graphical console, they just hang and eat
> the CPU.  There are no other clues - no messages in dmesg or xm dmesg or xm
> log.  Attached is one of the qemu-dm*.log files from one of the domains
> that''s currently eating as much CPU as Xen will allow.  Also
attached is
> the config file for that domU.

The only thing that looks suspicious is the ''bridge=xenbr108''
option. (You
also don''t need the trailing '','' in
''disk='' either.) One of the things that
changed in 3.2 is the default bridge is eth0, same as the non-xen net
interface. Check ''brctl show'' to make sure that your bridge is
actually being
created, and which bridge shown has peth0 (the xen physical interface) in it.

Something else you could try is create a test Windows domain, and compare the
config created to the one you have.




This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.