No Network within WinXP and NAT

[voojagig]

Hi

Since I had to reboot my box because of a hanging Screensaver my guest OS (WinXP) doesn't get a IP address anymore. It worked fine for several weeks. But since that reboot just nothing. I do use NAT and the PCnet-FAST III network driver.
If I try to switch to host adapter or bridge and start the guest it reboot immediately.

I don't see anything in /var/adm/messages or in the virtual box log.

On Solaris I have following network running:

root@Marvin:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
inet [public IP removed] netmask fffffe00 broadcast 129.156.59.255
ether f0f1:5f:2a:a8
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
inet6 ::1/128
e1000g0: flags=20002004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::f2de:f1ff:fe5f:2aa8/10
ether f0f1:5f:2a:a8

On the guest I see:

C:\Documents and Settings\robert>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : rkriz-vm
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : uk.oracle.com
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapte
r #2
Physical Address. . . . . . . . . : 08-00-27-2A-CA-02
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 10.0.2.2
DNS Servers . . . . . . . . . . . : 192.135.82.44
192.135.82.60


I read somewhere I need to add:
ifconfig vboxnet0 plumb up

But that doesn't help.

Any hint how to solve this?

Thanks
Robert

[Sasquatch]

As it looks like in your post, the Guest doesn't get an IP address. Check if the DHCP Client service is still running and execute ipconfig /renew on the Guest to see if that helps. If nothing helps, then check the IP configuration in the interface properties. Last option is to give it a static IP of 10.0.2.15, netmask 255.255.255.0, gateway 10.0.2.2. DNS: whatever you host has, but it seems that the Guest has that already.

[voojagig]

I check all the settings and there where fine. From XP and VM side.
- ipconfig /renew doesn't help
- dhcp was set in the client at TCP/IP level (I have no idea how to check dhcp client in XP if there is a way)
- setting a static address doesnt' help
- setting bridging mode reboots the notebook when starting the guest
- setting host adapter mode reboots the notebook when starting the guest
- VB is running as user and not root, but reboots immediately in above two settings ?

Yesterday I reinstalled the XP guest and it works again with exactly the same settings. I don't know what happens but I guess after the enforced shutdown the Windows recovery mixed something up.

So far I'm fine and hope it doesn't happen again.
Side question: Are there any strong BIOS settings that VirtualBox relies to?

thx
Rob

[Sasquatch]

There aren't any specific BIOS settings that are required for VB, but some do help. E.g. enabling hardware virtualisation will allow you to run 64 bit Guests if the CPU is 64 bit. It also allows you to give a VM more than one CPU/core. But there is a security setting, I believe it was called virtual execution or something, that can break hardware virtualisation support in VB.
If the Host suddenly reboots when using certain network settings, it would seem you have either a corrupt installation for those kernel modules or you have a bug. The latter is not very likely, because you're the first I see that mentions this (but then again, I don't read the Solaris Hosts section much).

[Ramshankar]

More relevant information would be useful.

1. Which Solaris version are you using as the host?
2. Which reboots when you start with bridged/host-only network modes? Guest or the host?
3. Upload a copy of your VBox.log for the VM in question.