I first tried upgrading to 4.8 but then none of my VM’s would launch. I’m guessing there was a change to the config files that I did not look in to.
I then tried going to 4.6.2 before, but the issue happens there as well.
I was able to revert back to 4.5.1 and the issue went away.
Kind of surprised no one else has heard of this. I can’t be the only one seeing it.
From: Xen-users [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Marc Tousignant
Sent: Friday, January 6, 2017 9:30 AM
To: xen-users@xxxxxxxxxxxxx
Subject: [Xen-users] Xen 4.7.1 - Issue with NIC's saying network cable unplugged on reboot of domU
Since August 2015 I have been running xen 4.5.1 without issue. The other day I updated to 4.7.1 and now my domU are losing their network cables after a reboot. Only way to get the network cables to show back up as connected is to reboot the dom0.
Now here is the kicker, I am passing through physical NIC cards to each of my domU. I have a server card with 4 NIC ports/devices and am using 2 on one domU and one on the other with 1 left over for another project I have not started yet. The network cables are not actually unplugged. I have tried disconnecting and reconnecting the physical cable with no results.
If I do a pci-detach and pci-attach of the same device, there is no change. But if I detach the errored one and attach the spare NIC it works, until I do another reboot. And since I’m actually doing an initial install on one of the domU’s I’m having to reboot quite frequently. Once the NIC is in this state no matter how many times I detach/attach or shutdown/restart the domU they will not come back up.
Nothing has changed hardware wise on the machine.
Anyone got an idea as to why xen is misreporting the NICs as having the cable unplugged?
I am running the same dom0 kernel I compiled back in 2015 atm, because I need to troubleshoot a kernel panic my new one is giving me on startup.
