Search results

I've successfully built a Debian 9 host with Proxmox and ZFS. My understanding is that with the availability of resource sharing (e.g., "balloon" memory) it is common to overcommit resources. In other words, on a machine with 64GB, with several VMs running the same OS, I might be able to get...

Right now the VM is bridged to the physical NIC. I suppose I could buy an additional network card to passthrough, but last time I tried passthrough with Proxmox things got rather complicated. I managed to get passthrough working at the time, but if my current config remains stable and the load...

Turning off checksum offloading in pfSense seemed to work. If it helps to narrow the problem down, the host's adapter is an onboard Realtek 8168FB. So is KVM trying to pass through the hardware checksum offloading to the host's physical NIC, but failing in odd ways? Would putting in a genuine...

No, checksum offloading was enabled. I've turned it off. On my Proxmox host (actually full install of Debian 9 + Proxmox kernel & packages) uname -r reports: 4.15.18-7-pve So it looks like I'm on the latest kernel, but that pfSense option may be causing problems. I'm working remotely right now...

I recently set up pfSense in a Proxmox VM, and while it works as an OpenVPN endpoint, it has displayed a couple of odd issues when attempting to connect from the VM to the host (ie, to the Proxmox GUI.) When the VirtIO NIC is selected, I cannot connect to the Proxmox host (though, weirdly, I can...

Thanks, removing 'disk-images' seemed the most painless way to do it.

When creating a VM, Proxmox by default tries to put the disk image on my 'local' storage pool, which happens to be a very small SSD. I'd much rather have it default to my ZFS pool, but I haven't been able to figure this out. Any hints?

I am attempting to install a legacy Nvidia driver (version 340.102 for a Quadro FX 3800) on kernel version 4.13.4-1-pve and running into a brick wall. Installing the legacy driver per the Debian wiki produced no errors, so I ran the nvidia-xconfig utility and rebooted. However the driver did not...

I fixed this by disabling VGA pass through and booting the VM through the VNC console. The problem then magically sorted itself out when I re-enabled VGA pass through. I was able to install AC97 drivers in Windows, but I got much crackling and distortion. Like @Stewge I found the best option...

I've tried various experiments to improve the audio quality in my Windows 10 VM, but this seems to have killed it. USB pass through of keyboard and mouse stopped working when I enabled this option. Well, sort of. I can still use the passed through keyboard to navigate the EFI boot menu, but once...

Thanks. Just adding the EFI disk allowed the VM to boot, no need to change or save any settings.

That looks right to me assuming you want to keep the Proxmox console available. The one that works for me looks like: hostpci0: 22:00,pcie=1,x-vga=on You know if you're using Proxmox for serious use (ie, there's money involved) you might want to consider getting a support contract.

I think the top example is closer to the one you want. I'm a little confused. If you have x-vga=on, you should only be able to see the Windows desktop on a monitor attached to the GPU you're passing through. So are you viewing the Windows desktop from the Proxmox console, or on a seperate...

Sometimes if you wait a few minutes at the Proxmox logo, it'll drop to the UEFI shell. Good idea creating a new VM. IIRC, Win8 or later is required for UEFI booting. Also, I think you need balloon: 0 for GPU passthrough to work properly.

My OS was already installed, so I was able to select 'Misc UEFI Device' in the boot manager. Are you sure that a bootable ISO is selected in your VM settings/config file?

The audio distortion with significant I/O is worse than I thought. So no one has any idea how to get decent sound out of KVM? Audio is fine when there's no network I/O, but the cracks start to show when streaming video or downloading in the background. It's not the hardware, because ESXi can...

So try booting with the same settings that got you to the EFI shell, type 'exit' then select Boot Manager and try to boot with the CD/DVD ROM option. Hopefully that'll work...

I had the same problem after experimenting with ovmf and SeaBios. After you get to the EFI shell, type 'exit', then select 'Boot Manager'. From the Boot Manager select 'Misc UEFI Device'. Unfortunately, I have to do that every time I boot the VM with GPU passthrough. I'm working on a permanent...

I have created a VM with GPU passthrough. After a lot of experimentation, I finally got it working. However, there remains one weird consequence of changing so many VM settings. When I try to boot the VM, instead of booting the virtual disk, it boots up an EFI shell. If I quit the shell, select...

Well I found a functional, if not perfect, answer to my problem. The biggest problem was the OS. I was trying to get audio working with Windows Server 2012 R2. Once I switched to Windows 10, things became easier. After switching, I still had to enable Message Server Interrupts to prevent an...