-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Zhang, Xing Z wrote: > Do you check your "disk" parameter is right? > "Error: Device 768 (vbd) could not be connected. Hotplug scripts > not working." often has relation to un-correct disk image path or you mount > the image somewhere but forget unmount it. > In the newest XEN/IA64 changeset, the error info is more readable, you can > update to a new one. > If you want to debug it, see /var/log/xen/xend.log and search key word > "Error". Then you can get a series of python error info. > The python code of Xend is at /usr/lib/python/xen. Good luck.
Two other suggestions... 1) the vbd not connecting *could* be selinux preventing usage of the disk image, so you may be able to start the guest up correctly after running 'setenforce 0' (or booting with selinux in permissive or disabled mode). 2) try creating the guest using virt-manager. Always works for me. >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On >> Behalf Of Kayvan Sylvan >> Sent: 2007?11?14? 8:43 >> To: Tristan Gingold >> Cc: xen-ia64-devel >> Subject: RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create >> fails: Hotplugscripts not working. >> >> I tried commenting the vif= line out and I get: >> >> Error: Device 768 (vbd) could not be connected. Hotplug scripts >> not >> working. >> >> I'm also not getting a console or anything else that I can >> interact >> with. >> >> I'm not sure how to proceed to try to debug this. >> - -- Jarod Wilson [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHOmFLtO+bni+75QMRAr0zAKC7Te5Xh/dJO7fOKhRB9WBax821YwCgo7Zh bi6v3YfTXD2LGaAK84AE4so= =h6tC -----END PGP SIGNATURE----- _______________________________________________ Xen-ia64-devel mailing list [email protected] http://lists.xensource.com/xen-ia64-devel
