similar to: vbd could not be connected

This is a known issue. It has been fixed in xen unstable. The problem is loop device is not leased after the guest destroyed. If execute "losetup -d /dev/loopX" in domain0, the problem will be solved temporarily. >-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Thomas Karsten >Sent:

> I have my disk file stored on a NFS server. > I have tried these two approaches: > > A) Mounting the NFS directory in RW mode on a local directory > and specifying in my config file the complete path of my disk file. > > xm create configFile returned with this error: > Error: Error creating domain: vbd: Segment not found: > uname=file:/MountPoint/diskfile

Hello all, I have some DomU''s with root and swap images on files under Xen 3.0.0 Investigating some cases of boot failure of domUs, I stumbled upon the fact that when a domU is shutdown via xm shutdown, not all of its images are released from their /dev/loopX - devices. That is, for i in /dev/loop*; do losetup $i; done still shows output for that image. It seems to me that the

I''m a complete newbie at Xen, just getting started. I was happy to see that Ubuntu 11.10 includes Xen again, http://zulcss.wordpress.com/2011/09/04/xen-4-1-1-on-ubuntu/ So I installed ubuntu 11.10''s precompiled Xen, and started playing around with it. I''m not even trying to start another VM at the moment, just playing around with mounting block devices, and had trouble

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Hi! $ xm create -n -f xmtest Using config file "xmtest". (vm (name testdomain) (memory 128) (image (linux (kernel /boot/vmlinuz-2.6.8-foo1-XenU) (ip :1.2.3.4:::tesmo:eth0:dhcp) (root ''/dev/xda1 ro'') (args 1) ) ) (device (vbd (uname phy:loop0) (dev xda1) (mode w))) (device (vif (mac

We run our dom0''s with 128MB of RAM using xen 2.0.6, kernel 2.6.11 for dom0 and domUs, and typically have ~10 domUs per server. All the domU filingsystems are loopback files served from dom0 using the file method. We''ve found that really busy servers sometimes get out of memory problems on dom0. This appears as lots of x-order memory allocation failures with a variable

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

Hi I had installed Xen-3.0.4 in Scientific linux 4 (kernel version 2.6.16.33) by following the instructions given in following link project-xen.web.cern.ch/project-xen/xen/howto_slcXen.html I ve created the guest Domain with fedora image of size 2.2GB , disk space as 10GB and the domain started successfully . when i logged into the xm console and checked the disk space its showing only 2.2GB ..

Hi, I wanted to create a new btrfs fs for my backups. When trying to mkfs.btrfs for that device, I''m getting "error checking /dev/loop2 mount status" With strace I see where the problem is: lstat("/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-par", 0x7fffa30b3cf0) = -1 ENOENT (No such file or directory) The problem is there is something missing

Hi all, Now I use xentop to get disk statistical information. NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR VBD_RSECT VBD_WSECT SSID Domain-0 -----r 96233 0.7 3902464 23.3 no limit n/a 12 0 0 0 0 0 0 0 0 0 0 slave3

Hi all, we are running two servers with Ubuntu 8.04 LTS Server with Xen 3.2 and two dual-core CPUs: processor : {0-3} vendor_id : AuthenticAMD cpu family : 15 model : 65 model name : Dual-Core AMD Opteron(tm) Processor 2218 HE stepping : 3 cpu MHz : 2613.394 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu :

Good morning everybody, I get a: Error: Adding extent to vbd failed: device (vbd (uname file:/xen/slackware-linux-10/linu.img) (dev hda1) (mode w)), error 8 What is "error 8"? Where are those error-codes listed? My linux.conf: kernel="/xen/slackware-linux-10/vmlinuz-install" # <- the one from Xen memory=64 name="Linux" # <- is it right that this cannot have

Hi, I''ve been trying to boot from a RHEL4 install iso without much luck (the xen way). The Host is: RHEL 5.1 xen-3.0.3-41.el5 Here is my guest config: # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using

Hi, xm destroy CRASHED_DOMAIN does not cleanup the vbd nor the vif. The loopback backend is busy, so losetup -d fails. This is inconvenient, as it results in an unclean shutdown of your physical machine. Best, -- Kurt Garloff, Director SUSE Labs, Novell Inc. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [

Hi, I have installed debian 3.1 on an Intel Pentium D processor 920 ( including vanderpool.) The installation worked fine and i''m able to start guest-domains. When I try to start the 5.th Guest-Domain, I Get the following error: Error: Device 769 (vbd) could not be connected. Backend device not found. this problem exists still if i have shutdown or destroyed all guests, after

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

I have Xen 3.0.2 running on Debian Unstable with a straightforward setup, mainly based on this howto http://www.debian-administration.org/articles/396. When I have restarted dom0, I get this error, when I start a domU with xm create -c vm.cfg Error: Device 769 (vbd) could not be connected. Backend device not found. Google have pointed me to this solution:

Hi Konrad, I just tried linux-3.4-rc0 (linus his tree, last commit f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your tree pulled on top of that: branch stable/for-ingo-3.4.v2 (required for dom0 to boot) branch stable/for-jens-3.4 branch stable/for-jens-3.4-bugfixes Hypervisor is xen-4.1.3-rc1-pre linux 3.3 vanilla works fine Booting dom0 goes fine, but