Network Interface error
10 views
Skip to first unread message
Chalasani, Ashant
Aug 30, 2011, 5:07:11 AM8/30/11
to oxidvm
Checkout the latest OXID e-Sales Virtual Machine 2.0.
Chalasani, Ashant
Oct 2, 2011, 6:43:58 AM10/2/11
to oxidvm
Now this looks completely jacked. See attached.
How can I exist the Management Console, get to the root prompt and fix this?
TIA / Ashant
Attached error is obtained when the VM is (attempted) loaded on a Host which doesn't have network access.
This is how one would integrate a JQuery Datepicker in OXID Admin.
Stöhr, Florian
Oct 15, 2011, 12:45:37 PM10/15/11
to oxi...@googlegroups.com
Hi,
you cannot. It is not made to run on a non-networking host (what
should it be good for without network?). frontend is login-shell for
root, but you may login with the other user name.
-Flo
Chalasani, Ashant
Oct 17, 2011, 4:14:55 PM10/17/11
to oxi...@googlegroups.com
Hi Flo,
There should be networking on the VM, but not necessarily on the host. It could be quite a usual use-case for the VM that a programmer is travelling on the train or sitting out in the city-park, or simply doesn't want to get ripped off by his mobile-carrier for broadband when changing airports;)
My VM is currently jacked, and I don't know how to get it back; hence I haven't been able to write code on it.
Chalasani, Ashant
Oct 22, 2011, 1:40:14 PM10/22/11
to oxi...@googlegroups.com
Next trial was to select Debian's Recovery Mode at boot-time on GRUB. It also brought the management console up, again with the failing Python scripts.
IMHO it would be a good idea to skip the MC in recovery mode.
Ashant
Stöhr, Florian
Oct 27, 2011, 5:43:11 AM10/27/11
to oxi...@googlegroups.com
Ah, now I understand. Of course you're free to set it up for static
networking -which requires linux skills- or sharing with the host
only. The *normal* use case in your company network is "bridged" so it
will get its IP from the router. In the travelling case, this doesn't
make any sense as it will of course not get any IP. Just the NAT route
is completely useless at it will not allow accessing the VM from the
laptop, only the other way round.
networking -which requires linux skills- or sharing with the host
only. The *normal* use case in your company network is "bridged" so it
will get its IP from the router. In the travelling case, this doesn't
make any sense as it will of course not get any IP. Just the NAT route
is completely useless at it will not allow accessing the VM from the
laptop, only the other way round.
-Flo
Stöhr, Florian
Oct 27, 2011, 5:44:27 AM10/27/11
to oxi...@googlegroups.com
not possible. script is setup as rootshell. you can boot single-user,
log in as the other user and sudo the commands. anyway i cannot detect
whether it is running in recovery mode or not.
log in as the other user and sudo the commands. anyway i cannot detect
whether it is running in recovery mode or not.
On Sat, Oct 22, 2011 at 11:10 PM, Chalasani, Ashant
An Schall
Oct 12, 2012, 3:41:28 AM10/12/12
to oxi...@googlegroups.com, flor...@euroblaze.de
Hey there,
I got the same error message as in vm_error.png as well. The VM is configured with a network bridge and my host system is connected to the internet via WiFi. I tried different host OSes including Ubuntu, Mac OSX Snow Leopard and Win 7. The VM always stucks while booting with that error message. I am using virtualbox 4.2. and I also tried all the different options of the network device regarding the promiscious mode. No success. Using NAT of course lets the vm boot successfully but it is not assigned a valid ip (10.0.x.y) therefore the machine is not accessible from the outside.
What am I doing wrong?
Cheers
I got the same error message as in vm_error.png as well. The VM is configured with a network bridge and my host system is connected to the internet via WiFi. I tried different host OSes including Ubuntu, Mac OSX Snow Leopard and Win 7. The VM always stucks while booting with that error message. I am using virtualbox 4.2. and I also tried all the different options of the network device regarding the promiscious mode. No success. Using NAT of course lets the vm boot successfully but it is not assigned a valid ip (10.0.x.y) therefore the machine is not accessible from the outside.
What am I doing wrong?
Cheers
Chalasani, Ashant
Oct 14, 2012, 4:42:48 AM10/14/12
to oxidvm
The guy who originally designed the VM is not with the company any longer. We'll have to look into this, but am not able to commit a solution-timeframe.
In the meanwhile, we'd appreciate any insight you may have developed into the problem.
Regards
Reply all
Reply to author
Forward
0 new messages