[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] SVM: Windows install Black Screen


  • To: "Jess Mahan" <jess@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Fri, 3 Nov 2006 11:02:45 +0100
  • Delivery-date: Fri, 03 Nov 2006 02:06:43 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acb+tdOptoghhyuJR3alM4NKHBINMgAePv4g
  • Thread-topic: [Xen-users] SVM: Windows install Black Screen

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jess Mahan
> Sent: 02 November 2006 19:32
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] SVM: Windows install Black Screen
> 
> Hi,
> I've been attempting to install Windows XP SP2 in an HVM DomU.
> 
> I'm running Debian testing with xen-testing (3.0.3) on an AMD X2 64
> (AM2).
> 
> The initial install of Windows is perfect, everything install 
> without a
> hitch (no more need for the F5 trick). However once the 
> installation is
> complete and windows "boots" for the first time after installation, I
> see the qemu bios, then the VNC window size changes (as if windows is
> changing the resolution), and it hangs at a black/blank screen. xm top
> reports: CPU(sec) 1, CPU(%) = 0.0
> 
> I've tried this with many different settings in my hvm config: every
> conceivable combination of the pae, acpi, and apic settings. I've also
> tried NTFS and FAT during the install.
> 
> If I set the pae, acpi, and apic all to zero, I get the qemu bios, and
> then a blank screen again, however the VN window size does not change,
> and xm top reports: CPU(SEC) 201, CPU(%) = 99.0. So I can see 
> that there
> is some sort of race condition.
> 
> Has anyone had a similar issue or have any insight as to what the
> problem may be?

First of all do "ps ax|grep qemu" to see if you still have a living QEMU
in the system. If not, try to see if /var/log/xen/qemu-dm*.log has
anything of interest in it (look for the latest one with "ls -ltr
/var/log/xen/qemu*"). 

There's all sorts of possible reasons here, so it's hard to say what
could be wrong... But it seems like your BIOS isn't quite working. 

It would probably also make sense to build Xen with "debug=y" and
connect a serial line to see if there's anything "unusual" being caught
by the debug code. 

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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.