From: Joerg Roedel <joro@8bytes.org>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: IO_PAGE_FAULT while booting.
Date: Fri, 28 Jan 2011 16:44:43 +0100 [thread overview]
Message-ID: <20110128154443.GS6376@8bytes.org> (raw)
In-Reply-To: <AANLkTin0CYJrDAXRQ71oGpMKzjUBG5-27Y6f5F45oPWi@mail.gmail.com>
On Fri, Jan 28, 2011 at 03:31:17PM +0000, Prasad Joshi wrote:
>On Fri, Jan 28, 2011 at 3:15 PM, Joerg Roedel <joro@8bytes.org> wrote:
>
> On Thu, Jan 27, 2011 at 06:43:19PM +0000, Prasad Joshi wrote:
> > AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0002
> > address=0x00000000bb447000 flags=0x0000]
> > AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0002
> > address=0x00000000bb447040 flags=0x0000]
> > AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0002
> > address=0x00000000bb447080 flags=0x0000]
>
> Hard to tell whats going wrong here. How many memory have you given to
> the guest?
>
>I am allocating 1 GB memory to the VM
The address of the page-faults is around 3GB, so the guest sends DMA
commands to the GFX card which contains addresses outside its memory. I
Cc the list again, maybe they can bring some light into this issue.
In general GFX passthrough is not expected to work. But if it works for
you with -net none and doesn't without there must be another issue.
Joerg
>
>
> What type of GFX card do you try to pass through?
>
># lspci -vvv
>02:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B64 [FireGL
>V3100 (PCIE)] (rev 80) (prog-if 00 [VGA controller])
> Subsystem: ATI Technologies Inc Device 0102
> Interrupt: pin A routed to IRQ 32
> Region 0: Memory at c0000000 (32-bit, prefetchable) [size=128M]
> Region 1: I/O ports at a000 [size=256]
> Region 2: Memory at f9cf0000 (32-bit, non-prefetchable) [size=64K]
> Expansion ROM at f9cc0000 [disabled] [size=128K]
>
># dmidecode
>Handle 0x002E, DMI type 9, 17 bytes
>System Slot Information
> Designation: PCIEX16_2
> Type: 32-bit PCI Express
> Current Usage: In Use
> Length: Short
> ID: 27
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: ffff:02:00.0
>
>
>
> Joerg
prev parent reply other threads:[~2011-01-28 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 12:30 IO_PAGE_FAULT while booting Prasad Joshi
2011-01-17 14:03 ` Joerg Roedel
[not found] ` <AANLkTim+oRGAxxv43rrViCy3F8rWuGbPXBSqGBjA0hQT@mail.gmail.com>
2011-01-17 17:41 ` Joerg Roedel
2011-01-17 17:53 ` Joerg Roedel
[not found] ` <AANLkTik_qSfMBQ1q9VQTTnhWR1Qw4wyYkkwFMxdM=jzt@mail.gmail.com>
[not found] ` <20110128151522.GR6376@8bytes.org>
[not found] ` <AANLkTin0CYJrDAXRQ71oGpMKzjUBG5-27Y6f5F45oPWi@mail.gmail.com>
2011-01-28 15:44 ` Joerg Roedel [this message]
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=20110128154443.GS6376@8bytes.org \
--to=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=prasadjoshi124@gmail.com \
/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