qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: deniv@lavabit.com
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VFIO-VGA Issue
Date: Wed, 10 Apr 2013 16:32:07 -0400 (EDT)	[thread overview]
Message-ID: <58613.166.70.207.2.1365625927.squirrel@lavabit.com> (raw)
In-Reply-To: <1365618651.2918.88.camel@bling.home>

>> However, turning gfx_passthru off did
>> the trick. Win7 started loading with cirrus and switched to HD7750
>> halfway
>> through boot proccess. I didn't do any testing just let Windows
>> calculate
>> its score. The result was 7.4 and Aero was working.
>
> You should be able to do this with vfio too, use -vga cirrus and don't
> use the x-vga option on pci-assign.  The x-vga enables legacy VGA
> support for boot and primary console, as a secondary head normal PCI
> device assignment should be sufficient.
>
Oh, how I wish it was true! Trying to load with cirrus and vfio-pci
results in BSOD:
Attemp to reset the display driver and recover from timeout failed.

Trying the old pci-assign with kvm results in non-working GFX. Windows
shows code 10 and sometimes code 43 for the card.


P.S. I'm starting to go nuts because VGA assignment doesn't work. The
system was built with this sole intention. So, now I'm considering buying
another graphic card. Can you suggest any consumer card that is easy to
pass and can leave through vm resets? This HD7750 just hung the host when
I tried destroying Xen's VM and running it again.

  reply	other threads:[~2013-04-10 20:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 12:22 [Qemu-devel] VFIO-VGA Issue deniv
2013-04-09 17:18 ` Alex Williamson
2013-04-09 22:17   ` Alex Williamson
2013-04-10  9:01     ` Gleb Natapov
2013-04-10 15:20       ` Alex Williamson
2013-04-10 15:22         ` Gleb Natapov
2013-04-10 17:36         ` Paolo Bonzini
2013-04-09 22:33   ` deniv
2013-04-09 22:53     ` Alex Williamson
2013-04-10  0:02       ` deniv
2013-04-10 15:37         ` Alex Williamson
2013-04-10 17:11           ` deniv
2013-04-10 18:30             ` Alex Williamson
2013-04-10 20:32               ` deniv [this message]
2013-04-10 20:42                 ` Alex Williamson
2013-04-11 17:59                   ` deniv
2013-04-15 18:48                     ` Alex Williamson
2013-04-25 18:15                       ` deniv
     [not found]                       ` <517915C5.3020309@lavabit.com>
     [not found]                         ` <1366915789.2918.794.camel@bling.home>
2013-04-26 12:02                           ` deniv
  -- strict thread matches above, loose matches on Subject: below --
2013-05-16 20:46 Maik Broemme
2013-05-17 10:23 ` Paolo Bonzini
2013-05-20  3:10   ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58613.166.70.207.2.1365625927.squirrel@lavabit.com \
    --to=deniv@lavabit.com \
    --cc=alex.williamson@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).