upg 4.3.6 -> 4.3.8 modifies VM settings

[papin]

Host : XP Pro SP3
Guest : XP Pro SP3
Version : 4.3.6-91406

Downloaded and installed the newer 4.3.8-92456. A few remarks about this:

• downloaded the .exe from a third party because from the main website was extravagantly slow (< 30 kbps); same laziness for the extension pack, but no choice
• installation took a much longer time than usual

Bug 1: VB complains about the Intel Wireless Wifi 4965 AGN card connected to the 2nd NAT (access by bridge), and powers off the VM.

Disconnected the 2nd NAT. Restart.

Bug 2: After 2 or 3 failed attempts, loading XP in safe mode with F8. Some drivers load, then the VM shuts down unexpectedly.

Somewhere in the log, there are a few lines like this one:
00:00:17.580966 PIIX3 ATA: LUN#1: disk read error (rc=VERR_NO_MEMORY iSector=0xbc5b0f cSectors=0x80)

After I reverted to 4.3.6, the second crash kept on happening. I decided to verify the VM's settings.

I discovered the new 4.3.8 modified the .vdi storage:

• before upgrade, the .vdi was a SATA hard drive
• after upgrade, the .vdi was an IDE hard drive

In short, 4.3.8 may not like the settings of your VMs!

Don't know whether this behavior can be reproduced as I do *not* want to damage my VMs.

Please excuse me if this report is bad, it's the first time I fill a bug report.

[Frank Mehnert]

We need some case to reproduce. At least the VBox.log files from your 4.3.6 session as well as from your 4.3.8 session, otherwise we can't help you. The 4.3.8 log should still be in your settings folder even if you switched back to 4.3.6. Also having the 4.3.6 + 4.3.6 settings would help debugging.

It is very unlikely that 4.3.8 moves the disk from a SATA controller to a IDE controller and we never saw a similar report for 4.3.8.

[papin]

Last logs

[papin]

Attached 2 files:

• The logs, including "XP Pro SP3.vbox" ("XP Pro SP3.vbox-prev" is identical)
• The folder found in "Documents/user/.VirtualBox

When I upgrade VirtualBox, the first thing I do is to update the .vbox-extpack file to the same version number.

Regarding the HDD, I am positive that it was plugged into SATA and not IDE. One proof is the VM always ran successfully before I underwent the upgrade. A second proof is that the VM will not work if the .vdi is not correctly attached to the right controller. And a third proof is that I had to move the HDD from the IDE controller to the SATA controller which was empty. I have a laptop and I think VM are better off on SATA controllers using AHCI, especially for Windows.

I am also very careful with my .vdi files because once I opened some of them under Linux and they couldn't be opened under XP afterwards. So, when a Windows guest is working (and particularly the one that is concerned here because it contains special data), I never touch the storage settings again.

From all the above, I'm ready to sustain that 4.3.8 did modify the storage settings, because I didn't do it (and why would 4.3.6 do that?).

Once I posted this, I'll upgrade to 4.3.8 to see if it happens again. Of course, I'll check my backup first and do one if necessary.

[papin]

Logs - Last backup

[papin]

Found the last backup, done on January 5 this year. File name: "Logs_201401.7z". Included the .vbox file.

[papin]

Bug #1

[papin]

I upgraded 4.3.6 to 4.3.8.

I could reproduce Bug 1. See the last attachment "NAT error.png".

I couldn't reproduce the bug #2. I guess at some time something went wrong regarding the storage setting. Let say this issue is closed.

But, there is a big "but" now. Let's call it

Bug 3: My Internet connection is broken !!!

• No Internet connection inside the VM
• No Ethernet, no Wifi, no Nothin'
• Unable to fix the problem using MSIE (using the repair plugin)

How to fix Bug 3:

1. Uninstall 4.3.8. Afterwards, Internet connection still broken :(
2. Reinstall 4.3.6
3. Use Windows' restoration tool. Restore point: just before the first upgrade

Now, I'm tired of this 4.3.8, too much time lost for no real benefit for my limited uses. I will not try to reproduce "Bug 3".

This will be my last post unless somebody wants me to do some tests or attach some files.

[papin]

In case you wonder. After I reinstalled 4.3.6 and before restoring XP, the Internet connection was still broken. This is why I restored to the last good working Windows.

[papin]

Since I could reproduce "Bug 1" I'm filing it under another ticket: "VERR_INTNET_FLT_IF_NOT_FOUND crash at startup"

[papin]

"Bug 1" filed. See Ticket #12790

[papin]

VB 4.3.8 - Logs after the second upgrade (i.e testing) from 4.3.6 - VM started, closed via OS shutdown

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.