Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-14 at 01:01 +0100, Maik Broemme wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote
Public bug reported:
When I use hv-time sub option and run CPU-Z or 3DMark (Physics Test) the
Windows 7 guest stops with BSOD (SYSTEM_SERVICE_EXCEPTION). It can be
easily reproduced by running CPU-Z. It will fail every second or third
time you execute CPU-Z and fail during PCI detection. If I
Forgot to mention. Used qemu version was 2.0.0.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1318746
Title:
qemu Windows 7 BSOD when using hv-time
Status in QEMU:
New
Bug description:
When
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-14 at 01:01 +0100, Maik Broemme wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-14 at 01:01 +0100, Maik Broemme wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-07 at 01:22 +0100, Maik Broemme
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-07 at 01:22 +0100, Maik Broemme wrote:
Interesting is the diff between 1st and 2nd boot, so if I do the lspci
prior to the booting. The only difference
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Thu, 2014-02-06 at 01:25 +0100, Maik Broemme wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Another minor issue is that the R9 290X is not reset
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2014-02-07 at 01:22 +0100, Maik Broemme wrote:
Interesting is the diff between 1st and 2nd boot, so if I do the lspci
prior to the booting. The only difference between 1st start and 2nd
start are:
--- 001-lspci
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Thu, 2014-02-06 at 01:25 +0100, Maik Broemme wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Another minor issue is that the R9 290X is not reset during
shutdown of
VM (neither Linux nor Windows
Hi,
currently VFIO with multi GPU passthrough is working partially and
hopefully somebody has a hint about the problem. I'm doing passthrough
of an AMD Radeon R9 290X and AMD Radeon 7870 GHz Edition to a single VM.
If the VM is running Linux this works quite well with radeon or fglrx
driver.
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Wed, 2014-02-05 at 19:59 +0100, Maik Broemme wrote:
Hi,
currently VFIO with multi GPU passthrough is working partially and
hopefully somebody has a hint about the problem. I'm doing passthrough
of an AMD Radeon R9 290X
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Wed, 2014-02-05 at 22:10 +0100, Maik Broemme wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Wed, 2014-02-05 at 19:59 +0100, Maik Broemme wrote:
Hi,
currently VFIO with multi GPU passthrough
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Another minor issue is that the R9 290X is not reset during shutdown
of
VM (neither Linux nor Windows) but it can be tricked with doing
suspend-to-ram between two starts. That's why I use '-no-reboot'
option
Hi,
Alex Williamson alex.william...@redhat.com wrote:
On Tue, 2013-05-28 at 20:45 +0200, Maik Broemme wrote:
Hi,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote
Hi,
Maik Broemme mbroe...@parallels.com wrote:
Here is the DEBUG_VFIO output:
vfio: vfio_initfn(:04:00.0) group 14
vfio: region_add 0 - afff [0x7f869800]
vfio: SKIPPING region_add fec0 - fec00fff
vfio: SKIPPING region_add fed0 - fed003ff
vfio
Hi,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
Good to hear. It looks like you have the same motherboard as my AMD
test system. An HD7850 in that system runs quite
Hi Alex,
Maik Broemme mbroe...@parallels.com wrote:
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
Good to hear. It looks like you have the same motherboard as my AMD
test system. An HD7850 in that system runs quite reliably with the
branches above although I do
Hi Alex,
Alex Williamson alex.william...@redhat.com wrote:
On Sun, 2013-05-19 at 23:26 +0400, Maik Broemme wrote:
Hi Knut,
Knut Omang kn...@ifi.uio.no wrote:
On Mon, 2013-05-13 at 16:23 -0600, Alex Williamson wrote:
On Mon, 2013-05-13 at 22:55 +0200, Knut Omang wrote:
Hi
Hi Knut,
Knut Omang kn...@ifi.uio.no wrote:
On Mon, 2013-05-13 at 16:23 -0600, Alex Williamson wrote:
On Mon, 2013-05-13 at 22:55 +0200, Knut Omang wrote:
Hi all,
Perfect timing from my perspective, thanks Alex!
I spent the better part of the weekend testing your branches on
Hi Alex,
and what's the problem with q35/pc + vfio-pci (no
x-vga). If vfio-pci is the direct replacement for pci-assign it must be a
bug in vfio, huh?
It's either a bug in vfio or the above configuration issue with the
pcieport. I'd appreciate if you could advise how you're configuring
20 matches
Mail list logo
