Error Device 769 Vbd Could Not Be Connected
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top XEN: Error: Device 769 (vbd) could not be connected. Failed to find an unused loop device up vote 2 down vote favorite I'm trying to start a new DomU machine (Lenny) on an Ubuntu Dom0. However, I'm getting the following error when executing the xm-create command: # xm create vm3.rootspirit.com.cfg Using config file "./vm3.rootspirit.com.cfg". Error: Device 769 (vbd) could not be connected. Failed to find an unused loop device After some Googling I learned it was due to limit of loopback devices in /dev # ls -ls /dev/ | grep loop 0 brw-rw---- 1 root disk 7, 0 2009-07-17 04:01 loop0 0 brw-rw---- 1 root disk 7, 1 2009-07-22 12:49 loop1 0 brw-rw---- 1 root disk 7, 2 2009-07-22 12:49 loop2 0 brw-rw---- 1 root disk 7, 3 2009-07-22 12:49 loop3 0 brw-rw---- 1 root disk 7, 4 2009-07-22 12:49 loop4 0 brw-rw---- 1 root disk 7, 5 2009-07-22 12:49 loop5 0 brw-rw---- 1 root disk 7, 6 2009-07-22 12:49 loop6 0 brw-rw---- 1 root disk 7, 7 2009-07-22 12:49 loop7 I currently have 3 DomUs running: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 5352 2 r----- 945295.5 vm0.rootspirit.com 130 1024 1 -b---- 653791.0 vm1.rootspirit.com 106 1024 2 -b---- 48359.3 vm2.rootspirit.com 128 512 2 -b---- 18150.9 I have added the max_loop option to the loop module # cat /etc/modules | grep loop loop max_loop=64 But I am unable to reload the module # modprobe -r loop FATAL: Module loop is in use. I am unable destroy all the DomUs and/or to reboot the Dom0 at this time. Any other way to reload/force the use of extra loop devices? Thanks, Yeri debian xen loopback share|improve this question asked Oct 19 '10 at 13:09 Tuinslak 67731541 I ended up killing all my DomU VMs, edited /etc/modprobe.d/local-loop.conf and added: options loop max_loop=64; modprob
To: xen-users@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-users] Error: Device 769 (vbd) could not be connected... From: Robin Atwood
To: stephan.augustin@xxxxxx Subject: Re: [Xen-users] Error: Device 769 (vbd) could not be connected. Backend http://old-list-archives.xenproject.org/xen-users/2006-01/msg01233.html device not found. From: Molle Bestefich
Michael Mey wrote: > > Stephan Augustin wrote: > > > I have figured out that if it happens all loop-devices are fully used. > > > can i get more of them ? > > > > AFAIK you can set the number of loopback devices in your kernel config. > > Thus you have to recompile your xen-kernel. > > That may be true, but it's much easier to adjust it on the kernel command > line. Just add max_loop=128 or some such. Do you mean the commandline kernel /boot/xen.gz in /boot/grub/menu.lst ? stephan _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users Thread at a glance: Previous Message by Date: Re: [Xen-users] Debian packages for xen3 + kernel images for dom0/U Hi, the same problem i have figured out too. but in my information ( xensource manual ), the syntax has not changed, and i have the newest packets got from xen3 stephan Am Dienstag, 31. Januar 2006 12:06 schrieb Andy Smith: > On Mon, Jan 16, 2006 at 02:46:29PM +0100, Ralph Passgang wrote: > > I just wanted to let all interessted debian users know, that on my xen3 > > repository are now kernel images available for dom0/U. > > Hi Ralph, > > I just switched to your sarge xen3 packages from working from source > - very nice work indeed! > > My main reason for switching though was to get the vifname > functionality that recently got re-added to xen-testing. > > So, the vif line in my domain's config file now looks like: > > vif = [ 'mac=00:16:3e:6b:18:81, bridge=xenbr0, vifname=vif-test.0' ] > > which is what I am used to having work in xen 2.x, but I see no > difference. i.e. I still get the next vifx.0 interface. > > Do you know if the syntax changed with xen3, or were your packages > made before this feature was added? > > xen_changeset : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798 > > Thanks, > Andy -- Stephan Augustin Rosenpark 3 65795 Hattersheim 06190/9355448 0173/1735867 _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users Next Message by Date: Re: [Xen-users] Error: Device 769 (vbd) could not be connected. Backend device not found. Am Dienstag, 31. Januar 2006 14:20 schrieb Molle Bestefich: > Stephan Augustin wrote: > > > That may be true, but it's much easier to adjust it on the kernel > > > command line. Just add max_loop=128