On 16/10/17 17:20, Paolo Bonzini wrote:
On 16/10/2017 16:42, David Hildenbrand wrote:
Hopefully this is the last bunch of fixes for the cleanup series.
1. log_start() was called before region_add(), which is wrong.
2. I messed up the calculation of the delta when aligning the ram address
(m
On 16/10/17 12:23, David Hildenbrand wrote:
On 04.10.2017 17:48, Laszlo Ersek wrote:
Hi,
On 09/21/17 16:28, Auger Eric wrote:
Hi David,
On 20/09/2017 16:34, David Hildenbrand wrote:
On 20.09.2017 16:31, Gerd Hoffmann wrote:
Hi,
Dropping from os section:
/usr/share/edk2.git/ovmf-x64/OVM
More noise... OK, so I've tested the Windows 10 guest VM using the same
criteria but eliminating PCI-E pass-through and using virtio-vga
graphics instead, and the the guest boots up fine so perhaps my
assumption is correct.
Let me know if you need to see the memory I/O regions or dmesg of my
host
Apologies, the title of this bug might be very misleading. I've made a
huge assumption that PCI-E GFX card pass-through was triggering the bug,
purely because a Debian Stretch guest VM on the same host, using the
same build of QEMU, which uses virtio-vga for graphics and the same
version of OVMF fi
I should probably add that I am using a recent OVMF firmware from this
repo: https://www.kraxel.org/repos/jenkins/edk2/ namely edk2.git-
ovmf-x64-0-20170914.b2974.g7f2f96f1a8.noarch.rpm dated 18/9/17
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
lspci -tv
-[:00]-+-00.0 Intel Corporation 4th Gen Core Processor DRAM Controller
+-01.0-[01]--+-00.0 NVIDIA Corporation GM204 [GeForce GTX 970]
|\-00.1 NVIDIA Corporation GM204 High Definition Audio
Controller
+-02.0 Intel Corporation Xeon E3-12
Public bug reported:
Problem:
Passthrough of a PCI-E Nvidia GTX 970 GFX card to a Windows 10 guest from a
Debian Stretch host fails after recent changes to kvm in QEMU master/trunk.
Before this recent commit, everything worked as expected.
QEMU Version:
Master/trunk pulled from github 4/10/17
On 21/04/16 16:41, Joe Clifford wrote:
On 21/04/16 15:17, Gerd Hoffmann wrote:
- When booting without the device attached, then running the device
manager to watch what happens, inserting the device results in it
appearing as normal for ~30-50 seconds before the device manager view
refreshes
On 21/04/16 15:17, Gerd Hoffmann wrote:
- When booting without the device attached, then running the device
manager to watch what happens, inserting the device results in it
appearing as normal for ~30-50 seconds before the device manager view
refreshes and the yellow warning triangle appears nex
On 21/04/16 07:44, Gerd Hoffmann wrote:
On Mi, 2016-04-20 at 22:13 +0100, Joe Clifford wrote:
Hi folks,
I'm not a coder by any stretch of the imagination so I don't have a
patch unfortunately however, this commit:
https://github.com/qemu/qemu/commit/5f77e06baa84323e5bbc96c2c7f4fe
Hi folks,
I'm not a coder by any stretch of the imagination so I don't have a
patch unfortunately however, this commit:
https://github.com/qemu/qemu/commit/5f77e06baa84323e5bbc96c2c7f4fe627078b210
causes the failure of the ICH9 Universal Host Controller - 2934 and the
attached "Microsoft Com
11 matches
Mail list logo
