3

You will have to specify it like this: resource "libvirt_volume" "terraform-test" { name = "terraform-test.qcow2" pool = "default" source = "file:///var/lib/libvirt/images/base-image.qcow2" format = "qcow2" And remember that the Terraform will look for the image on the controller node (from ...


2

UPDATED ANSWER: as shown in the comments and the updated question, the specific issue was related to a 2 GB hardware memory reservation due to the specific machine type. Switching to an i440fx machine type solved the issue. ORIGINAL ANSWER (left here because it can help others with similar issues on 32 bit Windows): Try increasing the user-space memory ...


1

Libvirt provides a nss module which you can configure on the host, which uses the net-dhcp-leases information to provide host resolution https://libvirt.org/nss.html


1

Top line of the screenshot, and first line of the linked article. It requires an insider dev build of Windows. Mine was running the GA version. Enrolling in the insider program and downloading latest worked. All the settings in the screenshots are correct, and it should be bcdedit /set hypervisorlaunchtype auto. I got 400 KVM VM's launched from WSL on my ...


1

In addition to other answers about virt-sparsify: Temporary Folder virt-sparsify uses your /tmp folder to create/manipulate the new disk image before place it in destination folder. So, your / partition should have free space even if your volume file is in other partition. If you don't have enouth space, you can set a new temp folder with --tmp my_tmp_folder ...


1

Your DNAT rules are too generic. They attempt to forward all DNS traffic to your VM, rather than just what should apply to, DNS traffic originating from outside. Thus when your guest DNS server sends its own DNS queries, they get redirected back to itself. To fix the problem, also specify the interface on which incoming DNS traffic will arrive from the ...


1

Yes, that image is thin provisioned. It's qcow2, which only supports thin provisioning. You can tell, because the file claims to be 241G, yet only has 1.4G allocated. This file has a maximum capacity of 241G.


1

Try using the reset command. Its purpose is to reset the terminal to a sane state after it has gone haywire. The man page explains the specifics of how it reconfigures a terminal, if you need to get down into those weeds.


Only top voted, non community-wiki answers of a minimum length are eligible