kire137 wrote:lgd wrote:As Voldedore said, this also work for me!
How can I add this kernel parameter? I haven't been able to find it.
Thanks a lot
ibt=off
]]>lgd wrote:Voldedore wrote:I was struggling with this for a while.
Adding
ibt=off
to the kernel parameter solved it (as pointed out in https://wiki.archlinux.org/title/VirtualBox).
As Voldedore said, this also work for me!
How can I add this kernel parameter? I haven't been able to find it.
Voldedore wrote:I was struggling with this for a while.
Adding
ibt=off
to the kernel parameter solved it (as pointed out in https://wiki.archlinux.org/title/VirtualBox).
As Voldedore said, this also work for me!
How can I add this kernel parameter? I haven't been able to find it.
]]>I was struggling with this for a while.
Adding
ibt=off
to the kernel parameter solved it (as pointed out in https://wiki.archlinux.org/title/VirtualBox).
As Voldedore said, this also work for me!
]]>First, increase the virtual and actual size of the windows.vdi file. While the virtual size can be increased in the VirtualBox settings, the actual size also has to be increased, and that has to be done from within the Windows VM. I had to remove the recovery partition, as explained here: https://hkdb.medium.com/resizing-virtua … 1c91744aee
My guess is that the actual size did not have enough space to accommodate the updates, even though the virtual size was large enough. Increasing both undid the 'logjam'?
Second, uninstalled all Windows updates already installed beginning November 2021 and later.
Rebooted and ran Windows update again. Still failed, but at least now had the space to place a copy of the windows 10 iso within the VM, mount it, and use it to repair the installation. That finally enabled Windows update to work correctly.
]]>Adding
ibt=off
to the kernel parameter solved it (as pointed out in https://wiki.archlinux.org/title/VirtualBox).
]]>I encountered exactly the same problem. For me it worked after switching to LTS Kernel (5.15.63-1-lts). This implies changing to dkms for the host modules.
Using dkms on the newer 5.19.3.arch1-1 kernel showed exactly the same 20% problem as with the pre-build host modules.
I cannot confirm this upgrade will resolve the issue. My Windows update stuck at 20% then failed after processing the above LTS and associated DKMS upgrade.
]]>Using dkms on the newer 5.19.3.arch1-1 kernel showed exactly the same 20% problem as with the pre-build host modules.
]]>I am not managing my VMs remotely, it was just a step in most of the guides I saw. I know that something has to happen in the kernal on boot to ensure that you can run a virtual machine
Be careful following guides blindly. It is important you understand what the guide is pointing to. And with Arch, it is important to start from the official documentation.
https://wiki.archlinux.org/title/VirtualBox
I know this is a common problem but I have tried all of the solutions I have found online and am still stuck. I will outline everything I have done below:
First I enabled the hardware virtualization extension from BIOS. Then I installed virtualbox and virtualbox guest:
$ sudo pacman -S virtualbox virtualbox-guest-iso -S
I picked the second option because my linux kernal is not the LTS one, similarly I chose
virtualbox-host-modules-arch
over the option for
virtualbox-host-dkms
Next I installed the appropriate linux headers:
sudo pacman -S linux-headers
My next step was to install the virtual box extension, I had some permission issues but I found a good solution here, which led me to run the following two commands:
LatestVirtualBoxVersion=$(wget -qO - https://download.virtualbox.org/virtualbox/LATEST-STABLE.TXT) && wget "https://download.virtualbox.org/virtualbox/${LatestVirtualBoxVersion}/Oracle_VM_VirtualBox_Extension_Pack-${LatestVirtualBoxVersion}.vbox-extpack"
sudo VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-${LatestVirtualBoxVersion}.vbox-extpack
I checked that the versions matched using:
$ VBoxManage list extpacks
Finally I started and enabled the vbox service to start on boot:
$ sudo systemctl enable vboxweb.service
$ sudo systemctl start vboxweb.service
Next I updated my grub config with:
grub-mkconfig -o /boot/grub/grub.cfg
After this I rebooted and downloaded the windows 11 iso. I followed the standard instructions for setting up a virtual machine but when I tried to start my windows 11 vm with windows 11 iso loaded, it would just pause at 20%, until I forced it to close. The log files show no error. I have posted the contents of them below:
00:00:00.716225 VirtualBox VM 6.1.36 r152435 linux.amd64 (Jul 21 2022 10:08:57) release log
00:00:00.716227 Log opened 2022-08-18T22:40:45.086818000Z
00:00:00.716227 Build Type: release
00:00:00.716228 OS Product: Linux
00:00:00.716228 OS Release: 5.19.2-arch1-1
00:00:00.716229 OS Version: #1 SMP PREEMPT_DYNAMIC Wed, 17 Aug 2022 13:48:51 +0000
00:00:00.716242 DMI Product Name: Lemur Pro
00:00:00.716245 DMI Product Version: lemp11
00:00:00.716248 Firmware type: UEFI
00:00:00.716253 Secure Boot: Disabled
00:00:00.716276 Host RAM: 23886MB (23.3GB) total, 22676MB (22.1GB) available
00:00:00.716277 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:00.716278 Process ID: 1734
00:00:00.716278 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.723074 Installed Extension Packs:
00:00:00.723078 Oracle VM VirtualBox Extension Pack (Version: 6.1.36 r152435; VRDE Module: VBoxVRDP)
00:00:00.723563 Console: Machine state changed to 'Starting'
00:00:00.723680 Qt version: 5.15.5
00:00:00.723686 X11 Window Manager code: 0
00:00:00.731868 SUP: seg #0: R 0x00000000 LB 0x0004d000
00:00:00.731884 SUP: seg #1: R X 0x0004d000 LB 0x00119000
00:00:00.731886 SUP: seg #2: R 0x00166000 LB 0x00060000
00:00:00.731888 SUP: seg #3: RW 0x001c6000 LB 0x000350a0
00:00:00.846548 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:00.879330 X Server details: vendor: The X.Org Foundation, release: 12201003, protocol version: 11.0, display string: :0
00:00:00.879364 Using known keycode mapping for keycode to scan code conversion
00:00:00.915086 GUI: Machine-window #0 activated
00:00:00.915171 GUI: Machine-view #0 focused, reason=3
00:00:00.916168 GUI: Machine-window #0 deactivated
00:00:00.916177 GUI: Releasing mouse on focus out
00:00:00.916225 GUI: Machine-view #0 unfocused, reason=3
00:00:00.924705 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 969x13 x 462x1024
00:00:00.928369 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 1447x13 x 460x1024
00:00:00.948712 GUI: Machine-window #0 activated
00:00:00.948742 GUI: Machine-view #0 focused, reason=3
00:00:02.667604 GUI: Machine-window #0 deactivated
00:00:02.667647 GUI: Releasing mouse on focus out
00:00:02.667866 GUI: Machine-view #0 unfocused, reason=3
00:12:15.424083 GUI: Machine-window #0 activated
00:12:15.424172 GUI: Machine-view #0 focused, reason=3
00:12:15.552358 GUI: Machine-window #0 deactivated
00:12:15.552405 GUI: Releasing mouse on focus out
00:12:15.553063 GUI: Machine-view #0 unfocused, reason=3
"VBox.log" 43L, 2626B
I am at a bit of a loss for how to proceed from here. Any thoughts?
]]>