since I realize it only cost memory, I decide to run some KVM on my machine. Probably need BIOS/UEFI setting As this new friend is writing about libvirt, I decide to give it another go. Turns out the wiki is describing way too complicated while it just fall down to

  • install the necessary pacages.
  • add the required user into the security group
  • voila - launch just like normal vm

However i find myself run into the problem of no network - NAT is scuffed on my machine. It might very well is because of my weird setup (no Dnsmasq, TUN device hijacking, route table mangling …)

Lets try with bridges - turns out it is easier than it looked. https://wiki.archlinux.org/title/Systemd-networkd#Bridge_interface … turns out its not as much the same when I’m running wireless. wlan0: Failed to set master interface: Device does not allow enslaving to a bridge. Operation not supported https://wiki.archlinux.org/title/Network_bridge#Wireless_interface_on_a_bridge hostapdis mentioned. I can’t seem to get assigned to my ip as well.

turns out to be there being some sort of binding of the ip by dnsmasq. I think it can only really be solved by restarting. a lot of interfaces happening.

After reboot the interface is down and there aren’t any options in virt-manager to start it. I have to find out in some reddit notes and do these

virsh net-define /etc/libvirt/qemu/networks/default.xml
virsh net-autostart default
virsh net-start default

And still getting the same error. I realize I should get the logs. as it keep repeating failed to create listening socket for 192.168.122.1: Address already in use when I def wasnt planning anything on it, i realize i set my dns service wrong…

changing bind [::]:53 -> bind 127.0.0.1:53 and restart - it works. caviat is that - proxy works straight up - feels very sweet

Now I have more issue with the kvm - the ssh connection persists, but the display now shows Display output not active.

disabling energyf saving options —

#Kvm #Windows