Thanks for looking into this and sharing your findings here!found the problem:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg971771.html
Qemu changed the default SMBIOS version to 3.0 with 64 Bit, which breaks all Juniper products as they set the system information in SMBIOS at boot.
This would be one option, but it still would not be fully ideal, as I also think that it would be a bit nicer if this could be improved in either SMBIOS settings (for better compat with 32 bit) or Juniper vSRX in setting up the entry point for 64 bit SMBIOS too, if the VM afterwards runs as 64 bit anyway. Because both SMBIOS entry points can coexist, so setting them both up would be the nicest thing to do from an OS POV to ensure any firmware upgrade doesn't break boot.Could you maybe add a switch in the webinterface to change the SMBIOS to 32 bit?
Oh and actually, you can work around this by pinning the machine-type to 8.0, which can be done through the web interface already, and we do pin it for more finicky and fragile OS like Windows already by default.
Would be great if you could test that, i.e., drop your
args
override and pin the machine to 8.0 instead and see if that also works.If that works, and a fresh vSRX, directly installed under machine version 8.1, works too, I think we might avoid adding that extra flag.
Last edited: