Discuss the 5.1.24 release
Discuss the 5.1.24 release
Discuss the 5.1.24 release here.
You can download the release here.
You can download the release here.
-
- Posts: 6
- Joined: 20. Jun 2016, 19:21
Re: Discuss the 5.1.24 release
All,
Just upgraded to virtual box 5.1.24. Host is Ubuntu 14.04 x64. After starting virtual box, I am told extension are out dated (5.1.22), and I allow it to download new extensions.
Download seems to succeed, but then during "Verification" I get the following error message:
Hope this helps!
Just upgraded to virtual box 5.1.24. Host is Ubuntu 14.04 x64. After starting virtual box, I am told extension are out dated (5.1.22), and I allow it to download new extensions.
Download seems to succeed, but then during "Verification" I get the following error message:
Manual installation (downloading files manually) has no problems.The network operation failed with the following error:
During network request: Url not found on the server.]
Hope this helps!
-
- Posts: 79
- Joined: 9. May 2008, 15:54
- Primary OS: openSUSE
- VBox Version: PUEL
- Guest OSses: WinXP32 WinXP64 Win7-32 Win7-64 openSUSE64 OS2 Win10
- Location: Texas, USA
Re: Discuss the 5.1.24 release
The checksum files are missing from the web site "download" page. (SHA256, MD5).
https://www.virtualbox.org/wiki/Downloads
https://www.virtualbox.org/wiki/Downloads
-
- Posts: 14
- Joined: 19. Mar 2008, 06:20
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: OS/2, Linux, Windows, OpenSolaris, FreeBSD
- Contact:
Re: Discuss the 5.1.24 release
I've just installed this release, including updating the guest additions and my Win7-64 guest's Host Only networking stopped working. The host is Linux Mint 18.2 64 bit (4.10.0-26-generic kernel).
I found that the Linux network device, vboxnet0, existed but wasn't "up", even after a full system reboot. I was able to bring it up manually with "sudo ifconfig vboxnet0 up".
On the guest, I found that the network interface was now auto-configuring to have IP 169.254.80.150 instead of the expected 192.168.56.101. If I configure it manually to have the expected address it starts working again.
I found that the Linux network device, vboxnet0, existed but wasn't "up", even after a full system reboot. I was able to bring it up manually with "sudo ifconfig vboxnet0 up".
On the guest, I found that the network interface was now auto-configuring to have IP 169.254.80.150 instead of the expected 192.168.56.101. If I configure it manually to have the expected address it starts working again.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Discuss the 5.1.24 release
169.254.*.* is a self-assigned IP address in the case that a DHCP server is not found. Since your HostOnly network is not available, there is no DHCP server to hand out an address, that is to be expected.bjh wrote:On the guest, I found that the network interface was now auto-configuring to have IP 169.254.80.150 instead of the expected 192.168.56.101. If I configure it manually to have the expected address it starts working again.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 14
- Joined: 19. Mar 2008, 06:20
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: OS/2, Linux, Windows, OpenSolaris, FreeBSD
- Contact:
Re: Discuss the 5.1.24 release
Ok, so that means the DHCP server isn't active after I manually brought vboxnet0 up. Not too surprising. The question is, why doesn't it come up automatically like it used to?
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Discuss the 5.1.24 release
There are three reports so far from users that are running headless VMs where the process eats all the available RAM on the host (memory leak?). See 1) viewtopic.php?f=11&t=83860 and 2) viewtopic.php?f=6&t=83855
Edit: This seems to have been addressed in test builds ≥ 117099. See viewtopic.php?f=6&t=83855 |
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Discuss the 5.1.24 release
I have been using VirtualBox for a num ber of years without any major problems however I have just upgraded from VBox 5.1.22 on Windows 8.1 host to 5.1.24, installing the new Extension Pack as well. Rebooted PC as requested by installer. On restart when I try to run an existing Win7 guest I get:
The virtual machine 'Win7 64 bit SP1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\VirtualBox\Win7 64 bit SP1\Logs\VBoxHardening.log'.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
and in G:\VirtualBox\Win7 64 bit SP1\Logs\VBoxHardening.log:
20ac.18dc: New simple heap: #1 0000000000b90000 LB 0x400000 (for 1757184 allocation)
20ac.18dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox'
20ac.18dc: System32: \Device\HarddiskVolume2\Windows\System32
20ac.18dc: WinSxS: \Device\HarddiskVolume2\Windows\WinSxS
20ac.18dc: KnownDllPath: C:\Windows\system32
20ac.18dc: supR3HardenedVmProcessInit: Opening vboxdrv stub...
20ac.18dc: Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND
20ac.18dc: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
20ac.18dc: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
20ac.18dc: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
20a4.1c9c: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
20a4.1c9c: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
20a4.1c9c: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
I have checked and there is no 'vboxdrv' service installed on the host machine:
C:\Windows\system32>sc query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
C:\Windows\system32>
How do I get back to a working VirtualBox installation please ?
Thanks
Chris
The virtual machine 'Win7 64 bit SP1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\VirtualBox\Win7 64 bit SP1\Logs\VBoxHardening.log'.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
and in G:\VirtualBox\Win7 64 bit SP1\Logs\VBoxHardening.log:
20ac.18dc: New simple heap: #1 0000000000b90000 LB 0x400000 (for 1757184 allocation)
20ac.18dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox'
20ac.18dc: System32: \Device\HarddiskVolume2\Windows\System32
20ac.18dc: WinSxS: \Device\HarddiskVolume2\Windows\WinSxS
20ac.18dc: KnownDllPath: C:\Windows\system32
20ac.18dc: supR3HardenedVmProcessInit: Opening vboxdrv stub...
20ac.18dc: Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND
20ac.18dc: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
20ac.18dc: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
20ac.18dc: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
20a4.1c9c: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
20a4.1c9c: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
20a4.1c9c: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
I have checked and there is no 'vboxdrv' service installed on the host machine:
C:\Windows\system32>sc query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
C:\Windows\system32>
How do I get back to a working VirtualBox installation please ?
Thanks
Chris
Re: Discuss the 5.1.24 release
Please ignore my previous post. I thought I had run the installer 'As Administrator' but it seems that I may not have done so. I have rerun the installer 'As Administrator' and repaired the installation. This seems to have fixed my problem with VirtualBox 5.1.24 and it seems to be working normally.
Sorry.
Chris
Sorry.
Chris
Re: Discuss the 5.1.24 release
The issue of two entries for the VB guest window appearing in the taskbar on Linux Hosts (I'm using LM 18.2 64-bit) seems to be back:
viewtopic.php?f=7&t=68890
viewtopic.php?f=7&t=69908
Mike.
viewtopic.php?f=7&t=68890
viewtopic.php?f=7&t=69908
Mike.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Discuss the 5.1.24 release
Is that a regression? Was it working with 5.1.22? Because the two threads you linked to are quite old.mingle wrote:The issue of two entries for the VB guest window appearing in the taskbar on Linux Hosts (I'm using LM 18.2 64-bit) seems to be back:
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Discuss the 5.1.24 release
I'd say regression - it's been fine since 5.0.4 (I believe that's where it was fixed - haven't browsed those older threads completely)socratis wrote:Is that a regression? Was it working with 5.1.22? Because the two threads you linked to are quite old.mingle wrote:The issue of two entries for the VB guest window appearing in the taskbar on Linux Hosts (I'm using LM 18.2 64-bit) seems to be back:
Cheers,
Mike.
-
- Posts: 3
- Joined: 20. Jul 2017, 21:21
Re: Discuss the 5.1.24 release
AMD64 installer for Ubuntu 17.04 shows as version 5.1.22, not 5.1.24, in the installer:
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Discuss the 5.1.24 release
@"white horse"
Did you actually get the 5.1.24 installer? If so, where from? Remember that the only one that's supported here is the one from https://www.virtualbox.org/wiki/Linux_Downloads not from the distro.
Did you actually get the 5.1.24 installer? If so, where from? Remember that the only one that's supported here is the one from https://www.virtualbox.org/wiki/Linux_Downloads not from the distro.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.