similar to: Bug#588888:

On ia64 we have a desire to know the guest OS the user plans to run in an HVM domain. With this information we can make certain optimizations, for instance knowing if a guest identity maps a memory region can change how we handle page faults. In the past we''ve tried to do this via the guest firmware detecting the guest type, but this is error prone and doesn''t allow the user to

Greetings! I''ve got a FreeBSD-based (FreeNAS) appliance running as an HVM DomU. Dom0 is Debian Squeeze on an AMD990 chipset system with IOMMU enabled. The DomU sees six physical drives: one of them is a USB stick that I''ve passed through in its entirety as a block device. The other five are SATA drives attached to a controller that I''ve handed to the DomU with PCI

On Thursday 07 February 2008 05:19:26 pm Hamid Majidy wrote: > When I start guest with "xm create clientdom", I get: > xm create clientdom > Using config file "./clientdom". > VNC= 3 > Started domain clientdom >   > But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get: > VNC Viewer Free Edition 4.1.2 for X - built Mar 14

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

Hi, i''m a little bit stuck here with creating a HVM-Windows (w2k3) Guest under Xen 3.1. I''m using ubuntu 7,10 with a 2.6.22.16-xen-patched kernel which seems to be stable for single cpu-linux guests. Cpu is a Q6600 and XD,VT and VT-d is enabled in the bios. When i create the windows guest with ''xm create w2k3 -c" (conf below) I get: "Started domain

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

Hello, We are planning to install a Windows 2008 DomU in one of our servers (SUSE 10/SP2, XEN 3.2). Does someone have some experience in installing 2008 ? Are they some know problems (and solutions if possible) to success in thre process. Here is the setup we will use for that DomU : ------------------------------------------------------------------- # SR3 MV9 name="SAP-IDES-ECC"

I have an FC6 dom0 running on a headless server. I want to install a CentOS 4.4 domU with a console accessed using vnc from a remote machine. I *think* I should be able to do this from my understanding of the documentation. I''ve configured a domU to boot from an ISO image to do the CentOS install and run xm create. netstat on dom0 shows there''s a listener on 0.0.0.0:5900, but

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

Has anyone been able to get a Xen Windows domU to install or work properly on CentOS 5? I'm trying to do that now. It's able to boot and start he installation (from ISO), but after partitioning the disk and copying a few files to the hard drive, it cannot boot into the graphical installer. This is the config file I'm using: import os, re arch = os.uname()[4] if

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

Trying to install Debian Lenny amd64 from netinst cd on Xen HVM, the computer hangs and needs to reset physically. My computer supports HVM, I''ve a HVM Windows XP installed with no problems. Other ways to install Lenny on HVM are welcome. I tried with debootstrap, but it doesn''t boot disk image :-( My config is: import os, re arch = os.uname()[4] if

Dear all, In case of someone else is trying to do the same configuration as mine, I stated below the steps to configure HVM and PV''s domains to use FIXED VNC Ports (instead of having Xen automatically assign one unused port based on domain id): For HVM''s: vnc=1 # Enable VNC vncconsole=0 # Don''t start vncviewer after "create" the

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

Hi. I am trying to run Solaris 10 under Xen but I have few problems. First of all, there are some weird errors while booting up system. Here is a screenshot: http://kosjenka.srce.hr/~jsosic/xen-solaris10u8.png Messages are these: WARNING: xdf: couldn''t write version WARNING: xdf: couldn''t write version WARNING: Disk is too large: Model QEMU HARDDISK Serial# QM00002 NOTICE:

Greetings all, I''m having an issue getting a winxp hvm running. It will install just fine from iso, but then when I change the .cfg file to boot from ''c'', it will give me: invalid boot.ini file booting from c:\windows ntdetect failed Please see the below config file: import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir =

Hello, With kernel 3.4.0 as a dom0 and a 3.3.6 as a domU, i get the following oops on the dom0 kernel when I rsync / to a filesystem mounted on a loop device: http://77.36.72.222/P5230845.JPG The domU config: ierdnac-hp ~ # cat /mnt/gentoo/xen kernel = "/boot/vmlinuz-3.3.6-pf-c241.old" name="gentoo" memory = 2048 vcpus = 1 pae = 1 acpi = 1 apic = 1 stdvga=0

Hi, My Xen 3.2 does not boot. Its stuck at "Freeing unused kernel memory: 148k freed". I used a FC8 distribution from jailtime.org. My kernel is built using make KERNELS= # xm console src-fc-01 xen-vbd: registered block device major 8 blkfront: sda1: barriers enabled blkfront: sda2: barriers enabled netfront: Initialising virtual ethernet driver. vif vif-0: 2 parsing device/vif/0/mac

Hi, gang. I''m having major issues with getting the VNC consoles to accept keystrokes. I''m trying to get Windows 2003 Server SP2 to run as a fully-virtualized guest. I get the VNC window for the installer, but I can''t get it to accept any keystrokes (e.g. hitting the F5 so I can tell it to use a standard PC HAL). If I opt to use SDL, I get no console at all.

Hello community! I need help with a problem I haven''t been solved with the network team. I manage a network that has over a thousand computers, and the most of the servers are virtualized over Debian / Xen by me. The specific issue arises when I try to set up a DomU HVM running Debian Squeeze, the VM doesn''''t recognize the network but it runs. It gives an error