Thomas Schwinge <[EMAIL PROTECTED]> écrivait (wrote) : > Indeed I can confirm that `xen-hypervisor-3.0-unstable-1-i386' together > with `linux-image-2.6.17-2-xen-686' gets the Dom0 going again. So far, I > had no luck to get a DomU running, however: > > #v+ > [EMAIL PROTECTED]:~ $ sudo /etc/init.d/xendomains restart > Shutting down Xen domains:Starting auto Xen domains: riemannError: Device 0 > (vif) could not be connected. Hotplug scripts not working. > #v- > > Perhaps the syntax for the /etc/xen/DOMAIN files has changed?
http://lists.xensource.com/archives/html/xen-users/2005-11/msg00071.html Renaming vif by vif0 works for me : error gone. But I got an other one : # xm create orcal Using config file "/etc/xen/orcal". Error: Device 2048 (vbd) could not be connected. Hotplug scripts not working. My vbd conf : disk = [ 'phy:sda,sda,w', 'phy:sdb,sdb,w' ] No luck with google for now. -- > R : Tu vois ! || Jean Charles Delépine - Université de Picardie > > Q : Tu crois ? > > > R : Ça casse l'ordre chronologique de l'échange. > > > > Q : En quoi répondre au dessus est-il gênant ?
