Discuss the 4.3.22 release

[mpack]

@g2flyer: please discard the saved state associated with the VERR_NO_MEMORY VM. In future, best make sure VMs are fully shut down before you swap software versions from underneath them.

[ltbmoran]

Anyone's got problems with PXE-booting VM's? After the upgrade to 4.3.22 from 4.3.20 my VM's fail to PXE boot.

Yes. Unfortunately it's just broken in 4.3.22 (in a rather indirect way) and there's no workaround. If you need PXE, I'm afraid you have to go back to an earlier release.

PXE Boot is broken for me as well in 4.3.22. Reverting to 4.3.20 is the "workaround" I have used.

[Oblivion9999]

I am having the same resetting NAT problems other users have mentioned.
I upgraded to the 4.3.22 release yesterday, also upgrading Guest Additions on my two guests (and rebooting the guests after installation).
Host: Win 7 Pro SP1 64-bit 8GB RAM
Guest1: Debian Wheezy 64-bit, 3GB RAM
Guest2: Debian Wheezy 64-bit, 1.5GB RAM
Guest logs attached.

Networking was stable on 4.3.20, but now it resets periodically and connections, such as ssh, are dropped.

Let me know what else I can provide. This is an irksome bug.

Thanks.

[apaton]

Another report to say that NAT is causing regular network drops, on Windows 7 64bit host, with Debian Wheezy and Windows 8.1 guests.
Its unusable!! SSH & VPN drops.

Errors from kernel of Wheezy Guest
....
Feb 18 09:54:37 linpaton kernel: [46500.529257] e1000: eth0 NIC Link is Down
Feb 18 09:54:41 linpaton kernel: [46504.537222] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 18 09:55:39 linpaton kernel: [46562.680711] e1000: eth0 NIC Link is Down
Feb 18 09:55:45 linpaton kernel: [46568.693386] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 18 09:57:41 linpaton kernel: [46684.964512] e1000: eth0 NIC Link is Down
Feb 18 09:57:47 linpaton kernel: [46690.980724] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 18 09:58:41 linpaton kernel: [46745.109428] e1000: eth0 NIC Link is Down
Feb 18 09:58:47 linpaton kernel: [46751.129689] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 18 10:04:22 linpaton kernel: [47085.874093] e1000: eth0 NIC Link is Down
Feb 18 10:04:26 linpaton kernel: [47089.881892] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

[g2flyer]

@g2flyer: please discard the saved state associated with the VERR_NO_MEMORY VM. In future, best make sure VMs are fully shut down before you swap software versions from underneath them.

As i wrote, this time discarding saved state makes it work also for the future (not true in earlier versions).

Regarding your suggestion to do proactively shutdown all VMs before an upgrade is not a really good solution when you have lots of VM. And, more importantly, this was never necessary before the problem arrived in 4.3.18!!

[Martin]

There were many times where saved states didn't migrate correctly.
It has always been the official guideline to shutdown all VMs before doing an upgrade.

[mpack]

I don't see how it's possible to expect that a saved state might be portable across versions, when the hardware whose state has been saved might have changed in subtle or even major ways.

If you find the responsibility onerous then it is easily avoided: stop using saved states, fully shut down your VMs every time you use them.

[michael]

Fullscreen mode is stull bust (since 4.3.16): on the second/right screen it is shown only offset and hence only partially.

If you mean what I think you do this is an Ubuntu bug (though we fixed it and they made us jump through hoops to do so) and should now be fixed in 14.04. 14.10 was fixed long ago.

https://bugs.launchpad.net/bugs/1353675

[ShadowAce]

I have found what I believe is a bug that is unique to this version (4.3.22):

Windows 7 Professional as host
Linux Fedora 21 (64-bit) as a guest.

The guest continues to drop the NIC. This prevents me from using ssh from the guest at the least.

When I reverted back to 4.3.20, the problem went away--even though I am using the 4.3.22 Extension pack.

[pl2014]

VPN Problem
After upgrade to 4.3.22, when using VPN I have frequent disconnects and reconnects. This happens with less than one minute intervals and make the connection unusable.
Host OS is Windows 7 with latest patches. Guest OS is also Windows 7 with latest patches.
Connecting through VPN from the host OS works fine, problem only shows up when working in a machine in VirtualBox.

