On 15 Nov 2018, at 06:59, A Z wrote:
>
> This is an issue that involves a combination of different software packages,
> so my apologies in advance if this is the wrong list to post on.
>
> I'm experiencing terrible boot times when I assign a large amount of RAM to a
> VM when used in
On 10.01.2018 19:33, taii...@gmx.com wrote:
I am looking for a low power fanless/low price graphics card that can
be assigned to a VM without trouble.
NVidia GT 730 - (relatively) cheap and fan-less. Tested with an OS X
guest. The only downside is that mine doesn't have a DP output.
I am
On 05.11.2017 00:53, Patrick O'Callaghan wrote:
On Sat, 2017-11-04 at 12:09 +, Ferdinand Pöll wrote:
> Is there some special magic to make this work, or is this a known bug
> in QEMU/KVM and I should just forget about it?
This sounds like a common problem which occurs when you are using a
Am 23.08.2017 04:41, schrieb taii...@gmx.com:
On 08/16/2017 08:29 AM, Hristo Iliev wrote:
Works with iommu=pt, though I believe it also worked without it (I'm
not
really sure why I added the iommu parameter). I still haven't tried
passing
the Xonar to the VM. The two devices appear
Am 15.08.2017 05:26, schrieb taii...@gmx.com:
On 08/14/2017 11:16 PM, Alex Williamson wrote:
On Mon, Aug 14, 2017 at 9:07 PM, taii...@gmx.com
wrote:
I am not sure but I think there are no pci-e audio cards that support
IOMMU AFAIK.
False, especially for device assignment,
I faced the same problem after the last Arch upgrade. Once the initial
frustration was gone, I simply disabled the Hyper-V features and,
honestly, see no difference in how the games I play perform. The Witcher
3 even seems to run a tad smoother, but it could also be due to a recent
GPU driver
Hi,
You could look up the MSR numbers in Intel's CPU manual. Those are most
likely the power control and frequency scaling registers. Should be safe
to ignore them.
Cheers,
Hristo
Am 15.03.2017 23:25, schrieb sL1pKn07 SpinFlo:
Hi
since, sincerely, idk, i get tons of this message in my
-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
--
Hristo Iliev
@h_iliev
http://hiliev.eu
"Computo ergo sum"
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
,
Hristo
On October 4, 2016 9:15:56 AM PDT, Hristo Iliev <hri...@hiliev.eu>
wrote:
Hi Martin,
Am 04.10.2016 10:09, schrieb Martin Schrodt:
Hi Hristo,
No need to sleep/wake - my X99-based system starts with TSC disabled:
$ dmesg | grep TSC
[ 0.00] tsc: Fast TSC calibration usi
Hi Martin,
Am 04.10.2016 10:09, schrieb Martin Schrodt:
Hi Hristo,
No need to sleep/wake - my X99-based system starts with TSC disabled:
$ dmesg | grep TSC
[0.00] tsc: Fast TSC calibration using PIT
[0.077986] TSC deadline timer enabled
[0.203383] TSC synchronization [CPU#0
Am 01.10.2016 22:07, schrieb Martin Schrodt:
Hi,
after
https://www.redhat.com/archives/vfio-users/2016-September/msg00114.html
was not sufficiently answered, resulting in me spending two more days
into finding a cure, I'm ready to give up. I'm about to switch to X99.
To do it, I need to be
Have you tried enabling MSI for the passed-through sound device as
described on Alex' blog here:
http://vfio.blogspot.de/2014/09/vfio-interrupts-and-how-to-coax-windows.html
This usually solves the problems with choppy audio.
Cheers,
Hristo
Am 30.09.2016 13:00, schrieb Jonathan Scruggs:
Hi
Am 05.08.2016 10:22, schrieb Rokas Kupstys:
Okay this is unexpected luck. After more tinkering i got it to work!
Here is my setup:
* AMD FX-8350 CPU + Sabertooth 990FX R2 motherboard
* :01:00.0 - gpu in first slot
* :06:00.0 - gpu in third slot
* UEFI on host and guest.
* Archlinux
On Tue, 12 Apr 2016 14:50:55 -0600 Will Marler wrote:
> "options kvm ignore_msrs=1"
>
> On the wiki page as it stands now there is a warning, "Silently ignoring
> unknown MSR accesses could potentially break other software within the VM
> or other VMs." I'm not clear on all of
On Tue, 19 Jan 2016 16:20:15 + Curlen M wrote:
> Current install is Arch with kernel 4.3.3
>
Hi,
Try using the linux-vfio-lts kernel from AUR. It is based on 4.1.x and
currently is the only kernel that works for me on my setup (same chipset, CPU,
and amount of memory as
On Tue, 1 Dec 2015 15:30:58 +0700 Okky Hendriansyah wrote:
> ...
> I just noticed that your platform is a Haswell-E but you’re using a
> patched kernel. Do you still need it? Have you tried using the plain
> linux-lts kernel?
>
Hi Okky,
Just to add another data point. My
16 matches
Mail list logo