https://bugzilla.novell.com/show_bug.cgi?id=465379 Summary: xendomains does not start: Device 51952 (tap) could not be connected Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: novell-web@zmi.at QAContact: qa@suse.de Found By: --- I've been searching a very long time investigating this problem. We're trying to use XEN in production, but currently documentation is very sparse, mostly outdated and wrong. Too bad! We've had the problem on one server where a single XEN domU was installed on openSUSE 11.0. After upgrading to openSUSE 11.1, xendomains didn't start the domain anymore. Symptom: autostart: # # rcxendomains start Starting auto Xen domains mailsrv2: Error: Device /dev/xvdp (tap) could not be disconnected. manual start: # xm create /etc/xen/auto/mailsrv Error: Device 51952 (tap) could not be connected. Hotplug scripts not working. You can google around, a lot of people have this problem with no real answer. I then found a first step: use "file:" instead "tap:aio" in the config works: 'tap:aio:/disks/daten/xen/mailsrv/root20080923.xvd,xvda,w', 'tap:aio:/disks/daten/xen/mailsrv/swap20080922.xvd,xvdb,w', 'tap:cdrom:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] changed to 'file:/disks/daten/xen/mailsrv/root20080923.xvd,xvda,w', 'file:/disks/daten/xen/mailsrv/swap20080922.xvd,xvdb,w', 'file:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] Then the domain can be created and runs without problems. But changing it back to tap:aio brings the error back also: # xm create /etc/xen/auto/mailsrv Using config file "/etc/xen/auto/mailsrv". Error: Device 51952 (tap) could not be connected. Hotplug scripts not working. And this leads into the totally wrong direction. The problem is elsewhere: When we started with XEN I read the Novell docs, especially http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7000062&sliceId=1&docTypeID=DT_TID_1_1&dialogID=74609719&stateId=0%200%2074607316 and how to use LVMs. But using LVMs within a simple file needs "xm block-attach", followed by a "vgchange -a y" in order to bring up the LVM. This seems to be done automatically by "xendomains", but there must be something that disturbs this, as after our upgrade 11.0 -> 11.1 it didn't work anymore. Also, as many people have problems with this, maybe you could post an article describing the problem and explaining the solution. I believe the solution is to either not use LVMs within files for XEN, and use files as disks directly. 1) The question remains, why the XEN scripts seem to remember to setup the LVM once, and then forgets it. The error messages should be cleaned up to explain the problem and point to the right direction. 2) # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 4 30 8 /local/domain/0/backend/tap/0/51952 It would be good that "xm block-list" also tells which device it is connected to (/dev/xvdp in my case). 3) There are currently 2 different error messages on VM startup: xendomains or "xm create", and both do not help solve the problem really 4) Why can't xendomains *disconnect* the LVM? After all, we're just booting the machine, and it tells us it can't *disconnect*? Maybe this can be improved. Hope this helps, mfg zmi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.