Hi Jonathan,
You can correct that with the qemu vif script. It is located in
/etc/xen/scripts/qemu-ifup for newer XEN version (don't know about
older ones, but it should exist there, too) and controls the setup
of the tapX.X device. You can put your network setup code in that
script, too, and both interfaces will be set up with your bridge /
routing / whatever scenario. Note that I did not find a way to
change the qemu-ifdown script, but you could add code to the xen vif
script, that also brings down the tap device (if necessary).
It is possible to rename the tap device to the vif's name after
renaming the vif to something else, but there are only rare cases
where this is necessary.
In server environments or for Windows Server domUs, I would also
recommend the pv_ops drivers, because they are really faster than
emulated network devices (same for disks, btw).
Regards,
Felix
Am 27.07.2010 19:33, schrieb Jonathan Tripathy:
On 27/07/10 11:49, Jonathan Tripathy wrote:
Re: [Xen-users] HVM Network Interfaces
On Tue, Jul 27, 2010 at 3:14 PM, Jonathan
Tripathy
<jonnyt@xxxxxxxxxxx>
wrote:
> What is the point of Xen showing the vif interfaces
then for HVM
guests?
Because that's the interface that will be used if your HVM
domU has PV
drivers
> Is there any way to fix the name of the tap
interfaces?
Not that I know of.
> There are some iptables rules that I need to script
when starting
PV guests, but they need to know the HVM guest's tap name.
>
> BTW, my HVM guest is a FreeBSD firewall, so GPLPV
isn't an option
:(
You might be able convert it to PV guest. From Google:
http://forums.freebsd.org/showthread.php?t=10268
http://wiki.freebsd.org/FreeBSD/Xen
Is there any way to create iptables rule upon HVM boot then (With
rules
matching by tap interface)?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
