@MrXeon So, the actual root issue here I believe, is opnsense installs come with an IP and dhcp server already assigned and enabled on the lan interface (I believe it's 192.168.1.1, but don't quote me). If your existing home network already uses 192.168.1.x/24 and already has a dhcp server, booting an opnsense install with it's virtual lan nic set to your existing home lan, there will be a lot of conflicts. Virtual nic order can be whatever you'd like (you can change and move around assignments in opnsense), but if it's preconfigured lan interface gets set to your preexisting lan network, there will be conflicts 🙂
Agreed, but the downside is to update the template from time to time. We'll probably create a new Packer plugin to work with XO API, so it will be easier to use and rely on 🙂 (Packer goal is to prep' a template from scratch and up to date for you, that you can use for solution 2. then)
@olivierlambert its looks like it was not from XCP but from the cloud provider managing it (Cloudstack). as soon as max restrictions were removed i could assign all 128 threads as vCPUs to a single VM.
This means: start with 1GiB (dynamic min is memory on boot basically). You can balloon up to 4GiB while running (by changing dynamic min to 4GiB), and go down again to 1GiB by set again dynamic min to 1GiB => dynamic is your "live" range.
You can change the dynamic max (while the VM is running) up to 5GiB.
Ballooning will change the amount dynamically (if needed) inside your 1GiB->4GiB range while live.
But frankly, stick with static memory in general (having dynamic min == dynamic max == static max), this will solve a lot of headaches.
@Andrew I’ve started to experiment with Duet + OpenCore chain loading but I'm getting the same results…
I’ve tested it now on two different Legacy Machines, so either I’m setting it up wrong or Duet is the issue all around the baord… why could Duet potentially not be happy?
It’s not my target system, it’s gotta be something to do with the file structure or the DuetPkg itself, I've also checked for Debug Logs from OpenCore, seems it ain't booting at all, so it's definitely an issue early on.