So let me apologize in advance if this question is in the wrong place or there is a fix for it. I am at work and short on time so I wanted to post this before I got too snowed under.

I have a CENTOS 7 (up top date on patches and such) where I am running a KVM virtual host. I have two working guests... Windows 2012 RS Standard server and a Windows 10 workstation. All my physical boxes are Linux. Everything was working perfectly until I had an internet issue with my carrier (Xfinity) which caused a BIG problem with my wireless and even the hardwired network (CENTOS Server is hard-wired). Xfinity replaced the Router/Modem and now everything is working again... except my Windows 2012 RS Standard Server. It boots and it runs find.. the problem.. The NIC. I get a 169.X.X.X Microsoft your dead in the water IP. Now it can't be the DHCP server since all my servers have static IP addresses (this one was 10.0.0.202). It still has that IP in the settings but it looks like the NIC is not responding to the software or something else very screwy is going on. I have tried to even set it up on DHCP to no avail. Just weird. I think it could be something on the KVM side but I am not an expert on that software so I am clueless with it.

I get a 169.X.X.X is APIP automatic private ip assignment. MS put that in for a sort of safety net.

So, virtual machines have two basic ways to allow a client to access the wan. One is using a bridged connection to host. The second is a virtual router in the VM program. Every VM has it's own subnet. Yours being the standard QEMU/KVM subnet I suspect. Go from there.
https://www.linux-kvm.org/page/Networking

I will try that... Liked your quote!