WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Regression in PCI pass-through from qemu-xen changeset "pass

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Regression in PCI pass-through from qemu-xen changeset "passthrough: Fix older kernel assigned device resume failure problem"
From: Simon Horman <horms@xxxxxxxxxxxx>
Date: Sat, 2 May 2009 12:10:15 +1000
Cc: Yu Zhao <yu.zhao@xxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Liping Ke <Liping.Ke@xxxxxxxxx>
Delivery-date: Fri, 01 May 2009 19:10:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
Changeset "passthrough: Fix older kernel assigned device resume failure
problem" (dbb8aafa702b8b4f5568e08641d98471fd04e0f8) in
qemu-xen-unstable.git appears to cause a regression. This changeset was
applied between the xen-3.4.0-rc2 and xen-3.4.0-rc3 tags of
qemu-xen-unstable.git.

[ This problem was previously reported as being in the previous
  changeset, "Fix hvm guest cirrus_vga hvm s3 resume failure".
  Apologies for any confusion that may cause ]

The problem that I am seeing is that with this changeset applied
I am not able to correctly initialise Intel network cards. Though
I assume the problem is not specific to this hardware.

In the case of an Intel e100 82557/8/9/0/1 the problem manifests as the
EEPROM being declared invalid, although the device seems to be usable
by domU.

In the case of an Intel igb 82576 the card is initialised by the
guest operating system but is unable to establish a link and
ethtool returning invalid values for the supported ports -
it tells me the card has fibre when in fact it has copper.

domU is running x86_32 2.6.30-rc4. dom0 is x86_64.

-- 
Simon Horman
  VA Linux Systems Japan K.K. Satellite Lab in Sydney, Australia
  H: www.vergenet.net/~horms/            W: www.valinux.co.jp/en

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel