What does lxc config show --expanded Windows10LTSC show you?
Note that this relies on the DHCP client using a MAC address as main identifier, if it’s using something else, then dnsmasq will not be able to match the static address to the client. Maybe there’s some way to configure your VM to this DHCP behavior.
I mainly need an IP set because my server doesnt have a GUI and I’m not trying to set one up if I don’t have to so I’m trying to remote in through a SSH tunnel but cant since there’s no IP to connect to.
Ok, that server is configured to boot from an ISO, the Windows installation environment doesn’t have networking support so configuring an IP won’t do you much good.
What you probably should do is run:
lxc config set core.https_address :8443
lxc config set core.trust_password some-password
And then on your client system (this assumes Ubuntu but this can be made to work with other Linux distros as well as Windows and macOS), you’d do:
This will make your desktop system talk to LXD on your server and using the LXD API will let you access the interactive graphical console so you can perform your installation and initial configuration.
So how could I go about doing this with a windows client? I have the virt-viewer client on Windows but cant access the VM unless I somehow connect to it which is why I tried using a SSH tunnel.
That’s assuming you can get chocolatey on your system, if not, considering you already have virt-viewer installed, just getting the LXD binary client for Windows from Github may be sufficient (it may depend on whether LXD manages to locate your current virt viewer install though).
Thank you I can finally see the Windows installation process. Once I install windows should I delete the ISO device and delete the iso? BTW I used choco and that worked perfectly.
Is there a way for me to change the resolution to 1080p instead of 800x600? Also the VM feels kinda slow, is there a way to increase how many cores it has or something?
You should set limits.cpu to the number of cores you want and limits.memory to at least 4GiB for a reasonable Windows experience.
For VGA, there currently aren’t native Windows drivers for virtio-vga, so you’re stuck with basic VGA. Usually I just do the install through the low res output and then switch to RDP for a proper desktop experience.
Distrobuilder doesn’t support Windows Server 2016. TBH we only considered Windows Server 2012 and Windows Server 2019. Anyway, I’ll fix that as there is no reason to exclude Windows Server 2016.