similar to: booting an ISO inside Xen (full virt)

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'],

In spite of reading howtos and this mailing list now for several weeks, I am still not able to get the network of my winXP guest connected to the host (opensuse 10.2) or the external network. There are some network interfaces missing on my host (peth0, vif0.0). ifconfig: eth0 Protokoll:Ethernet Hardware Adresse 00:18:8B:B3:1A:AC inet Adresse:192.168.0.66 Bcast:192.168.0.255

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

Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

Hi I''m using Xen on my AMD64 / Ubuntu 7.10 server which I recently upgraded, and my 2 VMs are decidedly flaky. They seem to be blocked for most of the time, and networking doesn''t work properly. How can I debug this and get them online reliably? Any tips gratefully received! * I can log in via console or ssh, can ping the server''s NICs but can''t ping the

Hi folks I deploy a two Dell PowerEdge T300 to test Virtualization with kvm+drbd+heartbaet. The KVM drbd and heartbeat work properly. However, I have doubt!! When the primary node has down, the secondary node start the VM that has original running on primary node... So, this required a full stop of hole system... This is not we wish here... Is there something way to live migrate VM from

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 =

Hello, We''re running Xen Unstable changeset 15468 with SLES10 on a Unisys ES7000/one 56x cpu and 160GB memory. Xen is built with NR_DYNIRQS=1024 and max_phys_cpus=64, and booted with dom0_mem=1024 and xenheap_megabytes=64. We have 320 para-virtualized SLES10 VMs on external storage. Our script starts a VM, waits for the start to complete, then starts the next: "for i in *.cfg;

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

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

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

Hi all, I''d like to know if it''s possible to have more verbose output when running a block-prefix script. Other than xend.log. To be more specific I''d like to use bash -x to see why I''m running into the following error: > # xm create -c host.cfg > Using config file "host.cfg". > aa:bb:cc:dd:ee:ff > Error: Device 51712 (vbd) could not be

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

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

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

Hello everyone! I''m new with Xen and i''ve been dealing with the same error the last week. I''m pretty much lost, i don''t know what else to do so i ask for your help. In my case i installed Xen on a amd64 Pc, with Gentoo. I installed the following packages: xen, xen-tools and xen-sources from the gentoo repositories. I''m using 2.6.31-xen-r10 gentoo

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