Discuss the 4.3.26 release

[frank]

Discuss the 4.3.26 release here. See the changelog for details.

Most important are fixes for running VirtualBox on Linux 4.0 and for running VirtualBox on Mac OS X Yosemite on Intel Broadwell CPUs.

[TwisterMagnet]

I hope the bugs are fixed that cause crashing when using USB flash drives.

[mpack]

You can check the bug ticket(s) to find out. You reported the issue, right?

[Polix]

I have installed 4.3.26 this morning, and I have the same VERY unstable network problem I got after updgrading to 4.3.22 and already described on the forum

This very annoying network problem was solved in 4.3.24. Why is it back in 4.3.26???

[Dulus]

I am also having this issues from when i installed 4.3.26.

[michaln]

What is "this issue"? Please don't bother worthless comments. If you have a specific problem, describe it in detail. It will be looked at.

On the other hand "I am also having this issue" will be ignored.

[michaln]

This very annoying network problem was solved in 4.3.24. Why is it back in 4.3.26???

Let me guess -- because you have a ridiculously short DHCP lease?

At any rate, if you have the same problem discussed in this ticket https://www.virtualbox.org/ticket/13839 then please take the discussion there. If not, create a different ticket and describe the problem you're actually having.

[Polix]

Let me guess -- because you have a ridiculously short DHCP lease?

At any rate, if you have the same problem discussed in this ticket https://www.virtualbox.org/ticket/13839 then please take the discussion there. If not, create a different ticket and describe the problem you're actually having.

Well, thank you for being so helpful

I have absolutely no clue how to solve this DHCP lease on my up-to-date Windows 7 host, or what I should do about that in my up-to-date Fedora Core 20 guest. All I'm saying is that I had no network related problem till 4.3.22 and that I appreciated a lot that 4.3.24 solved my problem. I'm just confused that the problem is back and I thought it would be useful to report that, but maybe this Discuss the 4.3.26 release thread is not about reporting problems

I humbly apologize for not finding ticket 13839 (that I will now follow) and only citing viewtopic.php?f=6&t=66086

[michaln]

Here's the trouble. You think that because the symptoms are the same (at least superficially), it must be the same problem. So you say "the problem is back". But we know that it can't be the same problem because it really was fixed, and we don't see it anymore. So we need to know exactly what your setup is, but you assume that we don't so you don't provide any details. In the end it's just wasting everyone's time.

Anyway, I think it is now apparent what the problem is and yes, it is related to what happened in 4.3.22, but no it's not the same and probably happens on a far smaller set of hosts.

The whole story does underscore that we can either have stable releases or new features, but not both.

[g2flyer]

The ""Failed to load unit 'pgm' (VERR_NO_MEMORY)." error on resume of VMs still persists on 4.3.26 (it existed in all versions since 4.3.14, see
viewtopic.php?f=1&t=66394#p315589 for more info). Again and strangely enough it happens only after a few suspend/resume cycles; maybe depending on how much virtual memory was used?

[Polix]

@michaln OK, I understand about the stable/new feature problem, that's why I'm trying to report the symptoms I get in order to get an even better product, rather just doing nothing. But I'm not a system expert, so I can only report symptoms when it comes to low level network problems.

I also understand it must be boring to moderate vague reports and I appreciate your patience and help, so my apologies in only pointing to a global thread rather than to my original 4.3.22 report that had the details about my symptoms (viewtopic.php?f=6&t=66086#p312985)

[michaln]

@michaln OK, I understand about the stable/new feature problem, that's why I'm trying to report the symptoms I get in order to get an even better product, rather just doing nothing.

That's definitely good -- some people never report problems, assume that everyone must have the same issue, and act surprised when unreported bugs don't fix themselves

But I'm not a system expert, so I can only report symptoms when it comes to low level network problems.

That's why we have VBox.log, there's quite a lot we can get out of it even if it's gibberish to users.

I also understand it must be boring to moderate vague reports and I appreciate your patience and help, so my apologies in only pointing to a global thread rather than to my original 4.3.22 report that had the details about my symptoms (viewtopic.php?f=6&t=66086#p312985)

It's not boring, but it can be maddening

As for the problem you ran into, you should monitor the ticket to see when any fix is available. You could also probably work around it by extending the DHCP lease time on your network, but that may not be under your control (so I'm not suggesting that's a real fix, just a potential workaround).

[GuyBeam]

Really a question / suggestion.
When I started the 4.3.26 installation on my Windows 7 64 bit host the setup program gave no indication that virtualbox was already installed (4.3.20). I did not complete the installation because I did not know what might happen to my virtual machines.

So my question / suggestion is: what happens when an installation is really an upgrade to a newer version? Shouldn't the setup program tell the user what will happen before the user clicks the "Install" pushbutton?

[mpack]

What happens to your .doc files when you upgrade MS Office?

The same thing happens to your VMs.

[Dulus]

What is "this issue"? Please don't bother worthless comments. If you have a specific problem, describe it in detail. It will be looked at.

On the other hand "I am also having this issue" will be ignored.

Sorry about that. I may try to elaborate.

I have installed VirtualBox-4.3.24 on a fresh install on Windows 7. Created/Imported (some were created on older versions) various guest OSs (cisco, android x86, linux ([l]ubuntu, core, vyatta/vyos, windows 7 - all latest stable and updated) and they worked without any (observable) issues. Then i have installed VirtualBox-4.3.26 and VMs started to have issues with network links. The network link was flapping every 30-90 seconds. I have confirmed this in lubuntu, core, and vyos. After reinstall back to VirtualBox-4.3.24 the issues have disappeared. Attached are the logs.