I think this was working properly before. Oh well, I'll keep going. Replying to JamieJackson :. BTW, according to my "steps to reproduce" you'll see that this time I was enabling the NAT connection, and that caused error this time. I think I've also had the problem on bridged connections. After reboot Win find all interfaces and now working correct. Same here on Ubuntu 9 with WinXP as guest.
It seems that as soon as more than one network connection is present in the guest, it's not working to re-enable one disabled interface. Duplicate of , fixed in SVN. Contact — Privacy policy — Terms of Use. Login Preferences. Browse Source. There are no problems with 5. So one have had to change the setting to the PIIX3 to get guru meditation. I saw some changes in Git because of some register problems between 5.
My host is Windows 8. Hope this could help. You say that you can also reproduce this Guru with VBox 5. Could you attach a VBox. Thank you! So after installing 5.
I thought that guru meditation was fixed, but later I could see that I was wrong. After BSOD in the guest guest OS restarts automatically and tries to go into recovery, there are two choices here, normal start and the recovery mode. But recovery also fails because of the BSOD.
SYS, tries to start and fails here once again. So now the VM is in the infinity loop of the recovery mode until one downgrade to the working version.
Lucky for me somebody else already got some problems with a new version and this ticket suggested the change of the chipset as a temporary solution for the problem. If you take a look at the changelog, you will see, that there are some changes in the 5. And there are more changes in the 5. Looks like it was here all the time, we just simply got one more issue earlier with chipset with x86 guests in the 5.
I hope now is everything clear. One more interesting thing. After changing the chipset and starting VM I got a guru as usual on 5. So I boot the guest in the safe mode, which was always possible.
This time OS saw the hardware changes and asked me to reboot the system to apply the driver changes. This time the VM was simply blown away with exception, so I only saw the manager on the screen. Next boot in the safe mode went without any problems. I completely understood that you got a BSOD with 5. Of course this works only once you are able to fully boot your guest.
From your above description I also understood that this Guru is a 5. Thanks for the additional logs. I red in the change log, that only the x86 raw mode clients were affected.
In spite of the fact that my virtual HDD is a normal file and not a raw mode device, the 5. I know about the control panel setting. One can also do this by pressing F8 at the very beginning of the boot process and selecting the item with disabling reboot in case of error.
As already mentioned I can start a guest OS in safe mode without any problems. So the triggered instruction must be in some driver or service which is only loaded in the normal start scenario. At the end I like to mention, that this guru meditation is here from 5. As long as 5.
Just a comment I still have the guru meditation with 5. Not more or less. Install the Guest Additions. Currently you have the GAs CD mounted but you did not run the installer. Remember to eject the CD later. I note that you are running the VM from drive D:. I hope that this is not a USB flash drive, as those will be very slow and are also most likely to overheat and destroy themselves trying to be the primary drive for an OS they are designed to transport data, not be written to continuously as will happen when running Windows.
0コメント