qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: lejeczek <peljasz@yahoo.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] a user here - pci-assign
Date: Fri, 28 Sep 2012 13:48:36 -0600	[thread overview]
Message-ID: <1348861716.2320.379.camel@ul30vt.home> (raw)
In-Reply-To: <5065F072.6070504@yahoo.co.uk>

On Fri, 2012-09-28 at 19:46 +0100, lejeczek wrote:
> thanks Alex for your patience, appreciate it I do
> 
> what would be the droids I need?
> I'm experiencing guests' "puzzling" behavior and was 
> suggested that command line arguments were wrong/incomplete.
> 
> same box/hardware and radeon 5450 and ...
> - winXP-32bit -> OK - I assumed getting the guest on a 
> external computer monitor was an ultimate test
> - win7-64bit -> OS reports device as disabled cause the 
> device reported an error

I've had this same card working with both of these guests.  I believe
one trick on win7 was to use -cpu host.  Also, don't try to disable the
emulated vga device, just set it up like a dual-head system.  Once you
load the catalyst driver windows will switch to use the assigned device
exclusively.  I was using the new vfio assignment driver, but someone
else recently report it working with the existing driver as well.  The
5450 should be a secondary graphics card on the host system, trying to
assign the primary graphics is going to cause more problems.  Also
blacklist the radeon driver on the host, we don't need any leftover
state from the Linux driver causing problems since most of these
graphics cards don't support a reset mechanism.

> same box as above and geforce gt640 and ..
> for both XP and 7 report device with exclamation marks (thus 
> did not even bother to connect any screens like in working 
> case with XP & radeon)

I don't think we've seen any reports yet of Nvidia cards working,
there's another thread on the kvm list speculating at some of the
problems.

> I'll try to get hold of ROMs of the cards, meanwhile, how 
> can I troubleshoot it? how to get more verbose feedback and 
> what to specifically look for?

ROMs are only going to help if you're getting errors trying to read the
ROM.  Nvidia seems to have this problem, but I don't think radeons
typical do.  There's a #define in the code that can be enabled to get
more logging, but it's not terribly useful unless you know what you're
looking at.  VGA has plenty of issues with legacy PC address ranges that
are known problems, but there are also plenty of unknown problems that
make it a pretty difficult black box debugging project.  Thanks,

Alex

  reply	other threads:[~2012-09-28 19:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  9:54 [Qemu-devel] a user here - pci-assign lejeczek
2012-09-28 16:05 ` Alex Williamson
2012-09-28 18:46   ` lejeczek
2012-09-28 19:48     ` Alex Williamson [this message]
2012-10-01 11:10       ` lejeczek
2012-10-01 13:51         ` Alex Williamson
2012-10-02  7:46           ` lejeczek
2012-10-02 15:33             ` Michael Roth
2012-10-03 14:30               ` lejeczek
2012-10-03 14:46                 ` Alex Williamson
2012-11-06 13:17                   ` [Qemu-devel] a user here - pci-assign VGA lejeczek
2012-10-01 14:04         ` [Qemu-devel] a user here - pci-assign lejeczek

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=1348861716.2320.379.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=peljasz@yahoo.co.uk \
    --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).