boot failure upgrading to 25.03.b.20250306.0140 i
-
@patient0 It was the pen drive that was plugged into the USB, I was almost reinstalling everything, I tried a little more and it worked lol
That's what I selected in the boot menu, I know it worked but if I restart it won't work, I'll leave it like that and see later, I didn't even sleep today. It's 5:00am here and I get up to work at 6:30am lol
-
@stephenw10 Just for clarity this is an upgrade from 24.11 to the latest beta.
Didn't try the previous beta. -
@netblues Yes, I'm aware, it really was a problem, I always participate in betas but after restarting I had this problem.
-
Mmm, so just to review; if you change the disk type to something other than vitio block device (modern) it finds it and boots but still fails to find the virtio (modern) NICs?
-
@stephenw10 said in boot failure upgrading to 25.03.b.20250306.0140 i:
Mmm, so just to review; if you change the disk type to something other than vitio block device (modern) it finds it and boots but still fails to find the virtio (modern) NICs?
Yes, this is exactly the case.
If I change virtio ethernet to e1000, it also finds network interfaces.
-
@stephenw10 fiddling around I think I found the curlpit.
At some point kvm switched default emulated machine from i440fx to q35.
Latest supported os under latest kvm (or at least redhat supported) is freebsd14So if hypervisor defaults are
Then virtio drivers don't work under freebsd15
changing to
makes virtio work again.
The problem is that changing this with virsh edit isn't easy, since it also changes pci configuration.
The obvious way forward is creating a new freebsd 14 vm, with manual config.
Add interfaces as needed,
adjust vlans/passthrough/bridges and maybe mac addresses as need
and then move the disk subsystem to the new config with virsh edit.This allowed me to upgrade ce 2.7.2 to ce 2.8 without issues, and most probably it will also work
for plus,
I don't know if older chipset has any performance or other penalties, but pf used to work under this, and only changed to q35 recently.
I suspect freebsd15 dropped/changed something in virtio driver support. -
@netblues And also plus updated to 25.03 beta, with no issues. Dirty upgrade too.
-
Hmm, interesting. I tried usssing a Q35 machine in Proxmox and it booted fine. That in itself also didn't change the PCI device type either.
I think it must be changing the presented PCIe controller since it seems to fail to detect entirely any NICs or the drive controller. Still couldn't make Proxmox do it though even with a bunch of custom command hackery.
-
@stephenw10 actually pcie isn't supported in i440fx, you have to change this to pci
In older kvm implementations, creating a new freebsd13.1 would create a q35 based virtual machine.
Now if you create a new freebsd14 i440fx is selected.Proxmox isn't a redhat derivative as you know , too.
In any case, no issues in new installations. Upgrades will hurt "randomly" since this isn't really pfsense related. Its upstream freebsd
-
@netblues said in boot failure upgrading to 25.03.b.20250306.0140 i:
actually pcie isn't supported in i440fx,
Hmm, interesting. I wonder if my change didn't really apply somehow then.
