Replies: 5 comments 14 replies
-
|
In my testing using Virtual Manager the system starts up with the minimum configured of 1GB, so that looks good here. Technically, HAOS commes with VirtIO ballooning support, and the kernel module is loaded by default. So it really should work. Does ballooning in your Proxmox setup work with other Linux distribution? |
Beta Was this translation helpful? Give feedback.
-
|
To be honest, I haven't tried other Linux distributions, but can certainly try it for validation of how "it should work". |
Beta Was this translation helpful? Give feedback.
-
|
It seems that Virtual Manager doesn't support dynamic ballooning, but changing the current assignment at any point in time seems to work and apply to the system:
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting! I'll have to do some further testing in Proxmox. |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I've just installed my new Raspberry Pi 5, and as it's slightly overpowered to just run HomeAssistent I run an AlmaLinux 9 as a KVM base below. At first I gave HAOS 6 of 8GB of memory as I thought ballooning will prevent my memory to flow over (and Swap might clear the rest...). Or at least I can write some automations for that... I've tested with another VM running AlmaLinux 9 and setting current allocation limit works just fine. Given that, it seems the virtio ballooning driver is not included - or loaded - within the HAOS image. I'm using the Image haos_generic-aarch64-15.1.qcow2 . Am I missing a peace here, maybe using the wrong image? Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
What does |
Beta Was this translation helpful? Give feedback.
-
The XML generated by cockpit is this: HomeAssistent.xml<domain type='kvm' id='1'>
<name>HomeAssistent</name>
<uuid>6f7af8a7-c257-4526-b498-6aad78a50394</uuid>
<description>Home Assistant OS</description>
<metadata xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0" xmlns:cockpit_machines="https://github.com/cockpit-project/cockpit-machines">
<libosinfo:libosinfo>
<libosinfo:os id="http://libosinfo.org/linux/2022"/>
</libosinfo:libosinfo>
<cockpit_machines:data>
<cockpit_machines:has_install_phase>false</cockpit_machines:has_install_phase>
<cockpit_machines:install_source_type>disk_image</cockpit_machines:install_source_type>
<cockpit_machines:install_source>/var/lib/libvirt/images/haos_generic-aarch64-15.1.qcow2</cockpit_machines:install_source>
<cockpit_machines:os_variant>linux2022</cockpit_machines:os_variant>
</cockpit_machines:data>
</metadata>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>4</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os firmware='efi'>
<type arch='aarch64' machine='virt-rhel9.4.0'>hvm</type>
<firmware>
<feature enabled='no' name='enrolled-keys'/>
<feature enabled='no' name='secure-boot'/>
</firmware>
<loader readonly='yes' type='pflash' format='qcow2'>/usr/share/edk2/aarch64/QEMU_EFI-silent-pflash.qcow2</loader>
<nvram template='/usr/share/edk2/aarch64/vars-template-pflash.qcow2' templateFormat='qcow2' format='qcow2'>/var/lib/libvirt/qemu/nvram/HomeAssistent_VARS.qcow2</nvram>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<gic version='2'/>
</features>
<cpu mode='host-passthrough' check='none'>
<topology sockets='4' dies='1' clusters='1' cores='1' threads='1'/>
</cpu>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='volume' device='disk'>
<driver name='qemu' type='qcow2' discard='unmap'/>
<source pool='images' volume='haos_generic-aarch64-15.1.qcow2' index='2'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</disk>
<disk type='volume' device='disk'>
<driver name='qemu' type='qcow2' discard='unmap'/>
<source pool='images' volume='haos_data.qcow2' index='1'/>
<backingStore/>
<target dev='vdb' bus='virtio'/>
<alias name='virtio-disk1'/>
<address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
</disk>
<controller type='usb' index='0' model='qemu-xhci' ports='15'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x8'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x9'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0xa'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0xb'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='5' port='0xc'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0xd'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0xe'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
</controller>
<controller type='pci' index='8' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='8' port='0xf'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
</controller>
<controller type='pci' index='9' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='9' port='0x10'/>
<alias name='pci.9'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='10' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='10' port='0x11'/>
<alias name='pci.10'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='11' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='11' port='0x12'/>
<alias name='pci.11'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</controller>
<controller type='pci' index='12' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='12' port='0x13'/>
<alias name='pci.12'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
</controller>
<controller type='pci' index='13' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='13' port='0x14'/>
<alias name='pci.13'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
</controller>
<controller type='pci' index='14' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='14' port='0x15'/>
<alias name='pci.14'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
</controller>
<controller type='pci' index='15' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='15' port='0x16'/>
<alias name='pci.15'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
</controller>
<controller type='pci' index='16' model='pcie-to-pci-bridge'>
<model name='pcie-pci-bridge'/>
<alias name='pci.16'/>
<address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:36:c8:d5'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target type='system-serial' port='0'>
<model name='pl011'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/0'>
<source path='/dev/pts/0'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/run/libvirt/qemu/channel/1-HomeAssistent/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='keyboard' bus='usb'>
<alias name='input1'/>
<address type='usb' bus='0' port='2'/>
</input>
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0'/>
<alias name='tpm0'/>
</tpm>
<graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<audio id='1' type='none'/>
<video>
<model type='virtio' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
</video>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0x6015'/>
<address bus='1' device='2'/>
</source>
<alias name='hostdev0'/>
<address type='usb' bus='0' port='3'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x1b1f'/>
<product id='0xc020'/>
<address bus='3' device='3'/>
</source>
<alias name='hostdev1'/>
<address type='usb' bus='0' port='4'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x10c4'/>
<product id='0xea60'/>
<address bus='3' device='2'/>
</source>
<alias name='hostdev2'/>
<address type='usb' bus='0' port='5'/>
</hostdev>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</memballoon>
<rng model='virtio'>
<backend model='random'>/dev/urandom</backend>
<alias name='rng0'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</rng>
<vsock model='virtio'>
<cid auto='yes' address='3'/>
<alias name='vsock0'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</vsock>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c262,c371</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c262,c371</imagelabel>
</seclabel>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+107:+107</label>
<imagelabel>+107:+107</imagelabel>
</seclabel>
</domain>
Please note that I have not cleaned the output, you will still find my device passthrough configuration in it (ZigBee and Thread coordinator). I do also use 2 partitions, one for the OS named And as automated ballooning is, as far as i know, still not implemented I actually do not use it and haven't written a script that could trigger manual ballooning as necessary. I do still hope such an automatism will be added to linux as proxmox f.e. gets more popular. If someone knows about an automated approach I would be very happy to hear about it :) Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Probably a node red script to check current memory usage in HA, then triggering something outside to run a basic script with the correct command (I forget what it is but it works; and also can be done directly in virt-manager). In my case, I've only just moved esphome externally as this was the major stumbling block with some compiles bursting 4GB (from a baseline of 1.xGB); I'm also in the process of moving node-red out (was using about a gig) but it's a been a bit of a pain to recreate home assistant entities. I see you have roughly the same setup as mine including "linux 2022" but it's odd that mine had the correct memory lines already. I suppose in my case I may have clicked Generic Linux by accident or habit then. Yours is currently set at 4GB Max and 4GB allocated btw? I might pause my move for a bit to investigate the semi auto ballooning. I think proxmox does have auto memory ballooning though? Could be wrong, I've only just started researching this. But I'm quite sure I saw it does. Thanks for sharing! |
Beta Was this translation helpful? Give feedback.
-
|
Gladly. I already had same thoughts about scripting something and already found scripts written by others, see [1] for an example. But finally I deemed it to much work, especially maintaining such a script in the long run. My main fear is that multiple VMs start shifting memory between them selfs constantly. And I'm using HAOS as I know I will be to lazy to maintain HomeAssistent manually, therefore minimizing maintenance tasks is my goal. However, as you pushed this topic back in my mind I re-searched the topic and it seems that proxmox uses the features of libvirt [2] that implement an hassle free (hopefully) automation — others such as kubevirt do seem to use this feature as well. If someone is interested the relevant part of the XML schema should be this: Domain XML SchemaAnd I would really appreciate a format translation the the XML I can actually past into my VM configuration :) It also seems that these features are implemented for quite some time now, the patch for At first I had the "linux" variant not from 2022 and the older variant does not had the ballooning device, once I re-setup the VM with "linux 2022" ballooning worked out-of-the-box. Just the automated ballooning did not. Best regards, [1] https://blog.angrydev.net/using-virsh-and-systemd-to-automatically-size-ballooning-device-of-kvm-guest |
Beta Was this translation helpful? Give feedback.
-
|
It actually itched in my fingers to get ballooning running, so I figured the proper configuration out yesterday evening. <memballoon model='virtio' autodeflate='on' freePageReporting='on'>
<stats period='10'/>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</memballoon>From within HAOS I now see 6GiB of RAM (my [new] max configuration) and the ballooning driver consumes 2GiB to reach my current (minimum) memory assignment. I haven't checked the actual reconfiguration rate of the memory balloon (necessary statistics are generated every 10s, see Please note: All absolute values are for my setup, if yours is larger / different in any respect check your actual requirements and determine values as your setup needs them. Best regrads, |
Beta Was this translation helpful? Give feedback.
-
|
Woops I posted my earlier reply in a new comment. I suspect autodeflate has always worked; particularly when the host needs the resources. Having moved yet another service off the HA vm, and having disabled my node-red script temporarily, the ram visible to HA seems to have automatically dropped to about ~1GB. Manually increasing it to 1.1 and all the way up to 1.7, it still reports ram as 1GB. Allocating 1.9 results in HA reporting 2GB though. |
Beta Was this translation helpful? Give feedback.
-
|
Managed to get something working in Node-Red; though for performance and security reasons, it's probably best to recreate this as a shell script on the host and run it there. Nevertheless, I'm still testing how it works out. Some notes:
Node-red js nodes``` [{ "id": "6cc21fdecb4deef3", "type": "ssh-v3", "z": "6edd28544c3c6e49", "name": "", "conf": "ba6b74662ac26833", "debug": false, "x": 390, "y": 2600, "wires": [["fe59cc48dc519971"]] }, { "id": "cb76e37e78830a20", "type": "inject", "z": "6edd28544c3c6e49", "name": "", "props": [{ "p": "payload" }, { "p": "topic", "vt": "str" } ], "repeat": "17", "crontab": "", "once": false, "onceDelay": "10", "topic": "", "payload": "", "payloadType": "date", "x": 110, "y": 2580, "wires": [["3b518d35aa77f652"]] }, { "id": "08cbe2472ffaacc2", "type": "change", "z": "6edd28544c3c6e49", "name": "", "rules": [{ "t": "set", "p": "currentusage", "pt": "msg", "to": "payload", "tot": "msg" }, { "t": "set", "p": "payload", "pt": "msg", "to": "sudo virsh domstats --balloon linux2022", "tot": "str" } ], "action": "", "property": "", "from": "", "to": "", "reg": false, "x": 220, "y": 2660, "wires": [["6cc21fdecb4deef3"]] }, { "id": "fe59cc48dc519971", "type": "function", "z": "6edd28544c3c6e49", "name": "function 1", "func": "var current, max;\n\nmsg.session.stdout.forEach((cur) => {\n cur.split(/(\\s+)/).forEach((line) => {\n let regex = /balloon\\.(.+?)=(.+?)$/;\n let found = line.match(regex);\n if (found !== null && found[1] == \"current\") {\n current = found[2]; \n } else if (found !== null && found[1] == \"maximum\") {\n max = found[2]; \n }\n //msg.session.stdout.push(found)\n });\n});\nmsg.session = null;\n\nmsg.current = parseInt(current);\nmsg.max = parseInt(max);\n\nreturn msg;", "outputs": 1, "timeout": 0, "noerr": 0, "initialize": "", "finalize": "", "libs": [], "x": 540, "y": 2700, "wires": [["c630667fb2e40329"]] }, { "id": "3b518d35aa77f652", "type": "api-current-state", "z": "6edd28544c3c6e49", "name": "", "server": "ef06c680.510d68", "version": 3, "outputs": 1, "halt_if": "", "halt_if_type": "num", "halt_if_compare": "is", "entity_id": "sensor.system_monitor_memory_usage", "state_type": "str", "blockInputOverrides": true, "outputProperties": [{ "property": "payload", "propertyType": "msg", "value": "string", "valueType": "entityState" }, { "property": "data", "propertyType": "msg", "value": "", "valueType": "entity" } ], "for": "0", "forType": "num", "forUnits": "minutes", "override_topic": false, "state_location": "payload", "override_payload": "msg", "entity_location": "data", "override_data": "msg", "x": 280, "y": 2500, "wires": [["08cbe2472ffaacc2"]] }, { "id": "c630667fb2e40329", "type": "switch", "z": "6edd28544c3c6e49", "name": "Current Usage:\\n 1. < 70%\\n 2. > 90%", "property": "currentusage", "propertyType": "msg", "rules": [{ "t": "lt", "v": "70", "vt": "num" }, { "t": "gt", "v": "90", "vt": "num" } ], "checkall": "true", "repair": false, "outputs": 2, "x": 720, "y": 2720, "wires": [["dbf8cf6c7ef6718d"], ["f7ce5a417e064be7"]] }, { "id": "f7ce5a417e064be7", "type": "function", "z": "6edd28544c3c6e49", "name": "Increase Ram Allocation by <= 500,000KiB", "func": "var newAlloc;\n\nif ((msg.max - msg.current) > 500000) {\n newAlloc = msg.current + 500000;\n/*} else if (msg.max == msg.current) {\n //commented out because we might think to save the service call\n //but it's too troublesome for now.\n //So if already max, still set again with max\n*/\n} else {\n newAlloc = msg.max;\n}\n\n//also todo, to set domain name externally\n\nmsg.payload = `sudo virsh setmem --domain linux2022 --sizeHeavily considering moving to a docker and seeing how I can make up the loss of the addons/apps with HACs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Does anyone know if the HA OS VM build supports memory ballooning as described at the below link?
https://pmhahn.github.io/virtio-balloon/
I tried to set a minimum of 1GB and a max of 2GB, but the memory footprint always appears to be 2GB as reported in Proxmox. The actual memory utilized appears to only be about 835MB, so I'd have thought it would shrink to only 1GB.
It would be fantastic if this worked, so if anyone has attempted this and can share your experience, I would greatly appreciate it!
Thanks,
David
Beta Was this translation helpful? Give feedback.
All reactions