Discuss the 5.0.12 release

[loukingjr]

I did suggest to Bobbix he post to Bugtracker and he said he would but I guess we'll see.

And your correct Don, I think it's been covered.

[Bobbix]

I did suggest to Bobbix he post to Bugtracker and he said he would but I guess we'll see.

And your correct Don, I think it's been covered.

Hi, i've been already blocked in "suggestions" Forum by moderators, because cross-posting is not permitted.
I think it's the same rule for "Bugtracker" forum.

The developers can see the Bug here too... and i'm sure this is already a known problem.
Thanks to all (if i will have sufficient time i will try to make a better video and a complete testing with more than two hosts).

For my issue i think we have already discussed a lot... i don't need to add other.
Merry Christmas to You all.

[Perryg]

I did suggest to Bobbix he post to Bugtracker and he said he would but I guess we'll see.

And your correct Don, I think it's been covered.

Hi, i've been already blocked in "suggestions" Forum by moderators, because cross-posting is not permitted.
I think it's the same rule for "Bugtracker" forum.

--> No it is not. That is where you should post the issue

The developers can see the Bug here too... and i'm sure this is already a known problem.
Thanks to all (if i will have sufficient time i will try to make a better video and a complete testing with more than two hosts).

--> The DEVs do come by but it is not often and the bugtracker is the proper place for this issue. If you don't post this there it may never get corrected.

For my issue i think we have already discussed a lot... i don't need to add other.
Merry Christmas to You all.

[socratis]

There seems to be an audio regression bug in OSX clients. More details on viewtopic.php?f=22&t=75363

[Sakiyurai]

Virtualbox 5.0.10 & 5.0.12 breaks Ethernet adapter?

I had Windows 10 Pro build 1511 working with Virtualbox 5.0.6, installed the new 5.0.12 and connection breaks. Intel 82579V network adapter shows up as "unidentified network". Saw Virtualbox Host-only adapter appearing that wasn't there before. Also noticed IPv4 was missing when I did a ipconfig /all command. Windows network adapter diagnose said "One or more network protocols are missing on this computer". Had to system restore to get things working again.

Anyone run into this problem?

[Armando]

Virtualbox 5.0.10 & 5.0.12 breaks Ethernet adapter?
...
Anyone run into this problem?

I remember running into a quite similar problem a few years ago, while upgrading VBox in a WinXP x64 host.
After the (flawless) upgrade I found out I had no more Ethernet connection. The adapter was reported as "running" in Device Manager but simply had stopped working. After several attempt (disable/enable, uninstall driver and so on) I ended up re-installing the whole host OS and everything as I didn't have any system backup (my fault there). Since then I always made registry backups before upgrading VBox and so, obviously, the broken NIC never occurred again... :]

So maybe this is not an issue with a certain VBox release but something that VBox can rarely cause on some systems.
Any hint about possible causes would be useful anyway.

[rsktuxedo]

I just had a similar problem as Sakiyurai, but it doesn't appear to have been the result of an upgrade, though I originally thought so. I've managed to get my network working again, though I can't say what step made the difference, so the following may or may not help.

Win7 host, CentOS 7 guest. I was running 4.3.32, then upgraded to 5.0.8 and 5.0.10 in November, and finally to 5.0.12 today. The last time I can verify that the network had worked was 12/22/2015, based on the guest's yum history, and I've not found anything that changed after that date. I first noticed the problem on 12/28.

I tried creating a new NAT, NatNetwork1, with a different address range and DHCP enabled, then assigned it to the guest. This step may have worked, but I discovered later that I had configured a static IP in the guest, so I don't know.

Next I switched to a bridged network connection, which also failed because of the static IP. Once I discovered that config problem and set the guest to use DHCP, the bridged connection worked.

I decided to test NatNetwork again, and discovered it was working.

So, you might benefit from switching (permanently or temporarily) to a different type of network connection on your guest's Ethernet adapter.

[jrc55]

After upgrade from 5.0.10 to 5.0.12 I cannot start a guest after a restore any of my Linux Fedora snapshots. I get a ....
Failed to load unit 'hda' (VERR_INVALID_PARAMETER) .... vrc=VERR_INVALID_PARAMETER, rc=E_FAIL (0X80004005)

I can "discard" the state and the guest will do a proper cold start.

I have even installed a clean Fedora KDE 23 which works fine but it too will fail to restore a saved snapshot.

Host is Win 8.1 with 16 GB
Guest is Fedora KDE 64 with guest additions. 3GB memory

[mpack]

Frankly, we've been telling people for years not to upgrade VirtualBox while VMs are in a suspended state. It's just begging for trouble. It seems to me obvious that if the underlying virtual hardware changes in any way then the contents of the sav file might be rendered useless. Happily the worst outcome is that you have to discard the saved state - and we have to hear about it.

[jrc55]

>we've been telling people for years not to upgrade VirtualBox while VMs are in a suspended state.

Sorry I wasn't clear enough. Let me try again. I had trouble with an existing VM after the upgrade but let's ignore that. While in 5.0.12 I installed a fresh Fedora 23 KDE 64bit into a new VM. After a while I successfully saved a snapshot. Then after a short time I tried to restore to that snapshot. But it fails to restore. I can discard the saved state and Fedora completes a cold boot as it should.

I agree that upgrading VB while a VM is in a suspended state is a bad idea. I would even go so far as to recommend to the developers they put in some kind of warning during the upgrade install ... to give the user a chance to abort the upgrade and power off the VM's in a normal manner. We humans are an excitable bunch aren't we. And we sometimes forget that in the excitement over a shiny new upgrade for a product we've all come to love so much.

Thanks for your time.

[socratis]

Take a look at viewtopic.php?f=2&t=75335

[mpack]

Sorry I wasn't clear enough. Let me try again.

Ah, thanks. I didn't realize the bug was that serious, but I've now seen more discussion of it elsewhere, including a test build. I see that Socratis has posted a link.

[jrc55]

Thanks for pointing me to the other thread with the test build. But .... sadly the 5.0.13.r104845 did not fix my problem.

I get the same error while testing it under different scenarios but I got another message too. I am attaching another log since that other error message which may prove useful ....
Unsupported version 5 of data unit 'hda' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION)

If there is a sequence of events I should follow regarding old/new snapshots/etc then please advise.

Thanks for you help. Cross fingers.

[mpack]

We prefer not to have duplicated discussions on this site, so it would be best if those with HDA saved state problem participated the other discussion since a dev is already involved there.

[Sakiyurai]

Virtualbox 5.0.10 & 5.0.12 breaks Ethernet adapter?
...
Anyone run into this problem?

I remember running into a quite similar problem a few years ago, while upgrading VBox in a WinXP x64 host.
After the (flawless) upgrade I found out I had no more Ethernet connection. The adapter was reported as "running" in Device Manager but simply had stopped working. After several attempt (disable/enable, uninstall driver and so on) I ended up re-installing the whole host OS and everything as I didn't have any system backup (my fault there). Since then I always made registry backups before upgrading VBox and so, obviously, the broken NIC never occurred again... :]

So maybe this is not an issue with a certain VBox release but something that VBox can rarely cause on some systems.
Any hint about possible causes would be useful anyway.

So the fix is to make a registry backup before upgrading VBox? How does that prevent the broken NIC?