similar to: Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

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 all Greetings from Patagonia Argentina - this is my first message to this list. I''m having a weird problem: when I reboot some domU, some OTHER domU gets killed. Scenario: > cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 > uname -sri Linux 2.6.32.43-0.4-xen x86_64 > rpm -qa | grep xen- kernel-xen-base-2.6.32.43-0.4.1

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

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

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"

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

Hi guys, actually i use the following packages from etch-backports: =========================== ii linux-headers-2.6.18-6-xen-vserver 2.6.18.dfsg.1-18etch1 Common header files for Linux 2.6.18 ii linux-headers-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-18etch1 Header files for Linux 2.6.18 on AMD64 ii linux-image-2.6.18-6-xen-vserver-amd64

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

I was trying to install a guest OS with the following command. $ virt-install -r 1024 --accelerate -n ubuntu-first-test -f /var/lib/libvirt/images/guest.img --cdrom /root/ubuntu-12.04-desktop-i386.iso --hvm and it says the following. Starting install... ERROR POST operation failed: xend_post: error from xen daemon: <Fault 3: ''ubuntu-first-test''> Domain installation

I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

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 installed the xen in server with CentOS 6, but not create vm. [root@localhost oracleteste]# xm create oracleteste.cfg Using config file "./oracleteste.cfg". Started domain oracleteste (id=9) [root@localhost oracleteste]# xm list Name                                        ID   Mem VCPUs      State   Time(s) Domain-0                                     0  1024     1     r-----   

Hi all, when i try to create a new virtual machine in a new instalation of xen3.4 ( compiled from source) i get this error: xm create windows2.hvm Using config file "./windows2.hvm". Error: Domain ''y'' does not exist. And this is the log: [2009-06-25 17:59:42 13862] TRACE (XendDomainInfo:291) domain_getinfo(2) failed, ignoring: (3, ''No such process'')

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

Hi All, I''m having a similar issue as Ian Tobin some weeks ago here: http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html I''m using Debian Squeeze amd64, downloaded the experimental debian xen-amd64 kernel with pv_ops support. linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb

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

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains