From owner-freebsd-xen@FreeBSD.ORG Mon Jan 24 11:49:28 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C77D8106564A for ; Mon, 24 Jan 2011 11:49:28 +0000 (UTC) (envelope-from c2n.rybicki@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9138F8FC0A for ; Mon, 24 Jan 2011 11:49:28 +0000 (UTC) Received: by iyb26 with SMTP id 26so4019235iyb.13 for ; Mon, 24 Jan 2011 03:49:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=1OGkkiKi2zwpsMDItQ7P3c2iJK9DU/5jRB5QZWQBpdI=; b=jyDm/yZPtqMjnm5Sp9DKzJzEHbC6g/9nVkj1562eEP/pMuwqrc1+VJ8oC2BQrnwjxJ aIpSf6qVnMs57/0SEFF28I3cC1D/2u67IgkzLzJAX1Au1gjMSfhReQPJDT4DG8OdF4Tk x0fViMWv867GjV56aff5SRGGzi044AIBIyi3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=nRtiUt25VXExXYfuPHpkPdNEdZp5opZ+xVuqR9g5mFAnARrxLgqHF67rNqalumnTWr TTnMKdr7yXFRY7PuEBKd8KSUe/EyuJ+2bC0SXA8X3iodG/OifXSYnEAvdA6/dG70lTye UZ391E/fiN9olS3jHJmzwt7podppCbImLdSx0= MIME-Version: 1.0 Received: by 10.42.219.137 with SMTP id hu9mr2634644icb.363.1295869767933; Mon, 24 Jan 2011 03:49:27 -0800 (PST) Received: by 10.42.220.72 with HTTP; Mon, 24 Jan 2011 03:49:27 -0800 (PST) Date: Mon, 24 Jan 2011 12:49:27 +0100 Message-ID: From: Grzegorz Rybicki To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: I have a problem with iSCSI on AMD64 Xen HVM X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 11:49:28 -0000 Hello, I saw another network interface problems: xennet_get_responses: too many frags 11 > max 5 xennet_get_responses: too many frags 9 > max 5 xennet_get_responses: too many frags 8 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 8 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 7 > max 5 Regards