-
-
Notifications
You must be signed in to change notification settings - Fork 2k
-
Hello. I'm curious why this project is using the i440fx machine type by default on (the scripts I've looked at so far).
According to docs, it does not support a lot of features. There's a larger discussion here about it as well.
RHEL 10 is now also saying that i440fx is deprecated.
In addition, using the q35 machine type provides additional benefits in comparison to i440fx, such as Advanced Host Controller Interface (AHCI) and virtual Input-output memory management unit (vIOMMU) emulation.
--
Am I crazy for thinking this should be the default on VM scripts?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment 2 replies
-
This is simply due to the downward compatibility of old hardware. Many users have old Dell or Lenovo servers, so there is a high risk that the VMS will not run properly. Q35 may require a little more configuration. It would be more conceivable to offer 2 variants; if one fails, the second variant should be used. But that makes the effort even greater for us
If necessary, a note from my own installation, I wanted to use q35 for my Homeassistant OS, no matter what I did, it no longer started properly. (Intel Ultra Processor)
Beta Was this translation helpful? Give feedback.
All reactions
-
Makes sense, and thanks for the feedback.
I'm not super clear on what the cutoff point is for 'old', but I imagine another Bash function could be used to identify those elements, and steer the default selection accordingly. But as you say that's more work and code.
a note from my own installation, I wanted to use q35 for my Homeassistant OS, no matter what I did, it no longer started properly
It sounds like you switched the architecture after the VM was created and built, which is effectively the same as a motherboard swap and from what I understand, will cause everything to break. You'd need to fully rebuild your machine for the proper drivers, etc.
Beta Was this translation helpful? Give feedback.
All reactions
-
nope, a full new install. now i managed the install, but nothing of the terminal works with haos.
You can try it here, if you found a solution, feel free to push it:
bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/haos-vm.sh)"
Beta Was this translation helpful? Give feedback.