similar to: virtual machines refuse to start up

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

Anybody out there running Windows XP, Windows XP SP2 or Windows 2003 server with the default XEN 3.0.3 on Ubuntu Feisty ? Have Ubuntu Feisty Dom0 with a number of Ubuntu 6.1/7.04, Debian and FC6 DomUs all working lovely. But it will not work for any windows versions. The install gets as far as the blue "Setup is Starting Windows" screen. Intel VT extensions are enabled and the F5 trick

Hi, I''m kinda new to XEN stuff, and I''ve been trying to create a fully virtualized guest on CentOS 5.3 for almost 3 months and no luck yet. I approached this process through several methods, one with virt-install and creating config file manually. Following is what happens when I try to create a guest, and I have included qemu-dm and last part of xend.log logs below too.

Hi I m trying to install a full virtualized guest on my dell poweredge 1950 with centos 5.1 64 bits. I just launched the following command virt-install -n elaphe -r 4096 -f /var/lib/xen/images/elaphe -s 40 -b vlanbr15 --hvm Would you like to enable graphics support? (yes or no) yes What is the virtual CD image, CD device or install location? /var/lib/xen/F-7-i386-DVD.iso Starting

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"

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

Hi, I am trying to install Windows 2003 server as a guest OS in Centos 5 Xen and installation is freeze , i am attaching screen shot, here is xend log file details [2007-10-29 17:04:11 xend.XendDomainInfo 3413] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'testwin'], ['memory', '1024'], ['maxmem', '1024'],

I am running Pentium D 930 with 2 gigs of ram. Fedora Core 6 with Xen enabled. I am able to start the install and it goes to the first stage of needing to be rebooted. I restart the Domain and it starts to finalize the windows install. And is fine until it starts asking for serial numbers or computer names. Then all of a sudden the guest freezes. The guest CPU goes to zero and so does the

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

Hi, I''m running a two node xen-Cluster with CentOS 5.3. I''m using gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP for Dom0 (xen 3.0.3). Live migration works fine as long as the DomU guest is running CentOS 5.3 or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is running the current 2.6.9-78.0.17.EL.cern kernel, the migration

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =

Hi Everyone, I''m trying to get Xen to use a native DRBD device but it seems it will not create the virtual machine. It does not seem to like the DRBD device type, any ideas on what might be wrong? I''m pretty sure my xen config file is OK and the DRBD device looks fine too. Full details below. xm create centostest Using config file "./centostest".

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

Hello, I''m running 6.26-2-xen-amd64 with xen-hypervisor-3.2-1-amd64. Now I try to pass through a controller card to WHS, at the moment without success because the card isn''t present in DomU. At the first moment I guess it''s a windows problem ;) so I''d tried to boot a Knoppix .iso but same problem there, the passed through device isn''t present in DomU.

Hi all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

Hi, since I upgraded from Lenny, DRBD VBD scripts not works at all. This config works : disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ] But his one doesn't work at all : disk = [ 'drbd:ads-disk,xvda,w' ] I obtain this error : # xm create ads.cfg Using config file "/etc/xen/ads.cfg". Error: Device 51712 (vbd) could not be connected. Hotplug scripts