similar to: help with "error extent to vbd failed: ... error 8"

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

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 installed Kubuntu 8.04 with xen 3.2 on kernel 2.6.24-16-xen on amd64 hardware. Then I have created a new domU with xen-tools. The domU is using loopback-images. When I try to start the domU it ends with this: Error: Device 51713 (vbd) could not be connected. losetup /dev/loop0 /home/xen/domains/xx/swap.img failed. loopx is raised by 2 for every try. It looks like a classic and simple

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

I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 lvextend --size=+1M /dev/vg-xen/virt-test-0 xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 The xenstore backend isn''t updated to reflect the new size

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Hi, I encountered a problem while porting Solaris as a guest OS on Xen. The problem I found is that when frontend vbd driver get unloaded, it will close the vbd interface by changing the state to XenbusStateClosed. This appears to cause the dom0 hotplug scripts to remove the vbd entry from xenstore for the domU guest, preventing the vbd from being re-attached. So, my questions are: + This

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! 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 trying to get PV drivers running on both Centos 5.1 and Centos 5.3 HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. For the network drivers to work I had to unload the Realtek NIC driver and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias to modprobe.conf then got the PV NICs working nicely (Much

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

hello list i got the following pb: # xm create -f mac1/mac1.xen Using config file "mac1/mac1.xen". Error: Error creating domain: vbd: Segment not found: uname=file:/xen/mac1/swapfs but: # dmesg | grep loop loop: loaded (max 32 devices) # ls -l /xen/mac1/swapfs -rw-r--r-- 1 root root 268435457 2005-04-12 11:25 /xen/mac1/swapfs # xm list Name Id Mem(MB) CPU State

Hi everyone, Just a quick question: Is there a limit on the vbd size for pv guest domains, I''ve found only rumors on the Internet about a 2TB limit, but from my experience with xen-3.0.3 /linux-kernel-2.6.18-5 (installed from a debian etch packages) I can say that a lvm volume of 3.7TB as created and formated in Dom0 is seen as 1.85TB only of course reporting a corrupted xfs filesystem

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

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04

My LAN includes a server machine running FC4, with several shares mounted with Samba. Yesterday, I upgraded the packages on the FC4 machine, and these included Samba, which is now at 3.0.23a. Unfortunately, this seems to have broken the mounted shares for my Ubuntu 6.06 installation on my Acer 1682WLMI laptop. The cifs module on Ubuntu reports as version 1.39. The symptoms are that I can

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.

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal I get this error with xen after some debug cycles, start / stopping nodes. I found this fix on the net, which fixes the problem: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01070.html in /etc/init.d/xen: start) + modprobe loop max_loop=64 + cd /dev && /dev/MAKEDEV loop xend start

Hi, I don''t see any obvious flush to disk taking place for vbd''s on the source host in XendCheckpoint.py before the domain is started on the new host. Is there a guarantee that all written data is on disk somewhere else or is something needed? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com