I''m trying to understand how networking is intended to work for HVM
domains in Xen 3.4-rc3. My domain config file contains:
vif = [ ''type=ioemu, mac=00:16:3e:5b:f8:ed, bridge=eth2'' ]
and the bridge is correctly configured on eth2. But the xm create
command gets hung waiting for something to happen with the vif, and
eventually fails with:
Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.
xend.log shows it''s waiting for something to be written to xenstore:
[2009-04-28 15:33:37 5592] DEBUG (XendDomainInfo:1708)
XendDomainInfo.handleShutdownWatch
[2009-04-28 15:33:37 5592] DEBUG (DevController:139) Waiting for devices vif.
[2009-04-28 15:33:37 5592] DEBUG (DevController:144) Waiting for 0.
[2009-04-28 15:33:37 5592] DEBUG (DevController:629) hotplugStatusCallback
/local/domain/0/backend/vif/4/0/hotplug-status.
which seems to be related to the udev hotplug rules.
But what happens with the vif is that qemu has
invoked /etc/xen/qemu-ifup, and that has added the tap device to the
bridge:
# brctl show
bridge name bridge id STP enabled interfaces
eth2 8000.000e0cb1a72d no peth2
tap4.0
Is qemu supposed to be involved in the hotplug mechanism, or is there
something else I''m missing?
If modify qemu-ifup to write a value for the xenstore key, then the
domain finishes booting and the network works.
Thanks,
Gary
--
Gary Grebus
Virtual Iron Software, Inc.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Gary Grebus writes ("[Xen-devel] HVM networking in Xen
3.4-rc3"):> I''m trying to understand how networking is intended to work for
HVM
> domains in Xen 3.4-rc3. My domain config file contains:
>
> vif = [ ''type=ioemu, mac=00:16:3e:5b:f8:ed, bridge=eth2''
]
This looks plausible. Although I''m not 100% sure that the spaces are
permitted. None of my config files have them ...
> and the bridge is correctly configured on eth2. But the xm create
> command gets hung waiting for something to happen with the vif, and
> eventually fails with:
What does your /var/log/xen/xen-hotplug.log say ?
> Is qemu supposed to be involved in the hotplug mechanism, or is there
> something else I''m missing?
It''s all very complicated (much more so than it needs to be). Most of
the messing about is done by xend and by the hotplug script run by
xend.
> If modify qemu-ifup to write a value for the xenstore key, then the
> domain finishes booting and the network works.
The xenstore key is supposed to be done by the xend script, not
qemu-ifup. And anyway the xenstore key is not relevant to the
operation of qemu. I think xend is hanging up on itself.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Wed, 2009-04-29 at 17:04 +0100, Ian Jackson wrote:> Gary Grebus writes ("[Xen-devel] HVM networking in Xen 3.4-rc3"): > > I''m trying to understand how networking is intended to work for HVM > > domains in Xen 3.4-rc3. My domain config file contains: > > > > vif = [ ''type=ioemu, mac=00:16:3e:5b:f8:ed, bridge=eth2'' ] > > This looks plausible. Although I''m not 100% sure that the spaces are > permitted. None of my config files have them ...Spaces don''t make any difference. I''ve tried various things in the "vif=".> > > and the bridge is correctly configured on eth2. But the xm create > > command gets hung waiting for something to happen with the vif, and > > eventually fails with: > > What does your /var/log/xen/xen-hotplug.log say ?It''s empty, but that''s because nothing is ever running the hotplug scripts.> > > Is qemu supposed to be involved in the hotplug mechanism, or is there > > something else I''m missing? > > It''s all very complicated (much more so than it needs to be). Most of > the messing about is done by xend and by the hotplug script run by > xend. > > > If modify qemu-ifup to write a value for the xenstore key, then the > > domain finishes booting and the network works. > > The xenstore key is supposed to be done by the xend script, not > qemu-ifup. And anyway the xenstore key is not relevant to the > operation of qemu. I think xend is hanging up on itself.Which is the xend script? The hotplug scripts in /etc/xen/scripts seem to be driven by the "online" and "offline" events in /etc/udev/xen-backend.rules, but I can''t see anything that generates those events when qemu is involved. Maybe there is some kernel piece that I am missing? I''m using a 2.6.27.21 (openSUSE 11.1) Xen kernel. I''m not sure how this would work for PV-on-HVM drivers either, since xend is blocking before it boots the guest. Gary _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel