Ideally, everything would use fe80:: internally, but it didn’t, and that was likely due to me mucking about with things. Additionally, the uncertainty of whether any connection will come as fe80:: vs my regular routable address was a pain (especially when my IPv6 network changed). While I have an IPv6 connection and IPv6 network, my router will stop advertising the IPv6 network if the Internet goes down, causing connectivity issues. However, that was becoming increasingly troublesome, unfortunately due to IPv6. My Gateway is 192.168.50.During my most recent server-build, I had to tackle exposing host-managed files to VMs. The IP addresses that are generated don't match my network. Can anyone help me get either of these solutions to work? I have been at this for three days and followed many guides one of which told me to install gdm which gave me a very broken GUI, that took a long time to fix because I didn't have terminal or SSH. I can't find a guide that works only through command line interface. I then tried an alternative, mounting a shared folder to the virtual machine. so I can't get it to show up on my network, I was hoping to use samba. If I go set up NAT, the virtual machine says the cable is unplugged.

I can use my Windows 10 Pro guest from the web interface, but I need it to save my DVR recordings to /Data/Tank/Plex/Playon. I installed the following packages to get virtual machines working: qemu qemu-kvm libvirt-daemon libvirt-clients bridge-utils virt-manager. I am using Ubuntu server and controlling it with cockpit.

Hi I am posting this because all of the guides I can find involve a GUI.

Qemu shared folder