Discuss the VirtualBox 7.0.2 release
Re: Discuss the VirtualBox 7.0.2 release
I believe that VB7 has an issue with the serial port sharing, at least with a Windows 7 VM. I can monitor the ports with a RS232 breakout. As soon as Windows 7 load, all handshaking lines, DTR, DSR, RTS, DCD, and RI pull low and will not change no matter how you address the RS232 port. If the device attached VIA RS232 does not use CTS->RTS, then full duplex communications works great. I have one device that does use RTS (internally it is referred to as CTS, but hooks to pin 7 RTS), you can not get data from it at all in the VM.
-
- Posts: 21
- Joined: 20. Aug 2016, 02:44
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: Ubuntu WinXP Win7 Win10
Updating Guest Additions is strange
I started updating Guest Additions as I have done for many years now. An odd notice is displayed
operating system"? I simply continued on, answering yes to the prompt, and it seemed to work as it always has.
What is this long message trying to tell me? What should I do differently?
What is the user to do in this situation? I did "get a notification when you start the system", but how am I to "remove the current version first, following the instructions for theThis system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
operating system"? I simply continued on, answering yes to the prompt, and it seemed to work as it always has.
What is this long message trying to tell me? What should I do differently?
3d Broken on Virtualbox 7.0.2
hi,
if I want start a virtual machine with 3d acceleration i got the following message:
if I want start a virtual machine with 3d acceleration i got the following message:
Code: Select all
rtldrNativeLoad: dlopen('D3DCompiler_47.so', RTLD_NOW | RTLD_LOCAL) failed: D3DCompiler_47.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
-
- Volunteer
- Posts: 825
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: Discuss the VirtualBox 7.0.2 release
This is a standard 'Linux' Warning Message (not a VirtualBox message) advising what update action is being taken. I've regularly seen the same message whenever manually updating VirtualBox Guest Additions; and all that is necessary is to follow the further advisory messages to see that the automated update actions complete satisfactorily. If not, then user intervention will be required using the normal OS methods to address any problem, or when successful, there will be a normal advisory message to reboot the OS to complete the installation.Organic_Marble wrote:I started updating Guest Additions as I have done for many years now. An odd notice is displayed
Last edited by mpack on 21. Oct 2022, 11:39, edited 1 time in total.
Reason: Add quote for context.
Reason: Add quote for context.
-
- Posts: 2
- Joined: 8. Jul 2012, 19:40
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: Windows, Linux, FreeBSD, Solaris
- Location: Hanau, Germany
Unable to access cloud virtual machines
The "ListAvailabilityDomains: status 404: NotAuthorizedOrNotFound: Authorization failed or requested resource not found." error reported/detailed here unfortunately still persists. Is anyone else seeing this?
-
- Posts: 77
- Joined: 20. May 2020, 02:50
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: MS Windows 10
Error VERR_PDM_DEVICE_NAME_CLASH when installing
Uninstalled 7.0 beta 2 (had not done that previously, just installed).
Copied VM to a backup.
Ran VirtualBox-7.0.2-154219-Win
Received a message about having to install Python ... continued
Received
Powering VM up
VBoxDeviesRegister failed with rc=VERR_PDM_DVICE_NAMECLASH for module VBoxEhci (C:\Program Files\Oracle\VirtualBox_ExtensionPack\win.amd64\VBoxEhciR3.DLL) (VERR_PDM_DEVICE_NAME_CLAS)
Copied VM to a backup.
Ran VirtualBox-7.0.2-154219-Win
Received a message about having to install Python ... continued
Received
Powering VM up
VBoxDeviesRegister failed with rc=VERR_PDM_DVICE_NAMECLASH for module VBoxEhci (C:\Program Files\Oracle\VirtualBox_ExtensionPack\win.amd64\VBoxEhciR3.DLL) (VERR_PDM_DEVICE_NAME_CLAS)
- Attachments
-
- Development VM 2-2022-10-22-11-01-59.zip
- (7.59 KiB) Downloaded 26 times
Last edited by Ken S on 22. Oct 2022, 09:01, edited 1 time in total.
-
- Posts: 77
- Joined: 20. May 2020, 02:50
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: MS Windows 10
Error VERR_PDM_DEVICE_NAME_CLASH when installing
Uninstalled, installed again without Python support, same result.
Re: Discuss the VirtualBox 7.0.2 release
Hi,
I updated today from 6.1.38 to 7.0.2 on my Mac host (Intel).
So far everything is working great but the (new) host network is still not working.
HostNetwork
Mask: 255.255.255.0
Lowest IP: 192.168.56.1
Upper IP: 192.168.56.199
Error: vmnet_start_interface returned 1001 (VERR_INVALID_PARAMETER).
Failed to attach the network LUN (VERR_INVALID_PARAMETER).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
The feature is still marked as experimental but am I missing something here at the moment?
Best,
Bernhard
I updated today from 6.1.38 to 7.0.2 on my Mac host (Intel).
So far everything is working great but the (new) host network is still not working.
I created a new host network and changed the adapter within my VM from host-only adapter to hot-only network with the new hostnetwork (also the legacy vbox0net) but I'm still getting issues whenever I try to start the machine within a window/headless.macOS hosts: Re-introduced support for internal networking, this is considered a bit experimental still
HostNetwork
Mask: 255.255.255.0
Lowest IP: 192.168.56.1
Upper IP: 192.168.56.199
Error: vmnet_start_interface returned 1001 (VERR_INVALID_PARAMETER).
Failed to attach the network LUN (VERR_INVALID_PARAMETER).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
The feature is still marked as experimental but am I missing something here at the moment?
Best,
Bernhard
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Discuss the VirtualBox 7.0.2 release
If "Lowest IP" refers to the DHCP range of the Host-Only network, then this could be your error. 192.168.56.1 is the default IP address of the Host-Only adapter on the host OS, so DHCP can't serve 192.168.56.1 to a VM. Give a little bit of room at the bottom, maybe start at 192.168.56.10. (VirtualBox's DHCP servers sometimes take their own separate IP address in the bottom few IPs, like .2 or .3)Helmut4 wrote:Lowest IP: 192.168.56.1
Re: Discuss the VirtualBox 7.0.2 release
Excellent idea,scottgus1 wrote:If "Lowest IP" refers to the DHCP range of the Host-Only network, then this could be your error. 192.168.56.1 is the default IP address of the Host-Only adapter on the host OS, so DHCP can't serve 192.168.56.1 to a VM. Give a little bit of room at the bottom, maybe start at 192.168.56.10. (VirtualBox's DHCP servers sometimes take their own separate IP address in the bottom few IPs, like .2 or .3)Helmut4 wrote:Lowest IP: 192.168.56.1
192.168.56.1 was the default value provided after creating that new network. I set the lowest entry to 192.168.56.10 but I get the exact same error message again.
Best,
Bernhard
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Discuss the VirtualBox 7.0.2 release
You forgot to uninstall or replace the VirtualBox Extension Pack 7.0.0 Beta2.Ken S wrote:VBoxDeviesRegister failed with rc=VERR_PDM_DVICE_NAMECLASH for module VBoxEhci (C:\Program Files\Oracle\VirtualBox_ExtensionPack\win.amd64\VBoxEhciR3.DLL) (VERR_PDM_DEVICE_NAME_CLAS)
-
- Posts: 77
- Joined: 20. May 2020, 02:50
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: MS Windows 10
Re: Discuss the VirtualBox 7.0.2 release
I think I have always just installed a new version on top of the previous, so I completely forgot about the Extension Pack.fth0 wrote: You forgot to uninstall or replace the VirtualBox Extension Pack 7.0.0 Beta2.
Your reply is appreciated
Ken
-
- Posts: 77
- Joined: 20. May 2020, 02:50
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: MS Windows 10
Re: Discuss the VirtualBox 7.0.2 release
Yep, that fixed it, thanks.
Guest Additions were a lot easier to install with this build!
Ken
Guest Additions were a lot easier to install with this build!
Ken
-
- Posts: 77
- Joined: 20. May 2020, 02:50
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: MS Windows 10
Upgrading guest from Windows to Windows 11
Following on from earlier ... viewtopic.php?f=15&t=106980
I ran PC Health with the latest build, and there is no longer any mention of an incompatible driver ... good news.
Two issues, "must support secure boot" and "TPM not detected".
In Vbox Manager, I set General, Basic, Version to Windows 11 (64-bit), then Settings, System, TPM to v2.0 and ran the VM, no change.
If I check "Enable EFI (special OSes only)" and run the VM it does not proceed to Windows, rather a command line screen, in which I appear to be trapped.
Any suggestions
Ken
PS Host has been previously upgraded to Windows 11, no registry changes.
PPS Host is UEFI as far as I can see
I ran PC Health with the latest build, and there is no longer any mention of an incompatible driver ... good news.
Two issues, "must support secure boot" and "TPM not detected".
In Vbox Manager, I set General, Basic, Version to Windows 11 (64-bit), then Settings, System, TPM to v2.0 and ran the VM, no change.
If I check "Enable EFI (special OSes only)" and run the VM it does not proceed to Windows, rather a command line screen, in which I appear to be trapped.
Any suggestions
Ken
PS Host has been previously upgraded to Windows 11, no registry changes.
PPS Host is UEFI as far as I can see