Re: Juniper vSRX

On Wed, Apr 29, 2026 at 3:22 PM Tom Smyth <[email protected]>
wrote:

> What kvm /qemu vm type are you using ? Q35 or i440bx
> Q35 would be more modern with support for pci-e sriov network interfaces
>
> Q35 is the way to go with the v25 images. They explode in weird ways
trying to mount the iso uzip images. I really dont get why.
I am going to have to accept that.

Juniper was telling me to use a v23 image that would only boot in BIOS
mode. I am going to say that what ever was done to FreeBSD 14
to get it to v23 has some super finicky boot requirements. That image would
exit into the bootloader at an ok prompt depending on how many
vcpus I had assigned. Entering "boot-junos" worked but I had no idea why
the forth boot loader was doing this. Its happy with 8 or more.

I am going to stick with junos-vsrx3-uefi-x86-64-25.4R1.12 , for now.

Now if I could only get all of this to work from bhyve and convince the
powers that be that bhyve is a good idea .....


> Id suggest playing around with cpu flags and the boot disk atachment ( ide
> sata ) scsi etc
> Try
>
> Kindest regards,
> Tom Smyth.
>
> On Wed 29 Apr 2026, 7:29 PM Mark Saad, <[email protected]> wrote:
>
>>
>>
>> On Wed, Apr 29, 2026 at 2:19 PM Marco Moock <[email protected]> wrote:
>>
>>> Am 29.04.26 um 19:52 schrieb Mark Saad:
>>> > I am super curious why Junos 24 and 25 fail to boot on KVM hosts were
>>> > the stock FreeBSD 14 and 15 work with out issues.
>>>
>>> FreeBSD is an on for general hardware, JunOS is designed to run on
>>> Juniper's devices. It is reasonable to to remove the support for
>>> anything else in the images they distribute. You should ask at a place
>>> for JunOS, e.g. https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>> --
>>> Gruß
>>> Marco
>>> Muell und Spam bitte an [email protected]
>>>
>>
>> Marco
>>   I'll check on the other lists too.  I wasn't trying to boot a real SRX
>> code on non Juniper hardware.
>> My problem is the Stock images from Juniper for virtual SRX firewalls are
>> super temperamental on what
>> hardware they will boot on. There isn't a lot of guidance on why or what
>> Juniper has changed . The Images
>> are designed to boot on x86_64 KVM hosts. They just don't always do that.
>>
>> --
>> mark saad | [email protected]
>>
>

-- 
mark saad | [email protected]