I had a similar problem as yours passing through a GTX980, ie after upgrading from 4.1 to 4.2, Win 10 does not detect audio device, ie
the speaker icon at bottom right of task bar shows a white cross on red circle.
GPU works fine. However, from Device Manager->Sound. video and game...
Thanks. Tried that still not able to get Windows 10 to offer up other screen resolutions.
Has anyone at all actually managed to get Window 10 VM to recognise there are more resolutions than 800x600 available ?
Thanks,
FXD
Ok thanks found it. However, I am starting to get BSOD on boot up now. Not sure if this is just Win10 specific or what.
I may have to try my luck with installing from scratch now and see how goes it.
BTW, with the disk changed to SCSI & controller as virtio, UEFI still fails to remember the...
HI Spirit,
Is there instruction on how this can be done for both disk and controller?
I was able to remove the disk, edit and change its disk type to scsi.
However, I think I am missing the part about virtio.
With only the disk type changed to scsi and re-added to VM when I start up VM, UEFI...
Dont
Figured it out grub file got over written to default!!!
Have to add back the following:
GRUB_CMDLINE_LINUX="quiet intel_iommu=on"
However, even after upgrading to 4.2, my other Windows 10 VM still don't have the ability to change screen resolution. :-(
I just did an upgrade from 4.1 to 4.2 with GPU pass-through working previously.
After upgrade, when I attempt starting the Windows 10 VM, I got the following error:
TASK ERROR: Cannot open iommu_group: No such file or directory
Anyone can help ?
Thanks,
FXD
Hi experts,
I've got a couple of Windows 10 VM installed on PVE 4.1.
The Display adapter driver is Microsoft Basic Display Adapter and as a result screen resolution is fixed
at 800x600 and no other option available.
On PVE VM Hardware->Display, I have tried:
Default
Standard VGA
VMWare...
Is there a 4.1 to 4.2 upgrade instruction somewhere?
Has anyone successfully upgraded a 4.1 with GPU pass-through and confirm it still works in 4.2?
Thanks
FXD
I have same issue and VM config looks like following. Boot order from GUI already set to virtio disk the first choice:
bios: ovmf
boot: cdn
bootdisk: virtio0
cores: 6
hostpci0: 03:00,pcie=1,x-vga=on
ide2: cdrom,media=cdrom
machine: q35
memory: 8192
name: WinTen
net0...
OK finally I've got the time to get this working. I switched the slots between GT610 & GTX980 so that GT610 is the last detected GPU and
as a result is used by the host.
However, with this set up on native Windows 10, GTX980 persistently getting error 43 which I have been trying to troubleshoot...
Hi experts,
I am starting MaaS installation under Proxmox 4.1-15 with the following:
VM1 running MaaS controller with 2 virtual NIC
eth0: Getting IP from a home router DHCP for external access
eth1: Managed by MaaS and running DHCP+DNS to serve other MaaS nodes/VM
VM2 starting up as normal...
HI Scomber, I read your post as by moving GPUs around different slots, you manage to get the intended GPU to be passed through, is that
correct?
Thanks,
FXD
No unfortunately I ran into some error running "make" but haven't got the time to investigate that further.
However, I did take a look at the vgaarb patch but again really unsure what it's meant to be fixing and as there is no configurable option or boot
switch that can be specified, I am...
Happy to report back that NVIDIA Graphics Driver 353.62 for GT610 manages to bring it back, recovering from boot up black screen ... Yay!
Now I can get back to part 2 of original attempt to get GTX980 to pass through.
Yup did that few times already. So I am being distracted to focus on downloading all older NVIDIA drivers and trying one at a time until I find the
working one :-( If/When I get the working one I will again share that back on this forum.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.