Discuss the 4.3.22 release
Re: Discuss the 4.3.22 release
Are there any plans to merge the newer Guest Additions (VBoxGuestAdditions_4.3.23-98282.iso) into the existing Virtual Box installer (currently VirtualBox-4.3.22-98236-Win.exe). If nothing else, this would reduce fault reports from anyone who downloads the installer in future.
Re: Discuss the 4.3.22 release
That is more likely to be the next release.m6477 wrote:Are there any plans to merge the newer Guest Additions (VBoxGuestAdditions_4.3.23-98282.iso) into the existing Virtual Box installer (currently VirtualBox-4.3.22-98236-Win.exe). If nothing else, this would reduce fault reports from anyone who downloads the installer in future.
Re: Discuss the 4.3.22 release
Hello,
I confirm there is an issue with the NAT or network management on this 4.3.22 release.
I am getting multiple disconnect/reconnect
00:08:27.399894 NAT: link down
00:08:32.400591 NAT: link up
So i am switching back to 4.3.20 release
Pierre
I confirm there is an issue with the NAT or network management on this 4.3.22 release.
I am getting multiple disconnect/reconnect
00:08:27.399894 NAT: link down
00:08:32.400591 NAT: link up
So i am switching back to 4.3.20 release
Pierre
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Discuss the 4.3.22 release
Note that a link has been added to the first message of this topic, pointing to a test build (4.3.23) which fixes the NAT disconnection issue.
Edit: Actually that link seems to be broken, no doubt it will be fixed soon. [Edit2] The link is now fixed. |
Last edited by mpack on 20. Feb 2015, 17:18, edited 1 time in total.
Reason: Update
Reason: Update
-
- Posts: 1
- Joined: 20. Feb 2015, 16:49
Re: Discuss the 4.3.22 release
As Mpack mentions the link to download the 4.3.23 release is dead in the first post, however if you look closely at the link it's pointing to 4.3.21.. on a hunch I changed the link as follows and it works:
VirtualBox-4.3.23-98406-Win.exe
OK I can't add link as a new member, sorry but if you take the broken link from the first post and change the file name to <above> it will let you download the test release. Maybe a more senior person can update with a clickable link.
I'm assuming someone made a typo but. I can't confirm if this fixes the network issues, they are killing me so I'll try and update in a few if it does.
VirtualBox-4.3.23-98406-Win.exe
OK I can't add link as a new member, sorry but if you take the broken link from the first post and change the file name to <above> it will let you download the test release. Maybe a more senior person can update with a clickable link.
I'm assuming someone made a typo but. I can't confirm if this fixes the network issues, they are killing me so I'll try and update in a few if it does.
Edit: - After 15 mins of testing I can say the 4.2.23 GuestAddition ISO fixes the network share issues for me, and my network has been rock solid since I upgraded Vbox to the 4.2.23 version. Good Luck Thanks guys for the help, John |
Last edited by John Polansky on 20. Feb 2015, 17:15, edited 1 time in total.
Re: Discuss the 4.3.22 release
Exactly same issue here.
Iuliu Pascaru wrote:I noticed that after upgrading from VirtualBox-4.3.20-96996-Win to VirtualBox-4.3.22-98236-Win, my guest Ubuntu 12.04 kept resetting 1 NIC about once per minute.
There are 3 NICs configured in this Ubuntu guest, but only the one connected as a NAT connection has this problem. Other NICs connected to an Internal Network and a Bridged Connection work fine.
Please see the guest-related log file attached. It shows that the NAT link is resetting very frequently without any apparent reasons:
After switching back to VirtualBox-4.3.20-96996-Win and restarting the guest, the problem went away.Code: Select all
01:34:16.371957 NAT: link down 01:34:21.372406 NAT: link up
As the 4.3.22 build contains changes made to the NAT-related components, according to the changelog, it probably means that an issue was introduced in this build:
NAT: new ping proxy for Windows hosts (bug #11871)
NAT: Properly report outbound connect(2) failures to guest with TCP RST or ICMP (bug #10525)
NAT Network: no need for frequent wakeups in VBoxNetDHCP and VBoxNetNAT (bug #11681)
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Discuss the 4.3.22 release
This might help... viewtopic.php?f=1&t=66067#p312593
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: Discuss the 4.3.22 release
Hello,
Network PXE boot appears to be broken on Windows 7 host. It worked fine in 4.3.20, but now all I see is immediately the "FATAL: Could not read from the boot medium! System halted." message.
Thanks
Reuben
Network PXE boot appears to be broken on Windows 7 host. It worked fine in 4.3.20, but now all I see is immediately the "FATAL: Could not read from the boot medium! System halted." message.
Thanks
Reuben
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Discuss the 4.3.22 release
And how did you get on with the test build linked from the first post?
-
- Posts: 11
- Joined: 8. Jun 2012, 20:56
- Primary OS: Other
- VBox Version: PUEL
- Guest OSses: Win 8, Kubuntu, DOS 2.0
- Location: Kolka
Re: Discuss the 4.3.22 release
Major Bug!! I was pulling my hair and pounding the table earlier. Confirmed that updating to "VBoxGuestAdditions_4.3.23-98282.iso" fixes this problem. Shared folders have returned in Windows 7 and 8. Thanks to all.
Re: Discuss the 4.3.22 release
Hi Michael,
thanks!
-michael-
Indeed! I have now compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 on 14.04 and full-screen does work now properly (or so it seems after a few quick tests . As i look now in the log-file, I upgraded to the new compiz only hours after testing VB (and still running in the problem)michael wrote: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.g2flyer wrote:Fullscreen mode is stull bust (since 4.3.16): on the second/right screen it is shown only offset and hence only partially.
https://bugs.launchpad.net/bugs/1353675
thanks!
-michael-
-
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: Discuss the 4.3.22 release
Thanks. Windows-only regression, will be fixed in the next maintenance release. There is a test build available.ReubenCox wrote:Hello,
Network PXE boot appears to be broken on Windows 7 host. It worked fine in 4.3.20, but now all I see is immediately the "FATAL: Could not read from the boot medium! System halted." message.
Thanks
Reuben
-
- Posts: 76
- Joined: 7. Oct 2012, 18:24
Re: Discuss the 4.3.22 release
I am running Solaris 11.2 as host. I have installed Win7 in a VM and it works fine. I have also cloned the VM but in the clone the sound does not work at all. Any clues?
-
- Posts: 2
- Joined: 24. Feb 2015, 18:51
Re: Discuss the 4.3.22 release
does this version still have that horrible mouse jitter when you start compiling something in the vm guest and uses 100% of the cpu? this was the only thing keeping me from moving from the horrible vmware....
Re: Discuss the 4.3.22 release
Relevant setup information
Host: Windows Professional 7 Service Pack 1, two monitors
Guest: Arch Linux, kernel 3.18.6, xorg server 1.17.1, xrandr 1.4.3
In 4.3.20, disabling one of the two monitors in the guest caused the corresponding virtualbox window on the host to close (e.g. xrandr --output VBOX1 --off). With 4.3.22 disabling the monitor causes the window to go blank, but remain open.
I think it is related to this from the changelog:
X11 guests: prevent unwanted hiding of guest screens on multi-monitor guests (bug #13287)
But what about wanted (as opposed to unwanted) hiding of guest screens? I found it very useful. Is it possible in 4.3.22 to close a virtual box window from inside the guest?
Host: Windows Professional 7 Service Pack 1, two monitors
Guest: Arch Linux, kernel 3.18.6, xorg server 1.17.1, xrandr 1.4.3
In 4.3.20, disabling one of the two monitors in the guest caused the corresponding virtualbox window on the host to close (e.g. xrandr --output VBOX1 --off). With 4.3.22 disabling the monitor causes the window to go blank, but remain open.
I think it is related to this from the changelog:
X11 guests: prevent unwanted hiding of guest screens on multi-monitor guests (bug #13287)
But what about wanted (as opposed to unwanted) hiding of guest screens? I found it very useful. Is it possible in 4.3.22 to close a virtual box window from inside the guest?