similar to: Hotplug script not working

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

Here''s the latest USB code against the xen 3.0.0 release. Since the last posting this version updates the code to use the new 32 bit grant references and the latest GNTTABOP_map_grant_ref definition. I''ve also changed the definition of the virtual USB HCD to have a single port rather than seven ports with six unused. Domains importing multiple USB devices will get a HCD for

We have test latest xen (ChangeSet 7608) on VT platform with Intel 915 chipset and Here is the test summary: IA32: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32 issues contain: VMX can not be created IA32E: Build&Boot SMP xen0 without problem Can startup XenU with different configuration IA32E issues

check_hotplug fails on one of my machines running ubunto 4.10 "Warty Warhog", due to misparsing the udevinfo version string. The problem is caused by an old version of sed that does not appreciate the regexp. This patch fixes it, and also works on debian unstable and SLES9SP2. Please apply... Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> Signed-Off-By: Orna Agmon

Hi, How can I figure why some domain is still in zombie state, like these ones: master-xen root /vm/ttylinux# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 574 1 r----- 90.5 Zombie-small-11 28 0 1 ---s-d 0.9 Zombie-small-17 34 0 1 ---s-d

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]

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 have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like

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

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

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

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

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

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, I''ve run into the following error when trying to create a domU: root@jupiter:/etc/xen# xm create node0-mgmt -c Using config file "node0-mgmt". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. root@jupiter:/etc/xen# Excerpt from xend.log: [2006-09-25 14:55:48 xend 2015] DEBUG (DevController:110) DevController: writing

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