Error Device 51712 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 - can't create domain because 'vdb could not be connected' up vote 1 down vote favorite I'm trying to start up a Xen VM, however I'm getting the following error: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. what does this mean? The dom0 is CentOS and the guest OS is Debian Lenny. The network interfaces I'm using are: vif = [ 'mac=00:16:3e:3e:53:5f, bridge=xenbr0', 'mac=00:16:3e:18:16:e5, bridge=xenbr1' ] The root filesystem of the guest OS is set to mount over NFS from the dom0, this is working for other guest OSs on the same host. The swap (and /var) is mounted from a local LVM logical volume UPDATE My fault. I hadn't written the config correctly, and hadn't set up the filesystems correctly. I was able to look at /var/log/xen/xen-hotplug.log to see that it was accessing the wrong device. linux xen virtual-machines share|improve this question edited Jul 15 '09 at 9:55 asked Jul 15 '09 at 9:47 Rory 11k36117196 That's much simpler :) Oh well, my answer might be of use to somebody else with the same error. –Dan Carley Jul 15 '09 at 10:37 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote Short version: Check that you have /etc/udev/rules.d/xen-backend.rules. The file may or may not be prefixed by a number. If not, check whether you have /etc/udev/xen-backend.rules and create a symlink from that to /etc/udev/rules.d/xen-backend.rules. Long version: I've seen this with a Gentoo 3.3 dom0, not CentOS. But I suspect the fix will be the same or similar. The Xen build scripts call a command udevinfo -V to determine the version of udev inst
Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug184194 - Device 51712 (vbd) could not be connected Summary: Device 51712 (vbd) could not be connected Status: CLOSED NOTABUG Aliases: None Product: Fedora Classification: Fedora Component: xen (Show other bugs) Sub Component: --- Version: rawhide Hardware: All Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Rik http://serverfault.com/questions/40947/xen-cant-create-domain-because-vdb-could-not-be-connected van Riel QA Contact: Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2006-03-06 22:50 EST by Justin Conover Modified: 2007-11-30 17:11 EST (History) CC List: 5 users (show) andreas.bernstein bstein katzj noa sct See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: https://bugzilla.redhat.com/show_bug.cgi?id=184194 Environment: Last Closed: 2006-03-22 10:22:11 EST Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) xend.log (24.85 KB, text/x-log) 2006-03-08 09:48 EST, Justin Conover no flags Details xend-debug.log (1.03 KB, text/x-log) 2006-03-08 09:50 EST, Justin Conover no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Justin Conover 2006-03-06 22:50:19 EST Description of problem: Initial xen install from xenguest-install.py errors out with: Error: Device 51712 (vbd) could not be connected. Backend device not found. If your install has exited, you can restart your guest by running 'xm create -c fc5-xen2'. xm create -c fc5-xen2 Using config file "/etc/xen/fc5-xen2". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 110, in get_config if is_disk_image(fn): File "/usr/bin/pygrub", line 78, in is_disk_image buf = os.read(fd, 512) OSError: [Errno 21] Is a directory Error: Boot loader didn't ret
Log In [x] | Forgot Password Login: [x] First Last Prev Next This bug is not in https://forge.univention.org/bugzilla/show_bug.cgi?id=20481 your last search results. Bug20481 - xend.err 'Device 768 (vbd) could https://community.oracle.com/thread/3774277 not be connected. Hotplug scripts not working. Summary: xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working. Status: CLOSED FIXED Product: UCS Classification: Unclassified Component: Virtualization - Xen Version: UCS 3.2 Hardware: Other Linux Importance: P5 normal (vote) TargetMilestone: UCS 3.2-0-errata error device Assigned To: Philipp Hahn QA Contact: Erik Damrose URL: Keywords: Depends on: 33924 Blocks: 35531 Show dependency tree /graph Reported: 2010-10-22 09:56 CEST by Arvid Requate Modified: 2014-07-31 09:22 CEST (History) CC List: 6 users (show) buesching damrose gohmann hahn jmm walkenhorst See Also: What kind of report is it?: --- What type of error device 51712 bug is this?: --- Who will be affected by this bug?: --- How will those affected feel about the bug?: --- User Pain: Enterprise Customer affected?: School Customer affected?: ISV affected?: Ticket number: Bug group (optional): Attachments /var/log/xen/qemu-dm-winxp-test001.log (875 bytes, text/plain) 2010-10-22 09:59 CEST, Arvid Requate Details /var/log/xen/xen-hotplug.log (36 bytes, text/plain) 2010-10-22 10:01 CEST, Arvid Requate Details /var/log/xen/xend.log (31.90 KB, text/plain) 2010-10-22 10:01 CEST, Arvid Requate Details Debug logs von libvirt und xend (539.49 KB, application/x-gtar) 2010-10-22 12:38 CEST, Arvid Requate Details View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Arvid Requate 2010-10-22 09:56:48 CEST Beim Starten eines frisch kopieren XP-Images im UMC Modul UVMM erschien das Popup: Error managing domain "bdb3a479-6e16-7427-09d3-f88271d29bcd": POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working.') Nach einem erneuten Startversuch der VM blieb das UMC Modul im Reload hängen. Nach ern
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Engineered Systems All PlacesServer & Storage SystemsEngineered Systems 2 Replies Latest reply on Mar 17, 2016 2:14 PM by NDEric OAKERR: 7007 starting VM on ODA X4-2 2887889 Jul 28, 2015 6:55 PM Hi,did anybody facea similar situation on an ODA X4-2:There is a VM (oel 6.6 x64) running hosting an OHS. Some days ago we could not access the VM even on the console: I/O error , dev xvda, sector xxxxx. We did a shutdown force of the VM and tried to start it up again, This resulted in "Attempting to start vm on node:0=>FAILED.