New answers tagged

1

Interesting. You do indeed have two IDE controllers defined, but both the virtual drives are using the first one. You should be able to safely remove the second IDE controller. Specifically this node should be deleted: <controller type='ide' index='1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </...


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


0

I suspect your problem is with hugepages, which you've explicitly asked KVM to use. -mem-path /dev/hugepages \ Do you actually have enough hugepages to give the VM the entire 4GB of RAM? I think you probably don't. Check with: # grep Huge /proc/meminfo AnonHugePages: 1325056 kB ShmemHugePages: 0 kB FileHugePages: 0 kB ...


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 ...


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

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 ...


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 ...


0

These are the things I do to get the best overall performance (and interactive performance!) out of a Windows VM: Use a virtual CPU type as close to the host CPU as possible. Ideally set host-passthrough if live migration is not required. Use the Virtio-SCSI controller and SCSI virtual hard disks (not Virtio or SATA virtual hard disks). This requires ...


0

Well, after couple of tries, I'm able to figure out an workaround. I followed the bridge way and that finally worked. I'm in a kind of impression, this is way better that leaving a port promiscuous, since that'll increase CPU overhead. In case someone followed through here, leaving the quick guide to setup the bridge: Create a bridge --> add the eth port ...


0

No, this message is not related. This warning message is reporting that the gust OS cannot access the PMU counters and should not be of any concern. The messages do not affect the functionality or performance of the operating system or the server and can be safely ignored.


1

Old topic, but I had the same problem today and I think the answer above is not the simplest solution: ssh root@node [root@node ~]# su kevin [kevin@node root]$ echo $XDG_RUNTIME_DIR /run/user/0 [kevin@node root]$ virsh capabilities error: failed to connect to the hypervisor error: Cannot create user runtime directory '/run/user/0/libvirt': Permission denied ...


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.


Top 50 recent answers are included