similar to: domU with no fstate lags in "xm list"

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

Hi folks, i have a problem to boot an Ubuntu CD in a hvm-enabled machine. I get a black screen when connecting via vnc to the virtual machine. When i change the line cdrom= to some other CD (grml Live CD, Windows CD, other ones) it runs fine. But any Ubuntu CD (kubuntu alternative, ubuntu server, ubuntu desktop) i get the mentioned error. I tried using sdl (no window opens) and with

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

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 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 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

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 = [

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

Hello! I''me run windows 2008 server in Debian etch amd64 8 gb memory. if given > 2gb memory to w2k8. dom0 is down. In no logs anything interesting. configs: (logfile /var/log/xen/xend.log) (loglevel DEBUG) (network-script ''network-virtual bridgeip="172.16.16.1/24" brnet="172.16.16.0/24"'') (vif-script ''vif-bridge

I have loaded FC6 with the virtualizations kernel, and I am attempting to load WinXP. I searched all the logs and docs and configured what I think is correct based on these. When I do an xm create dfw11286lv1.hvm, I get the following messages: Using config file "dfw11286lv1.hvm". Started domain dfw1128glv1 However, I never get a window with the installer. Also, when I open the

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

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

Hello everyone, I grabbed xen-3.3.1 sources from the Mercurial repository (xen-3.3-testing.hg, changeset 475:1cf755387728, from Oct. 23, 2008) and built Xen from these sources on a 32-core (8 quad core Barcelona CPUs) SunFire machine, running an Ubuntu 8.04 (Hardyy Heron) distribution. Everything seemed to be going OK until I booted an HVM (also Ubuntu 8.04) domain. That domain boots normally but

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

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

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

Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM

Hallo, if I try to PXE-boot a debian/ubuntu/clonezilla/debianlike live CD (with a directory "live", just for recognising this type) via LABEL clonezilla MENU LABEL ^Clonezilla (iso) kernel memdisk append iso initrd iso/clonezilla.iso that doesn't work: This Debian Live image failed to boot. ... ... The error message was Unable to find a medium containing a

> * Gene Cumm, 2014-06-10 : > > > If 4.05 or 3.86 acted nicely, this would mean a bug. > > OK, so, with unpatched official binaries: > > 3.86 > ---- > > pxelinux.0 > Loads fine, assumes terminal width 15, displays menu, but then freezes > (I suspect it does not process any input from the serial port) > > gpxelinux.0 > Displays: >

> > Anyway, in the F12 boot menu there is no clear indication of what thing > (or things) the BIOS thinks are or not present. (What made you think > that there would be?) > In some systems, in the BIOS F12 boot menu, when I have one internal SATA drive and one USB flashdrive connected, I could see them *both* under HDD, while under USB-HDD there is no device listed for the