My VirtualXp inside linux Host no inet after last update

Discussions related to using VirtualBox on Linux hosts.
Post Reply
ag3r
Posts: 2
Joined: 20. Feb 2008, 12:05

My VirtualXp inside linux Host no inet after last update

Post by ag3r »

Hi Guys!!

I wish you could help me

Well, this morning i updated (Ubuntu 7.10) virtualbox to version 1.5.6, when i was asked about removing old modules, i said yes, and now i don't have inet/lan in my virtualXp :cry: .

The VirtualXp is connected to a Windows 2003 server lan with a Domain, the router has no DHCP activated, and all the pcs in the lan has a static ips.

I have bridged the network connection to make it function, and the Linux host and the VirtualXp has different ips , the "/etc/network/interfaces" look like this :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.0.229
netmask 255.255.255.0
gateway 192.168.0.50

auto tap0
iface tap0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
tunctl_user angel

auto br0
iface br0 inet static
address 192.168.0.124
netmask 255.255.255.0
gateway 192.168.0.50
bridge_ports all tap0


The Linux Host has 192.168.0.229 ip
The VirtualXp has 192.168.0.124 ip
The router has 192.168.0.50 ip
The server who gives domain has 192.168.0.200 ip

pd: I'm from Spain, sorry for my english. Thx a lot.
sc0tty2h0tty
Posts: 6
Joined: 10. Jan 2008, 13:38

Post by sc0tty2h0tty »

I am in exatctly the same situation, running ubuntu server 7.10, upgrade this morning has killed my guest VM'snetworking.

my /etc/network/interfaces:

Code: Select all

auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual
        up ifconfig $IFACE 0.0.0.0 up
        down ifconfig $IFACE down

# network bridge, used by VirtualBox to provide networking access to guest OS's
auto br0
iface br0 inet static
        address 10.101.101.9
        netmask 255.255.255.0
        broadcast 10.101.101.255
        gateway 10.101.101.1
        bridge-ports eth0 vbox0 vbox1 vbox2
        bridge-ageing 7200
        bridge-fd 0
brctl show br0 shows the following:

Code: Select all

bridge name     bridge id               STP enabled     interfaces
br0             8000.0013723272ce       no              eth0
                                                        vbox0
                                                        vbox1
                                                        vbox2
sc0tty2h0tty
Posts: 6
Joined: 10. Jan 2008, 13:38

Post by sc0tty2h0tty »

I have tried downgrading to 1.5.4 but get the follwong in the VirtualBox GUI:

one of my VM's status is listed as Inacecssible, with the follwing in the details:

Could not load the settings file '/root/.VirtualBox/Machines/rootTIM/rootTIM.xml' (VERR_OPEN_FAILED).
FATAL ERROR: Unknown element 'IDEController'
Location: '/root/.VirtualBox/Machines/rootTIM/rootTIM.xml', line 34, column 38.


Result Code:
0x80004005
Component:
Machine
Interface:
IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}
so not only has it broke my install,but if i revert, it still does not work :-(
sc0tty2h0tty
Posts: 6
Joined: 10. Jan 2008, 13:38

Post by sc0tty2h0tty »

I have got it working again by reverting to 1.5.4.

goto http://www.virtualbox.org/wiki/Download_Old_Builds

download the relevant version.

run

Code: Select all

sudo dkpg -i virtualbox_1.5.4-27034_Ubuntu_gutsy_i386.deb


reload VirtualBox

you may get the error specified above - this is due to the modifications to the XML made by 1.5.6 for the extra features. you need to edit the XML file and delete the tags corresponding to the new features ( <IDEController type="PIIX3"/> and writable="true" for the <SharedFolders> tag on mine, you may have more or less) and reload the GUI. then restart the guest - networking now works again.


now that i am back to square one, can anybody explain how i can upgrade and not lose networking,and why this happens?
JshWright
Volunteer
Posts: 119
Joined: 13. Sep 2007, 00:33
Primary OS: Debian Lenny
VBox Version: OSE self-compiled
Guest OSses: Many...

Post by JshWright »

As mentioned in another thread in this forum, the host networking issue in 1.5.6 has been resolved. Reinstall with the updated 1.5.6 packages.

~JW
Post Reply