q35 with BIOS as that is the cluster default with >4.3. Running the dmesg messages through my mind as I remember them, the vio hardware may be all PCIe based, which would explain why this won't work on a virtual FX 440FX system, because those didn't have PCIe support AFAIK. Any special reason why you'd want them based on 440FX? And I also tested with GhostBSD, which is still 12.* based, and that doesn't seem to have vio support, at least I could not see a hard disk there, which confirms your observation there.
Seems strange. I want to use q35, but whenever I try even to start the installation (vm disk using virtio-scsi/virtio, net adapter using virtio) it always shows me the installer doesn’t detect any disk. I have an existing VM too that recently upgraded from 12.2 to 13. It uses i440FX with virtio-scsi disk and virtio network. If I try to change the machine into q35, it keeps stuck at boot after “promiscuous mode enabled”. Don’t know what’s wrong. Using oVirt 4.4.5. Can you share your VM Config ? From: Thomas Hoberg<mailto:thomas@hoberg.net> Sent: 20 April 2021 17:27 To: users@ovirt.org<mailto:users@ovirt.org> Subject: [ovirt-users] Re: FreeBSD 13 and virtio q35 with BIOS as that is the cluster default with >4.3. Running the dmesg messages through my mind as I remember them, the vio hardware may be all PCIe based, which would explain why this won't work on a virtual FX 440FX system, because those didn't have PCIe support AFAIK. Any special reason why you'd want them based on 440FX? And I also tested with GhostBSD, which is still 12.* based, and that doesn't seem to have vio support, at least I could not see a hard disk there, which confirms your observation there. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt... oVirt Code of Conduct: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt... List Archives: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi...
I tried again with a 440FX chipset and it still worked fine with VirtIO-SCSI and the virtual NIC. I also discovered the other reason I prefer VirtIO-SCSI, which is support for discard, always appreciated by SSDs. It would seem that the virtio family of storage and network adapters support both PCI and PCIe incarnations and whoever assembles the final KVM config does it right. Also cross-checked with FreeBSD 12.2 (instead of GhostBSD) and again the VirtIO-SCSI disk was not recognized, even if VirtIO support seems to have been added with FreeBSD 11. I'm afraid that I've exhausted my play-time budget with this, but since I used to be a fan of BSD (and still love pfSense) it was worth trying.
Sigh, please ignore my blabbering about PCI vs PCIe, it seems that the VirtIO adapters are all PCI not PCIe independant of the chipset chosen... In any case I posted the KVM xml configs generated via e-mail to the list and they should arrive here shortly.
participants (2)
-
Nur Imam Febrianto -
Thomas Hoberg