2016.06.21 19:50, rndbit wrote:
> I am again tinkering with my VM, trying to figure out why it is rather
> slow. And i noticed if i boot windows install straight on hardware
> process hacker displays interrupt delta ~4000 while running VM in qemu
> displays interrupt delta 8000+. Maybe any
I am again tinkering with my VM, trying to figure out why it is rather
slow. And i noticed if i boot windows install straight on hardware
process hacker displays interrupt delta ~4000 while running VM in qemu
displays interrupt delta 8000+. Maybe anyone have any clue what could be
causing this and
Check your DPC latency, it is one of causes for cracking sound. This is
exact reason i stopped using vga passthrough for gaming..
On 2016.06.09 10:07, Abdulla Bubshait wrote:
> I am not the only one who has this issue, but if you emulate an audio
> card you end up with occasional crackling audio o
I use emulated GPU for booting. Trick is to only use screen provided by
real GPU. Right-click desktop, go to "screen resolution", there you can
select to use only one display and which one is to be used. Then windows
will use emulated GPU for booting and switch to passed-through one after
boot.
On
> > "good dpc".
> >
> > I tested 3 modes:
> >
> > - all 8 core to vm without pinning: brutal dpc, did not tried to
> play games
> > on it. Only ungine valley => 2600 points
> > - 6 cores pinned to the vm + emulator on
It should be in qemu 2.5.
On 2016.01.11 19:31, Doug Applegate wrote:
> Hello,
>
> I recall someone mentioning that Alex had a patch to QEMU that avoids
> the need for disabling hypervisor enlightenments if you were using
> nVidia graphic cards.
>
> Is this in upstream QEMU, if it is has it been re
I dont think there is anything special you need to configure on qemu
side. Its just two pci devices passed-through. My guess is it should
work just fine.
On 2016.01.11 11:49, thibaut noah wrote:
> Hello guys, sorry to bother you with this silly question.
> Since i wanna to be able to play in 4k i
udo tee -a sys/cpuset.cpu_exclusive
> > /bin/echo 0 | sudo tee -a sys/cpuset.mem_exclusive
> > for T in `cat tasks`; do sudo bash -c "/bin/echo $T >
> sys/tasks">/dev/null
> > 2>&1 ; done
> > cd -
>
...@m-bauer.org>> wrote:
>
> I noticed that attaching a DVD-Drive from the host leads to HUGE
> delays. I had attached my /dev/sr0 to the guest and even without a
> DVD in the drive this was causing huge lag about once per second.
>
> Best regards
> M
I had same issue with "used" os. I ended up reinstalling windows.
On 2016.01.07 18:30, Eric Griffith wrote:
>
> Hey all
>
> First experiment with VFIO. I'm running
>
> Fedora 23 x64 with an Intel i7-6700k, and an R9 290. Host is booting
> with UEFI, guest is booting via UEFI. VT-D/VT-X/IOMMU are a
4000μs-16000μs here, its terrible.
Tried whats said on
https://lime-technology.com/forum/index.php?topic=43126.15
Its a bit better with this:
> 4
>
>
>
>
>
>
>
I tried /isolcpus/ but it did not yield visible benefits. /ndis.sys/ is
big offender here but i dont reall
I only half-managed to pass-though geforce 960m. got it to not display
any errors in device manager but it still did not work. However even if
you get it working ask yourself how you gonna use it. I am not aware of
laptop display being able to switch between graphics processors at will.
On 2015.12
back to virtio for my boot disk.
>
> Karsten
>
> 2015-12-28 9:40 GMT+01:00 rndbit :
>> I bumped into this strange issue - i can no longer boot windows guest
>> from VirtIO disk. Windows logo shows up briefly and then it throws
>> INACCESSIBLE_BOOT_DEVICE error. Switching d
I bumped into this strange issue - i can no longer boot windows guest
from VirtIO disk. Windows logo shows up briefly and then it throws
INACCESSIBLE_BOOT_DEVICE error. Switching disk to IDE works. Interesting
part is that i actually have installed virtio drivers and virtio disks
added after VM is
Oh this is something new. Could you explain what exactly replaces vfio-bind?
On 2015.12.16 15:38, Alex Williamson wrote:
> On Wed, Dec 16, 2015 at 1:34 AM, rndbit <mailto:rnd...@sysret.net>> wrote:
>
> Also i do not see it mentioned using vfio-bind shellscript to bind
>
Also i do not see it mentioned using vfio-bind shellscript to bind pci
device to be passed through to vfio driver. Also Roel try booting with
both emulated vga and passed-through card. Maybe it will yield some results.
On 2015.12.16 00:26, A de Beus wrote:
> I believe kernel 4.2.6 is broken. Use t
How about switching mouse? Or is it done at the same time when switching
keyboard as one would expect?
On 2015.12.14 18:44, thibaut noah wrote:
> So basically this remove the need for us to use synergy, how do we
> apply the patch to an existing config using libvirt?
>
> 2015-12-14 15:18 GMT+01:00
I updated my Win8.1 VM xml with changes i did not have from Hristo's
win10.xml. This is what i have discovered:
* 359.06 driver installer will not install driver claiming it can not
find nvidia GPU
* Installing driver from C:\NVIDIA via device manager's "update driver"
function works
* On boot nvi
Save xml to some location other than /etc/libvirt/.. and do all the
commenting/uncommenting there. virsh define /path/to/vm.xml to use
modified xml. You indeed are going the wrong direction. Even if libvirt
does not expose some functionality via xml it is also possible to pass
raw qemu flags. I nee
You can (even should) use intel hd graphics for host while
passing-through pci-e gpu.
Any CPU with virtualisation extensions (vt-x/vt-d) should work. Some
motherboards may not fully support all requirements for passthrough
though. To be sure of hardware compatibility you should look up what
hardwa
20 matches
Mail list logo
