Debian locks up when opening VM
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Debian locks up when opening VM
I'm running an XP guest on a Debian 11.5 host, using Virtual Box 7.0. Guest additions and extension pack are installed. The guest machine has worked well on previous versions of Debian, however, after upgrading to Debian 11 (from 9), the host system lockups as soon as the VM opens; the computer is completely frozen.
However, if I remove myself from the vboxusers group, all is fine with both host and guest, but the VM has no USB conectivity. I've tried rolling back to Vbox 6.1, but with the same result.
Any suggestions to get things working, please.
However, if I remove myself from the vboxusers group, all is fine with both host and guest, but the VM has no USB conectivity. I've tried rolling back to Vbox 6.1, but with the same result.
Any suggestions to get things working, please.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Debian locks up when opening VM
First, you'll need to be sure you're running official Virtualbox, not the Debian fork. In the VM's vbox.log, look at the first line. If you see "_Debian" or some such Linux distro flavor after the Virtualbox version number, then you're running the fork.
Either way, let's try a complete uninstall of Virtualbox, then run the official version's prerequisites https://www.virtualbox.org/manual/ch02. ... nux-prereq then install official Virtualbox https://www.virtualbox.org/wiki/Linux_Downloads
Either way, let's try a complete uninstall of Virtualbox, then run the official version's prerequisites https://www.virtualbox.org/manual/ch02. ... nux-prereq then install official Virtualbox https://www.virtualbox.org/wiki/Linux_Downloads
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
Thanks for this advice.
I did originally download VB from the link you pointed to. See below for the top line of the log file.
I have re-downloaded and checked the SHA256 checksum. I also re-downloaded the extensions pack and checked the checksum.
Qt is version 5.15.2
SDL is version 1.2.15
gcc, make, the kernel headers and linux-kbuild all check out OK.
I don't have UEFI.
Also, in BIOS, "Intel Virtual Technologies" is enabled.
To uninstall the existing program, I first unloaded the extensions pack from within VB, then uninstalled it with dpkg (actually, with a small front end called xfp).
I reinstalled the new downloads.
The result is the same - the host computer (and the VM) locks up during the VM's startup.
I monitored the log file folder during the start of the VM, and I could see that a new file was created in the folder, and data was being added to it. But to recover from the lockup, I have to force a hard shutdown, and for some reason the log file gets blanked. However, one time I created a symlink to a USB stick, which I removed before shutting down. This contained just 13 lines:
At the point of lockup, the terminal showed
Alas, I do need USB connectivity.
I did originally download VB from the link you pointed to. See below for the top line of the log file.
I have re-downloaded and checked the SHA256 checksum. I also re-downloaded the extensions pack and checked the checksum.
Qt is version 5.15.2
SDL is version 1.2.15
gcc, make, the kernel headers and linux-kbuild all check out OK.
I don't have UEFI.
Also, in BIOS, "Intel Virtual Technologies" is enabled.
To uninstall the existing program, I first unloaded the extensions pack from within VB, then uninstalled it with dpkg (actually, with a small front end called xfp).
I reinstalled the new downloads.
The result is the same - the host computer (and the VM) locks up during the VM's startup.
I monitored the log file folder during the start of the VM, and I could see that a new file was created in the folder, and data was being added to it. But to recover from the lockup, I have to force a hard shutdown, and for some reason the log file gets blanked. However, one time I created a symlink to a USB stick, which I removed before shutting down. This contained just 13 lines:
I also started the VM from a terminal with00:00:01.261567 VirtualBox VM 7.0.4 r154605 linux.amd64 (Nov 17 2022 18:36:32) release log
00:00:01.261570 Log opened 2023-01-02T20:57:40.502622000Z
00:00:01.261570 Build Type: release
00:00:01.261574 OS Product: Linux
00:00:01.261575 OS Release: 5.10.0-20-amd64
00:00:01.261576 OS Version: #1 SMP Debian 5.10.158-2 (2022-12-13)
00:00:01.261602 DMI Product Name: 20236
00:00:01.261612 DMI Product Version: Lenovo G500
00:00:01.261623 Firmware type: BIOS
00:00:01.261665 Host RAM: 5841MB (5.7GB) total, 5155MB (5.0GB) available
00:00:01.261670 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:01.261670 Process ID: 1656
00:00:01.261671 Package type: LINUX_64BITS__DEBIAN_11
Code: Select all
VirtualBoxVM --startvm
However, when I remove myself from the vboxusers group, I get the same terminal message, even though I have a working VM.Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s).
Alas, I do need USB connectivity.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Debian locks up when opening VM
I'm no Linux guru, but I wonder if your host OS's kernel is too new for Virtualbox 7.0.4. Try the test builds?
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
In the host OS, did you check dmesg or /var/log/syslog after restarting the host?
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
I found this in syslog. This is the point that I started VBox, followed, presumably, by the lockup event a minute or so later (the computer froze at 16:36:11), then the start of the reboot:fth0 wrote:In the host OS, did you check dmesg or /var/log/syslog after restarting the host?
Jan 4 16:35:03 debian NetworkManager[561]: <info> [1672850103.8075] manager: (vboxnet0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Jan 4 16:35:03 debian systemd-udevd[1647]: Using default interface naming scheme 'v247'.
Jan 4 16:35:03 debian systemd-udevd[1647]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
Jan 4 16:39:04 debian systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 4 16:39:04 debian systemd[1]: Finished Coldplug All udev Devices.
Jan 4 16:39:04 debian kernel: [ 0.000000] Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.158-2 (2022-12-13)
On the reboot, dmesg shows this:
2023-01-04T16:39:13,308386+00:00 vboxdrv: loading out-of-tree module taints kernel.
2023-01-04T16:39:13,309126+00:00 vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
2023-01-04T16:39:13,329539+00:00 vboxdrv: Found 4 processor cores/threads
2023-01-04T16:39:13,350575+00:00 vboxdrv: TSC mode is Invariant, tentative frequency 2394512037 Hz
2023-01-04T16:39:13,350578+00:00 vboxdrv: Successfully loaded version 7.0.4 r154605 (interface 0x00330004)
2023-01-04T16:39:13,666549+00:00 VBoxNetFlt: Successfully started.
2023-01-04T16:39:13,715540+00:00 VBoxNetAdp: Successfully started.
Do the first two lines indicate the problem? If so, what do I do to resolve it?
I suppose I could also try rolling back to Debian 9, or VBox6.0 for a short term solution. Any idea where I can download pre 6.1 versions?scottgus1 wrote:I'm no Linux guru, but I wonder if your host OS's kernel is too new for Virtualbox 7.0.4. Try the test builds?
I might look for some linux forums, too.
Thanks.
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
No. The VirtualBox kernel drivers (e.g. vboxdrv) are built during the VirtualBox installation and therefore aren't signed by the Linux distribution. In consequence, the Linux distribution cannot guarantee that their Linux kernel still functions correctly, and marks it as tainted.Pearl E Gates wrote:Do the first two lines indicate the problem?
The dmesg output doesn't show anything unexpected to me.
In your VBox.log file, the next (14th + 15th) lines would show the results of checking the VirtualBox Extension Pack (EP). You could try if uninstalling the EP helps. Note that in VirtualBox 7.0, you don't need the EP any more for USB support.
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
Thanks for that.
Unfortunately, I get the same result either with or without the extensions pack.
I even symlinked the log file to a USB stick again, but it only got the same 13 lines.
Unfortunately, I get the same result either with or without the extensions pack.
I even symlinked the log file to a USB stick again, but it only got the same 13 lines.
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
A few (not so) random ideas:
Check and provide the global log files in ~/.config/VirtualBox, especially VBoxSVC.log.
If you have any external USB devices connected to the host, for a test, disconnect them before starting the VM.
Provide the output of ls -lR /dev/vbox*.
Check and provide the global log files in ~/.config/VirtualBox, especially VBoxSVC.log.
If you have any external USB devices connected to the host, for a test, disconnect them before starting the VM.
Provide the output of ls -lR /dev/vbox*.
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
No USB devices connected.
I've zipped and attached ~/.config/VirtualBox/
ls -lR /dev/vbox* gives this:
I've zipped and attached ~/.config/VirtualBox/
ls -lR /dev/vbox* gives this:
Code: Select all
ls -lR /dev/vbox*
crw-rw---- 1 root vboxusers 10, 61 Jan 6 09:45 /dev/vboxdrv
crw-rw-rw- 1 root root 10, 60 Jan 6 09:45 /dev/vboxdrvu
crw-rw---- 1 root vboxusers 10, 59 Jan 6 09:45 /dev/vboxnetctl
/dev/vboxusb:
total 0
drwxr-x--- 2 root vboxusers 80 Jan 6 09:44 001
/dev/vboxusb/001:
total 0
crw-rw---- 1 root vboxusers 189, 2 Jan 6 09:44 003
crw-rw---- 1 root vboxusers 189, 3 Jan 6 09:44 004
- Attachments
-
- VirtualBox.zip
- ~/.config/VirtualBox/
- (21.29 KiB) Downloaded 5 times
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
The VirtualBox devices have the expected permissions, so far, so good.
The VBoxSVC.log file indicates that you restored a snapshot, and then VirtualBox tried to read two backup files ("WinXP VIDA-1.15-linux.vbox" and "WinXP VIDA-1.15-linux.vbox"). Please remove or rename those two files and try if the issue persists.
If the issue persists, reproduce it and provide a zip file containing the VBoxSVC.log, WinXP VIDA.vbox and VBox.log files.
The VBoxSVC.log file indicates that you restored a snapshot, and then VirtualBox tried to read two backup files ("WinXP VIDA-1.15-linux.vbox" and "WinXP VIDA-1.15-linux.vbox"). Please remove or rename those two files and try if the issue persists.
If the issue persists, reproduce it and provide a zip file containing the VBoxSVC.log, WinXP VIDA.vbox and VBox.log files.
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
Renamed the two files, but the issue persists. I've attached requested files.fth0 wrote:... VirtualBox tried to read two backup files ("WinXP VIDA-1.15-linux.vbox" and "WinXP VIDA-1.15-linux.vbox"). Please remove or rename those two files and try if the issue persists.
If the issue persists, reproduce it and provide a zip file containing the VBoxSVC.log, WinXP VIDA.vbox and VBox.log files.
I tried something else. I put the VM on an external HDD, connected via USB, and started the VM from there. Same result, with the host machine locking up, but the VBox.log file was saved to the external HDD, and is more extensive than the 13 lines I was previously able to save to a USB stick.
I also put Debian 11 on a desktop computer, and ran the same VM from the external HDD, so running exactly the same file. This time, things seemed to work properly. Does this indicate that maybe my old laptop is not up to VBox 7?
I really appreciate the help I'm getting with this. Many thanks.
- Attachments
-
- VBox logs.zip
- (21.31 KiB) Downloaded 3 times
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
The VBox.log file is missing significant parts around the 14th line from the beginning and around the 14th line from the end, so I'm not sure about the validity of its contents. I haven't seen such behavior in other log files yet, so I'd rather attribute that to problems on your host.
According to the VBox.log file, you started the VM from a snapshot taken from a running VM by VirtualBox 5.2.22 four years ago. This "paused" VM run cannot be guaranteed to "continue" running on a newer VirtualBox version like 7.0.4. If you don't need the saved VM state, I'd suggest to use "Discard Saved State...".
According to the VBox.log file, you started the VM from a snapshot taken from a running VM by VirtualBox 5.2.22 four years ago. This "paused" VM run cannot be guaranteed to "continue" running on a newer VirtualBox version like 7.0.4. If you don't need the saved VM state, I'd suggest to use "Discard Saved State...".
-
- Posts: 7
- Joined: 2. Jan 2023, 21:29
Re: Debian locks up when opening VM
I may have found a workaround. The issue seems to be caused by one particular entry in the list of USB devices available to the VM. Specifically, there is one device listed as "Generic USB2.0-CRW [3960]". If I uncheck that before I start the VM, then no lockup, but select it at any time after starting the VM, and the whole system instantly freezes.
I seem to be able to select anything else in the list of USB devices, and I'm not sure what this entry refers to.
Unfortunately, in trying to figure this out I broke the original VM, so I've created a new VM from scratch. It's not fully configured yet, but as long as I can avoid the generic USB device, it seems to be functioning OK.
Thanks for everyone's help.
I seem to be able to select anything else in the list of USB devices, and I'm not sure what this entry refers to.
Unfortunately, in trying to figure this out I broke the original VM, so I've created a new VM from scratch. It's not fully configured yet, but as long as I can avoid the generic USB device, it seems to be functioning OK.
Thanks for everyone's help.
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Debian locks up when opening VM
Thanks for reporting back!
Pearl E Gates wrote:Specifically, there is one device listed as "Generic USB2.0-CRW [3960]". [...] I'm not sure what this entry refers to.
WinXP VIDA.vbox wrote:<DeviceFilter name="Generic USB2.0-CRW [3960]" active="true" vendorId="0bda" productId="0129" revision="3960" manufacturer="Generic" product="USB2.0-CRW" serialNumber="20100201396000000" remote="0"/>
The USB ID Repository (http://www.linux-usb.org/usb.ids) wrote:0bda Realtek Semiconductor Corp. 0129 RTS5129 Card Reader Controller