Agreed. I need to do some more testing on another machine than our main production one. And v7.0.0 is "too new" to be yet thoroughly tested on headless systems.Whiskeyjack wrote:You will need to give us specific reproduction steps. Your current report is too vague to be helpful.
Discuss the VirtualBox 7.0.0 release
Re: VBox 7 Activity Monitor: Does it lock VMs?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VBox7.0 can not start while 6.1.38 works well
Make sure you are not starting from a saved state.Yuking wrote:7.0 can not start any VM while 6.1.38 works well.
-
- 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.0 release
VB764w10ProGuestLogsIn64w10ProHost
64bitW1122H2homeVB7crashLogs25a4.2274: supR3HardenedWinFindAdversaries: 0x0
25a4.2274: VirtualBoxVM.exe: Differences in section #7 (.00cfg) between file and memory:
25a4.2274: ntdll.dll: Differences in section #8 (.00cfg) between file and memory:
25a4.2274: kernel32.dll: Differences in section #2 (.rdata) between file and memory:
25a4.2274: kernelbase.dll: Differences in section #2 (.rdata) between file and memory:
25a4.2274: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000409
ea0.dcc: \Device\HarddiskVolume5\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_70cfb45e19c20af4\nvwgf2umx_cfg.dll: Signature #1/2: VERR_CR_X509_CPV_NOT_VALID_AT_TIME for 0x632b41ce; retrying against current time: 0x6344bfc1.
A strange exit code on the hardening logs, possibly something odd about the Nvidia drivers. Something is hacking the Virtualbox and other core DLLs in RAM, but this something does not appear in the Adversaries section. Any other security or web-safe browsing/banking software besides Windows Defender?18b8.2da8: supR3HardenedWinFindAdversaries: 0x0
18b8.2da8: VirtualBoxVM.exe: Differences in section #7 (.00cfg) between file and memory:
18b8.2da8: ntdll.dll: Differences in section #8 (.00cfg) between file and memory:
18b8.2da8: kernel32.dll: Differences in section #2 (.rdata) between file and memory:
18b8.2da8: kernelbase.dll: Differences in section #2 (.rdata) between file and memory:
18b8.2da8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000409
ac4.5a4: \Device\HarddiskVolume5\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_70cfb45e19c20af4\nvd3dumx_cfg.dll: Signature #1/2: VERR_CR_X509_CPV_NOT_VALID_AT_TIME for 0x632b40f0; retrying against current time: 0x6344c221.
-
- Posts: 1
- Joined: 11. Oct 2022, 17:14
with 3D acceleration, 7.0 gives TPM error
Errors in Virtualbox 7 on Windows 11:
- cant start Win 10 with 3d acceleration or after 2nd start with reenabled 3d massive display problems, Chrome doesnt start, ..
- EventID 15, the device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error ..
- cant start Win 10 with 3d acceleration or after 2nd start with reenabled 3d massive display problems, Chrome doesnt start, ..
- EventID 15, the device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error ..
Last edited by scottgus1 on 11. Oct 2022, 17:24, edited 2 times in total.
Reason: changed title to reflect problem
Reason: changed title to reflect problem
Re: Discuss the VirtualBox 7.0.0 release
Might be similar to what I am seeing with a XP (32bit) guest VM crashing on boot (crashes on the XP logo, boots into Safe Mode fine, I am doing a Guest Additions update in there (taking a bit of time as it is starting with certificate updates, then it gets onto the drivers.), seems to crash on just after NAT: Link up (might be similar bug to Ubuntu guest crash on boot when using bridge adapter but XP is crashing with NAT in normal boot but is fine in safe mode). Attached my logs
- Attachments
-
- Win XP (old games)-2022-10-11-09-22-22.zip
- old XP logs
- (29.56 KiB) Downloaded 13 times
-
- 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
After upgrading to v7.0.0, I wanted to access the “cloud virtual machines” in conjunction with an existing free tier subscription.
I tried to follow the steps outlined in the “Required Keys and OCIDs” section of the Oracle Cloud Infrastructure Documentation by uploading a self-generated public key and creating an ~/.oci/config file containing the following entries:
After restarting VirtualBox, I see the corresponding OCI/DEFAULT entry next to existing local virtual machines; however, I cannot select the existing OCI instance as explained in section 1.16.5 (“Using the Cloud Profile Manager”) of the VirtualBox user manual:
What (steps) am I missing here? Thanks in advance!
I tried to follow the steps outlined in the “Required Keys and OCIDs” section of the Oracle Cloud Infrastructure Documentation by uploading a self-generated public key and creating an ~/.oci/config file containing the following entries:
Code: Select all
[DEFAULT]
user=ocid1.user....
tenancy=ocid1.tenancy...
fingerprint=xx:...
region=eu-frankfurt-1
key_file=/path/oci_api_key.pem
pass_phrase=...
-
- Posts: 17
- Joined: 26. Jul 2020, 17:18
Re: Error upgrading extension pack in 7.0
yes me too same setup same error but it could be trivial
cthart wrote:VirtualBox 7.0 on macOS Monterey 12.6
When upgrading the extension pack...
VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'. Result Code: NS_ERROR_FAILURE (0X80004005) Component: ExtPackManagerWrap Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
Re: Discuss the VirtualBox 7.0.0 release
Hi.
I just tried to upgrade to 7.0.0 on a Windows 10 host. It installed OK and seems to be working with a single-monitor Windows 10 VM, but not with a Windows 10 VM that has 3 monitors. It gets confused as to which monitor the mouse is clicking in, making it pretty much unusable. For example, I have the Windows task bar on the center monitor only, and when I try to click with the mouse pointer located over the Windows start button there, nothing happens. If I move the mouse pointer to the bottom left corner of the left monitor and click there, then the start menu opens on the middle monitor.
Further, I tried changing the VM's settings from all monitors to a single one, but when I then booted the VM, the display was still showing across all 3 monitors. I checked the settings and found that it had reverted itself to all monitors. I repeated this just in case I had made an error, and the same happened again. I then tried to disable 2 of the monitors from within Windows, but that was almost impossible with the mouse clicking on the wrong one.
Rolled back to 6.1.38 and all is hunky dory again.
Edit: My mistake on the "all monitors" setting not getting turned off - I had changed the monitor setting under scale factor, but hadn't reduced the monitor count from 3 to 1.
After re-installing 7.0.0 and having now properly reduced the monitor count to 1, all was OK with the VM like that. I then increased the monitor count to 2 and the issue immediately came back. With 2 monitors the mouse location is not as far off as it was with 3, but still quite a bit off from where it should be.
Ian
I just tried to upgrade to 7.0.0 on a Windows 10 host. It installed OK and seems to be working with a single-monitor Windows 10 VM, but not with a Windows 10 VM that has 3 monitors. It gets confused as to which monitor the mouse is clicking in, making it pretty much unusable. For example, I have the Windows task bar on the center monitor only, and when I try to click with the mouse pointer located over the Windows start button there, nothing happens. If I move the mouse pointer to the bottom left corner of the left monitor and click there, then the start menu opens on the middle monitor.
Further, I tried changing the VM's settings from all monitors to a single one, but when I then booted the VM, the display was still showing across all 3 monitors. I checked the settings and found that it had reverted itself to all monitors. I repeated this just in case I had made an error, and the same happened again. I then tried to disable 2 of the monitors from within Windows, but that was almost impossible with the mouse clicking on the wrong one.
Rolled back to 6.1.38 and all is hunky dory again.
Edit: My mistake on the "all monitors" setting not getting turned off - I had changed the monitor setting under scale factor, but hadn't reduced the monitor count from 3 to 1.
After re-installing 7.0.0 and having now properly reduced the monitor count to 1, all was OK with the VM like that. I then increased the monitor count to 2 and the issue immediately came back. With 2 monitors the mouse location is not as far off as it was with 3, but still quite a bit off from where it should be.
Ian
-
- Posts: 5
- Joined: 20. Jan 2012, 01:56
- Primary OS: Other
- VBox Version: PUEL
- Guest OSses: Windows XP
Re: Discuss the VirtualBox 7.0.0 release
VirtualBox 7.0.0 Guest Additions on Windows
Inserting the Image doesn't appear to do anything
Inserting the Image a second time causes an abrupt abort
Manually mounting the ISO and then running the install does a partial install
Late in the install it causes an abrupt abort of the machine during the VBoxDrvInst portion.
Inserting the Image doesn't appear to do anything
Inserting the Image a second time causes an abrupt abort
Manually mounting the ISO and then running the install does a partial install
Late in the install it causes an abrupt abort of the machine during the VBoxDrvInst portion.
-
- 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 VirtualBox 7.0.0 release
This is standard.GTVic wrote: Inserting the Image doesn't appear to do anything
Close out of a VM
It seems some procedures changed from v6.1 and I am missing how to configure it.
Previously when I close out of a Guest VM I selected "ACPI Shutdown" and once closed I give the snap a name i.e. Take....
Below the new snap name, the last entry, I then see "Current State" which confirms the state of the snap.
With v7.0 the last entry reads "Current State (changed)"
Should I close out in another manner?
Sept 13:
Via the manual noticed that the best is to select "Send the shutdown state" which is an ACPI shutdown.
Resolved but not resolved, found a way to remove the "Current State (changed)" snap name.
After naming a new snap which adds "(changed)" I generate another snap via Take, give it a name and then it is without the "(changed)".
A bit dumb because now for each snap there is a duplicate but at least I can now be sure I did make a snap.
Hopefully in future it will be fixed.
Previously when I close out of a Guest VM I selected "ACPI Shutdown" and once closed I give the snap a name i.e. Take....
Below the new snap name, the last entry, I then see "Current State" which confirms the state of the snap.
With v7.0 the last entry reads "Current State (changed)"
Should I close out in another manner?
Sept 13:
Via the manual noticed that the best is to select "Send the shutdown state" which is an ACPI shutdown.
Resolved but not resolved, found a way to remove the "Current State (changed)" snap name.
After naming a new snap which adds "(changed)" I generate another snap via Take, give it a name and then it is without the "(changed)".
A bit dumb because now for each snap there is a duplicate but at least I can now be sure I did make a snap.
Hopefully in future it will be fixed.
Last edited by nics on 13. Oct 2022, 16:23, edited 1 time in total.
Re: Discuss the VirtualBox 7.0.0 release
W10 21H2 fully patched host (up to 20221011).
Upgraded to VB 7. Booted W10 21H2 guest fully patched as well. Installed VB7 additions, mouse became erratic. Really difficult to click with precision, drag windows etc.
Uninstalled VB 7, installed 6.1.40. Same behavior, even after installing 6.1.40 additions.
Side note: another W10 guest same patch level with 6.1.38 additions works just fine.
Upgraded to VB 7. Booted W10 21H2 guest fully patched as well. Installed VB7 additions, mouse became erratic. Really difficult to click with precision, drag windows etc.
Uninstalled VB 7, installed 6.1.40. Same behavior, even after installing 6.1.40 additions.
Side note: another W10 guest same patch level with 6.1.38 additions works just fine.
VBox 7 intial thoughts
Hopefully this is the right topic area for this. I just upgraded to v7 and noticed some interesting things.
Stopped working:
* Open Indiana - now boot loops, worked in 6.1.xx
* Minix - now has memory errors that crashes on start up, again worked previously
* Visiopsys and and TempleOS both lost their boot disk links, same
* Plan9 - now forever loops checking disk, same
* Kolibri - may not be v7, lost mouse access, same
Working:
FreeBSD, Genode, ZorinOS, macOS12, Arca Noae, Menuet, ReactOS, Free and plain dos, Icaros, AROSOne, BeOS, Haiku, NeXT, Syllable
If anyone has experience with the newly non functional ones, I would appreciate the help getting them back up and can provide more of the technical details.
Rob
Stopped working:
* Open Indiana - now boot loops, worked in 6.1.xx
* Minix - now has memory errors that crashes on start up, again worked previously
* Visiopsys and and TempleOS both lost their boot disk links, same
* Plan9 - now forever loops checking disk, same
* Kolibri - may not be v7, lost mouse access, same
Working:
FreeBSD, Genode, ZorinOS, macOS12, Arca Noae, Menuet, ReactOS, Free and plain dos, Icaros, AROSOne, BeOS, Haiku, NeXT, Syllable
If anyone has experience with the newly non functional ones, I would appreciate the help getting them back up and can provide more of the technical details.
Rob
Re: Discuss the VirtualBox 7.0.0 release
This viewtopic.php?f=8&t=107346&p=525298#p525221 a macOS only error with the profile that is inside the installer and installed with Virtualbox 7.0.0?
VirtualBox 7: Unable to connect to system D-Bus
Hi,
After upgrade guest addon from version 6.1.38 to 7.0.0 the following errors start to appear:
Currently, dbus v1.10.24 is installed and used by many system components. This error does not appear with 6.1.38, is it because 7.0.0 has a dependency on higher dbus version? Can we safely ignore this error?
Thanks.
After upgrade guest addon from version 6.1.38 to 7.0.0 the following errors start to appear:
Code: Select all
sudo dmesg | grep -i error
[ 12.652420] 03:20:38.409119 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
[ 17.659991] 03:20:43.416822 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
[ 22.779770] 03:20:48.535811 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed
Thanks.