-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incus & LXD Windows 11 VMs work on Ubuntu 22.04 with limits.memory=16GiB - But FAIL on Ubuntu 24.04 #883
Comments
Look for |
I'll try that today. Odd thing to me is on 24.04 limits.memory is the only config option that has a problem. For example, limits.cpu use works w any valid # of cpu. |
Initial Log for New copy of Incus Windows 11 VM $ incus info --show-log win11-test ========================================================================== $ incus config set win11-test limits.memory=16GB $ incus start win11-test ========================================================================== Once win11-base starts, it gets an IPv4 $ incus ls ========================================================================== 20-30 seconds later... "Watching" $ incus ls win11 ========================================================================== $ incus info --show-log win11-test $ incus info --show-log win11-test Log: Log is Empty ? ======================================================= $ next I set win11-test to include raw.qemu -cpu host $ incus config show win11-test
============================================================== Next, retarted win11-test VM After 60-90 seconds the Host itself freezes and has to be reset with the Power Button! NOTE BEFORE setting raw.qemu -cpu host the same Windows 11 VM would experience High CPU Also, strange to me is that after either with or without ** raw.qemu -cpu host** the win11-test VM And NO Log entries get written during all those events/time (see below)? $ incus info --show-log win11-test Name: win11-test Log: |
The fact that it messes things up to the point of needing a hardware reboot makes it sound like a potential kernel issue. Any chance you can try the kernel from https://github.com/zabbly/linux? That would get you a "clean" (no distro patches) Linux kernel, currently a 6.8.10. |
Stephane I installed the Zabbly kernel & rebooted. First tried just 4GB memory $ incus config set win11 limits.memory=4GB and the Windows 11 VM boots and gets an IPv6, then IPv4 *$ incus config set win11 limits.memory=8GB $ incus config set win11 limits.memory=16GB System starts, VM gets IPv6 & IPv4 then after Next... $ incus config set win11 raw.qemu -- "-cpu host -device intel-hda -device hda-duplex -audio spice" Start the incus Windows 11 VM with "-cpu host" and "limits.memory=16GB" $ incus ls BUT... again (and this is with the Zabbly Kernel) Its got to be something that is common the both Incus & LXD. If kernel caused
So summary so far... Using the same TAR file to create the new Windows 11 VMs on both Ubuntu 22.04 and Ubuntu 24.04 On Ubuntu 22.04 LTS On Ubuntu 24.04 On Ubuntu 24.04 (default 24.04 kernel) .... VM starts, gets ipv4/6 then high cpu then the Host itself freezes requiring Power Button. On Ubuntu 24.04 (Zabbly Kernel) Exact same results as with non-Zabbly Kernel. |
Wanted to give you an update on this issue with limits.memory Not sure what got fixed as I did 2 things on my Ubuntu 24.04 this morning:
Regardless, the problem with VM limits.memory=8GB is fixed somewhere. I'm running a Windows11 VM with limits.cpu=2 limits.memory=*GB And this system is not crashing/freezing any longer. |
HOST system
12 core
64GB ram
btrfs file systems
Boot off an Ubuntu 22.04 SSD
Ubuntu 22.04
Create a new LXD Windows 11 VM using a backup LXD Windows11 VM image tarball
Create a new Incus Windows 11 VM using the Same backup LXD Windows11 VM image tarball
Set Both LXD and Incus VMs config.memory to 8GiB
$ lxc config set lxdwin11 limits.memory=8GiB
$ incus config set incuswin11 limits.memory=8GiB
Start both the Incus and LXD Windows 11 VMs
BOTH work as expected !
Set Both LXD and Incus VMs config.memory to 16GiB
$ lxc config set lxdwin11 limits.memory=16GiB
$ incus config set incuswin11 limits.memory=16GiB
Start both the Incus and LXD Windows 11 VMs
BOTH work as expected !
Using same HOST system.
Boot off an Ubuntu 24.04 SSD
Ubuntu 24.04
Create a new LXD Windows 11 VM again using the same backup LXD Windows11 VM image tarball
Create a new Incus Windows 11 VM again using the same backup LXD Windows11 VM image tarball
Set Both LXD and Incus VMs config.memory to 8GiB
$ lxc config set lxdwin11 limits.memory=8GiB
$ incus config set incuswin11 limits.memory=8GiB
Start both the Incus and LXD Windows 11 VMs
BOTH work as expected !
Set Both LXD and Incus VMs config.memory to 16GiB
$ lxc config set lxdwin11 limits.memory=16GiB
$ incus config set incuswin11 limits.memory=16GiB
This is where FAILURE occurs with both LXD and Incus Windows 11 VMs
Start both the Incus and LXD Windows 11 VMs
**Both LXD and Incus Windows 11 VMs with 16GB memory:
Something with Ubuntu 24.04 has changed that prevents configuring an LXD or Incus Windows 11 VM
with limits.memory=16GiB while it works on Ubuntu 22.04.
The text was updated successfully, but these errors were encountered: