All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Pfoh <pfoh@sec.in.tum.de>
To: kvm@vger.kernel.org
Subject: Re: pci pass-through on AMD architecture
Date: Wed, 05 Aug 2009 12:54:52 +0200	[thread overview]
Message-ID: <4A7964FC.3070703@sec.in.tum.de> (raw)
In-Reply-To: <4A7956C7.4030804@sec.in.tum.de>

Sry, prob informative to add that were running qemu-kvm-0.10.6 on a 
vanilla 2.6.30.4-0.1-default kernel.
-Jonas

Jonas Pfoh wrote:
> Hello,
> 
> I seem to be having some issues making the pci pass-through work from 
> the command line.  Interestingly, a hot-plug works (i.e., passing the 
> device through via the qemu console).  Any help would be appreciated.
> 
> Thanks,
> Jonas Pfoh
> 
> Below the attempt and error msgs:
> 
> # /usr/local/kvm/bin/qemu-system-x86_64 -m 2048 -hda 
> /srv/kvm/suseimg.img -vnc localhost:1 -pcidevice host=00:09.0 -net none
> create_userspace_phys_mem: Invalid argument
> assigned_dev_iomem_map: Error: create new mapping failed
> 
> 
> dmesg output:
> 
> ...
> pci-stub 0000:00:09.0: PCI INT A -> Link[LMAD] -> GSI 21 (level, low) -> 
> IRQ 21
> pci-stub 0000:00:09.0: irq 31 for MSI/MSI-X
> pci-stub 0000:00:09.0: PCI INT A disabled
> 
> 
> 
> /proc/cpuinfo (one of two identical procs):
> 
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 107
> model name      : AMD Athlon(tm) Dual Core Processor 5050e
> stepping        : 2
> cpu MHz         : 1000.000
> cache size      : 512 KB
> physical id     : 0
> siblings        : 2
> core id         : 0
> cpu cores       : 2
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
> mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext 
> fxsr_opt rdtscp lm 3dnowext 3dnow rep_good extd_apicid pni cx16 lahf_lm 
> cmp_legacy svm extapic cr8_legacy 3dnowprefetch
> bogomips        : 1999.98
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp tm stc 100mhzsteps
> 
> 
> lspci -v:
> 
> ...
> 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
>         Subsystem: nVidia Corporation Device cb84
>         Flags: 66MHz, fast devsel, IRQ 21
>         Memory at feaf5000 (32-bit, non-prefetchable) [size=4K]
>         I/O ports at b080 [size=8]
>         Memory at feafa000 (32-bit, non-prefetchable) [size=256]
>         Memory at feaf4c00 (32-bit, non-prefetchable) [size=16]
>         Capabilities: [44] Power Management version 2
>         Capabilities: [70] MSI-X: Enable- Mask- TabSize=8
>         Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ 
> Count=1/8 Enable-
>         Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
>         Kernel driver in use: pci-stub
>         Kernel modules: forcedeth
> ...
> 

      reply	other threads:[~2009-08-05 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  9:54 pci pass-through on AMD architecture Jonas Pfoh
2009-08-05 10:54 ` Jonas Pfoh [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=4A7964FC.3070703@sec.in.tum.de \
    --to=pfoh@sec.in.tum.de \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.