Discuss the 4.3.24 release

[frank]

Discuss the 4.3.24 release here. See the changelog for details. The worst regressions of VBox 4.3.22 should be fixed with this release.

[stampit]

I guess there is a wifi issue ... can't connect after upgrade to any wifi

[idrozd]

Extract VirtualBox-4.3.24-98716-Win.exe --extract

List files after extract:
03.03.2015 12:50 57 123 927 common.cab
16.02.2015 11:49 27 011 072 VirtualBox-4.3.14-r95030-MultiArch_amd64.msi
03.03.2015 12:50 28 073 984 VirtualBox-4.3.24-r98716-MultiArch_amd64.msi
03.03.2015 12:50 24 719 360 VirtualBox-4.3.24-r98716-MultiArch_x86.msi

Why do I need a file VirtualBox-4.3.14-r95030-MultiArch_amd64.msi (version 4.3.14 !) in install file ???

sorry, old file in temp folders. The question is removed.

[michaln]

Why do I need a file VirtualBox-4.3.14-r95030-MultiArch_amd64.msi (version 4.3.14 !) in install file ???

Why do you think it's there?

I extracted 109,917,271 bytes of data (3 files) out of a 111,197,384 byte VirtualBox-4.3.24-98716-Win.exe just now. How much did you get?

[mpack]

sorry, old file in temp folders. The question is removed.

My congratulations to "idrozd" for being honest about a silly mistake, which none of us are immune from.

[socratis]

Not sure if I should posting this here, because it is a very "weird" and specific problem that I noticed. Simply trying to see if others are seeing this too. But, I did noticed it with 4.3.24.

My pointing device that is set as a "USB Tablet" (the default for OSX guests) seems to fail "sometimes" to register the mouse movement. Not the keyboard, just the mouse. In fact, the mouse seems to be registered: clicking works, but it is stuck in the upper-left corner and can only "trigger" the Apple menu. It simply doesn't move. It doesn't happen all the time, just when the stars are not aligned.

• Only OSX guests on OSX host ( 10.6.8 ). 10.6 through 10.9 (10.10 still takes a couple of days to boot).
• If I have setup the VM as a multiprocessor one, the problem appears ~1/3 of the time. That's what I mean "weird".
• If I have setup the VM as a uniprocessor one, the problem does not appear.

Still going after VBox.logs and VBoxSVC.logs to see if I can see something. Just raising a "has anyone seen that?".

Edit: See strike through.

[michaln]

Just raising a "has anyone seen that?".

Yes. It is an uninitialized variable sometimes (unpredictably) causing mouse movement within guest to be effectively blocked. A very clever 4.3.24 regression.

[socratis]

Thanks for that! I thought I was going mad...

Edit: Does that mean that I can open a bug report and get the credit for it after it's been resolved?
Sorry, couldn't resist...

[darkangel]

Is the NAT issue mentioned here supposed to be fixed now?

I keep getting "Server unexpectedly closed network connection" from PuTTY when connected to my Ubuntu Server VM. (Note: I'm using a port forward [2222 -> 22])

/var/log/syslog shows:

Mar 5 19:20:30 ubuntu kernel: [10875.538215] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:21:27 ubuntu kernel: [10931.654878] e1000: eth0 NIC Link is Down
Mar 5 19:21:31 ubuntu kernel: [10935.663266] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:22:29 ubuntu kernel: [10993.832309] e1000: eth0 NIC Link is Down
Mar 5 19:22:35 ubuntu kernel: [10999.844587] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:45:42 ubuntu kernel: [12386.909043] e1000: eth0 NIC Link is Down
Mar 5 19:45:46 ubuntu kernel: [12390.917584] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:50:34 ubuntu kernel: [12679.529750] e1000: eth0 NIC Link is Down
Mar 5 19:50:38 ubuntu kernel: [12683.538251] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:51:37 ubuntu kernel: [12741.653612] e1000: eth0 NIC Link is Down
Mar 5 19:51:41 ubuntu kernel: [12745.663052] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:52:39 ubuntu kernel: [12803.808045] e1000: eth0 NIC Link is Down
Mar 5 19:52:43 ubuntu kernel: [12807.824771] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 5 19:53:57 ubuntu kernel: [12881.977504] e1000: eth0 NIC Link is Down

Any ideas?

[kahalia]

I have a Macbook running OS X Mavericks 10.9.5.

I just downloaded VirtualBox for the first time this morning from MyDesktop and am unable to install the Oracle Extension Pack.

When I look at the VirtualBox information, it says that I am running version 4.3.4. Is this a new release? I don't see any documentation about it.

The Extension Pack for 4.3.24 won't install; I receive a message stating "Failed to load the main module" with Reason "Incompatible library version: VboxPuelMain.dylib requires 4.3.24 or later, but VBoxVMM.dylib provides version 4.3.4."

I can provide the full error message information, but here is the result code, component, interface:

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

Any insight into this issue would be much appreciated!

[mpack]

If you are running 4.3.4 then it is not the current release, and discussion of it does not belong in this topic. The latest VirtualBox can be downloaded from here.

The extension pack version you install must match the version of the VirtualBox app it extends.

[trippingslowly]

Hello, I just upgraded from 4.3.6 to 4.3.24. I upgraded through the vbox "check for updates".

Everything seemed to go ok, but now my VMs won't load. I have a Windows XP and Ubuntu VM I need to get in to.

They start to load then hang. And then stop responding. Any suggestions to get them working?

[Perryg]

Hello, I just upgraded from 4.3.6 to 4.3.24. I upgraded through the vbox "check for updates".
Everything seemed to go ok, but now my VMs won't load. I have a Windows XP and Ubuntu VM I need to get in to.
They start to load then hang. And then stop responding. Any suggestions to get them working?

Cross posting is not allowed. Other post deleted.

Please click the link below
Minimal information needed to be able to help

[trippingslowly]

Sorry, wasn't sure which place would be better to post. Anyway, I just went back to 4.3.6 and I'll stick with that for now.

[g2flyer]

Alas, 4.3.24 still exhibits the problem of resuming VMs with a "Failed to load unit 'pgm' (VERR_NO_MEMORY)." error (as reported, e.g., for 4.3.22 ( viewtopic.php?f=1&t=66067&p=314396#p314396 viewtopic.php?f=1&t=66067&p=313105#p313105), 4.3.20 (viewtopic.php?f=1&t=64762&p=305271#p305271) and 4.3.18 (viewtopic.php?f=1&t=64104&p=301609#p301609).

Curiously, though, it did work for 2-3 suspend/resume cycles (with only activity when live was updating Symmantec A/V) before i got the error again.

Find attached the log for a failed session. Any advice on how to fix that would be great! thanks!

-michael-

PS: Host is Ubuntu 14.04 with (32-bit PAE!) 3.13.0-46-generic kernel ...