rumprun made image can not get network device working on xenserver 6.5

[bigben80]

Hi,

I'm trying to run rumprun kernel image on XenServer 6.5(SP1, build date 2015-04-17, build number 90233c), it's found the network device in a rumprun-baked image can not work correctly under XenServer 6.5, it can not get or receive any packet from xenbr0(linux bridge or open vswitch). here below is the link to the test result I got from the image after boot it in the XenServer 6.5 environment.

https://gist.github.com/bigben80/b761b060700b7f56457d

Also tried to setup a Ubuntu 15.10 + Xen 4.5.1 environemt for comparing, same image works fine in that environment(both Linux bridage and open vswitch verified).

[liuw]

Hello, there seems to be an error in you xenstore output.

hotplug-error = "Failed to read /xapi/2/private/vif/0/MTU"

Maybe this is the reason it doesn't work.

[bigben80]

Dear Wei,

It could be the problem, XenServer plug&play don't like this device.

but it's strange to see the device in "connected" state afterward.

2016-03-14 17:49 GMT+01:00 Wei Liu notifications@github.com:

Hello, there seems to be an error in you xenstore output.

hotplug-error = "Failed to read /xapi/2/private/vif/0/MTU"

Maybe this is the reason it doesn't work.

— Reply to this email directly or view it on GitHub https://github.com/rumpkernel/rumprun/issues/70#issuecomment-196406638.

[liuw]

On Tue, Mar 15, 2016 at 11:04 AM, bigben80 notifications@github.com wrote:

Dear Wei,

It could be the problem, XenServer plug&play don't like this device.

but it's strange to see the device in "connected" state afterward.

​ ​I'm afraid I have no idea how XenServer toolstack is arranged. I agree it feels a bit strange the backend doesn't disconnect the frontend when error occurs. All in all this is unlikely to be a frontend (rumpkernel) problem

Wei.

2016-03-14 17:49 GMT+01:00 Wei Liu notifications@github.com:

Hello, there seems to be an error in you xenstore output.

hotplug-error = "Failed to read /xapi/2/private/vif/0/MTU"

Maybe this is the reason it doesn't work.

— Reply to this email directly or view it on GitHub <https://github.com/rumpkernel/rumprun/issues/70#issuecomment-196406638 .

— You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/rumpkernel/rumprun/issues/70#issuecomment-196766722

[mato]

@liuw I debugged the problem with @bigben80 on IRC extensively, and it does indeed seem to be something XenServer-specific. Neither ping nor any ARP traffic gets through on the vif. @bigben80 I suggest you ask on XenServer support forums if anyone else can confirm the problem.

[liuw]

On Tue, Mar 15, 2016 at 5:39 PM, Martin Lucina notifications@github.com wrote:

@liuw https://github.com/liuw I debugged the problem with @bigben80 https://github.com/bigben80 on IRC extensively, and it does indeed seem to be something XenServer-specific. Neither ping nor any ARP traffic gets through on the vif. @bigben80 https://github.com/bigben80 I suggest you ask on XenServer support forums if anyone else can confirm the problem.

Well if the vif interface in backend was not up I wouldn't be surprised to see no ethernet packet was transferred. :-)

Yeah, it makes sense to just post this report to XenServer mailing list and / or support platform.​​

​Wei.​

—

You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/rumpkernel/rumprun/issues/70#issuecomment-196942209

[mato]

Ah, I didn't notice the NO-CARRIER on the vif. That's odd as both backend and frontend show state = 4 which would suggest they're online.