Hi you all:
Since I updated virtualbox to version 3.0.2 and still with 3.0.4 , my WindowsXP SP2 Virtual machine started to crash whenever I start a session on it.
Tweaking, I have noticed that if I disable my network interface on the HOST, then login into my windows machine, and finally enable my network interface on the HOST again, my Windows Machine works well, except for the NETWARE CLIENT that can't find the "NETWARE TREE".
In version 3.0.2, the problem was intermittent, and when I started the Virtual Machine again, It showed that a problem has occurred (I dont remember the error message, exactly)
Now, in version 3.0.4, the Virtual Machine crashes and when I stat it again, there is no message.
Is there a Bug introduced in version 3.0.2?
OR
How can I find a solution to this problem?
WinXP crashes on login Fedora Host
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: WinXP crashes on login Fedora Host
This is usually fixed by changing the virtual network adapter to the IntelPro/1000 T server on the guest.
-
solinem
- Posts: 24
- Joined: 1. Nov 2008, 02:26
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: WinXPsp2
- Location: Mexico City
Re: WinXP crashes on login Fedora Host
Thanks for your reply!!Perryg wrote:This is usually fixed by changing the virtual network adapter to the IntelPro/1000 T server on the guest.
I have changed the adapter to IntelPro/1000 T server, but the problem persists.
Is there any other solution?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: WinXP crashes on login Fedora Host
This usually fixes this but there are a lot of other reasons this may be failing. If it were mine I would make sure the host was up-to-date, then I would re-install the VBox program and select repair to make sure that all the package, and drivers were installed properly and then after starting the guest I would reinstall the guest additions, and make sure that the guest was up-to-date. Other than that it would be difficult to fix over the forums. I would need to actually touch the unit to figure it out. You can look at the VBox logs and see what it says. Maybe that will show you something that you could try.