From: Jan Kiszka <jan.kiszka@web.de>
To: Erik Brakkee <erik@brakkee.org>
Cc: kvm@vger.kernel.org
Subject: Re: PCI passthrough on Sony Vaio F11 laptop...
Date: Sat, 13 Nov 2010 12:20:10 +0100 [thread overview]
Message-ID: <4CDE746A.2090701@web.de> (raw)
In-Reply-To: <4CDDCE40.9050001@brakkee.org>
[-- Attachment #1: Type: text/plain, Size: 6406 bytes --]
Am 13.11.2010 00:31, Erik Brakkee wrote:
> Hi all,
>
>
> I have KVM running successfully on opensuse 11.3 (64bit) with a opensuse
> 11.1 guest. I am using hardware virtualization and want to experiment
> with PCI passthrough with the (wired) network card on my laptop because
> I want to repeat similar steps later on a server (with a TV card). The
> main specs of the laptop are Intel Core I7 Q720 1.6GHz with 8MB of memory.
>
> I have followed the instructions on
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/chap-Virtualization-PCI_passthrough.html.
> Everything is successful until I start the domain.
>
> In that case I get the following messages in the logs:
>
> Nov 13 00:23:45 pelican kernel: [ 3302.793043] pci-stub 0000:04:00.0:
> claimed by stub
> Nov 13 00:23:45 pelican kernel: [ 3302.793197] pci-stub 0000:04:00.0:
> claimed by stub
> Nov 13 00:23:45 pelican kernel: [ 3302.931578]
> kvm_vm_ioctl_deassign_device: device hasn't been assigned before, so
> cannot be deassigned
> Nov 13 00:23:48 pelican libvirtd: 00:23:48.136: error :
> qemuMonitorOpenUnix:269 : monitor socket did not show up.: Connection
> refused
> Nov 13 00:23:48 pelican libvirtd: 00:23:48.136: error :
> qemuConnectMonitor:1192 : Failed to connect monitor for other
>
> To be absolutely certa CPU0 CPU1 CPU2
> CPU3 CPU4 CPU5 CPU6 CPU7
> 0: 371 0 0 203026 0
> 0 0 0 IO-APIC-edge timer
> 1: 12870 0 0 39 173
> 0 0 0 IO-APIC-edge i8042
> 7: 259 0 0 0 0
> 0 0 0 IO-APIC-edge
> 8: 0 0 0 4 0
> 0 0 0 IO-APIC-edge rtc0
> 9: 2823 0 0 141 0
> 0 0 0 IO-APIC-fasteoi acpi
> 12: 15 0 0 155 0
> 0 0 0 IO-APIC-edge i8042
> 16: 0 298817 0 0 0
> 0 634 0 IO-APIC-fasteoi ehci_hcd:usb1, ohci1394,
> hda_intel, nvidia
> 17: 0 0 0 0 0
> 0 0 0 IO-APIC-fasteoi mmc0
> 19: 0 0 0 0 0
> 0 0 0 IO-APIC-fasteoi mmc1
> 23: 0 0 99 0 0
> 95116 0 0 IO-APIC-fasteoi ehci_hcd:usb2
> 24: 687633 0 0 0 0
> 0 0 0 HPET_MSI-edge hpet2
> 25: 0 637204 0 0 0
> 0 0 0 HPET_MSI-edge hpet3
> 26: 0 0 199161 0 0
> 0 0 0 HPET_MSI-edge hpet4
> 27: 0 0 0 134606 0
> 0 0 0 HPET_MSI-edge hpet5
> 28: 0 0 0 0 237717
> 0 0 0 HPET_MSI-edge hpet6
> 34: 58784 0 0 7780 0
> 0 0 0 PCI-MSI-edge ahci
> 36: 939 0 0 0 138686
> 0 0 0 PCI-MSI-edge iwlagn
> 37: 0 0 0 0 0
> 210 0 0 PCI-MSI-edge hda_intel
> NMI: 0 0 0 0 0
> 0 0 0 Non-maskable interrupts
> LOC: 1535 1438 1347 1257 1168
> 396803 120435 79080 Local timer interrupts
> SPU: 0 0 0 0 0
> 0 0 0 Spurious interrupts
> PMI: 0 0 0 0 0
> 0 0 0 Performance monitoring interrupts
> PND: 0 0 0 0 0
> 0 0 0 Performance pending work
> RES: 4164 4332 2050 1413 3244
> 2790 1630 1200 Rescheduling interrupts
> CAL: 1394 1395 1279 1195 1431
> 1430 1429 575 Function call interrupts
> TLB: 5007 2623 3751 3045 5617
> 3902 4486 4115 TLB shootdowns
> TRM: 0 0 0 0 0
> 0 0 0 Thermal event interrupts
> THR: 0 0 0 0 0
> 0 0 0 Threshold APIC interrupts
> MCE: 0 0 0 0 0
> 0 0 0 Machine check exceptions
> MCP: 14 14 14 14 14
> 14 14 14 Machine check polls
> ERR: 259
> MIS: 0
> in I also removed the driver for the network card using 'rmmod sky2'.
>
> I have also specified the intel_iommu=on option in the command line (cat
> /proc/cmdline gives: root=/dev/system/root resume=/dev/system/swap
> splash=silent quiet nomodeset intel_iommu=on vga=0x314). Also, the
> output of 'dmesg | grep -i iommu' gives:
>
> [ 0.000000] Command line: root=/dev/system/root
> resume=/dev/system/swap splash=silent quiet nomodeset intel_iommu=on
> vga=0x314
> [ 0.000000] Kernel command line: root=/dev/system/root
> resume=/dev/system/swap splash=silent quiet nomodeset intel_iommu=on
> vga=0x314
> [ 0.000000] Intel-IOMMU: enabled
>
> So it seems that IOMMU is available.
>
> I read somewhere that there could be a problem in the interrupts and
> some users had success by disabling them but I really don't know how to
> debug this.
> The output of 'cat /proc/interrupts' is as follows:
What IRQ is the sky2 using when assigned to the host? Is it really a
shared IRQ (I bet not as it should be using MSI)?
Also, check in the libvirt logs what qemu-kvm reports on the console.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-11-13 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:31 PCI passthrough on Sony Vaio F11 laptop Erik Brakkee
2010-11-13 11:20 ` Jan Kiszka [this message]
2010-11-13 11:42 ` Erik Brakkee
2010-11-13 19:03 ` Jan Kiszka
2010-11-14 13:21 ` Erik Brakkee
2010-11-14 15:57 ` Jan Kiszka
[not found] ` <4CE1AC5E.4050604@brakkee.org>
2010-11-15 22:53 ` Jan Kiszka
2010-12-05 21:47 ` Erik Brakkee
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=4CDE746A.2090701@web.de \
--to=jan.kiszka@web.de \
--cc=erik@brakkee.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox