similar to: Device 0 (vif) could nto be connected: backend device not found

Hi, Thanks or all the suggestions. The problem was the lack of hotplug support! The problem was solved by a reinstall of the native linux (RHEL4) with selecting all packages. I had initially chosen some packages and I believe hotplug support was left off (don''t know which package it belonged to. Regards - Padma -------------- Original message ---------------------- From: Nivedita

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

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

I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb()

Hi, I have 6 DomU's with 4-virtual interfaces and 1 DomU with only one. When starting the DomU's in order where the domain with only one interface is started last it refuses to start with following error. If I start it first there is no problem starting them all. ---Error--- [2011-10-02 18:37:33 xend.XendDomainInfo 6728] DEBUG (XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch

Hi all When I have a domU that resides in the auto directory I get ''Error: Device 2049 (vbd) could not be connected'' and the domain starts in a paused mode. Shutting it down and restarting has the same effect. Following is some output from the xm log and an attempted restart. Directly after dom0 reboot: xen0:/etc/xen/scripts # xm list Name ID

Hi. We are running xen-3.0-testing. We use loop back mounted file systems. The server we are running restarts itself/crashes. This seems to happen around setting up loop back devices. (>63 loop back devices seems to trigger a crash, but we have seen then with fewer devices mounted as well). We have swapped all hardware (bar the disks) to a new server. Same issue. I see no disk

Hi. I''ve just upgrade my xen 3.0.1 to xen unstable. I noticed that there is no vmx driver here, only hvm. Actually I cannot start my VT domain: root@akira:/etc/xen# xm create bluszcz.hvm Using config file "bluszcz.hvm". Error: Device 768 (vbd) could not be connected. Backend device not found. root@akira:/etc/xen# my config: import os, re arch = os.uname()[4] if

Hi, I have been getting the following error (logged in /var/log/xen/xend.log) when I try to migrate a VM from one particular host to the other (the reverse migration works fine). My system was working fine for a long time (i did several migrations in both the directions). I am using Xen-3.4.3 (installed from source code) with CentOS 5.4. I am using drbd to replicate the disks.

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

Hi I''m a sysadmin and I''ve installed on my server Red Hat Enterprise Linux 5 to use its xen embedded with six virtual machines just created and running. Now I have a problem: when I attempt to create my seventh virtual machine, xen gives me this error: Error: destroyDevice() takes exactly 3 arguments (2 given) In /var/log/xen/xend.log find this errors: [2007-11-13 11:34:00

Hello list, I want to virtualize my physical CentOS 4.5 yet. Therefor I download the CentOS 4.5 iso. After mounting the iso on my notebook and make the mounted iso available via nfs I start on my CentOS 5 xen machine following command: virt-install -n myServer --ram=512 -f /virt/myServer.disk -s 150 --nographics -p --location=nfs:nbk:/media/centos This works for CentOS 5 DomUs but CentOS 4.5

Hi List, beneeth some debian domU''s I tried fedoraCore3 from xen-get... My tests are sucessfull bu I can''t reboot this domU. The domU seem to shutdown correctly but doe not start again. xm list does not show my fedore domU again and an manual xm create leads to: Error: Device 2049 (vbd) could not be connected. File /opt/xen/domains/tta/disk.img is loopback-mounted through

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, I am trying to install RSRuby (http://rubyforge.org/projects/rsruby/) which somewhat analogous to RPy. Installation fails using the cran R 2.8.0 packages for Ubuntu Intrepid because RDevices.h does not appear to be included in the r-cran-core package as it was previously. It is in the rbase_2.8.0.orig.tar.gz in the same directory meaning it hasn't been taken out of R altogether, and I

I''ve compiled xen-3.0.2-2 from sources. I''ve went to the end without errors. The ./install.sh script have been created the /etc/grub.conf file as it : # initrd /boot/initrd-version.img #boot=/dev/hdc default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.15-1.2054_FC5) root (hd0,0) kernel

Hello, I noticed a bug in Xen-4.1-3, which is also still present in xen+git. I know that the Python xend is deprecated, but I''m stuck with xen-4.1 until xen is usable with libvirt, so my patch might still be helpful for others. This is a follow-up to <http://lists.xen.org/archives/html/xen-users/2012-11/msg00069.html>, which still keeps me busy. /xen/xend/server/SrvDomain.py

I''m using RHEL 5. One of the virtual machines I have running is a WinXP install. I start this up after I login to X. If I log out of X, the virtual WinXP is still running (that''s fine with me). However when I log back into X and start the Virtual Machine Manager, I am unable to open the machine. It normally says "Virtual Machine Console is unavailable." There does

Package: xen-utils-common Version: 4.1.0~rc6-1 Severity: important Currently xend fails to create a fully virtualized vm because it has a different path hardcoded to it. Unable to complete install: 'POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found")' The correct path to use