Re: [Xen-API] [Pkg-xen-devel] Bug#702428: HVM networking tap/vif bug (Debian bug 702428)

[Daniel Pocock <daniel@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 17/03/13 18:49, Ian Campbell wrote:
> On Sun, 2013-03-17 at 18:44 +0100, Daniel Pocock wrote:
>> 
>> On 17/03/13 18:38, Ian Campbell wrote:
>>> I'm afraid I don't know about the issue you are seeing but I
>>> can comment on one part:
>>> 
>>> On Sun, 2013-03-17 at 15:02 +0100, Daniel Pocock wrote:
>>>> while the output from dmesg suggests that the interface
>>>> vif10.0 was created.  It appears there is confusion between
>>>> the vifX.Y and tapX.Y naming schemes.
>>> 
>>> An HVM guest with a network device should get *both* vifX.Y
>>> and tapX.Y, they are kind of two faces of the same "device".
>>> The tapX.Y is the emulated NIC (rtl8169 or e1000 or something)
>>> while the vifX.Y is the PV NIC which the guest can choose to
>>> switch over too (for increased perf etc) if it has a suitable
>>> driver (e.g. Linux PVHVM support, PV drivers for Windows etc
>>> etc).
>>> 
>>> As to why tapX.Y cannot be added to a bridge, I've no idea,
>>> sorry. Are you using bridge or vswitch? Can you manually
>>> enslave the tap device to the bridge?
>>> 
>> I'm using Open vSwitch
> 
> I wonder if something might be logged by ovs about why it is
> refusing this operation? I think OVS has pretty extensive logging
> capabilities too so you might be able to increase the verbosity.
> 

Ok, I played with it some more, there is definite progress but I still
believe something is wrong in one of the scripts:

I notice this in syslog:

 domid: 19
 -c config qemu network with xen bridge for
 tap19.0 xapi1
 can't add tap19.0 to bridge xapi1: Operation not supported
 /etc/xen/scripts/qemu-ifup: could not launch network script
 Could not initialize device 'tap'


After seeing that, I decided to look inside the script mentioned
there, /etc/xen/scripts/qemu-ifup

I found the brctl command in the script

    brctl addif $2 $1


Commented out that line so the script now returns 0 (success)

Booted the VM - it boots successfully, but without network
connectivity.  It has a VIF, but no ping

Looking at `brctl show xapi1' and I see vif20.0 is in there, but
tap20.0 is not

Manually run the command

    ovs-vsctl add-port xapi1 tap20.0

Now it is possible to ping the running HVM domU

Should the script be using the ovs-vsctl command instead of brctl?  Or
have I misconfigured something and the wrong script is being run?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJRSjkEAAoJEOm1uwJp1aqDw8EP/3Er1BTtGmfZn16kndFzklUl
gU901PTVtNOaLODI9c+ecE4Z+vBMWebPhwwXeiDEjCS32xlufJAeSBG5hf31lHt2
mhPjHMzO8MjvIicC4zqN85soNIYz0T57bjWJhUoYhPvZCnwFSoi7vegteE9der+C
J1xfh3BzdyUHNMphDsuHPuZSninEpUrZT4Ez9jRKM585UpNgM75tIMoHzzm+j/Ek
qwTZKISyc+0sd/QGwCzet3/P3lUkKXhZ296SjsBcPjqq0IHkO391xD9jCX4XMLxR
2lQMfVlvW+KciZwnKsvPWQC9NsyhtnTBZ9sSof9e/WYYsxZ9PWRDZ60QPn8RIHrg
pP0WwYbfGvs1cGj5Gu7kjq0ikhRQ4HLcE/b3S8Y8knv4/LyIZj98D+RAiIbPuq48
MF8BHFZw5QjLPPe24Dhq7684YiFUpInFvHx1i7PBJdv1RwxA32pmauPNUHLOg232
qoBjoY5IjEUJI3+OwV772DF38WqsZru25ANwbNXh4PSs4PVnCt6eXc/w70UQeNEG
7OEEkQ7qyPG4iAWQvaFlvrOnwS47g1E9ARMnLhjPGKXwU88PMawmqMf0pVlaR499
199GIc28lAnTkLJHfNs6FdJlGvp8xl0BzhGK7BSPgEm0Y83PV/COwvDFpDNLXNng
MDh3YrAb/VHQxzTnNmzj
=zyPi
-----END PGP SIGNATURE-----

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api