[7.385] Interfaces lost in reboot on ESXi

I have a problem installing beta version on my VMware ESXi server. Steps I've taken:
-Create a new VM with two E1000 type network adapters
-Install Astaro
-Login to web interface, skip wizard.
{-Let up2date to prefetch 7.380->7.385 update (I have 7.380 iso)}
{-Click install update}
-After reboot there is no network connectivity

Logging to console after this I still see the IP address before the login prompt, but ifconfig shows only loopback interface. E1000 module is also unloaded. Somehow the interface definitions get deleted on a reboot.

Note that this also happens if I don't do the up2date to 7.380. Also happens if I restore a working config from another box. It works until first reboot and then loses interfaces.

I have tried taking exactly same steps on a real hardware (Dell 2650) and it works as it should.

Also if I try to up2date my currently working (latest non-beta Astaro) virtual machine to 7.385 I get this same behavior. All ok until the first reboot.

Do you have any suggestions? Anyone running in a VM not seeing this?

0 BrucekConvergent over 16 years ago

I'd almost be willing to bet it's the same issue as this:

https://community.sophos.com/products/unified-threat-management/astaroorg/f/95/t/67243

Looks like the up2date rehashed the init scripts...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 KillJoy over 16 years ago in reply to BrucekConvergent

Also happens on 7.380, so this is not same issue.

E1000 module does not get loaded at all. I can load it by hand and restart mdw, but still no go. I'm going to check if there is documentation somewhere on how to (try) configure ip address from command line the proper way (not directly with ifconfig)...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 da_merlin over 16 years ago in reply to KillJoy

Whats in /etc/modules and /etc/modules.conf ?

Should have something like:

[/etc/modules]
e1000

[/etc/modules.conf]
alias eth0 e1000
alias eth1 e1000
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 KillJoy over 16 years ago in reply to da_merlin

A-ha!

/etc/modules:
vmxnet

also this is in /etc/init.d/vmware-tools:
if ! grep -q vmxnet /etc/modules
then
echo "vmxnet" > /etc/modules
echo "alias eth0 vmxnet" > /etc/modules.conf
fi

So... this means Astaro forces usage of vmxnet driver when running on vmware. Too bad since I have a lot of problems on ESXi if I switch to vmxnet type network adapters. Astaro kernel panics on vmxnet driver. This was the case with 7.380, I haven't tried with 7.385 yet though.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 theproto over 16 years ago in reply to KillJoy

I am running ASG 7.380 and have upgraded to 7.385 without issue on ESXi 3.5 U3.

I have chosen to do the initial install fro mthe ISO opposed to using the virtual machine image since VMware tools is included in the distribution.

I have yet to run into a single network issue and I am running 4 physical NICs and 4 virtual networks.

vmxnet is being used and the initial install was done at 7.300.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 KillJoy over 16 years ago in reply to theproto

Good to hear theproto,

Are you using ipsec vpn connections? If I recall the appliance kernel panicked as soon as site-to-site vpn connection established.

I will try installing again with vmxnet tomorrow.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 theproto over 16 years ago in reply to KillJoy

KillJoy,

I am using IPSEC for user VPN connections but have not attempted to open a site to site tunnel on this platform yet.

I do have an ASG 120 on order and may need to try that out if I have the time.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thilo over 16 years ago in reply to theproto

Hi all,

I have a very simple Test-Setup with VMWare Workstation. Updatet to 7.380 and just changed the internal IP. no problems until this point, rebbot was workuing fine.

Next Step: applied 7.385, after reboot no access to webadmin, within ifconfig we will find nothig else then the "lo" interface.

Maybe there is an essential Problem with the VM-environment, not with special astaro-konfig like VPN etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thewood16 over 16 years ago in reply to thilo

When setting up your VM in ESX use SUSE linux as the OS - this allows you to not use the E1000 driver and allows you to use the flexible. I had the same problem on reboot losing the interfaces this seems to have resolved the issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel