Discuss the VirtualBox 7.0.0 release
-
- Posts: 334
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
V7 doesn't run in macOS Mojave v10.14.6. :(
FYI. It doesn't run in old updated macOS Mojave v10.14.6. It told me this AFTER (install/upgrad)ing VirtualBox v6.1.38-153438. I had to uninstall v7 and reinstall the older version. It should had told me that BEFORE running the (install/upgrad)ing.
I wrote a ticket to add that checker to macOS installer: https://www.virtualbox.org/ticket/21124
I wrote a ticket to add that checker to macOS installer: https://www.virtualbox.org/ticket/21124
-
- Posts: 334
- Joined: 9. Jul 2007, 20:02
- Primary OS: MS Windows other
- VBox Version: OSE other
- Guest OSses: Windows and macOSes
- Location: An Ant Farm
- Contact:
Hardening issues new with 7.0
I didn't have these abort/crash problems before with v6 in my updated 64-bit W10 Pro host PC (16 GB of RAM). I even rebooted my host PC after VB upgrade just to be sure. I attached their zipped logs.
I had no problems with my 64-bit W7 HPE SP1 guest VM though. I hope I don't have to downgrade VB back to v6.1.38-153438.
Thank you for reading and hopefully answering soon.
I had no problems with my 64-bit W7 HPE SP1 guest VM though. I hope I don't have to downgrade VB back to v6.1.38-153438.
Thank you for reading and hopefully answering soon.
- Attachments
-
- 64bitW1122H2homeVB7crashLogs.zip
- 64bit W11 22H2 Home guest VM crash logs with VB7 in an updated 64-bit W10 Pro PC host.
- (49.5 KiB) Downloaded 14 times
-
- VB764w10ProGuestLogsIn64w10ProHost.zip
- 64-bit W10 Pro's guest VM crash logs in VB v7 in my updated 64-bit W10 Pro PC host.
- (54.47 KiB) Downloaded 7 times
Last edited by scottgus1 on 11. Oct 2022, 19:25, edited 2 times in total.
Reason: changed title to reflect problem
Reason: changed title to reflect problem
Windows 11 - Virtualbox 7.0
Running Windows 11 on Virtualbox 7.0 Mac Intel not working. Doesn't matter if headless or with console. Attached both crash reports
Both have the same exception
Crashed Thread: 14 EMT-0
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Windows 10 works. Linux also.
Both have the same exception
Crashed Thread: 14 EMT-0
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Windows 10 works. Linux also.
- Attachments
-
- crash_reports.txt.gz
- (30.78 KiB) Downloaded 10 times
VirtualBox 7.0.0 Unattended Installation
Unattended Installation does not work!
Warning:
Networking feature will reset your network connection and temporarily disconnect you from the network.
blocks the installation.
Parameter available to skip this message?
Thx
Warning:
Networking feature will reset your network connection and temporarily disconnect you from the network.
blocks the installation.
Parameter available to skip this message?
Thx
-
- Posts: 3
- Joined: 8. Feb 2011, 15:34
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Windows 10
- Location: Frösön, Sweden
- Contact:
Error upgrading extension pack in 7.0
VirtualBox 7.0 on macOS Monterey 12.6
When upgrading the extension pack I'm getting a notification:
In addition, when trying to share a USB 3.0 device from the host to the guest, I get:
When upgrading the extension pack I'm getting a notification:
Installing package ... Name: Oracle VM VirtualBox 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}
In addition, when trying to share a USB 3.0 device from the host to the guest, I get:
Can't attach USB device ... Failed to attach the USB device SanDisk Ultra [0100] to the virtual machine Planigale. Failed to create a proxy device for the USB device. (Error: VERR_SHARING_VIOLATION). Result Code: NS_ERROR_FAILURE (0X80004005) Component: ConsoleWrap Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}I'm not sure if the second error is caused by the USB 3.0 support being installed incorrectly.
-
- Oracle Corporation
- Posts: 122
- Joined: 28. Aug 2017, 13:14
Re: VirtualBox 7.0.0 Unattended Installation
Are you somehow confusing VirtualBox installation with creating a new vm? When exactly do you see that message?DARO75 wrote:Unattended Installation does not work!
Warning:
Networking feature will reset your network connection and temporarily disconnect you from the network.
blocks the installation.
Parameter available to skip this message?
Thx
VBox 7 Activity Monitor: Does it lock VMs?
Hi, thanks for the new Virtualbox 7.0! I especially like that USB 2.0 and 3.0 is now a core feature. Well done
The new "Activity Monitor" found in the UI is also a very nice and useful feature. However, I observed some strange behaviour:
We have an Ubuntu 22.04 LTS based CI server that automatically clones, configures (= sets guest properties) starts, stops and deletes Virtual machines. Most of the time, it's running headless (= no user logged in to the graphical user interface). When this is the case, it's all good. However, when I log into the UI, open VirtualBox and leave the new activity monitor running, the CI server reports errors running several commands and in the UI I also cannot Remove & Delete stopped VMs. When I try via the VBoxManage cli, it says that the machines are locked. Rebooting the host unlocked the VMs and I was able to remove them.
Could it be that observing a VM using the activity monitor locks them? Could there be some "lock contention"/deadlocking when activity monitor is running and lots of CLI commands are being executed?
The new "Activity Monitor" found in the UI is also a very nice and useful feature. However, I observed some strange behaviour:
We have an Ubuntu 22.04 LTS based CI server that automatically clones, configures (= sets guest properties) starts, stops and deletes Virtual machines. Most of the time, it's running headless (= no user logged in to the graphical user interface). When this is the case, it's all good. However, when I log into the UI, open VirtualBox and leave the new activity monitor running, the CI server reports errors running several commands and in the UI I also cannot Remove & Delete stopped VMs. When I try via the VBoxManage cli, it says that the machines are locked. Rebooting the host unlocked the VMs and I was able to remove them.
Could it be that observing a VM using the activity monitor locks them? Could there be some "lock contention"/deadlocking when activity monitor is running and lots of CLI commands are being executed?
-
- Posts: 45
- Joined: 25. Dec 2010, 13:33
- Primary OS: MS Windows 7
- VBox Version: OSE self-compiled
- Guest OSses: Windows XP
Re: VirtualBox 7.0: Windows 11 guest not launching UI
I have fixed this by installing v7 extensions addon in safe mode, but the UI still has some glitches. Some windows don't show close button or dialog text is yellow for example. Needs to be fixed.
Re: Discuss the VirtualBox 7.0.0 release
@Whiskeyjack
no I mean the MSI installer (I extract the standard installer with the parameter -x)
now the installation works!
no I mean the MSI installer (I extract the standard installer with the parameter -x)
now the installation works!
Re: VBox 7 Activity Monitor: Does it lock VMs?
Well, the strange locking behaviour also occurs with the UI not running at all. Sometimes. So for the moment I went back to 6.1.38JannisSEA wrote:We have an Ubuntu 22.04 LTS based CI server that automatically clones, configures (= sets guest properties) starts, stops and deletes Virtual machines. Most of the time, it's running headless (= no user logged in to the graphical user interface). When this is the case, it's all good. However, when I log into the UI, open VirtualBox and leave the new activity monitor running, the CI server reports errors running several commands and in the UI I also cannot Remove & Delete stopped VMs. When I try via the VBoxManage cli, it says that the machines are locked. Rebooting the host unlocked the VMs and I was able to remove them.
VBox7.0 can not start while 6.1.38 works well
7.0 can not start any VM while 6.1.38 works well. The error messags are:
00:01:24.716523 nspr-3 Launched VM: 3489673264 pid: 5701 (0x1645) frontend: GUI/Qt name: Win10
00:01:24.725143 nspr-3 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is PoweredOff)}, preserve=false aResultDetail=0
00:01:25.217120 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The virtual machine 'Win10' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0
00:01:25.233418 nspr-5 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={300763af-5d6b-46e6-aa96-273eac15538a} aComponent={MachineWrap} aText={The machine is not mutable (state is PoweredOff)}, preserve=false aResultDetail=0
0
Re: Discuss the VirtualBox 7.0.0 release
Another thing that seems to have changed (Windows 10, amd64 as host):
- Have two external monitors attached to the laptop
- Run machines in full-screen mode on the external monitors
- Disconnect the external screens
=> The machines are no longer visible, clicking them in the task bar has no effect. Pressing HostKey + F makes them appear again
- Have two external monitors attached to the laptop
- Run machines in full-screen mode on the external monitors
- Disconnect the external screens
=> The machines are no longer visible, clicking them in the task bar has no effect. Pressing HostKey + F makes them appear again
-
- Oracle Corporation
- Posts: 122
- Joined: 28. Aug 2017, 13:14
Re: VBox 7 Activity Monitor: Does it lock VMs?
You will need to give us specific reproduction steps. Your current report is too vague to be helpful.JannisSEA wrote:Well, the strange locking behaviour also occurs with the UI not running at all. Sometimes. So for the moment I went back to 6.1.38