On Sun, Oct 29, 2006 at 06:08:52PM -0800, John McCullough wrote:
> On Thu, Oct 26, 2006 at 05:17:50PM +0100, Daniel P. Berrange wrote:
> > I've been attempting to get the network-route/vif-route scripts running
> > instead of using the traditional bridging setup, but running into some
> > puzzelling issues.
>
> Are you using an hvm or pv guest?
Nope, this was all with paravirt guests. I think I've got the problem 
sorted out now, so I'll try & post a patch for the pv network scripts
tomorrow sometime.
> Routing under hvm requires a bit of hacking. Qemu uses /dev/tap*
> devices rather than the vif*.* devices and is by default invoked in a
> bridging mode (the default /etc/xen/qemu-ifup script that is invoked by
> qemu-dm on launch simply adds the tap device to the bridge xenbr0).
>
> I've found that turning the vif script executed by xend into a no-op,
> changing the qemu-ifup script to invoke a vif-like script with the
> correct vif and XENBUS_PATH defined, and modifying image.py to invoke
> qemu-dm without the bridging.
Ok, I'll take a look at the pv stuff too - we ought to make sure both
pv & hvm work in the same way if feasible.
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel