similar to: black screen when booting ubuntu cd in hvm

Hello. Trying 3.0.3 xen with hvm virtualization it run into an issue that an win 2003 host does install in text mode, but after first reboot only a black screen is greeting me ( after 2 noticable resolution changes ). Win 2000 works fine. hvm config: import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else:

Hello, I want to install a 2003 guest on a Debian Etch with xen binary packages (apt-get install), but through a vnc console (no graphical interface). So I launch the xm create in an ssh connection, and want to connect through vnc to complete the installation of windows. So the domain gets created with xm create but no VNC port is displayed: ----- Using config file "2003.hvm". VNC= 1

Greetings xen gurus... I''m working with xen-3.0-testing downloaded on July 3, 2006. I have configured an hvm domain and want to use vif-route and network-route to configure the communication. The domU starts up fine. I was able to complete the installation of the OS (RHES3) and can restart the domain repeatedly. However, I cannot ping the network interface from dom0 using the

Hi,   We've deployed Xen 3.0.2-2 successfully on a CentOS 4.3 installation running on a Dell PE 2950 servers. On a HVM/VMX guest also running CentOS 4.3 with the configuration below, we see occasional DMA messages in the guests dmesg output, they don't occur often and for no obvious reason - it seems they normally occur when the load on the host system is low.   hda: dma_timer_expiry: dma

Hi I`m trying to start win2k3R2 in XEN with this config # grep -v ^# /etc/xen/win2k3.hwm | grep -xv '''' import os, re arch = os.uname()[4] if re.search(''64'', arch):     arch_libdir = ''lib64'' else:     arch_libdir = ''lib'' kernel = "/usr/lib/xen-3.2-1/boot/hvmloader" builder=''hvm'' memory = 1024 name =

I have XEN 3.0.2_09749-0.4 on Linux t60 2.6.16.21-0.8-xen #1 SMP my w2k3.hvm: import os, re arch = os.uname()[4] arch_libdir = ''lib'' kernel = ''/usr/lib/xen/boot/hvmloader'' builder=''hvm'' memory = 512 name = "w2k3-001" vif = [ ''type=ioemu, mac=00:16:3e:00:00:94, bridge=xenbr0'' ] disk = disk = [

Hi all, I now have Xen running on Intel Core2 duo system, and am running a HVM domU with Microsoft Windows XP Home Edition, cold-installed from distribution CD. Problem is, Windows can''t get to the network. My dom0 ifconfig looks correct, as far as I can tell. I have a DHCP server on my local network, but the Windows XP domU claims to be unable to find DHCP. I''ve also tried

Hi all, Anybody know what it means for a DomU to show up in the "xm list" as follows: Name ID Mem VCPUs State Time(s) Domain-0 0 256 2 r----- 43929.3 Clonezilla 16 512 1 ------ 6.2 The domU "Clonezilla" does not have an "r" state

stubdom: add example config file Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r e69570f85e85 tools/examples/stubdom-ExampleHVMDomain --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/examples/stubdom-ExampleHVMDomain Thu Jul 17 19:31:13 2008 +0100 @@ -0,0 +1,21 @@ +# Not to be started directly, +# See xmexample.hvm-stubdom and stubdom/README for more details

Surely you hear plenty about what''s not working, so I thought I''d shoot a quick message on something that did work. I got Windows Server 2008 RC2 installed. I have yet to even activate it and prove all internal features/devices work, but installation alone satisfied me! I had to fight a couple issues and I''ll mention them here, i think they''d be pretty

Hello, I''m trying to get my first HVM domU installed (another Debian domU is already working under the same dom0). I intend to install the guest OS from a bootable CD-ROM. But when I create the new HVM domU with ''xm create xp1-cd.cfg'' , I don''t get the expected installation-window and find this in /var/log/xen/qemu-dm.6575.log: domid: 6 qemu: the number

Hello, I am currently using a Dell Poweredge SC 1435 at the moment and am trying to virtualize windows on xen however it seems windows does not really understand what its supposed to do. Anyone have an idea what could be the problem I think there is something windows doesn''t understand from the virtualized hardware. With WinXP I get a black screen on reboot (with a grey bar at

Hi koonz I noticed that you are using the cdrom parameter in the config file I believe that''s no longer used in recent versions of Xen. I am running debian etch here atm and am trying to virtualize windows guests aswell I am able to boot up windows with the following configs although they do tend to hang at some point during the installation. ----- Config windows xp ----- import os,

All, We are facing some issues bringing up a DomVT on Xen x86_64(changeset 9267). We created a disk image with dd 8 G in size. We then booted an associated Dom-VT with a CD-ROM and did net-install of the sles-9 OS. This completes successfully. Then, when the system is brought around for a reboot (having changed the boot option from cdrom to disk), the system hangs after the line

I have a self built system using an Intel D 920 processor and a MB that supports VT. I''m able to run HVM domains fine, but have trouble getting multiple VCPUs for these domains. Here is an example of one of my configs. # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. #

Hi First of all I want to say I''m new to xen so please be patient. I want to run xen on a PentiumD Dual with Vanderpool. I use OpenSuse 10.1 as Hostsystem. VM settings: disk = [ ''phy:/dev/hda5,ioemu:hda,w'' ] memory = 256 vcpus = 2 builder = ''hvm'' device_model = ''/usr/lib/xen/bin/qemu-dm'' kernel =

hi xen-list, i have installed xen-3.3.1 from source on a core2duo. the xen kernel boot fine. i create a file image with dd and a simple domU config file for windowsXP: import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader"

Hi. I am trying get use xen vmx, it shows only black window. I attach my config and logs. config: import os, re arch = os.uname()[4] if re.search(''64'', arch): else: kernel = "/usr/lib/xen/boot/vmxloader" builder=''vmx'' memory = 128 name = "bluszcz" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [

Hi Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and Xen package (NOT unstable or debug). When start, a window pops up for few seconds.. then it dies and another one comes up... and it disappears too. (Xen is trying to restart and giving up because the restart happens in 2 seconds..) It seems DomU is not able to read/understand something from Cirrus VGABIOS.

Hi Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and Xen package (NOT unstable or debug). When start, a window pops up for few seconds.. then it dies and another one comes up... and it disappears too. (Xen is trying to restart and giving up because the restart happens in 2 seconds..) It seems DomU is not able to read/understand something from Cirrus VGABIOS.