[yohann]

same annoying network disconnects as many others.

host version: 4.3.20
guest addons: 4.3.20
no network disconnect issue

host version: 4.3.22
guest addons: 4.3.22
network disconnect issue visible


host: windows 7 enterprise SP1 64bits, latest updates
guest: debian 7 64bits, latest updates

log attached, not minimalistic but at least it gives something to investigate.

In logs, here is what I can see many times:
NAT: link down
NAT: link up

Her are the previous messages I get before:

00:10:10.387472 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
00:10:13.651351 NAT: link down
00:10:14.315298 EHCI: USB Operational
...
00:29:24.143791 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content..
00:49:30.192070 NAT: link down
00:49:35.193743 NAT: link up
...
01:26:54.915378 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content..
01:32:38.618019 NAT: link down
01:32:43.618387 NAT: link up
...
01:45:47.112191 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content..
01:49:46.244671 NAT: link down
01:49:51.244867 NAT: link up
...
01:49:51.263442 NAT: DNS#2: 135.120.0.246
01:51:06.808138 NAT: link down
01:51:11.808564 NAT: link up
...
01:51:11.820354 NAT: DNS#2: 135.120.0.246
01:52:22.198920 NAT: link down
01:52:27.199262 NAT: link up
...
(many times the same down and up messages)
...

hope this helps, I'll switch back to 4.3.20 for the moment.

Thanks,

yohann

[jgillespie]

VirtualBox Version 4.3.22-98236
VirtualBox Extension Pack 4.3.22-98236
Windows 7 64 bit

Settings > Motherboard > Boot Order: Network is enabled and set to 1st
Network Adapter 1 is Enable and set to Bridged Adapter
I've tried setting the Adaptor Type to: Intel Pro/1000 MT Desktop (82540EM), PCnet-PCI II, PCnet-Fast III

Every time I try to boot the machine, all I get is the message:
FATAL: No Bootable Medium found! System halted.

Also, I'm able to PXE boot physical machines on my network with out any problems.

Thanks

[Edit] Downgrading both virtualbox and the extensions to Version 4.3.20 appears to have fixed the problem

[RunWild]

This is a WARNING about VB 4.3.22.

I am running VB on Windows 7-64. The version I am currently using is 4.3.20.

I installed 4.3.22 and found I was continually getting disconnected from the server for no apparent reason. I uninstalled VB completely and re-installed 4.3.20 and the problem went away. To confirm the issue I completely uninstalled VB again and tried 4.3.22 and the issue returned. I am thus back on 4.3.20.

Just a gotcha! warning!

[devJack]

Not sure if this issue has been mentioned already, i didn't see it, so here it is:
1) VirtualBox not auto-resuming after macbook air goes to sleep. VirtualBox goes into aborted state.
2) Changing internet connection (switching wifis for example) makes VirtualBox go into aborted state. Even connecting/disconnecting from vpn triggers that. Might be this is the real issue behind the one up above.

Downgraded to 4.3.20 and the issue is gone.

VirtualBox 4.3.22 is where I see the issue happen.
MacBook air with OSX Yosemite 10.10.2
Tried creating several new virtual boxes and tested on old ones too. Same issue everywhere.
Tried turning it off and on again

Tried looking at the log, nothing that I can see. Last entry is when the virtual box goes into suspended mode.

[RunWild]

Not sure if this issue has been mentioned already, i didn't see it, so here it is:
1) VirtualBox not auto-resuming after macbook air goes to sleep. VirtualBox goes into aborted state.
2) Changing internet connection (switching wifis for example) makes VirtualBox go into aborted state. Even connecting/disconnecting from vpn triggers that. Might be this is the real issue behind the one up above.

Downgraded to 4.3.20 and the issue is gone.

VirtualBox 4.3.22 is where I see the issue happen.
MacBook air with OSX Yosemite 10.10.2
Tried creating several new virtual boxes and tested on old ones too. Same issue everywhere.
Tried turning it off and on again

Tried looking at the log, nothing that I can see. Last entry is when the virtual box goes into suspended mode.

In my case, the number (2) above is not the cause - there were no network changes or disconnections while VB was open. This is purely a 4.3.22 issue. Oh, and to clarify, when I said "disconnect from the server", I meant disconnect from the VM server (guest) running on VB.