Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: Jan46 on 2021/07/27, 22:13:20
-
With the latest kernel updates 5.13.5-1-siduction-amd64 and 5.13.5-3-siduction-amd64 I cannot start Windows-10 in virtualbox.
When I reboot with kernel 5.12..17-1-siduction-amd64 there is no problem.
-
As allways, use a recent vbox release and it will work, even with the latest kernel.
-
I've installed virtualbox 6.1.24 from virtualbox.org to get the Win10-VM running.
-
Virtualbox should run on kernel 5.13.x
- if you use distributed Debian packages, with version 6.1.22-dfsg-2 since June 23 (see -> Debian changelog (https://metadata.ftp-master.debian.org/changelogs//contrib/v/virtualbox/virtualbox_6.1.22-dfsg-4_changelog) )
- if you use Oracle's packages, with version 6.1.24 since July 20 (see -> Oracle changelog (https://www.virtualbox.org/wiki/Changelog-6.1#v24) )
-
https://www.virtualbox.org/wiki/Changelog
The 6.1.24 has a bugfix for linux kernel 5.13. I found also a patch but I was not able to apply to compile it.
That release is not avalaible yet on Debian.
Seems that a kernel parameters fix the issue https://forums.opensuse.org/showthread.php/556271-VirtualBox-crash-(guru-meditation)-with-new-kernel-5-13-0?p=3048343#post3048343
-
... That release is not avalaible yet on Debian. ...
The Debian maintainers patched that already for 6.1.22-dfsg-2
virtualbox (6.1.22-dfsg-2) unstable; urgency=medium
[ Andrea Righi ]
* Support linux 5.13 with vbox-guest drivers (LP: #1929193):
- debian/patches/40-linux-5.13-support.patch
-- Gianfranco Costamagna <locutusofborg@debian.org> Wed, 23 Jun 2021 15:45:42 +0200
(well, at least "works for me", though)
-
I didn't saw that.
Anyway on my instance it wasn't working with the latest vbo version, I was getting a guru meditation error.
Added that kernel parameter, reboot and now is working.
-
Error by starting siduction 21.6.0 Xfce or other VM's.
I use the same solution as Mte90 and added kernel boot parameter "randomize_kstack_offset=off".
Error:Ein schwerwiegender Fehler ist aufgetreten, und die Ausführung der virtuellen Maschine wurde unterbrochen.
Zusätzliche Informationen zu diesem Fehler suchen Sie bitte in der Community-Sektion auf https://www.virtualbox.org bzw. handeln Sie gemäß Ihres Supportvertrages. Bitte geben Sie die Logdatei VBox.log, den Screenshot VBox.png, den Sie im Verzeichnis /home/<name>/VirtualBox VMs/siduction 21.6.0 Xfce/Logs finden können, sowie eine Beschreibung der Maßnahmen, die zu diesem Fehler führten, weiter. Sie können diese Dateien auch durch Auswahl von Zeige Log... im Menü Maschine des Hauptfensters finden.
Wählen Sie OK, wenn Sie die virtuelle Maschine beenden wollen. Wählen Sie Ignorieren, wenn Sie diese für Debugging offen lassen wollen. Zum Debuggen sind spezielle Kenntnisse und Tools notwendig, so dass die empfohlene Aktion hier OK ist.
LOG:
00:01:38.384895 VUSB: Detached 'HidMouse' from port 1 on RootHub#0
00:01:38.385374 VMSetError: /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:01:38.385386 VMSetError: Failed to reserve physical memory (0x4604 -> 0x4600; VMMDev Heap)
00:01:38.385554 VMSetError: /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:01:38.385556 VMSetError: Failed to reserve physical memory (0x4604 -> 0x4204; VMMDev)
00:01:38.385692
00:01:38.385693 !!R0-Assertion Failed!!
00:01:38.385693 Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf
00:01:38.385693 Location : /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT)
00:01:38.385698 ffffc9000a0bc000 <R3_STRING>: ffffffffffffffff != 00007f501c11e700; cLockers=-1 cNestings=1
...
00:01:38.410726 GIM: KVM: Resetting MSRs
00:01:38.411122 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:01:38.414362 Console: Machine state changed to 'PoweredOff'
00:01:39.022836 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:01:39.128794 GUI: UIMachineViewScale::resendSizeHint: Restoring guest size-hint for screen 0 to 1280x947
00:01:39.128825 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:01:39.128907 GUI: Aborting startup due to invalid machine state detected: 1
System: Host: sid6 Kernel: 5.13.6-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
Distro: siduction 15.1.0 Paint It Black - xfce - (201601171211) base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: ASUSTeK model: P8H67-M v: Rev X.0x serial: <superuser required> BIOS: American Megatrends
v: 3901 date: 09/12/2013
CPU: Info: Quad Core model: Intel Core i5-2500K bits: 64 type: MCP arch: Sandy Bridge rev: 7 L2 cache: 6 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27191
Speed: 3438 MHz min/max: 1600/3700 MHz Core speeds (MHz): 1: 3438 2: 1975 3: 1752 4: 1706
apt policy virtualbox
virtualbox:
Installiert: 6.1.22-dfsg-4
Installationskandidat: 6.1.22-dfsg-4
Versionstabelle:
*** 6.1.22-dfsg-4 500
500 http://httpredir.debian.org/debian unstable/contrib amd64 Packages
100 /var/lib/dpkg/status
-
here my XP VM did not start - virtualbox 6.1.22-dfsg-4
00:00:06.557425 ********************* End of statistics **********************
00:00:06.557957 AssertLogRel /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMR3/VMM.cpp(2333) int VMMR3CallR0Emt(PVM, PVMCPU, VMMR0OPERATION, uint64_t, PSUPVMMR0REQHDR): rc == VINF_SUCCESS || RT_FAILURE(rc)
00:00:06.557969 enmOperation=257 rc=VINF_PGM_SYNC_CR3
00:00:06.557990 VMSetError: /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_IPE_UNEXPECTED_INFO_STATUS
00:00:06.557992 VMSetError: Failed to reserve physical memory (0x8404 -> 0x8400; VMMDev Heap)
00:00:06.559457
00:00:06.559458 !!Assertion Failed!!
00:00:06.559458 Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf
00:00:06.559459 Location : /build/virtualbox-FinRt2/virtualbox-6.1.22-dfsg/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT)
00:00:06.559473 Stack :
00:00:06.559473 00007fb529413951 VBoxRT.so!RTAssertMsg2V+0x9f (rva:0x173951)
00:00:06.559474
00:00:06.559494 00007fb510132000 PGM: ffffffffffffffff != 00007fb4f9770700; cLockers=-1 cNestings=1
System: Host: siductionbox Kernel: 5.13.6-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 dm: LightDM 1.26.0 Distro: Debian GNU/Linux 11 (bullseye)
base: Debian GNU/Linux 11 (bullseye)
apt policy virtualbox
virtualbox:
Installiert: 6.1.22-dfsg-4
Installationskandidat: 6.1.22-dfsg-4
-
You might think about using the version directly from oracle. It has less problems and you can install it from the .run file. There is a howto on https://axebase.net/blog/2019/01/06/virtualbox-installation-ueber-run/. If there is a new kernel that is not yet supported you can switch to the testing-version that has this support earlier.
-
the newest version from this evening solved my problem.
[2021-07-29] Accepted virtualbox 6.1.26-dfsg-2 (source) into unstable
apt policy virtualbox
virtualbox:
Installiert: 6.1.26-dfsg-2
Installationskandidat: 6.1.26-dfsg-2
uname -r
5.13.6-1-siduction-amd64
-
Danke devil und jure.
After the update to virtualbox 6.1.26-dfsg-2 and a reboot (without the earlier used kernel boot parameter) I have no problems here to start my VM's.
-
Hi,
Yesterday i did the update and after that W 10 is working again with vbox.
Thanks for the support!
Jan
-
Regular updates are a must with siduction and other rolling releases.