When I get error 43, I generally just delete the video card (and the
virtual one) from the device manager a few times, rebooting in between.
Eventually it comes back just fine. It's definitely not ideal, but it's
worked for me so far.
On Sat, Jun 11, 2016 at 8:53 AM, David
mail.com>
>> wrote:
>>
>>> 2 things:
>>> - this msrs are not called from StarCraft on Win8.1.
>>> - i wonder if forcing virtual CPU model to something older will disable
>>> them in Win10.
>>>
>>> This msrs issue is what holds
ard games. It could very
> well be that this is used as some anti-tamper tool in these blizzard games,
> but I find it odd that it only does this in Win10 and that returning 0
> doesn't cause a problem.
>
> On Tue, Jun 14, 2016 at 12:06 PM Jayme Howard <g.pr...@gmail.com>
s it
> constantly keep calling the MSRS throughout the game?
>
> On Tue, Jun 14, 2016 at 8:55 AM thibaut noah <thibaut.n...@gmail.com>
> wrote:
>
>> They have the warden which is constantly checking your system
>>
>> 2016-06-14 14:36 GMT+02:00 Jayme
Truthfully, I don't know offhand. If you can tell me how to determine
that, I can check it out when I get home.
On Mon, Jun 13, 2016 at 4:44 PM, Abdulla Bubshait <darkst...@gmail.com>
wrote:
> What msrs does doom call?
>
> On Mon, Jun 13, 2016, 17:36 Jayme Howard <g.pr..
y outputs the ignored msrs to dmesg.
>
> On Mon, Jun 13, 2016, 17:45 Jayme Howard <g.pr...@gmail.com> wrote:
>
>> Truthfully, I don't know offhand. If you can tell me how to determine
>> that, I can check it out when I get home.
>>
>> On Mon, Jun 13, 2016 at 4:44 PM,
I've seen exactly the same behavior with DOOM. ignore_msrs fixed the
problem for me.
On Mon, Jun 13, 2016 at 4:35 PM, Brett Peckinpaugh
wrote:
> I wanted to see if anyone else has been able to play this on a VM. At
> this time it is the only one, and it forces a reboot. I
For what it's worth, I believe I was getting them on Overwatch as well.
It's not happening with EVERY game I have though.
On Mon, Jun 13, 2016 at 8:28 PM, Abdulla Bubshait <darkst...@gmail.com>
wrote:
>
>
> On Mon, Jun 13, 2016 at 6:27 PM, Jayme Howard <g.pr...@gmail.com&
Does the vendor ID need to be exactly 12 characters to work reliably? I
believe I've been using nvidia43fix as mine, and had unreliable results.
~75% of the time my VM boots with code 43.
On Fri, Jun 17, 2016 at 10:30 AM, Alex Williamson <
alex.l.william...@gmail.com> wrote:
> On Fri, Jun 17,
Possibly more appropriate to the spirit of another thread, but for what
it's worth Alex, I'm using both emulated graphics and an NVIDIA GTX 970
together, successfully. Not going to try to derail this further, just felt
that it's worth noting for anybody who catches this in the archive.
On Mon,
Okay wow, Alex. That made a huge difference immediately. That dropped me
from 90% to 33% on the main thread, and all the children are below 10%.
On Sun, Apr 3, 2016 at 8:07 PM, Alex Williamson wrote:
> If this is the issue I think it is, the unraid folks bisected
Alternately, if that doesn't help you, Razer's got a virtual surround app
that generates a virtual sound card. I use that as my default sound card
in the VM. That doesn't solve the problem if you're using the sound
directly on the host, though. I play through in-home streaming, and Steam
picks
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
Alright, this one I'm struggling to come up with an answer for.
Last night, I added a USB 3 PCI-E expansion card to my PC. Luckily, it
ended up in its own IOMMU group, so I passed it through to my VM with no
problems at all. For reference, I've got a USB device switch connected to
both the new
I've used both together, but I don't remember if one was mirroring the
other or if I did it as dual-monitor. It was a configuration I abandoned
early on. It DID work, but it caused (about 75% of the time) Nvidia code
43 issues for me. But it definitely did work outside of that.
On Wed, Jan 18,
le contiguous desktop across them? If yes then I'd
> guess that what you're asking is at least theoretically possible, though
> I've never tested personally.
>
> On Wed, Jan 18, 2017 at 12:19 PM, Jayme Howard <g.pr...@gmail.com> wrote:
>
>> I've used both together, but I
Solving the libvirt version issue is easy enough. Add
ppa:jacob/virtualisation and upgrade libvirt. He's got 2.1.0 in there,
along with updated versions of qemu and virt-manager.
On Tue, Sep 6, 2016 at 1:00 PM, Alex Williamson wrote:
> On Tue, Sep 6, 2016 at
I can confirm that GFE doesn't care if the CPU doesn't match what the
physical CPU offers in terms of cores. My i5-4670k is chugging along just
fine with 3 cores, as far as Windows knows.
On Tue, Oct 4, 2016 at 3:42 PM, Hristo Iliev wrote:
> Am 04.10.2016 18:32, schrieb Brett
Put the 960 into the one that goes 4x if you're that worried about it, but
it shouldn't be a huge deal. I don't know if the 960 can even saturate a
4x. It might be able to, but since it's a lower performance card anyway,
it shouldn't really matter.
On Fri, Oct 7, 2016 at 12:36 PM, Berillions
I'm doing exactly this with no significant problem. The way I handle it is
that I've got a script that binds the specific card to vfio-pci at runtime,
and I call that as a part of my startup script for the VM.
/usr/local/bin/vfio-bind
#!/bin/bash
modprobe vfio-pci
for dev in "$@"; do
I actually use the script. On a quick glance though
the patch looked solid to me, though I'm not a kernel dev.
On Tue, Oct 25, 2016 at 1:32 PM, Laszlo Ersek <ler...@redhat.com> wrote:
> On 10/25/16 16:30, Jayme Howard wrote:
> > I'm doing exactly this with no significant prob
I do exactly what you described as your original solution, though I've got
a USB switch inline as well, because my monitor doesn't have USB
passthrough.
On Sun, Mar 19, 2017 at 9:14 AM, Patrick O'Callaghan wrote:
> I have VFIO passthrough working with a Windows 10 VM, running on
Are you backgrounding qemu? If you just call it from the CLI, it won't
fork into the background and return the terminal to you. You could launch
it with "nohup &" and it should return the terminal to you.
On Mon, May 8, 2017 at 7:16 PM, Roman Mamedov wrote:
> On Mon, 8 May
23 matches
Mail list logo