Florian Stöhr
unread,Sep 20, 2011, 6:41:10 PM9/20/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to OXID e-Shop Virtual Machine
Hi,
I modified the VM frontend so in case of an IP problem, it will just
spawn a root shell and not crash anymore.
I had a case myself ... problem was that the debian OS received eth1
as network interface, not eth0. The VM frontend will catch this now
(and use eth1 or eth2 if available), but the DHCP client on the VM
will scan for eth0 only.
We will fix that with the next VM snapshot (I cannot fix this
remotely).
In order to fix it manually, you may
- update the VM frontend via menu
- spawn a root shell
- edit the file /etc/network/interfaces
- replace
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
by this:
# The primary network interface
allow-hotplug eth0
allow-hotplug eth1
allow-hotplug eth2
iface eth0 inet dhcp
iface eth1 inet dhcp
iface eth2 inet dhcp
(so adding identical eth0-like configs for eth1 and eth2).
-Flo