From: Jean Baptiste Favre <xen-devel@jbfavre.org>
To: xen-devel@lists.xensource.com
Subject: Re: PCI passthrough issue
Date: Thu, 27 Jan 2011 22:47:26 +0100 [thread overview]
Message-ID: <4D41E7EE.4060502@jbfavre.org> (raw)
In-Reply-To: <20110127202755.GA4194@dumpdata.com>
Hello Konrad,
Le 27/01/2011 21:27, Konrad Rzeszutek Wilk a écrit :
> On Sat, Jan 22, 2011 at 11:22:59AM +0100, Jean Baptiste Favre wrote:
>> Hello,
>> Last investigations show that I've the latest BIOS version for my
>> motherboard.
>> Do you need more tests, if yes which ones ?
>
> I tried it on my 2.6.32.27 (32-bit and 64-bit) and I am not seeing
> the failures you have. These are the devices I passed in:
>
> 00:00.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> 00:00.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> 00:00.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> 00:00.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> 00:01.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
> 00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
> 00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
> 00:03.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>
> Granted the kernel I am using a jeremy/xen/stable-2.6.32.x so not sure
> how divergent from Debian or Debian Squeeze it is.
>
> How are you launching your guest? Do you something like this:
>
> kernel="/mnt/lab/2.6.32.27/vmlinuz"
> ramdisk="/mnt/lab/2.6.32.27/initramfs.cpio.gz"
> extra="console=hvc0 debug test=crashme iommu=soft"
> memory=1024
> maxmem=2048
> vcpus=4
> on_crash="preserve"
> pci= ["00:1d.0","00:1d.1","00:1d.2","00:1d.7","0a:00.1","0000:06:01.1","0000:06:01.0", "09:00.0"]
> vif = [ 'mac=00:0f:4b:00:00:68, bridge=switch' ]
Here is my domU config file:
####################
kernel = '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem'
ramdisk = '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem'
builder = 'linux'
memory = '256'
memory = '512'
vcpus = '1'
cpus = '2'
localtime = 0
serial = 'pty'
disk = [ 'drbd:xps-106,xvda,w' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = "root=/dev/mapper/xps--106-root ro iommu=soft swiotlb=force
console=hvc0 xencons=tty"
pci = [ '04:00.0' ]
name = 'xps-106'
hostname = 'xps-106.clichy.jbfavre.org'
####################
As I privately told you, I made the tests you suggested and the result
is that problem occurs with 256mb of memory, but is solved with 512mb or
more.
Basically, what I find surprising is that with 256mb of memory, the max
size for incoming packets to be blocked is 128 bytes.
Makes me think about an unsigned integer or something like that, but I
don't have enough kernel knowledge to be more precise.
Regards,
JB
next prev parent reply other threads:[~2011-01-27 21:47 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:38 PCI passthrough issue Jean Baptiste Favre
2011-01-12 15:43 ` Konrad Rzeszutek Wilk
2011-01-12 15:53 ` Jean Baptiste Favre
2011-01-12 16:09 ` Jean Baptiste Favre
2011-01-12 16:36 ` Konrad Rzeszutek Wilk
2011-01-12 16:56 ` Jean Baptiste Favre
2011-01-12 17:26 ` Konrad Rzeszutek Wilk
2011-01-12 17:44 ` Jean Baptiste Favre
2011-01-12 18:32 ` Konrad Rzeszutek Wilk
2011-01-12 20:07 ` Jean Baptiste Favre
2011-01-12 21:40 ` Konrad Rzeszutek Wilk
2011-01-12 21:46 ` Jean Baptiste Favre
2011-01-12 22:18 ` Jean Baptiste Favre
2011-01-13 11:28 ` Jean Baptiste Favre
2011-01-13 19:18 ` Jean Baptiste Favre
2011-01-13 20:19 ` Konrad Rzeszutek Wilk
2011-01-13 20:44 ` Jean Baptiste Favre
2011-01-14 14:53 ` Konrad Rzeszutek Wilk
2011-01-14 23:29 ` Jean Baptiste Favre
2011-01-17 8:59 ` Jean Baptiste Favre
2011-01-17 13:58 ` Jean Baptiste Favre
2011-01-22 10:22 ` Jean Baptiste Favre
2011-01-27 20:27 ` Konrad Rzeszutek Wilk
2011-01-27 21:47 ` Jean Baptiste Favre [this message]
2011-01-28 15:47 ` Jean Baptiste Favre
2011-02-01 11:34 ` Ian Campbell
2011-02-01 12:17 ` Jean Baptiste Favre
2011-02-01 13:20 ` Ian Campbell
2011-02-01 14:12 ` Jean Baptiste Favre
2011-02-01 14:18 ` Ian Campbell
2011-02-01 15:14 ` Jean Baptiste Favre
2011-02-01 15:38 ` Jean Baptiste Favre
2011-02-01 16:23 ` Ian Campbell
2011-02-01 19:37 ` Konrad Rzeszutek Wilk
2011-02-01 22:06 ` Jean Baptiste Favre
2011-02-02 9:12 ` Ian Campbell
2011-02-01 23:01 ` Jean Baptiste Favre
2011-02-02 9:44 ` Ian Campbell
2011-02-02 15:38 ` Konrad Rzeszutek Wilk
2011-02-02 15:55 ` Ian Campbell
2011-02-02 15:56 ` Jean Baptiste Favre
2011-02-01 22:04 ` Jean Baptiste Favre
2011-02-02 9:27 ` Ian Campbell
2011-02-02 10:24 ` Jean Baptiste Favre
2011-02-02 10:59 ` Ian Campbell
2011-02-02 11:33 ` Jean Baptiste Favre
2011-02-02 17:42 ` Konrad Rzeszutek Wilk
2011-02-04 8:43 ` Jean Baptiste Favre
2011-02-04 8:53 ` Ian Campbell
2011-02-04 8:54 ` Jean Baptiste Favre
2011-02-04 10:12 ` Jean Baptiste Favre
2011-02-04 11:04 ` Ian Campbell
2011-02-04 11:25 ` Jean Baptiste Favre
2011-02-04 11:28 ` Ian Campbell
2011-02-04 13:15 ` Jean Baptiste Favre
2011-02-04 13:50 ` Ian Campbell
2011-02-04 14:01 ` Jean Baptiste Favre
2011-02-09 9:59 ` Jean Baptiste Favre
2011-02-18 21:14 ` Jean Baptiste Favre
2011-02-25 14:40 ` Konrad Rzeszutek Wilk
2011-02-28 10:00 ` Jean Baptiste Favre
2011-02-28 12:18 ` Jean Baptiste Favre
2011-02-28 15:01 ` Konrad Rzeszutek Wilk
2011-02-28 15:17 ` Jean Baptiste Favre
[not found] ` <4D6CB851.40103@jbfavre.org>
2011-03-03 22:12 ` Konrad Rzeszutek Wilk
2011-03-03 22:47 ` Jean Baptiste Favre
2011-03-03 22:58 ` Konrad Rzeszutek Wilk
2011-03-04 7:25 ` Jean Baptiste Favre
2011-03-16 3:14 ` Konrad Rzeszutek Wilk
2011-03-25 13:06 ` Jean Baptiste Favre
2011-02-01 15:38 ` Ian Campbell
2011-02-01 16:16 ` Jean Baptiste Favre
2011-01-12 21:44 ` Jean Baptiste Favre
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=4D41E7EE.4060502@jbfavre.org \
--to=xen-devel@jbfavre.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).