You are not logged in.
Hello,
I am a long time user of VirtualBox and, when I created a new virtual machine, I successfully loaded the live environment without any problem.
Recently I am seeing that I have to modify the kernel line of the ISO image adding nomodeset to the end, something that I never did before.
If I do not add this, the boot process freezes at a certain point.
Why now I need to add nomodeset?
These are my VirtualBox-related installed packages:
$ pacman -Ss virtualbox | grep -i installato
core/linux 6.6.3.arch1-1 [installato]
extra/virtualbox 7.0.12-1 [installato]
extra/virtualbox-guest-iso 7.0.12-1 [installato]
extra/virtualbox-host-modules-arch 7.0.12-8 [installato]
Also I installed virtualbox-ext-oracle via AUR.
Last edited by aldolat (2023-12-10 19:18:22)
Offline
how did you set the VM? graphics/chipset/ram?
Offline
Graphics: VMSVGA 128MB
Chipset: PIIX3
RAM: 4096 MB
Also, no TPM, no EFI.
Last edited by aldolat (2023-12-03 10:55:11)
Offline
I tried with same options, it didn't get stuck.
when does it freeze for you? (with error? or without error?)
Offline
Does the host run the same version of VBox as the guest ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Does the host run the same version of VBox as the guest ?
Do you mean the Guest Additions? Yes.
I have installed these packages:
virtualbox: 7.0.12-1
virtualbox-guest-iso: 7.0.12-1
virtualbox-host-modules-arch: 7.0.12-8
virtualbox-ext-oracle (from AUR): 7.0.12-1
when does it freeze for you? (with error? or without error?)
I made some tests and here are the results.
Without nomodeset
All (Arch, Fedora, and Tails) hang at boot - see screenshots below.
With nomodeset
Arch (installed) boots but no graphical.target (SDDM and KDE are installed)
Tails (live) boots but no graphical.target
Fedora (live) boots and reaches the graphical.target
Regarding the errors, here are the points where the boot process gets stuck:
Arch without nomodeset:
https://i.imgur.com/9ze64aV.png
Fedora without nomodeset:
https://i.imgur.com/manW17y.png
Tails without nomodeset:
https://i.imgur.com/QSORtq5.png
Tails gives me a feed back if I activate nomodeset:
https://i.imgur.com/1AHt6hV.png
Last edited by aldolat (2023-12-07 17:38:15)
Offline
Somehow this makes me wonder if the recent framebuffer changes (simpledrm) in archlinux kernel is involved.
What are the last version of the iso that works and the first were this fail happens ?
Also the kernel versions used on those isos and the kernel versions from fedora & tails
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
What are the last version of the iso that works and the first were this fail happens ?
I use VirtualBox mainly for testing purposes and very often I delete the virtualized machines.
At this moment I have only 4 machines created with the current ISOs.
But I can confirm that I have been creating machines and installations without any problem.
If you have a link to the old versions of the ISOs, I can make some tests.
Also the kernel versions used on those isos and the kernel versions from fedora & tails
Here the kernel versions of the current machines in my VirtualBox:
Arch: 6.6.3-arch1-1
Tails: kernel in ISO named "tails-amd64-5.20.iso"
Fedora: 6.5
Offline
If you have a link to the old versions of the ISOs, I can make some tests.
https://archive.archlinux.org/iso/ has all of them since archlinux was created.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I tried Arch Linux 2022.06.01 and 2020.06.01 but both hang at boot.
Below you can find the screenshots.
Now I think there is something wrong in my installation. But I have no idea.
archlinux-2022.06.01-x86_64.iso
https://i.imgur.com/3XWfiTZ.png
archlinux-2020.06.01-x86_64.iso
https://i.imgur.com/vfE7Ohx.png
Last edited by aldolat (2023-12-07 17:39:42)
Offline
Please stop posting large images, see https://wiki.archlinux.org/title/Genera … s_and_code .
There should be a .vbox file for every VM that contains the exact settings used in xml format.
Boot a VM without nomodeset , then boot it with nomodeset .
We need the the log of the boot without nomodeset.
Use a command like journalctl -b -1 | curl -F 'file=@-' 0x0.st (run as root) to upload the journal and post the link it shows after finishing upload.
Every Vbox VM should have a .vbox file which holds the exact settings used in xml-format.
Also post the .vbox file for that VM.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
We need the the log of the boot without nomodeset.
I can't post the log of journalctl because the VM (Arch, for example) hangs before reaching the login shell.
It hangs at "Triggering uevents", almost immediately after GRUB menu.
Offline
from post #6
With nomodeset
Arch (installed) boots but no graphical.target (SDDM and KDE are installed)
The screenshot for that VM booting without nomodeset shows it hang at "starting virtual console setup"
Do you still have that VM ?
If so , its journal should have info about previous boots without nomodeset.
https://wiki.archlinux.org/title/System … ing_output has details about how to get older parts of the journal.
Last edited by Lone_Wolf (2023-12-08 11:09:47)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I found that disabling the option Display > Screen > Extended Features > Enable 3D Acceleration every machine loads correctly.
In addition, removing nomodeset from GRUB of the guest machine, the graphic environment loads correctly, at full resolution.
So the culprit was "Enable 3D Acceleration". An option that I have always used for every machine in the past. But why now I cannot use it anymore?
Offline
If the hardware acceleration does not work as expected, try changing the Graphics Controller option found under the Screen tab in the Display options of the settings GUI. It seems that depending on the host GPU type, not all emulated controllers work equally well.
Try other graphics controllers in VBox .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
If I enable 3D acceleration, VB automatically switches to VMSVGA.
Offline
This is beginning to sound like a change in virtualbox, hopefully host logs have some info .
boot the host, start and exit the vm with nomodeset and 3d enabled.
start and exit (or kill) the same vm without adding nomodeset.
After you've done that
journalctl -b | curl -F 'file=@-' 0x0.st
Run the above command as root (or with root rights) on the host and post the link it shows on the commandline .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Here is the link: https://0x0.st/H3_s.txt
Thank you for your patience.
Offline
Your I3 3220 should have an integrated intel videocard, is that disabled ?
dic 09 23:16:24 zen kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts)
Looks like you are using https://aur.archlinux.org/packages/nvidia-390xx-dkms ?
dic 09 23:17:41 zen kernel: ------------[ cut here ]------------
dic 09 23:17:41 zen kernel: WARNING: CPU: 1 PID: 1745 at /build/virtualbox-host-modules-arch/src/vboxhost/7.0.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:564 rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
dic 09 23:17:41 zen kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic crct10dif_pclmul crc32_pclmul ledtrig_audio snd_hda_codec_hdmi polyval_clmulni snd_hda_intel polyval_generic snd_intel_dspcfg ses gf128mul iTCO_wdt snd_intel_sdw_acpi at24 ghash_clmulni_intel mei_hdcp enclosure snd_hda_codec mei_pxp intel_pmc_bxt scsi_transport_sas iTCO_vendor_support snd_hda_core cryptd sha512_ssse3 sha256_ssse3 pktcdvd sha1_ssse3 mousedev joydev snd_hwdep r8169 rapl realtek snd_pcm i2c_i801 intel_cstate intel_uncore mdio_devres snd_timer i2c_smbus pcspkr libphy mei_me snd mei soundcore lpc_ich mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) i2c_dev sg crypto_user loop fuse dm_mod nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 crc32c_intel uas sr_mod usbhid cdrom usb_storage xhci_pci xhci_pci_renesas nvidia_drm(POE) nvidia_uvm(POE)
dic 09 23:17:41 zen kernel: nvidia_modeset(POE) nvidia(POE) video wmi ipmi_devintf ipmi_msghandler
It's clearly related to the videocard / driver, but there are mentions of invalid operation in the crash info .
dic 09 23:17:41 zen kernel: ? exc_invalid_op+0x17/0x70
dic 09 23:17:41 zen kernel: ? asm_exc_invalid_op+0x1a/0x20
Try linux-lts ?
Last edited by Lone_Wolf (2023-12-11 09:25:04)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Your I3 3220 should have an integrated intel videocard, is that disabled ?
No. My BIOS gives the following choice: Auto, IGD (Integrated Graphics Device), PEG (PCI Express Graphics).
It always has been set to Auto.
Looks like you are using https://aur.archlinux.org/packages/nvidia-390xx-dkms ?
Yes, I confirm.
It's clearly related to the videocard / driver, but there are only mentions of invalid operation in the crash info .
[snip]
Try linux-lts ?
I tested my machines without 3D acceleration, and I am seeing that this option can stay deactivated for my purposes.
Indeed my PC is really outdated, especially the video card, but for now it's enough for my needs.
I can consider this post resolved.
Really, really thank you for your kind help and time.
Last edited by aldolat (2023-12-10 19:19:02)
Offline