Ok, after all these weeks I must say, I’m very disappointed of Leap 42.3.
Last time I used openSUSE was 3 years ago when it was still plain openSUSE; becoming Leap was supposed to bring more stability to everything in general, but it turned to be just as stable/unstable, or even only more unstable. Now laptop no longer boots.
First of all, I didn’t like how Yast “created the bridge device”:
Yast > System > Network settings > Summary tab
-------- fast ethernet --------- - no ip address – eth0 – slaved in br1
wireless network adapter – not configured --------------------------------
-------- passthrough ----------------------------------- br0 -----------------------
-------- passthrough ----------------- dhcp --------- br1 -----------------------
2 bridge devices instead of just one needed; worse, one faulty created -br0-. Seriously, WTH?
Second, exactly since the moment I enabled wicked for networking Connection settings in Virt-manager NEVER worked: it always makes GNOME crash, and some few times entire kernel. Going back to NetworkManager did not solve, only times it seemingly worked was when unplugging ethernet cable, and I’m not sure since my memory is not good to begin with…
Sometimes the bridged devices did appear in virt-installer’s 5th step, but when trying to create vm error ocurred: “the network device is already in use”
Later, there’s the fact of Suse/openSUSE virtualization docs being not quite good as in lacking information, just liek mentioned in previous threads of mine. Even though there’s the SPICE docs at spice-space website, it wouldn’t be excessive to have this matter covered in Suse docs, SPECIALLY when trying to correctly choose which paravirtualized drivers to use for Windows guests: either fedoraproject’s iso or spice-guest-tools. I think this is not a stupid question, but perhaps some do…
Also the lack of information about this realtively new macvtap driver, and when to use either this one or the common bridging schemes…
Now it’s too late. As I mentioned, now the piece of **** doesn’t boot anymore. Maybe all the attempts I did plus this issue Leap 42.3 shipped with all had to do…