latsclub.blogg.se

1. Virtualbox arch linux boots blank command prompt update#
2. Virtualbox arch linux boots blank command prompt iso#

Virtualbox arch linux boots blank command prompt update#

Something in the last kernel update has changed, or something in a recent Arch package update has changed. If it boots, then the updates inside the existing VM are giving trouble.Įxactly.

Virtualbox arch linux boots blank command prompt iso#

Please try making a new Arch VM, using the Arch ISO you originally used. The "failing" log does not look to me to show a failure. OS updates inside the VM can hose the OS or move the OS out of compliance with Virtualbox, but the OS's help features and channels must be used to fix the OS, same as if the problem happened on a real PC. Jack21 wrote:after updating my various VM's (some based on Arch, some on Debian), upon opening VB later to launch a given VM, it gets to GRUB, boots, and then stops about 1-2 seconds into the process and freezes. Can someone look at these and maybe clue me in as to what may be happening? As a side note, the fellows over at Arch forums gave me the usual snotty RTFM response, which of course was no help at all because I have read the Arch wiki and scoured the Internet in an attempt to solve this problem.Ĭomputer specs: Home built, Asus VII Crosshair x470, AMD Ryzen 7 3700x, AMD Radeon 580 GPU, 16MB DDR4 One is the zipped log of the failed Arch VM, and the other is the zipped log of a successful boot of a Debian VM. I'm attaching two log files to this post. There seems to be one or two things going on here: A problem between VB and the Linux kernel on the HOST machine, but also a problem with the Linux kernel on the GUEST machine as it relates the host. So I uninstalled VB 6.1.34 and again, installed version 6.1.36 but again no joy. A day or so later I noticed the same thing happening on my VB installation on Linux Mint. I chalked it up to a Fedora issue, then uninstalled VB 6.1.34 and installed 6.1.36 thinking that would solve it, but no joy. At first I noticed this failure of Arch-based VM's to open on my Fedora system. Two of these distros have VB installed: Fedora 36 (cinnamon) and Linux Mint 20.3 (cinnamon). On my desktop computer I have several different Linux distros installed to various dedicated SSD's.

This is not happening with my Debian or Debian-based VM's, only Arch based. At that point I am obligated to go to File > Power > Force to Close the close out the failed VM. A few days ago after updating my various VM's (some based on Arch, some on Debian), upon opening VB later to launch a given VM, it gets to GRUB, boots, and then stops about 1-2 seconds into the process and freezes. Arch_fail_to_ Arch VM boot fail (31.06 KiB) Downloaded 9 times