similar to: Kernel types and xen caps : PV/HVM, 32/64 bit, PAE/non-PAE

I installed a 32 bit Windows 2003 enterprise edtion domU. xm list shows the domU has 7G RAM. But Windows 2003 shows only 3.75G RAM. I do not know what''s wrong. Anyone knows? [root@sjd-hot w2k3e]# xm info host : sjd-hot.rashost.com release : 2.6.18.8-xen version : #1 SMP Fri Nov 27 03:53:01 UTC 2009 machine : x86_64 nr_cpus

I''m trying to install RHEL 4 on an HVM (Core 2 Duo). However, when the RHEL installer tries to start the kernel, it complains that the CPU doesn''t support extended mode, and that I should use a 32-bit installer. However: hrm@willow:~$ sudo xm info | grep xen_caps xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Is there some magic I

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.

Hi, I''m now blocked for 2 days on getting the network to work in my domU. Here is the problem : The domU refuses to start when a vif is configured. It''s just staying paused for about 1m40s, then the xm create command line give back with an "Error: Device 0 (vif) could not be connected. Hotplug scripts not working.", and the domU is destroyed. Nothing particular

Hi, I have been trying to create a xen HVM Centos4.4 image on centos 5 with a DRBD filesystem installing from DVD. However I get an IO error on the filesystem during the centos installation process which then aborts. The DRBD filesystem seem to be setup correctly and is functioning as a block device as I can mkfs -t ext3 /dev/drbd1 read and write without error. If I replace the disk

I just downloaded Debian Squeeze and installed Xen from packages, following the instructions here: http://wiki.debian.org/Xen I am able to get PV guests up and running easily, but HVM guests will not even boot. The HVM I am currently trying to run is Debian sarge, which I installed into a disk image and configured using qemu. I am running on an HP Proliant ML150G6, which has Intel-VT hardware

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

I''ve been trying to compare memory access speed between bare-metal, xen-pv and xen-pvhvm (hvm with pv drivers). In all 3 setups I''m running the same kernel (3.6.6), built with support for xen, on a 64 core AMD Opteron 6378. The output of xm info (relevant parts): machine : x86_64 nr_cpus : 64 nr_nodes : 8 cores_per_socket : 16

Hi -- I wanted to boot s10 HVM in 64-bit mode but it always boots in 32-bit mode. Is there a special grub entry to boot s10 HVM domU in 64-bit mode? Or is it HVM loader? The grub entry is like this title Solaris 10 5/08 s10x_u5wos_01 X86 kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive s10.py file is as follows :- import os, re arch = os.uname()[4] if

Hello. I''m trying to set up hvm for linux or windows. I start with a very simple configuration without disks at all. but the virtual machine does boot or even "power up". If i remove the ioemu from the network device and specify type=brige or type=route everything goes fine, the boot process is starting but then I cant get network working in the guest.

Just successfully installed SLES9.3-32bit as file-backended HVM domU. Everything went OK, the distributive partitioned its "harddisk" into root and swap OK, have its grub installed into sda boot sector, but I could not make to boot no one single first time after installation. Every domU boot gives the following screen for a short time and dies: Booting from Hard Disk... Boot from

Hi, I''ve been trying to boot from a RHEL4 install iso without much luck (the xen way). The Host is: RHEL 5.1 xen-3.0.3-41.el5 Here is my guest config: # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using

Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for

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, I have some trouble to create hvm machines. Xen just tell me that the domain creation failed: # xm create /etc/xen/xenwin2008 Using config file "/etc/xen/xenwin2008". Error: Creating domain failed: name=xenwin2008 The last time i had this error there was some trouble with ne vif line, but the configuration worked perfectly until I had to restart my system (and change the netmask

Hi All, Sorry if this is a stupid question. I am walking into someone else''s xen install, and don''t have access to the host os at the moment. How do I tell just from a domU (with Ubuntu) if it is PV or HVM. I have looked through the forums and documentation and it seems to be very easy to figure this out from dom0, but unfortunately that isn''t possible at the

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting following error. I tried doing googling but none of suggested solution is working for me. Please guide me through my first experience with xen.for more details please see

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,