Hi,
I have some weird experience with audio on VM with windows with gpu
passthrough. I was using windows 10 with emulated hda sound drivers and
pulseaudio, and because I have some problems with sound distortions
(sound is cracking), I attached Geek Out v2 to VM, but this didn't
solved any problems
Awesome, thanks for the link.
On Sun, Feb 21, 2016 at 1:09 PM, wrote:
> For your quick question is there answer. I ask litle bit same in this
> thread.
> https://www.redhat.com/archives/vfio-users/2016-February/msg00033.html
>
>
> 2016-02-21 17:45 GMT+01:00 Nick Sarnie :
>
>> Hi Alex,
>>
>> Yea
For your quick question is there answer. I ask litle bit same in this
thread.
https://www.redhat.com/archives/vfio-users/2016-February/msg00033.html
2016-02-21 17:45 GMT+01:00 Nick Sarnie :
> Hi Alex,
>
> Yeah it seems you're right, the qemu command has "-device
> vfio-pci,host=01:00.0,id=hostd
I checked dmesg and there wasn't anything that stood out. There was a DRM
error message for nvidia but it wasn't critical. I'll look into this more
tomorrow. I have to go to sleep (I work at night). Thanks, Alex. I'll
let you know if and when the advice you and Ben have shared works.
On Sun,
On Sun, Feb 21, 2016 at 10:01 AM, Garland Key
wrote:
> It seems xorg crashed because the nvidia kernel module failed. Here's the
> xorg log file:
>
Did the intended device get bound to the nvidia module? Are there dmesg
errors? You could try creating a file like:
/etc/X11/xorg.conf.d/10-nvid
Thank you. I'll work on this again tomorrow after work. I really
appreciate your willingness to help and your patience. Once I have this
all setup, I going to update the arch wiki on this topic thoroughly -
including what to do if you have identical GPUs.
Best,
Garland
On Sun, Feb 21, 2016 at
Yes. You have no choice but to PCI stub both since pci stubs can only work
by device ID. So you need to PCI stub them, then vfio bind the guest card,
then nvidia bind the host card. You can probably set that up to happen on
launch using systemd but I currently just have a script that I launch
manua
Just to be sure I understand you correctly, you're suggesting that I pci
stub both of them and then bind one of them to nvidia after that, correct?
I just want to be clear that this is correct and that I'm using the correct
terminology so that I can research it further with the best results.
On Su
Did you pci stub them? If you pci stubbed both cards then then X obviously
won't launch since it has no active graphics device. The module is probably
failing because it has no card to bind to and X is set to launch using the
nvidia driver. If you bind one of the cards to nvidia, X will probably
la
I don't think a systemd module will make it work any better or worse - I
think it was just poor advice. Someone did recommend the following:
echo $bus-path > /sys/bus/pci/devices/${bus-path}/{un,}bind
echo $bus-path > /sys/bus/drivers/{nvidia,vfio-pci,pci-stub}/bind
Your thoughts?
On Sun, Feb 2
It seems xorg crashed because the nvidia kernel module failed. Here's the
xorg log file:
[10.474] (--) Log file renamed from "/var/log/Xorg.pid-1427.log" to
"/var/log/Xorg.0.log"
[10.474]
X.Org X Server 1.18.1
Release Date: 2016-02-08
[10.474] X Protocol Version 11, Revision 0
[10
Hi Alex,
Yeah it seems you're right, the qemu command has "-device
vfio-pci,host=01:00.0,id=hostdev2,bus=pci.0,addr=0x2", so it seems it is
using vfio-pci.Thanks for the information.
One more quick question: I'm using SeaBIOS for my VM. My GPU doesn't
support UEFI Secure/Fast booting. Can I use a
On Sun, Feb 21, 2016 at 9:06 AM, Nick Sarnie
wrote:
> Sorry, I'm not sure if I'm using legacy device assignment. My script is
> stop xdm, echo ":01:00.0" > /sys/bus/pci/drivers/radeon/unbind echo
> ":01:00.1" > /sys/bus/pci/drivers/radeon/unbind and then start xdm. I
> use virt-manager wi
On Sun, Feb 21, 2016 at 9:04 AM, Garland Key
wrote:
> Thanks Alex,
>
> I consider myself an intermediate power user. I know enough to understand
> what the line that you provided does, but not enough to write a solution of
> my own. I inserted the line that you provided above in
> /modprobe.d/vfi
Sorry, I'm not sure if I'm using legacy device assignment. My script is
stop xdm, echo ":01:00.0" > /sys/bus/pci/drivers/radeon/unbind echo
":01:00.1" > /sys/bus/pci/drivers/radeon/unbind and then start xdm. I
use virt-manager with libvirt, and I added the gpu to the VM with PCI Host
Device
Thanks Alex,
I consider myself an intermediate power user. I know enough to understand
what the line that you provided does, but not enough to write a solution of
my own. I inserted the line that you provided above in
/modprobe.d/vfio.conf and it caused X to fail. I had to alt+f2 to comment
it out
Actually i'm a few hours away to format my harddrive and install arch, it's
either that or i will throw that godamn computer by the window
2016-02-21 14:49 GMT+01:00 thibaut noah :
> Because i have no idea how to do that and where to start.
> Enable fedora repo allow me to update to this kernel b
Because i have no idea how to do that and where to start.
Enable fedora repo allow me to update to this kernel but i don't want to
update i want a kernel to patch so...
And i don't see any other way, this is not my area of expertise, i'm lost,
half of the things i bump into i don't understand
2016
El 21 feb. 2016 2:28 p. m., "thibaut noah"
escribió:
>
> I already cannot manage to patch my kernel, this is really unlikely that
i'll be able to create my own fedora package :/
>
> 2016-02-21 1:13 GMT+01:00 sL1pKn07 SpinFlo :
>>
>> 2016-02-21 0:52 GMT+01:00 thibaut noah :
>> > Okay thanks.
>> > H
I already cannot manage to patch my kernel, this is really unlikely that
i'll be able to create my own fedora package :/
2016-02-21 1:13 GMT+01:00 sL1pKn07 SpinFlo :
> 2016-02-21 0:52 GMT+01:00 thibaut noah :
> > Okay thanks.
> > How did you manage the update? I only have 4.3.5 on my update list,
20 matches
Mail list logo
