I've run a M$ Windows VM under VirtualBox for seemingly decades. My nearly only reason was to continue using Quicken for family finances. Please, no comments about alternatives, that is for another discussion The latest incarnation, Win8 was on a Fedora 34 system. It It no longer boots completely to the Windows user interface so I decided to investigate Qemu/KVM for a new installation. The new install is on Fedora 36 and is Win10. I had copies of the Quicken data file on the Fedora disk, so installing Quicken on the new VM and importing the data file has me back up and running ... Almost. The only significant difference is the network interface. Under VBox the Windows VM had its own static LAN IP address. The VBox configuration called it a network (or ethernet) bridge. I don't recall ever creating the bridge so it was either Long ago or VBox did it for me. I would like the Win10, Qemu/KVM VM to also have its own static address, but it seems I have to create the bridge myself to do that. All the procedures I find for creating a bridge require 2 distinct network interfaces. Is it impossible to have a bridge with only one hardware interface. I expected something like an alias (an alternative IP address that the interface also responds to) could be used. -- Jon H. LaBadie jonfu@xxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
