Hyper-V with 2 Legacy Network Cards issue

[Darren]

Hi,

We installed the version turnkey-lamp-12.0-squeeze-x86.iso today, everything went well, we use Hyper-V and have 2 legacy cards set, one for WAN, one for LAN.

The 2 IP addresses were set (external and internal), and everything was responding on both networks fine, until it was restarted.

Upon a restart, one of the network settings were lost, resulting in just one card being set, I tried this a number of times and the same results were obtained, the only way it would be OK, was if I only used one network card.

I re-installed on the same virtual turnkey-lamp-11.3-lucid-x86.iso, the version 11.3 and this works fine.

I used the legacy network adaptor in Hyper-V as need to use this version, and confirm that both the networks were different.

Regards

Darren

[Jeremy Davis (jedmeister)]

How did you configure the cards? Did you do this manually? Via Webmin?

[Darren (darren-hst)]

Hi,

Thank you for your reply.

I used the console to configure these, via Static IP (Not DHCP), with one IP it was fine, with 2 IP's this was an issue, only one was allowed, I can confirm that using the same Hyper-V settings, the older version worked fine.

I have LAN and WAN adaptors.

If you need anything else, want me to test anything, please let me know.

Regards

Darren

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of JedMeister
Sent: 15 September 2012 15:08
To: <email address hidden>
Subject: [Bug 1045320] Re: Hyper-V with 2 Legacy Network Cards issue

How did you configure the cards? Did you do this manually? Via Webmin?

** Tags removed: issue turnkey
** Tags added: hyper-v

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1045320

Title:
  Hyper-V with 2 Legacy Network Cards issue

Status in TurnKey Linux:
  New
Status in TurnKey Linux 12.x series:
  New

Bug description:
  Hi,

  We installed the version turnkey-lamp-12.0-squeeze-x86.iso today,
  everything went well, we use Hyper-V and have 2 legacy cards set, one
  for WAN, one for LAN.

  The 2 IP addresses were set (external and internal), and everything
  was responding on both networks fine, until it was restarted.

  Upon a restart, one of the network settings were lost, resulting in
  just one card being set, I tried this a number of times and the same
  results were obtained, the only way it would be OK, was if I only used
  one network card.

  I re-installed on the same virtual turnkey-lamp-11.3-lucid-x86.iso,
  the version 11.3 and this works fine.

  I used the legacy network adaptor in Hyper-V as need to use this
  version, and confirm that both the networks were different.

  Regards

  Darren

To manage notifications about this bug go to:
https://bugs.launchpad.net/turnkeylinux/+bug/1045320/+subscriptions

[Jeremy Davis (jedmeister)]

I have just had a big search online and don't have a clear answer. I also have never used Hyper-V so have no way of testing. The Debian wiki page on Hyper-V (http://wiki.debian.org/WindowsServerHyperV) is quite out of date, but gives some sound advice IMO "Microsoft Virtual PC is a non-free (proprietary) software. It isn't supported by Debian. It's probably wiser to use a free Virtualization tool." As you may or may not be aware, TKL v12.0 is based on Debian.

So with that in mind, perhaps the Debian kernel driver bug mentioned in that wiki (this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490816) is still relevant in 2.6.32 (the kernel in TKL)? I think it may be...

So let me provide a guesstimate of what is happening: TKL Confconsole manages to somehow avoid the problem of the first NIC appearing as unplugged, but as Confconsole only applies to one NIC (I don't think it can even be configured to handle 2?)

If that's the case it would explain why it worked fine, but disappeared on reboot.

So let me suggest a possible workaround - installing the 3.2 kernel from backports. Apparently the Hyper-V drivers in 3.2 were/are still pretty flakey, but apparently the 3.2 kernel in Debian backports contains drivers backported from 3.4 kernel (where they have finally been fixed).

So, enable the backports repo and install the newer kernel, folled by a reboot. Hopefully you won't, but perhaps you'll need to reconfigure your second NIC. I would test this on a TKL install that doesn't matter, as there is a serious risk that it could go very pear shaped! Be warned - backup anything that matters! So here is the code to try:

echo 'deb http://backports.debian.org/debian-backports squeeze-backports main' > /etc/apt/sources.list.d/squeeze-backports.list
apt-get update
apt-get install -t squeeze-backports linux-image-3.2.0-0.bpo.3-686-pae

[Jeremy Davis (jedmeister)]

I have confirmed that this is a bug in confconsole (or one of the supporting packages). Whichever interface is last edited seems to stick beyond reboot, the other is lost.

[Jeremy Davis (jedmeister)]

PS I don't think this is Hyper-V specific, I had the same issue in VirtualBox

[Alon Swartz (alonswartz)]

Fix committed and will be included in upcoming release as well as package archive update.

For those who need the fix and can't wait for the archive update:
/usr/lib/confconsole/ifutil.py
- if line.startswith("auto") or line.startswith("iface"):
+ if line.startswith("auto"):