Success!
The cookie goes to Philip for the suggestion that the card wasn't working
in UEFI mode due to firmware.
I flashed a newer version of the firmware on the GPU. Repeating all steps
in my original post resulted in a successful installation and the GPU is
now successfully functioning on the G
On Mon, 25 Jul 2016 21:39:56 -0400
Steven Bell wrote:
> Hey Alex,
>
> I really appreciate all your help and your quick responses (and everyone
> else too, thanks!).
>
> I have found a Utility from MSI that will detect if there is an updated
> version of the my card's firmware, but it won't run
Hey Alex,
I really appreciate all your help and your quick responses (and everyone
else too, thanks!).
I have found a Utility from MSI that will detect if there is an updated
version of the my card's firmware, but it won't run on the VM (I assume
it's looking for some version bit for Win10_64bit
On Mon, 25 Jul 2016 20:15:15 -0400
Steven Bell wrote:
> So I tried a BIOS VM, freshly created from scratch. Reinstalled Windows 10
> and was able to get the NIC and USB passthrough working fine. When I
> removed the VNC Graphic device and Video Display, then add the NVIDIA card
> (graphics and au
So I tried a BIOS VM, freshly created from scratch. Reinstalled Windows 10
and was able to get the NIC and USB passthrough working fine. When I
removed the VNC Graphic device and Video Display, then add the NVIDIA card
(graphics and audio) the machine doesn't boot and needs to be forced off.
Even r
On 07/25/2016 04:29 PM, Steven Bell wrote:
On Mon, Jul 25, 2016 at 5:23 PM, Philip Abernethy wrote:
Did you make sure that the card actually supports UEFI mode?
Because my GTX 660 didn't. But the OS (Arch in my case) would
happily boot with the UEFI set to UEFI-only mode and the card would
silen
Interesting. I'll give the nvflash a try and post back my results.
On Mon, Jul 25, 2016 at 5:23 PM, Philip Abernethy
wrote:
> Did you make sure that the card actually supports UEFI mode? Because my
> GTX 660 didn't. But the OS (Arch in my case) would happily boot with the
> UEFI set to UEFI-only
Did you make sure that the card actually supports UEFI mode? Because my GTX
660 didn't. But the OS (Arch in my case) would happily boot with the UEFI
set to UEFI-only mode and the card would silently run in legacy mode. I had
to update the card's ROM. I used nvflash to check the card's UEFI
capabil
On Mon, 25 Jul 2016 17:11:13 -0400
Steven Bell wrote:
> Hi Alex,
>
> My original XML config created by virt-manager did not have any hyperv
> related options. There was no tag, nor was there a clock for
> hyperv.
>
> Why would these be missing? Since they aren't there and I still have a
> prob
Hi Alex,
My original XML config created by virt-manager did not have any hyperv
related options. There was no tag, nor was there a clock for
hyperv.
Why would these be missing? Since they aren't there and I still have a
problem, should I try adding them and setting the vendor_id value to
"Nvidia
On Mon, 25 Jul 2016 15:50:51 -0500
Jayme Howard wrote:
> I don't have an XML example handy, but you're missing the Nvidia workaround
> flags. In the CLI version, they look like the following:
>
> OPTS="$OPTS -cpu
> host,kvm=off,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=Nvidia
Hi Jayme,
Thanks for the reply! My QEMU version is 2.6.0-5.fc23. I'm pointed to the
Fedora virt-preview repo. I'd imagine that's why I've got 2.6 not 2.5.
I'll look into the hv_flags and see if I can't find the XML equivalent to
enable them. Will post my results.
On Mon, Jul 25, 2016 at 4:50 PM,
I don't have an XML example handy, but you're missing the Nvidia workaround
flags. In the CLI version, they look like the following:
OPTS="$OPTS -cpu
host,kvm=off,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=Nvidia43FIX"
All those hv_ flags are necessary to get around Nvidia's vi
Hello,
I am currently trying to setup a Windows 10 VM on a Fedora 23 host with
QEMU-KVM passing through a NIC, a USB controller, and a NVIDIA GPU (GTX
670). With my current setup, the NIC and USB Controller are both passed
through and function without issue. The GPU driver gives the message
"Windo
Hi,
it still sound to me like some qemu misconfiguration, it doesn't seem
normal that the VM pauses and then fast-forwards the paused time. (eg.
if you watch spinning circle that does 1spin/s, when doing IO heavy
stuff, it will hang the machine completely for eg. 10s, you can't even
move mouse or
15 matches
Mail list logo
