| View previous topic :: View next topic |
| Author |
Message |
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
 Posted: Tue Sep 29, 2020 11:15 pm Post subject: |
 |
|
Can you post the message again, please?
Re Old tango's remarks: I use the same method but I use a script to load .config from the running kernel and after rebuilding the kernel and modules. I run "emerge @module-rebuild"
Which builds all out of kernel modules including the vbox modules.
| Code: | tony@MSI ~ $ emerge -p @module-rebuild
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] app-emulation/virtualbox-modules-6.1.14
|
When I had out-of-kernel R8168, it built that too. |
|
| Back to top |
|
 |
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 30, 2020 8:23 am Post subject: |
|
|
| Tony0945 wrote: | | Can you post the message again, please? |
I start the GUI successfully, then I try starting any existing or newly created VM, I get a dialog box with the following error:
| Code: | The virtual machine 'VM' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} |
| Tony0945 wrote: | Re Old tango's remarks: I use the same method but I use a script to load .config from the running kernel and after rebuilding the kernel and modules. I run "emerge @module-rebuild"
Which builds all out of kernel modules including the vbox modules.
| Code: | tony@MSI ~ $ emerge -p @module-rebuild
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] app-emulation/virtualbox-modules-6.1.14
|
When I had out-of-kernel R8168, it built that too. |
I do emerge @module-rebuild after each kernel rebuild as well.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 30, 2020 10:40 am Post subject: |
|
|
Ok, I removed virtualbox-bin, renamed ~/.Virtualbox, checked /opt for any potential remnants, and emerged virtualbox-6.1.14a. When I started the GUI, I got the same strange COM error OldTango was mentioning, which was solved by a reboot:
| Code: | Failed to initialize COM or to find the VirtualBox COM server. Most likely, the VirtualBox server is not running or failed to start.
The application will now terminate.
Callee RC: NS_ERROR_FILE_TARGET_DOES_NOT_EXIST (0x80520006) |
Then I created a new VM, tried to start it, and I got the same error message.
For reference, here's what's in dmesg:
| Code: | > dmesg | grep -i vbox
[ 4.284720] vboxdrv: Found 8 processor cores
[ 4.302136] vboxdrv: TSC mode is Invariant, tentative frequency 1995456354 Hz
[ 4.302138] vboxdrv: Successfully loaded version 6.1.14 (interface 0x002e0000)
[ 4.325979] VBoxNetFlt: Successfully started.
[ 4.341680] VBoxNetAdp: Successfully started. |
I will now downgrade to 6.0.24, and see what happens, but I don't expect the issue to be solved by the downgrade.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 30, 2020 1:25 pm Post subject: |
|
|
Mine is slightly longer:
| Code: | ~ $ dmesg | grep -i vbox
[ 0.000000] vboxdrv: loading out-of-tree module taints kernel.
[ 0.000000] vboxdrv: Found 16 processor cores
[ 0.000000] vboxdrv: TSC mode is Invariant, tentative frequency 3699995612 Hz
[ 0.000000] vboxdrv: Successfully loaded version 6.1.14 (interface 0x002e0000)
[ 0.000000] VBoxNetAdp: Successfully started.
[ 0.000000] VBoxNetFlt: Successfully started.
[ 0.000000] vboxdrv: 00000000e82c2c9e VMMR0.r0
[ 0.000000] vboxdrv: 00000000f9395fd2 VBoxDDR0.r0
[ 0.000000] VBoxNetFlt: attached to 'eth0' / 30:9c:23:1b:42:51
[ 0.000000] vboxdrv: 00000000dfbe4b82 VBoxEhciR0.r0
[ 0.000000] vboxnetflt: 1 out of 145914 packets were not sent (directed to host |
Looking for the module: | Code: | ~ $ locate vboxdrv
/etc/modprobe.d/vboxdrv.conf
/lib64/modules/4.14.194-gentoo/misc/vboxdrv.ko
/lib64/modules/4.17.19-gentoo/misc/vboxdrv.ko
/lib64/modules/4.19.141-gentoo/misc/vboxdrv.ko
/lib64/modules/5.4.66-gentoo/misc/vboxdrv.ko
|
I'm suspicious that your system doesn't show the warning.
I think downgrading will muck it up worse. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 30, 2020 1:38 pm Post subject: |
|
|
More info
| Code: | tony@MSI ~ $ locate VMMR0.r0
/usr/lib64/virtualbox/VMMR0.r0
tony@MSI ~ $ equery b /usr/lib64/virtualbox/VMMR0.r0
* Searching for /usr/lib64/virtualbox/VMMR0.r0 ...
app-emulation/virtualbox-6.1.14a (/usr/lib64/virtualbox/VMMR0.r0)
tony@MSI ~ $ ls -l /usr/lib64/virtualbox/*.r0
-rwxr-x--- 1 root vboxusers 247904 Sep 10 17:01 /usr/lib64/virtualbox/VBoxDDR0.r0
-rwxr-x--- 1 root vboxusers 1926440 Sep 10 17:01 /usr/lib64/virtualbox/VMMR0.r0
tony@MSI ~ $ grep vboxusers /etc/group
vboxusers:x:304:tony,root
|
|
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 30, 2020 2:29 pm Post subject: |
|
|
| Tony0945 wrote: | Mine is slightly longer:
| Code: | ~ $ dmesg | grep -i vbox
[ 0.000000] vboxdrv: loading out-of-tree module taints kernel.
[ 0.000000] vboxdrv: Found 16 processor cores
[ 0.000000] vboxdrv: TSC mode is Invariant, tentative frequency 3699995612 Hz
[ 0.000000] vboxdrv: Successfully loaded version 6.1.14 (interface 0x002e0000)
[ 0.000000] VBoxNetAdp: Successfully started.
[ 0.000000] VBoxNetFlt: Successfully started.
[ 0.000000] vboxdrv: 00000000e82c2c9e VMMR0.r0
[ 0.000000] vboxdrv: 00000000f9395fd2 VBoxDDR0.r0
[ 0.000000] VBoxNetFlt: attached to 'eth0' / 30:9c:23:1b:42:51
[ 0.000000] vboxdrv: 00000000dfbe4b82 VBoxEhciR0.r0
[ 0.000000] vboxnetflt: 1 out of 145914 packets were not sent (directed to host |
|
How come your dmesg doesn't have proper timestamps? It may be that the extra output you have is due to starting up a VM...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 30, 2020 3:29 pm Post subject: |
|
|
| Lori wrote: | | How come your dmesg doesn't have proper timestamps? It may be that the extra output you have is due to starting up a VM... |
That's a very good question. I just rebooted it remotely because I noticed in the whole dmesg that the usb modules were being loaded in the wrong order which might account for my printer problems.
EDIT: no change. at this point xdm is running but no one is logged in. I'll be opening my own support thread on this. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 30, 2020 4:57 pm Post subject: |
|
|
I do have have timestamps while running as root. Not when running as user.
| Code: | MSI /home/tony # dmesg | grep -i vbox
[ 7.512299] vboxdrv: loading out-of-tree module taints kernel.
[ 7.514561] vboxdrv: Found 16 processor cores
[ 7.550191] vboxdrv: TSC mode is Invariant, tentative frequency 3699995704 Hz
[ 7.550191] vboxdrv: Successfully loaded version 6.1.14 (interface 0x002e0000)
[ 7.561183] VBoxNetAdp: Successfully started.
[ 7.572101] VBoxNetFlt: Successfully started.
|
|
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 30, 2020 5:00 pm Post subject: |
|
|
| Tony0945 wrote: | I do have have timestamps while running as root. Not when running as user.
| Code: | MSI /home/tony # dmesg | grep -i vbox
[ 7.512299] vboxdrv: loading out-of-tree module taints kernel.
[ 7.514561] vboxdrv: Found 16 processor cores
[ 7.550191] vboxdrv: TSC mode is Invariant, tentative frequency 3699995704 Hz
[ 7.550191] vboxdrv: Successfully loaded version 6.1.14 (interface 0x002e0000)
[ 7.561183] VBoxNetAdp: Successfully started.
[ 7.572101] VBoxNetFlt: Successfully started.
|
|
Now your output looks almost the same as mine. The only difference is the "TSC mode" line.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 30, 2020 8:09 pm Post subject: |
|
|
| Lori wrote: | | I will now downgrade to 6.0.24, and see what happens, but I don't expect the issue to be solved by the downgrade. |
As expected, the downgrade didn't help, same behavior.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
x90e
n00b
Joined: 30 Sep 2020
Posts: 40
|
| Posted: Wed Sep 30, 2020 8:18 pm Post subject: Re: Switching from virtualbox-bin to virtualbox (6.1.14a) |
|
|
| Lori wrote: | I have been using virtualbox-bin until yesterday, when it was removed from the tree and I was forced to switch to virtualbox from source. I'm using ~amd64, so version 6.1.14a. I can no longer start my existing VMs, I get this error:
| Code: | The virtual machine 'VM' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} |
Digging a bit further, I see this in ~/.VirtualBox/VBoxSVC.log
| Code: | ...
00:00:00.129199 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:00.208743 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.209891 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={027bc463-929c-40e8-bf16-fea557cd8e7e} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
... |
Permissions on those files:
| Code: | > ls -la /dev/vbox*
crw------- 1 root root 10, 60 Sep 22 2020 /dev/vboxdrv
crw------- 1 root root 10, 59 Sep 22 2020 /dev/vboxdrvu
crw------- 1 root root 10, 58 Sep 22 2020 /dev/vboxnetctl |
I think these were the permissions previously as well, and virtualbox-bin was still working, but to see if it helps, I change ownership to my user. That solves the access issue to /dev/vboxdrvu, but then this happens:
| Code: | 00:00:00.141930 nspr-2 failed to create vboxnet0, error (0x80004005)
00:00:00.144688 nspr-2 failed to create vboxnet1, error (0x80004005)
00:00:00.147383 nspr-2 failed to create vboxnet2, error (0x80004005)
00:00:00.150141 nspr-2 failed to create vboxnet3, error (0x80004005)
00:00:00.152906 nspr-2 failed to create vboxnet4, error (0x80004005)
00:00:00.155705 nspr-2 failed to create vboxnet5, error (0x80004005)
00:00:00.158442 nspr-2 failed to create vboxnet6, error (0x80004005)
00:00:00.161316 nspr-2 failed to create vboxnet7, error (0x80004005)
00:00:00.164146 nspr-2 failed to create vboxnet8, error (0x80004005)
00:00:00.166783 nspr-2 failed to create vboxnet9, error (0x80004005)
00:00:00.166977 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.167053 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={027bc463-929c-40e8-bf16-fea557cd8e7e} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
|
What's the RightWay(TM) to get virtualbox working...?! |
Try disabling all network interfaces in the virtual machine configuration settings before you start the VM. I would also go into the storage settings and remove the guest additions .iso if you still have it attached. You might be able to get it booted this way and then attach or download the new drivers.
Also, groups / permissions changes on the host usually don't take effect until you logout / log back in or reboot, so be sure to do that whenever you change or add yourself to a new group. i'd also open up a terminal and run the command for the virtualbox GUI from the console and see what errors it throws at you (post the output here). I would also try running it as root (just for troubleshooting purposes) and see if it allows you to start a VM, then. I'm guessing it's something to do with permissions related to the virtual drive |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Wed Sep 30, 2020 8:43 pm Post subject: |
|
|
| Lori wrote: |
I start the GUI successfully, then I try starting any existing or newly created VM, I get a dialog box with the following error:
| Code: | The virtual machine 'VM' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} |
|
When you create a new VM, do you enable 3D acceleration in the VM. If so try to create one with that option disabled and see if it will run.
I didn't provide all of the information about the warning VirtualBox gave me when starting my WinXP VM. It basically told me that the combination I had selected would cause the VM's to fail in VirtualBox Versions => 6.1 in the future. I haven't done any more research into to this yet.
In the past when I used virtualbox-bin, my VM's would sometimes fail to start after some package upgrades but the fails were almost always due to the kernel modules not matching or not loaded. Always quick fixes. When searching your error in google again the only relative (older) information pointed to a modules problem. So I am kind of at a loss as to why you are having this problem. There is a chance this is related to ~amd64 but I have no way to test for this.
Alos | Code: | michael@SuperTux ~ $ dmesg | grep -i vbox
[ 5.634934] vboxdrv: loading out-of-tree module taints kernel.
[ 5.637205] vboxdrv: Found 32 processor cores
[ 5.654275] vboxdrv: TSC mode is Invariant, tentative frequency 3393576067 Hz
[ 5.654275] vboxdrv: Successfully loaded version 6.0.24 (interface 0x00290008)
[ 5.663830] VBoxNetFlt: Successfully started.
[ 5.673085] VBoxNetAdp: Successfully started.
[ 366.612290] vboxdrv: 00000000fd4ba2fb VMMR0.r0
[ 366.944753] vboxdrv: 00000000ddc57e54 VBoxDDR0.r0
[ 367.013526] vboxdrv: 00000000d68bebd6 VBoxEhciR0.r0
[ 768.657436] vboxdrv: 00000000bd2678a9 VMMR0.r0
[ 768.725940] vboxdrv: 00000000ddc57e54 VBoxDDR0.r0
[ 768.763586] vboxdrv: 00000000d68bebd6 VBoxEhciR0.r0
[ 845.642176] vboxdrv: 00000000107b6a0e VMMR0.r0
[ 845.752915] vboxdrv: 0000000039d63c99 VBoxDDR0.r0
[ 845.845388] vboxdrv: 000000009b24fec6 VBoxEhciR0.r0
[102943.717359] vboxdrv: 00000000fd4ba2fb VMMR0.r0
[102943.845727] vboxdrv: 00000000ddc57e54 VBoxDDR0.r0
[102943.913968] vboxdrv: 00000000d68bebd6 VBoxEhciR0.r0 |
mine is even longer.... 
Best Tango....  |
|
| Back to top |
|
|
x90e
n00b
Joined: 30 Sep 2020
Posts: 40
|
| Posted: Wed Sep 30, 2020 8:54 pm Post subject: |
|
|
| If you google the error code, you will find different problems other than kernel modules. Combined with the inability to create vboxnet interfaces or find the guest additions .iso, it sounds like the VM is still configured for the old way of doing things. They might need to disable all network interfaces and for example the guest additions storage controller / any other storage controller just to get the system to boot up so they can update / install new drivers. I ran into a similar problem with passing through an nvme raw disk image after an upgrade. I needed to unattach everything but the boot drive to boot up and update everything. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 30, 2020 9:39 pm Post subject: |
|
|
| Lori wrote: | | The error happens when I launch the GUI application, independent of a particular VM. I checked the headless binary just out of curiosity. |
Is this still true? Is the problem when launching the GUI? Or have we moved on to a particular VM (including all VM's? I have the idea there is a shifting target.
It sounds like the GUI is now coming up and a particlur VM is failiung. Which OS is being run. Windows? (which type?)
I have VM's for XP, Win7, win10, Devuan, and Void Linux. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Wed Sep 30, 2020 9:54 pm Post subject: |
|
|
| x90e wrote: | | If you google the error code, you will find different problems other than kernel modules. Combined with the inability to create vboxnet interfaces or find the guest additions .iso, it sounds like the VM is still configured for the old way of doing things. |
True but they didn't seem relative to his problem. In addition his newly created VM's also fail to start.
| x90e wrote: | | They might need to disable all network interfaces and for example the guest additions storage controller / any other storage controller just to get the system to boot up so they can update / install new drivers. I ran into a similar problem with passing through an nvme raw disk image after an upgrade. I needed to unattach everything but the boot drive to boot up and update everything. |
Sounds reasonable even though I have never encountered these sort of errors in the past with the exception of having to reinstall the guest-additions.iso after some updates. The virtualbox-guest-addtions don't seem to even be necessary as I get the same functionality with the packages I have installed. | Code: | eix -I app-emulation/virtualbox
[?] app-emulation/virtualbox
Available versions: 5.1.26 ~5.1.28 ~5.1.30 {alsa debug doc headless java libressl lvm +opengl pam pax_kernel pulseaudio python +qt5 +sdk +udev vboxwebsrv vnc ELIBC="FreeBSD" PYTHON_TARGETS="python2_7"}
Installed versions: 6.0.24(06:43:50 PM 09/27/2020)(alsa java opengl opus pam pulseaudio python qt5 sdk udev -debug -doc -dtrace -headless -libressl -lvm -pax_kernel -vboxwebsrv -vnc ELIBC="-FreeBSD" KERNEL="linux" PYTHON_SINGLE_TARGET="python3_7 -python3_6 -python3_8")
Homepage: http://www.virtualbox.org/
Description: Family of powerful x86 virtualization products for enterprise and home use
[?] app-emulation/virtualbox-additions
Available versions: 5.1.26^m ~5.1.28^m ~5.1.30^m
Installed versions: 6.0.24^m(06:47:06 PM 09/27/2020)
Homepage: http://www.virtualbox.org/
Description: CD image containing guest additions for VirtualBox
[?] app-emulation/virtualbox-extpack-oracle
Available versions: 5.1.26.117224^ms ~5.1.28.117968^ms ~5.1.30.118389^ms
Installed versions: 6.0.24.139119^msd(06:50:42 PM 09/27/2020)
Homepage: http://www.virtualbox.org/
Description: PUEL extensions for VirtualBox
[?] app-emulation/virtualbox-modules
Available versions: 5.1.26 ~5.1.28 ~5.1.30 {pax_kernel KERNEL="linux"}
Installed versions: 6.0.24-r1(07:09:00 PM 09/27/2020)(-pax_kernel KERNEL="linux")
Homepage: http://www.virtualbox.org/
Description: Kernel Modules for Virtualbox
Found 4 matches |
Best Tango.... |
|
| Back to top |
|
|
x90e
n00b
Joined: 30 Sep 2020
Posts: 40
|
| Posted: Wed Sep 30, 2020 10:08 pm Post subject: |
|
|
| OldTango wrote: | | x90e wrote: | | If you google the error code, you will find different problems other than kernel modules. Combined with the inability to create vboxnet interfaces or find the guest additions .iso, it sounds like the VM is still configured for the old way of doing things. |
True but they didn't seem relative to his problem. In addition his newly created VM's also fail to start.
Best Tango.... |
I'm assuming he's creating new VMs with the same configuration as his old ones, trying to set up a similar/the same VM. I could be wrong in that assumption but i'm just going off the log files he posted. It shouldn't be looking for Guest Additions.iso or be trying to create vboxnet interfaces unless he has previously configured it to do so, and it would make sense in the case that he was re-using an old configuration after an update, perhaps not having set the proper access permissions for groups/users/virtual disks/interfaces, etc. I don't usually have these problems but stranger things have happened so it's not too much of a problem to try them out in troubleshooting. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Fri Oct 02, 2020 1:57 pm Post subject: |
|
|
| OldTango wrote: | | I didn't provide all of the information about the warning VirtualBox gave me when starting my WinXP VM. It basically told me that the combination I had selected would cause the VM's to fail in VirtualBox Versions => 6.1 in the future. I haven't done any more research into to this yet. |
Based on the ChangeLog for 6.1.x they removed the VBoxVGA virtual graphics controller, you need to switch to either VMSVGA or VBoxSVGA: "Graphics: New style 3D support (with VBoxSVGA and VMSVGA) remains, old style 3D support (with VBoxVGA) has been completely removed"
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Fri Oct 02, 2020 4:04 pm Post subject: |
|
|
| Lori wrote: | | OldTango wrote: | | I didn't provide all of the information about the warning VirtualBox gave me when starting my WinXP VM. It basically told me that the combination I had selected would cause the VM's to fail in VirtualBox Versions => 6.1 in the future. I haven't done any more research into to this yet. |
Based on the ChangeLog for 6.1.x they removed the VBoxVGA virtual graphics controller, you need to switch to either VMSVGA or VBoxSVGA: "Graphics: New style 3D support (with VBoxSVGA and VMSVGA) remains, old style 3D support (with VBoxVGA) has been completely removed" |
Thanks for the information. That link is very useful. I had already made the switch and disabled 3D support completely as I don't really need it for my purposes anyway.
Also do you have anything set in your kernel under CONFIG_VIRTUALIZATION=y? My settings are: | Code: | CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_VHOST_NET is not set
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set |
Best Tango.... |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Fri Oct 02, 2020 4:19 pm Post subject: |
|
|
Running VBoxVGA with 3D acceleration here on Virtual XP
VBoxSVGA with 3D on Virtual Windows 7 and Virual Windows 10
VBoxVGA no acceleration on Virtual Void Linux and Virtual Devuan Linux
That's why I asked which virtual machine is failing, so I can give my specs. 6.1.14a |
|
| Back to top |
|
|
cz0
Guru
Joined: 13 Jun 2005
Posts: 313
Location: /earth/russia/moscow
|
| Posted: Tue Oct 06, 2020 2:41 pm Post subject: |
|
|
| BTW, is there are any chances to get virtualbox-bin-6 or building from sources is the only actual way to get it running? |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Oct 06, 2020 3:20 pm Post subject: |
|
|
Ok, we can lay to rest the speculations that this issue is permissions related. I just tried running VirtualBox as root, and I get the same behavior. Here's the full /root/.config/VirtualBox/VBoxSVC.log:
| Code: | 00:00:00.002789 main VirtualBox XPCOM Server 6.1.14_Gentoo r140239 linux.amd64 (Oct 4 2020 14:26:45) release log
00:00:00.002797 main Log opened 2020-10-06T15:11:15.789506000Z
00:00:00.002800 main Build Type: release
00:00:00.002810 main OS Product: Linux
00:00:00.002814 main OS Release: 5.4.66-gentoo
00:00:00.002818 main OS Version: #1 SMP PREEMPT Tue Sep 22 14:46:29 EEST 2020
00:00:00.002882 main DMI Product Name: Dell System XPS L502X
00:00:00.002891 main DMI Product Version:
00:00:00.002900 main Firmware type: BIOS
00:00:00.002936 main Host RAM: 15911MB (15.5GB) total, 15721MB (15.3GB) available
00:00:00.002943 main Executable: /usr/lib64/virtualbox/VBoxSVC
00:00:00.002944 main Process ID: 3327
00:00:00.002944 main Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.004114 main IPC socket path: /tmp/.vbox-root-ipc/ipcd
00:00:00.110941 nspr-2 VirtualBox: object creation starts
00:00:00.111669 nspr-2 Home directory: '/root/.config/VirtualBox'
00:00:00.122890 nspr-2 Successfully initialised host USB using sysfs
00:00:00.127735 nspr-2 HostDnsMonitor: initializing
00:00:00.127975 nspr-2 NAT: resolv.conf: nameserver 10.81.80.5
00:00:00.127997 nspr-2 HostDnsMonitor: updating information
00:00:00.128014 nspr-2 HostDnsMonitor: old information
00:00:00.128017 nspr-2 no server entries
00:00:00.128020 nspr-2 no domain set
00:00:00.128023 nspr-2 no search string entries
00:00:00.128026 nspr-2 HostDnsMonitor: new information
00:00:00.128028 nspr-2 server 1: 10.81.80.5
00:00:00.128031 nspr-2 domain: icanhas.net
00:00:00.128034 nspr-2 search string 1: icanhas.net
00:00:00.130521 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.133402 nspr-2 VirtualBox: object created
00:00:31.923367 createBase Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:32.460203 nspr-3 Saving settings file "/root/.VirtualBox/Machines/Test/Test.vbox" with version "1.16-linux"
00:00:32.475825 nspr-2 Saving settings file "/root/.VirtualBox/Machines/Test/Test.vbox" with version "1.16-linux"
00:00:32.486535 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:32.501914 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:32.517727 nspr-3 Saving settings file "/root/.VirtualBox/Machines/Test/Test.vbox" with version "1.16-linux"
00:00:34.780690 nspr-3 Launched VM: 4026540016 pid: 3437 (0xd6d) frontend: GUI/Qt name: Test
00:00:35.281185 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'Test' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0
00:00:48.128847 nspr-4 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:48.138951 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:48.151443 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:48.162630 nspr-4 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:48.177097 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:48.192025 nspr-2 Saving settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:53.712338 main VirtualBox: object deletion starts
00:00:53.712389 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/root/.VirtualBox/Machines/Test/Test.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:53.712769 main HostDnsMonitor: shutting down ...
00:00:53.713082 main HostDnsMonitor: shut down
00:00:53.717052 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:53.717165 main VirtualBox: object deleted |
Disregard the last two errors, they happen at shutdown. This is the main culprit:
| Code: | 00:00:34.780690 nspr-3 Launched VM: 4026540016 pid: 3437 (0xd6d) frontend: GUI/Qt name: Test
00:00:35.281185 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'Test' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0 |
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Oct 06, 2020 4:21 pm Post subject: |
|
|
| cz0 wrote: | | BTW, is there are any chances to get virtualbox-bin-6 or building from sources is the only actual way to get it running? |
Not officially. However, if you really want to run it, you can resurrect the ebuild from the gentoo ebuild Git repository, and use it from your local overlay. That's what I do when I'm not trying to get the source version to work.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Oct 06, 2020 4:28 pm Post subject: |
|
|
| OldTango wrote: | | When you create a new VM, do you enable 3D acceleration in the VM. If so try to create one with that option disabled and see if it will run. |
What I try to do now is creating a new Ubuntu Linux 64-bit VM with all default settings, which is 3D acceleration disabled, 1 network interface, no CD attached, empty HDD created on VM creation. I can't get the VM console dialog box to open.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
cz0
Guru
Joined: 13 Jun 2005
Posts: 313
Location: /earth/russia/moscow
|
| Posted: Wed Oct 07, 2020 9:17 am Post subject: |
|
|
| Lori wrote: | | cz0 wrote: | | BTW, is there are any chances to get virtualbox-bin-6 or building from sources is the only actual way to get it running? |
Not officially. However, if you really want to run it, you can resurrect the ebuild from the gentoo ebuild Git repository, and use it from your local overlay. That's what I do when I'm not trying to get the source version to work. |
So, as far as I can see, no source version is working, neither binary.. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Oct 07, 2020 11:29 am Post subject: |
|
|
| cz0 wrote: | | So, as far as I can see, no source version is working, neither binary.. |
Well, one person on this thread reported a working stable source version (6.0.x), another one a working testing source version (6.1.x). Have you already tried building from source?
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
|
Desktop Environments
