Xen devel - Apr 2007 - Hotplug problem when using xend and xm create

hi,

I am trying to use xm to create a new domain (normally I am using my own
home-brewed tools, but I would like to play with xm migrate to benchmark
it against my self-migration impl.), but when my domain has a vif
configured I am running into the following timeout error:

 Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.

The config-file for the domain looks like this:

name="cons"
memory=64
kernel="/root/vmlinux"
ramdisk="/root/domUinitrd"
vif=[ ''mac=aa:00:00:00:00:02, bridge=xen-br0'' ]
root="/dev/ram ro init=/linuxrc"

Xend has been started and I am using the standard xen-3.0.3 vif scripts
and config files.

For hotplug, my system is running udev. The
file /proc/sys/kernel/hotplug is empty, not sure what that means.
ifconfig shows no vif for the domain. The strange thing is that it all
works fine using my ''buscreate'' tool for creating a similar
domain.

Does anyone have a fix for this?

Thanks,
Jacob



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 10/4/07 16:24, "Jacob Gorm Hansen" <jacobg@diku.dk> wrote:
> For hotplug, my system is running udev. The
> file /proc/sys/kernel/hotplug is empty, not sure what that means.
> ifconfig shows no vif for the domain. The strange thing is that it all
> works fine using my ''buscreate'' tool for creating a
similar domain.
Does your own tool rely on the hotplug scripts though, or does it plumb the
vif into the network stack itself?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, 2007-04-11 at 22:37 +0100, Keir Fraser wrote:
> 
> 
> On 10/4/07 16:24, "Jacob Gorm Hansen" <jacobg@diku.dk>
wrote:
> 
> > For hotplug, my system is running udev. The
> > file /proc/sys/kernel/hotplug is empty, not sure what that means.
> > ifconfig shows no vif for the domain. The strange thing is that it all
> > works fine using my ''buscreate'' tool for creating a
similar domain.
> 
> Does your own tool rely on the hotplug scripts though, or does it plumb the
> vif into the network stack itself?
Hmm my tool write the ''script'' node, and the corresponding
script gets
triggered fine when the vif comes up. I am not too familiar with how
hotplug works, but I would expect that means I am using it.

Jacob


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel