similar to: Can''t destroy zombie domain, holding onto resources

I just tried to setup another domain on a server running 1 domain. When i try to start the domain it gives me an error Error: Device 0 (vif) could not be connected. Backend device not found. The entry in my xen config file for the disks is disk = [''phy:/dev/xen001/xen2-fun,sda1,w'',''phy:/dev/xen001/xen2-fun-swap,sda2,w''] Looking at /var/log/xend.log, i found

Hi All I have xen 4.0 in centos dom0 the machine was working fine for months and yesterday out of sudden I can no longer provision new vms and to make things worst If any vm shutdown I cannot re run it again . the vm stop at the process of detecting the (ubuntu and debian all versions) [!] Detect Disks "No disk drive was detected. If you know the name of the driver needed by your disk

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03

I am having the same problem, however on RHEL 2.6.16. I have tried setting up the bridge manually but it does not work. Can someone give some clues on what we should do to solve this problem in RHEL Thanks P. Krishna -------------- Original message -------------- From: Jens Nachtigall <nachtigall@web.de> > I found this at http://julien.danjou.info/xen.html > > Set up the

Last week, I mentioned an error I was getting, as described below. I''ve seen several mailing list posts describing a similar problem as far back as December, 2005. This seems to be a problem plaguing all Xen 3 releases (to date). > > 3. After booting and then destroying approximately 25 domains, the > system will require a reboot before I can add further domains. The

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4]

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, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

Hi again :) OK we''re making good progress. Dom0 booted with 2.6.16-xen kernel, Steve''s wonderful xen-create-image has done the biz for me with debootstrap and created a sid disk image+swap, and I can start the created ''joltpg1'' OK.. but when I go to connect to the console, I see this: jolt:/dev# xm console joltpg1 xenconsole: Could not read tty from store:

After a few times of building xen by source, I can''t start domU anyway. I tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again, but the problem is still exist. There are xenstore-write errors in /var/log/xen/xen-hotplug.log: xenstore-write: could not write path backend/vbd/1/2050/hotplug-error xenstore-write: could not write path

Hello, on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why. Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hi all, I have recently installed FC5 along with xen via yum. I''ve successfully rebooted using the dom0 (2.6.16-1.2133_FC5) kernel, started xend, and trying to start my first domU after following the instructions in the user guide. However, I keep receiving a kernel panic and an error about XENBUS timeout. Any help greatly appreciated as I am stumped. Should I be using the provided

Hello ! I yesterday updated one server to XEN 3.2 which was running 3.1.2 before. The default bridge setup stopped working (Guests network packets were not forwarded to physical ethernet connection on eth0) My bridge setup looked like this: root@quadxeon2:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.003048359fc0 no

I have Xen3 installed on Ubuntu 6.10 server, $ sudo xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 250 8 r----- 748.2 but whenever i try to create a new domain with anything listed for kernel at all, i get this: $ sudo xm create domu1 Using config file "domu1". Xend has probably crashed!

Hello, My name is Fermín Galán. I have started recently to use Xen (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected.

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

All, I have a domU running Ubuntu 12.04.1 LTS 64bit using PVonHVM which is working well but I noticed a quirk and just wanted to check it wasn''t just my misunderstanding. On my dom0 (Arch Linux, 64bit, AMD Phenom 2 X4 965 CPU, Xen 4.2.0 from my own PKGBUILD) I run "xl top" and xentop loads and shows all the currently running domains; only none of the domains have anything