I have a same problem either, but my OS is Windows 7, if I mount GTX480
into VM and installed driver, I got same BSOD message (but error code is
0x3B)
And this message happening when using kvm=off, but I got Code 43 if I
remove it.
2015-12-12 8:28 GMT+08:00 Will Marler :
> Are you going from Win
On December 12, 2015 at 10:53:17, Eddie Yen (missile0...@gmail.com) wrote:
So maybe I can try this on my issue? According from Okky, can boot with Seabios
before, until change the platform to X99, Sesbios get blank screen only on
pass-through already card.
Hi Eddie,
Erik’s question is a differe
> Worked perfectly!
>Thx Okky
So maybe I can try this on my issue? According from Okky, can boot with
Seabios before, until change the platform to X99, Sesbios get blank screen
only on pass-through already card.
2015-12-12 11:43 GMT+08:00 Erik Adler :
> > Hi Erik,
> >
> > I've documented my exp
> Hi Erik,
>
> I've documented my experience upgrading my Windows 10 to "November Update"
> a.k.a. "Threshold 2" on the launch day here [1]. Can you please try that
> first?
>
> [1] https://www.redhat.com/archives/vfio-users/2015-November/msg00164.html
>
> Best regards,
> Okky Hendriansyah
Worke
> Are you going from Windows 7 to Windows 10? If so, then yes, I had the same
> problem.
I am upgrading from Windows 10 Pro build 10240 to the build 10586. The
is retail install so can use my key as many times as I want on my
“hardware”
> The secret in upgrading from to Windows 10 is switching t
> On Dec 12, 2015, at 07:14, Erik Adler wrote:
> ...
> Anybody else having issues with upgrading their Windows 10 to version
> 1511, 10586 ?
Hi Erik,
I've documented my experience upgrading my Windows 10 to "November Update"
a.k.a. "Threshold 2" on the launch day here [1]. Can you please try th
> On Dec 12, 2015, at 07:28, Will Marler wrote:
>
> Are you going from Windows 7 to Windows 10? If so, then yes, I had the same
> problem.
>
> I couldn't solve it.
>
> I was only doing it to get a licensed & activated version of Windows 10; I
> had a Windows 7 key. If that's your situation,
Are you going from Windows 7 to Windows 10? If so, then yes, I had the same
problem.
I couldn't solve it.
I was only doing it to get a licensed & activated version of Windows 10; I
had a Windows 7 key. If that's your situation, simply use the Windows 7 key
you have with a fresh installation of 10
Wondering if there is a known problem upgrading Windows 10 pro to
version 1511, 10586. After the upgrade at the reboot I am getting a
BSOD that says:
“SYSTEM THREAD EXCEPTION NOT HANDLED”
No information about what caused it is presented. Windows then boots
and gives a message
Upgrade failed reve
Oh, I'm sorry. Got that to the wrong thread.
Never mind.
Sorry again.
Philip Abernethy
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
What do you mean? Updates for my vm are made directly in the xml file, why
rebooting?
I tried adding it directly with :
But same result, vm boots but none of the usb port is forwarded, i'm
confuse, and libvirt documentation doesn't have an example on how to add a
specific usb port fro
Could it be you just made updates and forgot rebooting?
On Fri, 11 Dec 2015 18:27 thibaut noah wrote:
Not working, did i miss something?
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
added ad the end of my xml file (before the /domain)
Not working, did i miss something?
2015-12-11 12:06 GMT+01:00 thibaut noah :
> Thanks, i will try to do this in libvirt xml
>
> 2015-12-07 10:23 GMT+01:00 aldum :
>
>> I think you are looking for this:
>>
>> -usb -device usb-host,hostbus=2,h
Thanks, i will try to do this in libvirt xml
2015-12-07 10:23 GMT+01:00 aldum :
> I think you are looking for this:
>
> -usb -device usb-host,hostbus=2,hostaddr=3 \
> -usb -device usb-host,hostbus=2,hostaddr=4 \
>
> Here's the whole script I use at work:
> http://lpaste.net/2025817901793017856
>
I have a theory I am playing with now that it could be something to do with
the PCI id's of the parts of the card. On the host machine they are as
follows:
06:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX
690] (rev a1)
06:00.1 Audio device: NVIDIA Corporation GK104 HDMI Aud
It appears it was the memory, i set 1G too much, fedora is using 5Go?
On Fri, 11 Dec 2015 at 15:43, Bradley Davis
wrote:
> Have u tested your memory?
>
> On Fri, Dec 11, 2015 at 7:07 AM, thibaut noah
> wrote:
>
>> Hi, i cannot launch my guest anymore, i thought this was due to some
>> customizat
Have u tested your memory?
On Fri, Dec 11, 2015 at 7:07 AM, thibaut noah
wrote:
> Hi, i cannot launch my guest anymore, i thought this was due to some
> customization on the xml file so i removed every modification i made to get
> a clean file back but i cannot launch the vm anymore, tried using
Hi, i cannot launch my guest anymore, i thought this was due to some
customization on the xml file so i removed every modification i made to get
a clean file back but i cannot launch the vm anymore, tried using both
virsh and virt-manager.
How can i get a log of what is happening?
_
Hmm I am starting to think that this is not nVidia's monkeying with the
driver. I just tried installing driver 337.50 which I believe is from
before they "accidentally" added the bugs that cause us problems and I am
still getting Code 43.
With regards to the ignore_msrs option for KVM it has been
So already I botched the Nvidia driver update, I decided to just
reinstall OSX over the same qemu disk file and start from 10.11.1 again.
I hadn't really installed much so getting everything back to the way it
was wasn't going to be much of an issue.
Interestingly enough, once I had installed over
On December 9, 2015 at 04:50:18, Hristo Iliev (hri...@hiliev.eu) wrote:
...
With linux-vfio-lts I can reboot the host at any time and the VM always
boots ok afterwards, even if the host was running linux-lts and the VM was
hanging before the reboot. So, a more complete version of the above scenar
On Fri, 11 Dec 2015 08:08:41 +
Alan Jenkins wrote:
> Hey guys,
>
> I have spent the last 2 days experimenting trying to get my GTX690 passed
> through to a Windows 10 guest and since succeeding have been getting
> nothing but Code 43 errors.
>
> In Windows 10 I am currently using the latest
Hey guys,
Just had another go using the i440FX chipset and unfortunately get Code 43
again. Here is the XML I used on this occasion: http://pastebin.com/kgV4HcG4
.
In an attempt to prevent the driver seeing it was in a VM I installed it
from scratch using the passed through GPU and passed throug
Hi Okky,
Thanks for the very prompt reply. I was unaware that x-vga was not required
with OVMF so it has been in my XML on all attempts so far. I just tried
removing it from the XML and rebooting the VM but unfortunately the Code 43
still is present. I will now try to reinstall the drivers and reb
On December 11, 2015 at 15:09:41, Alan Jenkins (alan.james.jenk...@gmail.com)
wrote:
Hey guys,
...
My libvirt version is: 1.3.0-1.
My Tianocore uefi is from this RPM:
edk2.git-ovmf-x64-0-20151209.b1361.gfaec499.noarch.rpm
...
Hi Alan,
I noticed you have x-vga=on in your device but you’re using O
Hey guys,
I have spent the last 2 days experimenting trying to get my GTX690 passed
through to a Windows 10 guest and since succeeding have been getting
nothing but Code 43 errors.
In Windows 10 I am currently using the latest nVidia driver (359.06).
My libvirt xml is here http://pastebin.com/KY
26 matches
Mail list logo
