From owner-freebsd-xen@FreeBSD.ORG Sun Jan 23 21:03:01 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 129F8106566C; Sun, 23 Jan 2011 21:03:01 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD0348FC1B; Sun, 23 Jan 2011 21:03:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0NL30C3042941; Sun, 23 Jan 2011 21:03:00 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0NL30VD042937; Sun, 23 Jan 2011 21:03:00 GMT (envelope-from brucec) Date: Sun, 23 Jan 2011 21:03:00 GMT Message-Id: <201101232103.p0NL30VD042937@freefall.freebsd.org> To: brucec@FreeBSD.org, brucec@FreeBSD.org, freebsd-xen@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: kern/118734: [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to boot under Xen fully virtualized 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: Sun, 23 Jan 2011 21:03:01 -0000 Synopsis: [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to boot under Xen fully virtualized Responsible-Changed-From-To: brucec->freebsd-xen Responsible-Changed-By: brucec Responsible-Changed-When: Sun Jan 23 21:02:38 UTC 2011 Responsible-Changed-Why: Back to the pool due to lack of time. http://www.freebsd.org/cgi/query-pr.cgi?pr=118734 From owner-freebsd-xen@FreeBSD.ORG Mon Jan 24 11:07:14 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 AA53410656CA for ; Mon, 24 Jan 2011 11:07:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 98A158FC0A for ; Mon, 24 Jan 2011 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0OB7EdL077999 for ; Mon, 24 Jan 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0OB7EXR077997 for freebsd-xen@FreeBSD.org; Mon, 24 Jan 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Jan 2011 11:07:14 GMT Message-Id: <201101241107.p0OB7EXR077997@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org 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:07:14 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 17 problems total. 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 From owner-freebsd-xen@FreeBSD.ORG Mon Jan 24 11:59:00 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 1D58F106566B for ; Mon, 24 Jan 2011 11:59:00 +0000 (UTC) (envelope-from c2n.rybicki@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CCCF78FC0A for ; Mon, 24 Jan 2011 11:58:59 +0000 (UTC) Received: by iwn39 with SMTP id 39so4017704iwn.13 for ; Mon, 24 Jan 2011 03:58:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=a7FGY8aVcv9e47S5w9tQLd1HU1ZatJigGGfhj70pPMI=; b=LS+epvAmz0q2CPy8x1ueQlv15vufMsXB/0I93JldRIoVokmGyKVpyI9bzpm4rNTY0P HQT2SiB9+ERTNwMBDx5xUw8smAQr3vmksgaYMMZVhy+nfm2eC/A3bFIwsaE6/hxL2eNk PV5KgoX0cyqTdaUox6E6qkEuhiOItJoWkel8A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Bt8wpbwF/BSR9lNhcAdr9dTAIumCtXBrUwuh+CJxLwQHKhHtm33GN0ceW7TmMWpLuv VuGFgtYtE6aFYiKBrQEJ+ftA8UZy/dEFUKRp1CZVnQnSUxf7WMfKED8jhZCDR4sDnRin rRYzGOFgEecM5zQJfRCh0NOQs9kCE9fmm0ngY= MIME-Version: 1.0 Received: by 10.42.177.6 with SMTP id bg6mr4672991icb.229.1295870339023; Mon, 24 Jan 2011 03:58:59 -0800 (PST) Received: by 10.42.220.72 with HTTP; Mon, 24 Jan 2011 03:58:58 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Jan 2011 12:58:58 +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: Re: 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:59:00 -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 2011/1/19 Grzegorz Rybicki > hello, > > I have a problem with ISCSI and XEN. > > Host: > > IBM Blade HS21 > Citrix XenServer 5.6 > > > Guest: > > Jan 19 13:12:38 mysql syslogd: kernel boot file is /boot/kernel/kernel > Jan 19 13:12:38 mysql kernel: Copyright (c) 1992-2011 The FreeBSD Project. > Jan 19 13:12:38 mysql kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, > 1989, 1991, 1992, 1993, 1994 > Jan 19 13:12:38 mysql kernel: The Regents of the University of California. > All rights reserved. > Jan 19 13:12:38 mysql kernel: FreeBSD is a registered trademark of The > FreeBSD Foundation. > Jan 19 13:12:38 mysql kernel: FreeBSD 8.2-RC2 #3: Tue Jan 18 13:24:03 CET > 2011 > Jan 19 13:12:38 mysql kernel: ryba@mysql.c2n.pl:/usr/obj/usr/src/sys/EDENamd64 > Jan 19 13:12:38 mysql kernel: Timecounter "i8254" frequency 1193182 Hz > quality 0 > Jan 19 13:12:38 mysql kernel: CPU: Intel(R) Xeon(R) CPU 5160 @ > 3.00GHz (3000.16-MHz K8-class CPU) > Jan 19 13:12:38 mysql kernel: Origin = "GenuineIntel" Id = 0x6f6 Family = > 6 Model = f Stepping = 6 > Jan 19 13:12:38 mysql kernel: > Features=0x781fbff > > Jan 19 13:12:38 mysql kernel: Features2=0x80002201> > Jan 19 13:12:38 mysql kernel: AMD Features=0x20000800 > Jan 19 13:12:38 mysql kernel: AMD Features2=0x1 > Jan 19 13:12:38 mysql kernel: TSC: P-state invariant > Jan 19 13:12:38 mysql kernel: real memory = 632291328 (603 MB) > Jan 19 13:12:38 mysql kernel: avail memory = 597741568 (570 MB) > Jan 19 13:12:38 mysql kernel: ACPI APIC Table: > Jan 19 13:12:38 mysql kernel: FreeBSD/SMP: Multiprocessor System Detected: > 2 CPUs > Jan 19 13:12:38 mysql kernel: FreeBSD/SMP: 2 package(s) x 1 core(s) > Jan 19 13:12:38 mysql kernel: cpu0 (BSP): APIC ID: 0 > Jan 19 13:12:38 mysql kernel: cpu1 (AP): APIC ID: 2 > Jan 19 13:12:38 mysql kernel: ioapic0: Changing APIC ID to 1 > Jan 19 13:12:38 mysql kernel: MADT: Forcing active-low polarity and level > trigger for SCI > Jan 19 13:12:38 mysql kernel: ioapic0 irqs 0-47 on > motherboard > Jan 19 13:12:38 mysql kernel: iscsi: version 2.2.4.2 > Jan 19 13:12:38 mysql kernel: kbd1 at kbdmux0 > Jan 19 13:12:38 mysql kernel: acpi0: on motherboard > Jan 19 13:12:38 mysql kernel: acpi0: [ITHREAD] > Jan 19 13:12:38 mysql kernel: acpi0: Power Button (fixed) > Jan 19 13:12:38 mysql kernel: acpi0: Sleep Button (fixed) > Jan 19 13:12:38 mysql kernel: Timecounter "ACPI-safe" frequency 3579545 Hz > quality 850 > Jan 19 13:12:38 mysql kernel: acpi_timer0: <32-bit timer at 3.579545MHz> > port 0x1f48-0x1f4b on acpi0 > Jan 19 13:12:38 mysql kernel: cpu0: on acpi0 > Jan 19 13:12:38 mysql kernel: cpu1: on acpi0 > Jan 19 13:12:38 mysql kernel: pcib0: port > 0xcf8-0xcff on acpi0 > Jan 19 13:12:38 mysql kernel: pci0: on pcib0 > Jan 19 13:12:38 mysql kernel: isab0: at device 1.0 on pci0 > > Jan 19 13:12:38 mysql kernel: isa0: on isab0 > Jan 19 13:12:38 mysql kernel: atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc320-0xc32f at device 1.1 on pci0 > Jan 19 13:12:38 mysql kernel: ata0: on atapci0 > Jan 19 13:12:38 mysql kernel: ata0: [ITHREAD] > Jan 19 13:12:38 mysql kernel: ata1: on atapci0 > Jan 19 13:12:38 mysql kernel: ata1: [ITHREAD] > Jan 19 13:12:38 mysql kernel: pci0: at device 1.2 (no > driver attached) > Jan 19 13:12:38 mysql kernel: pci0: at device 1.3 (no driver > attached) > Jan 19 13:12:38 mysql kernel: vgapci0: mem > 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff irq 24 at device 2.0 on pci0 > Jan 19 13:12:38 mysql kernel: xenpci0: port > 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 30 at device 3.0 on pci0 > Jan 19 13:12:38 mysql kernel: xs_probe: Probe retuns 0 > Jan 19 13:12:38 mysql kernel: xenstore0: on xenpci0 > Jan 19 13:12:38 mysql kernel: acpi_hpet0: > iomem 0xfed00000-0xfed003ff on acpi0 > Jan 19 13:12:38 mysql kernel: Timecounter "HPET" frequency 62500000 Hz > quality 900 > Jan 19 13:12:38 mysql kernel: atrtc0: port 0x70-0x71 > irq 8 on acpi0 > Jan 19 13:12:38 mysql kernel: atrtc0: port 0x70-0x71 > irq 8 on acpi0 > Jan 19 13:12:38 mysql kernel: atkbdc0: port > 0x60,0x64 irq 1 on acpi0 > Jan 19 13:12:38 mysql kernel: atkbd0: irq 1 on atkbdc0 > Jan 19 13:12:38 mysql kernel: kbd0 at atkbd0 > Jan 19 13:12:38 mysql kernel: atkbd0: [GIANT-LOCKED] > Jan 19 13:12:38 mysql kernel: atkbd0: [ITHREAD] > Jan 19 13:12:38 mysql kernel: psm0: irq 12 on atkbdc0 > Jan 19 13:12:38 mysql kernel: psm0: [GIANT-LOCKED] > Jan 19 13:12:38 mysql kernel: psm0: [ITHREAD] > Jan 19 13:12:38 mysql kernel: psm0: model IntelliMouse Explorer, device ID > 4 > Jan 19 13:12:38 mysql kernel: fdc0: port > 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > Jan 19 13:12:38 mysql kernel: fdc0: does not respond > Jan 19 13:12:38 mysql kernel: device_attach: fdc0 attach returned 6 > Jan 19 13:12:38 mysql kernel: uart0: FIFOs> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > Jan 19 13:12:38 mysql kernel: uart0: [FILTER] > Jan 19 13:12:38 mysql kernel: orm0: at iomem > 0xc9000-0xc97ff on isa0 > Jan 19 13:12:38 mysql kernel: sc0: at flags 0x100 on isa0 > Jan 19 13:12:38 mysql kernel: sc0: VGA <16 virtual consoles, flags=0x300> > Jan 19 13:12:38 mysql kernel: vga0: at port 0x3c0-0x3df > iomem 0xa0000-0xbffff on isa0 > Jan 19 13:12:38 mysql kernel: Timecounters tick every 10.000 msec > Jan 19 13:12:38 mysql kernel: acd0: CDROM at > ata1-slave WDMA2 > Jan 19 13:12:38 mysql kernel: xenbusb_front0: on > xenstore0 > Jan 19 13:12:38 mysql kernel: xn0: at > device/vif/0 on xenbusb_front0 > Jan 19 13:12:38 mysql kernel: xn0: Ethernet address: 02:b5:d6:76:27:ee > Jan 19 13:12:38 mysql kernel: xn1: at > device/vif/1 on xenbusb_front0 > Jan 19 13:12:38 mysql kernel: xn1: Ethernet address: 4a:bf:b0:1e:ee:af > Jan 19 13:12:38 mysql kernel: xenbusb_back0: on > xenstore0 > Jan 19 13:12:38 mysql kernel: xctrl0: on xenstore0 > Jan 19 13:12:38 mysql kernel: xbd1: 8192MB at > device/vbd/768 on xenbusb_front0 > Jan 19 13:12:38 mysql kernel: xbd1: attaching as ad0 > Jan 19 13:12:38 mysql kernel: SMP: AP CPU #1 Launched! > Jan 19 13:12:38 mysql kernel: GEOM: ad0s1: geometry does not match label > (16h,63s != 255h,63s). > Jan 19 13:12:38 mysql kernel: Trying to mount root from ufs:/dev/ad0s1a > Jan 19 13:12:38 mysql kernel: xn0: 2 link states coalesced > > And here I have a problem: > > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > (da1:iscsi0:0:0:1): WRITE(6). CDB: a 0 0 3f 1 0 > (da1:iscsi0:0:0:1): CAM status: SCSI Status Error > (da1:iscsi0:0:0:1): SCSI status: Check Condition > (da1:iscsi0:0:0:1): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, > or bus device reset occurred) > (da1:iscsi0:0:0:1): Invalidating pack > > It seems to me that iSCSI works, but something is not such a network > interface. > > Do you have any idea? > > Regards > > > From owner-freebsd-xen@FreeBSD.ORG Mon Jan 24 12:52:47 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 5A968106566C for ; Mon, 24 Jan 2011 12:52:47 +0000 (UTC) (envelope-from karim.allah.ahmed@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7EA8FC16 for ; Mon, 24 Jan 2011 12:52:46 +0000 (UTC) Received: by qyk36 with SMTP id 36so3865525qyk.13 for ; Mon, 24 Jan 2011 04:52:46 -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=2JGJzdWYsmG1q0TPzChjnh5VnKPOFnyn1O8W+RhAncM=; b=xzpx2sn8gGOzpIovqO29503qy6exeeTWxazmc62HRmfH5qXJsjZ1ER3D3KeMIZdtwy iHs7zfZjYlhyZQgRAPiylQR3KoBD8vfP7e8ATXTrs2uRxhspnwil54UxYwfrdpgDS1Gu xTXo/LgLI6bOywXNq0vExPOSjCAmgCj2PoTF0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RVdN/RPFrGjJhd+7lrjTYc3ZaIH9w9zxVRKJBOf36eIWgs++iXbiJTYoMEqK8T+hhE HsaS0H5iZIuTPaHbVlMGJkOzqMh74rQgJKR+a0l5/oxMAE7qbW2kiiDkDvZ/saQW45Al PR9rtx4rU8WLM6cO4Lb2G6+fhMEeln7MHP+TM= MIME-Version: 1.0 Received: by 10.229.28.133 with SMTP id m5mr3780694qcc.36.1295872028794; Mon, 24 Jan 2011 04:27:08 -0800 (PST) Received: by 10.229.212.208 with HTTP; Mon, 24 Jan 2011 04:27:08 -0800 (PST) Date: Mon, 24 Jan 2011 14:27:08 +0200 Message-ID: From: "karim.allah.ahmed@gmail.com" To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Issue with non-PAE enable i386 xen guest 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 12:52:47 -0000 In initvalues(start_info_t) function at "[[src]]/sys/i386/xen/xen_machdep.c" IdlePDTnew, IdlePTDnew, etc are only declared under PAE enabled guests as following: #ifdef PAE vm_paddr_t IdlePDPTma, IdlePDPTnewma; vm_paddr_t IdlePTDnewma[4]; pd_entry_t *IdlePDPTnew, *IdlePTDnew; #else vm_paddr_t pdir_shadow_ma; #endif However It's used later in the function without constraining it to certain guests ( without #ifdef PAE ), one of those is memcpy(((uint8_t *)IdlePTDnew) + ((unsigned int)(KERNBASE >> 18)), ((uint8_t *)IdlePTD) + ((KERNBASE >> 18) & PAGE_MASK), l1_pages*sizeof(pt_entry_t)) Is the current non-PAE xen guest implementation broke intentionally, or is this a merge issue or something ? ( This issue arises as a compile-time error as soon as you remove the "options PAE" in the XEN configuration file for the build ) -- Karim Allah Ahmed. LinkedIn From owner-freebsd-xen@FreeBSD.ORG Tue Jan 25 11:01:13 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 A12A9106564A for ; Tue, 25 Jan 2011 11:01:13 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6624D8FC18 for ; Tue, 25 Jan 2011 11:01:13 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0PB1CVv080679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jan 2011 11:01:12 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0PB1CVv080679 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1295953272; x=1296558072; bh=Pgw5UgCwm7rnmtN1ucIlz9xNk+6nXI5zmYzplRgVLnE=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=IWRMptA0jq0QJVm4uxwDwBqBu20gedBFbHZAyzxz7KGmUhBi8yabvqR0RDBaJBM9L 3w0CdeG2NmcD/QHK/xI42duDvpKZFk0kqrI+hyZS/SmOadhOsQUUcKe9NunjDDd0mY AFaR1PHenGYO08u5CdPcDvZBqQYrIY42zVSQrDIc= Date: Tue, 25 Jan 2011 11:01:12 +0000 (UTC) From: Janne Snabb To: "karim.allah.ahmed@gmail.com" In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Tue, 25 Jan 2011 11:01:12 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: Issue with non-PAE enable i386 xen guest 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: Tue, 25 Jan 2011 11:01:13 -0000 On Mon, 24 Jan 2011, karim.allah.ahmed@gmail.com wrote: > Is the current non-PAE xen guest implementation broke intentionally, or is > this a merge issue or something ? According to http://wiki.freebsd.org/FreeBSD/Xen it is not supposed to work: "Para-virtualized i386 kernels require options PAE to be included in the kernel configuration." -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Tue Jan 25 14:35:55 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 CABE21065679 for ; Tue, 25 Jan 2011 14:35:55 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8E97E8FC16 for ; Tue, 25 Jan 2011 14:35:55 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0PEZsdI070477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jan 2011 14:35:54 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0PEZsdI070477 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1295966154; x=1296570954; bh=mwQQ8O6U16C6R6jATQshJATCoKNfjcbwJVPu+WcfDxg=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=nSjPI2EAdTvQclwl9l0gQc2+/+x230S5vcr1u0YNjtNjIpDyamhnyDddbokFwZMhR x1L+eZoOdlDUV8uaiPj2OVH5iNnypBxy5IgvertFvsjneUWeRlQA057H6kzYHSLNmV UEJAcX5NEsqQxnJhm6GKk0dAVGXjXC0hrXvaNNlU= Date: Tue, 25 Jan 2011 14:35:54 +0000 (UTC) From: Janne Snabb To: Grzegorz Rybicki In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Tue, 25 Jan 2011 14:35:54 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: 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: Tue, 25 Jan 2011 14:35:55 -0000 On Mon, 24 Jan 2011, Grzegorz Rybicki wrote: > xennet_get_responses: too many frags 11 > max 5 [..] The following in sys/dev/xen/netfront/netfront.c xennet_get_responses() looks a little bit suspicious: > int max = 5 /* MAX_TX_REQ_FRAGS + (rx->status <= RX_COPY_THRESHOLD) */; ...together with the check at the end of the function (the only place where "max" is used) which produces the error message you see: > if (unlikely(frags > max)) { > if (net_ratelimit()) > WPRINTK("Too many frags\n"); > printf("%s: too many frags %d > max %d\n", __func__, frags, > max); > err = E2BIG; > } MAX_TX_REQ_FRAGS is defined as follows in the same file: > #define MAX_TX_REQ_FRAGS (65536 / PAGE_SIZE + 2) ...which produces already 18. Where does this "max = 5" come from? Either "max" is wrong or I do not understand the comment on the line where it is defined. There are some interesting and probably related comments in the same file about the Linux netback driver's lacking capabilities of handling many fragments. But why do we care about that when receiving? I would guestimate that either "max" should be higher than what it currently is (5) or the check which produces the error might be unneeded. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Tue Jan 25 15:58:49 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 64188106564A for ; Tue, 25 Jan 2011 15:58:49 +0000 (UTC) (envelope-from luke@digital-crocus.com) Received: from mail.digital-crocus.com (node2.digital-crocus.com [91.209.244.128]) by mx1.freebsd.org (Postfix) with ESMTP id 180AE8FC15 for ; Tue, 25 Jan 2011 15:58:48 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dkselector; d=hybrid-logic.co.uk; h=Received:Received:Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type:Organization:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-Spam-Score:X-Digital-Crocus-Maillimit:X-Authenticated-Sender:X-Complaints:X-Admin:X-Abuse; b=lMsOqrBt+nHU3cbYeMygGzFYfIuZkL9dWc0BLrXdZQyIQNowPex89TX3IPX/YoxmFdb79n4FV9hYBtOH3IIGOWHw4GsG4uGuEdhJikxOhV4N6q+FoYzhVl7pV6/NEim8; Received: from luke by mail.digital-crocus.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Phkqt-000Fdv-6X for freebsd-xen@freebsd.org; Tue, 25 Jan 2011 15:30:39 +0000 Received: from beaker.cictr.com ([204.9.220.41] helo=[10.10.104.194]) by mail.digital-crocus.com with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Phkqr-000FdS-AK; Tue, 25 Jan 2011 15:30:37 +0000 From: Luke Marsden To: Janne Snabb In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Organization: Hybrid Web Cluster Date: Tue, 25 Jan 2011 10:35:42 -0500 Message-ID: <1295969742.3187.48.camel@pow> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.0 X-Digital-Crocus-Maillimit: done X-Authenticated-Sender: luke X-Complaints: abuse@digital-crocus.com X-Admin: admin@digital-crocus.com X-Abuse: abuse@digital-crocus.com (Please include full headers in abuse reports) Cc: freebsd-xen@freebsd.org Subject: Re: I have a problem with iSCSI on AMD64 Xen HVM X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: luke@hybrid-logic.co.uk 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: Tue, 25 Jan 2011 15:58:49 -0000 On Tue, 2011-01-25 at 14:35 +0000, Janne Snabb wrote: > I would guestimate that either "max" should be higher than what it > currently is (5) or the check which produces the error might be > unneeded. In my tests commenting out that check entirely works fine. http://www.hybrid-cluster.com/blog/2010/11/running-freebsd-8-1-as-a-xen-hvm-domu-on-flexiant/ -- Best Regards, Luke Marsden CTO, Hybrid Logic Ltd. Web: http://www.hybrid-cluster.com/ Hybrid Web Cluster - cloud web hosting Phone: +441172232002 / +16179496062 From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 01:30:58 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 1A193106564A for ; Wed, 26 Jan 2011 01:30:58 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id CCDEA8FC18 for ; Wed, 26 Jan 2011 01:30:57 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0Q1Uuik099576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 01:30:56 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0Q1Uuik099576 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296005457; x=1296610257; bh=r8g69yZnvcqG3K1iqJPdAiC50p1samwwrybFfKmy814=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=LL1d0bqOPxfAQ/ToaoqwCkDGiVILA5P6nab/pu9R857JA90t3ZTx8aF8SU3n8P6C+ vBz5QDuN5RO36XnVjY5GC3M8KcoBpk23z8oOXqb0vXDW7EBEqcKLlfrFXIYEqy0XpV pIT4x/vgumGhA8n1t2H2UBjJZi4RtFMT0PMTrLg4= Date: Wed, 26 Jan 2011 01:30:56 +0000 (UTC) From: Janne Snabb To: luke@hybrid-logic.co.uk In-Reply-To: <1295969742.3187.48.camel@pow> Message-ID: References: <1295969742.3187.48.camel@pow> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Wed, 26 Jan 2011 01:30:57 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: 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: Wed, 26 Jan 2011 01:30:58 -0000 On Tue, 25 Jan 2011, Luke Marsden wrote: > On Tue, 2011-01-25 at 14:35 +0000, Janne Snabb wrote: > > I would guestimate that either "max" should be higher than what it > > currently is (5) or the check which produces the error might be > > unneeded. > > In my tests commenting out that check entirely works fine. It also appears that before SVN r181945 (2008-08-21 by kmacy) "max" was 24, so it was much less likely to hit the (possibly unneeded) "if (frags > max)" check limit: > int max = 24 /* MAX_SKB_FRAGS + (rx->status <= RX_COPY_THRESHOLD) */; I do not understand from the commit message why it was changed to 5. (I wish there was a bit more comments in the non-obvious parts of the code. Now it is difficult for a FreeBSD/Xen PV newbie to work on it without intimate knowledge of the history of the odd bits of the code. It clearly needs more care than what it is being given now. Things like the "do something useful" panic also indicate that there is no more than few people who actually play with and try out the code currently.) -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 06:07:18 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 C232E106564A for ; Wed, 26 Jan 2011 06:07:18 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9948FC12 for ; Wed, 26 Jan 2011 06:07:17 +0000 (UTC) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0Q3Rl2A031228 for ; Wed, 26 Jan 2011 14:27:47 +1100 Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0Q3RiAx004843 for ; Wed, 26 Jan 2011 14:27:44 +1100 Message-ID: <4D3F94B0.4080704@joovke.com> Date: Wed, 26 Jan 2011 14:27:44 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 06:07:18 -0000 Hi guys, I am having an issue with high network interface collisions when running freebsd under XEN (I am using freebsd as my OS for a VPS). I have filed a PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=154236 and have had some discussion with the driver maintainer, we're both at a loss as to what the issue is, perhaps someone here could take a look at it and see whether they have seen the same issue or know what may be causing it. From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 06:59:49 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 D06721065679 for ; Wed, 26 Jan 2011 06:59:49 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8D06B8FC1B for ; Wed, 26 Jan 2011 06:59:49 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0Q6xmj1040683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 06:59:48 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0Q6xmj1040683 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296025188; x=1296629988; bh=e55WMIAiAVMlYeYlGRVddRKhN5zR5DKkzE9eDg4xPec=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=XKJBDmYgItwZJtD+ZiOLyOh/y6czAvM6xCj/93jtwHGKZLqlmpI8Ou3nMv9OkmB5x YKpVg0QW9M/1u3WuBvOc+7CRBFZ6wa9cb5CHggN0rMT5Ub0ye/czavp131f0IPnuiw 4o/7iB1G+XKLLvsCIIpcVPRnhBnb7XmidvRakpNg= Date: Wed, 26 Jan 2011 06:59:48 +0000 (UTC) From: Janne Snabb To: Alex In-Reply-To: <4D3F94B0.4080704@joovke.com> Message-ID: References: <4D3F94B0.4080704@joovke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Wed, 26 Jan 2011 06:59:48 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 06:59:49 -0000 On Wed, 26 Jan 2011, Alex wrote: > I am having an issue with high network interface collisions when running > freebsd under XEN (I am using freebsd as my OS for a VPS). [..] > whether they have seen the same issue or know what may be causing it. I can confirm seeing it here also, you are not alone: $ netstat -i Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll re0 1500 00:16:3e:08:b4:c7 21150230 0 0 4101045 0 4019323 [..] I had not noticed it before. I am not encountering any packet loss or other networking problems. No idea about the reason. This is on FreeBSD 8.1-RELEASE-p2 amd64 with GENERIC kernel. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 08:43:19 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 79E30106566B for ; Wed, 26 Jan 2011 08:43:19 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.freebsd.org (Postfix) with ESMTP id D88358FC13 for ; Wed, 26 Jan 2011 08:43:18 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0Q8hGpw029495 for ; Wed, 26 Jan 2011 19:43:17 +1100 Message-ID: <4D3FDEA3.1070504@joovke.com> Date: Wed, 26 Jan 2011 19:43:15 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <4D3F94B0.4080704@joovke.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 08:43:19 -0000 Hi Janne, I don't know whether this is an issue with the "re" driver or something else that's affecting the "re" driver (the way Xen handles network traffic). Though as far as I know, when a collision is detected, the behavior is for the sender to invoke it's backoff algorithm and to wait a set amount of time before transmitting again. if this is actually occurring then there would be performance degradation. Would you mind adding your feedback on my PR up at freebsd.org just to let the "re" maintainer know it's not just me? The PR is 154236. Would Greatly appreciate it. Thanks in advance. On 26/01/11 17:59, Janne Snabb wrote: > On Wed, 26 Jan 2011, Alex wrote: > >> I am having an issue with high network interface collisions when running >> freebsd under XEN (I am using freebsd as my OS for a VPS). > [..] >> whether they have seen the same issue or know what may be causing it. > I can confirm seeing it here also, you are not alone: > > $ netstat -i > Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll > re0 1500 00:16:3e:08:b4:c7 21150230 0 0 4101045 0 4019323 > [..] > > I had not noticed it before. I am not encountering any packet loss > or other networking problems. No idea about the reason. > > This is on FreeBSD 8.1-RELEASE-p2 amd64 with GENERIC kernel. > > -- > Janne Snabb / EPIPE Communications > snabb@epipe.com - http://epipe.com/ > From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 09:03:09 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 71B7C106564A for ; Wed, 26 Jan 2011 09:03:09 +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 366B38FC16 for ; Wed, 26 Jan 2011 09:03:08 +0000 (UTC) Received: by iyb26 with SMTP id 26so164244iyb.13 for ; Wed, 26 Jan 2011 01:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=m+/tmLL9ZrLPX3JcAbRoSIhQ0ma57KqDgiAFAkNNKKY=; b=UGoKR3hoRI3BH4yCNOphLOUWkfochK+wVGsOSk59N29FMgUEH/DPERvWB0IZZP8NSg n5UcvFPfGb8EzYgkF208aq74YDP0iGGo+o/HfYy8xLh3ZHy8KRpUNuh2xrQwdZFxxwDl x2qdAH8SC8H34GuM3brAKa500nZxo4yg9qgPk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=LUm0H4qoWZw8jiHSMKsj8OG+wDsxJ7Z9OtDVw5EWn+UND1QeCKkeOBu4Up3fhimosf HR6WrjJFeKiPQP8Iasoqw5FcNiixiTkbVq1KW3mEGwBZWN0T5fvj9sBUxKO2g7NHLxYV WCeNzOB+Z4l9OiqZQzw7w0oZ1mOeGTGV/7IR4= MIME-Version: 1.0 Received: by 10.42.165.3 with SMTP id i3mr83410icy.430.1296032588103; Wed, 26 Jan 2011 01:03:08 -0800 (PST) Received: by 10.42.220.72 with HTTP; Wed, 26 Jan 2011 01:03:05 -0800 (PST) In-Reply-To: <1295969742.3187.48.camel@pow> References: <1295969742.3187.48.camel@pow> Date: Wed, 26 Jan 2011 10:03:05 +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: Re: 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: Wed, 26 Jan 2011 09:03:09 -0000 > > On Tue, 2011-01-25 at 14:35 +0000, Janne Snabb wrote: > > I would guestimate that either "max" should be higher than what it > > currently is (5) or the check which produces the error might be > > unneeded. > > In my tests commenting out that check entirely works fine. > > > http://www.hybrid-cluster.com/blog/2010/11/running-freebsd-8-1-as-a-xen-hvm-domu-on-flexiant/ > > Hi, > > That solved the problem "xennet_get_responses: too many frags 11> max 5. > thank you very much > > Unfortunately, the problem with ISCSI remained. Continues to receive > messages when you try to set up the file system. > > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > xn_txeof: WARNING: response is -1! > > Best Regards, > > > > > From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 09:05:50 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 BB34C1065673 for ; Wed, 26 Jan 2011 09:05:50 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5CB118FC1A for ; Wed, 26 Jan 2011 09:05:50 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0Q95n3s049297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 09:05:49 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0Q95n3s049297 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296032749; x=1296637549; bh=LA7vMd2TnUdqZXkzVB7K5jIxgNOKj1iQczu5o5PeprE=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=LG6HYPBTU3oWi1EOJBWT3DPpBWVIAb0t4PFKcLHP+kCTwVFOgANTSrwYVMqBiY1zu VDTf4a9KRRYRxkMTpjQFleVNZ/8P8xrzRnI7u9izQtNM5uXTIdlFuzCWHoLm7BQv2u jryHdkHCYzbt0VDUQCN73xBoP1dmxsvZsijUdyAo= Date: Wed, 26 Jan 2011 09:05:49 +0000 (UTC) From: Janne Snabb To: Nick Sayer In-Reply-To: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> Message-ID: References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Wed, 26 Jan 2011 09:05:49 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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: Wed, 26 Jan 2011 09:05:50 -0000 On Fri, 21 Jan 2011, Nick Sayer wrote: > +1 to the patch Janne Snabb posted. I have a domU at rootbsd and > had suffered the exact same "do something smart" panic when I tried > to build a xen kernel, but his patch fixed it for me. Thanks for confirming that I am not the only one suffering of this. I was wondering if I am doing something wrong. I did send-pr this with my patch so that it does not get forgotten. PR kern/154302 -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 09:25:32 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 F09C0106566C for ; Wed, 26 Jan 2011 09:25:32 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id ABD3B8FC14 for ; Wed, 26 Jan 2011 09:25:32 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0Q9PWiB095270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 09:25:32 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0Q9PWiB095270 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296033932; x=1296638732; bh=f31KOk022mpfXcdR9wFMkQu/Cq0Kg2MG1jRLIBxhaoY=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=TrebeZ/WqipzavStMvYTAhUz31jGzn/EbW7/fPSE8ELsgjz+fNscs4WC71OLUDF3L BkNTpFJmvfErFNrI9kPieOnG6DOiHKTsgGIZhKvMruxDZ/4BJiFvH3wp47JSQ4wZVz +4YPXhsYbVC0r8mM0ZbWQd1l456hNlqcGFK2K5Vw= Date: Wed, 26 Jan 2011 09:25:32 +0000 (UTC) From: Janne Snabb To: Alex In-Reply-To: <4D3FDEA3.1070504@joovke.com> Message-ID: References: <4D3F94B0.4080704@joovke.com> <4D3FDEA3.1070504@joovke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Wed, 26 Jan 2011 09:25:32 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 09:25:33 -0000 On Wed, 26 Jan 2011, Alex wrote: > Though as far as I know, when a collision is detected, the behavior is for the > sender to invoke it's backoff algorithm and to wait a set amount of time > before transmitting again. if this is actually occurring then there would be > performance degradation. Yeah, this would be bad if it is actually happening within Xen or dom0 and not just an issue with a counter. On bare metal this collision processing would happen within the network card. > Would you mind adding your feedback on my PR up at freebsd.org just to let the > "re" maintainer know it's not just me? The PR is 154236. Would Greatly > appreciate it. Done. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 11:00:09 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F20D2106564A; Wed, 26 Jan 2011 11:00:08 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BBDB28FC13; Wed, 26 Jan 2011 11:00:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0QB081R019773; Wed, 26 Jan 2011 11:00:08 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0QB08Rc019769; Wed, 26 Jan 2011 11:00:08 GMT (envelope-from linimon) Date: Wed, 26 Jan 2011 11:00:08 GMT Message-Id: <201101261100.p0QB08Rc019769@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/154302: [xen] [panic] [patch] xn0: Error 2 parsing device/vif/0/mac 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: Wed, 26 Jan 2011 11:00:09 -0000 Synopsis: [xen] [panic] [patch] xn0: Error 2 parsing device/vif/0/mac Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jan 26 11:00:00 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=154302 From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 15:48:32 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 642EB106564A for ; Wed, 26 Jan 2011 15:48:32 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:e09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F72A8FC18 for ; Wed, 26 Jan 2011 15:48:31 +0000 (UTC) Received: from arachne.kfu.com (arachne.kfu.com [IPv6:2001:470:1f05:16b7:5a55:caff:fef2:4efb]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0QFmQ7E041933 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 26 Jan 2011 07:48:31 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0QFmQ7E041933 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296056911; bh=B7vWd37LuhIZ8ckkWjoBGNHlMm5Wxu8Uyj2btSW0SMA=; h=From:Content-Type:Content-Transfer-Encoding:Subject:Date: Message-Id:To:Mime-Version; b=cVyeEEYWl8E8ktQieuMBVkzxJXhGx7YBXRMaGzNtkW277FWV8DBz+By0WixFFDGal c+K5H5/vFZwc4HZRaElpc5AONoTtu3A5qJiUhyEncOg9rEJWsT9+R5jwriAkR3N30y 05JSyOTGs6xdNto97ObXlgi2PAQMBvVbV1hb7GWo= From: Nick Sayer Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Jan 2011 07:48:25 -0800 Message-Id: To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [IPv6:2001:470:1f07:e09:216:3eff:fe2d:5c32]); Wed, 26 Jan 2011 07:48:31 -0800 (PST) Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 15:48:32 -0000 I saw this same high collision count before I converted my RootBSD domU = from GENERIC to XENHVM. I do not see any collisions show up in netstat = -i with xn0/xn1 instead of re0/re1. Of course, I needed kern/154302's patch to make the XENHVM kernel work. = I hope that gets committed and merged back in time for 8.2-RELEASE. From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 16:31:19 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 B94A11065672 for ; Wed, 26 Jan 2011 16:31:19 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:e09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 617268FC16 for ; Wed, 26 Jan 2011 16:31:19 +0000 (UTC) Received: from arachne.kfu.com (arachne.kfu.com [IPv6:2001:470:1f05:16b7:5a55:caff:fef2:4efb]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0QGVEqn042540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 26 Jan 2011 08:31:18 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0QGVEqn042540 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296059478; bh=FVtw9FHfzwpIYGD8J8tFCbhqPhhGUF4M+41BeiZVfQE=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=MOuxI7xwlPPXFuF+DSZ40zv2WPjfDYn3ciHpVohKWwFcJAPqaKIlgPU7XTgYbVETY edfwB87Dsz6TdLaY7PJse1FbCN4MoDpRwjVty+R01jIf/UxntdwWj7moChqa8ypPkV dk2hxxgj9q9gq+qCGq7FTWW7I+cmr/D1/elGf3qo= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Nick Sayer In-Reply-To: Date: Wed, 26 Jan 2011 08:31:13 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [IPv6:2001:470:1f07:e09:216:3eff:fe2d:5c32]); Wed, 26 Jan 2011 08:31:18 -0800 (PST) Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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: Wed, 26 Jan 2011 16:31:19 -0000 So what are the prospects of getting this applied and then merged back = in time for 8.2-RELEASE? On Jan 26, 2011, at 1:05 AM, Janne Snabb wrote: > On Fri, 21 Jan 2011, Nick Sayer wrote: >=20 > Thanks for confirming that I am not the only one suffering of this. > I was wondering if I am doing something wrong. >=20 > I did send-pr this with my patch so that it does not get forgotten. > PR kern/154302 From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 20:52: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 06570106566C for ; Wed, 26 Jan 2011 20:52:28 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.freebsd.org (Postfix) with ESMTP id 8182E8FC0A for ; Wed, 26 Jan 2011 20:52:27 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0QKqOKf021298 for ; Thu, 27 Jan 2011 07:52:25 +1100 Message-ID: <4D408984.3030502@joovke.com> Date: Thu, 27 Jan 2011 07:52:20 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 20:52:28 -0000 It's would be a logical conclusion that it's an issue with the "re" driver then. I cant get my 8.2-RC1 XENHVM kernel to boot so had to resort to GENERIC, the HVM kernel just panics and I remember seeing something along the lines of "do something smart?" does this patch you mention fix that? On 27/01/11 02:48, Nick Sayer wrote: > I saw this same high collision count before I converted my RootBSD domU from GENERIC to XENHVM. I do not see any collisions show up in netstat -i with xn0/xn1 instead of re0/re1. > > Of course, I needed kern/154302's patch to make the XENHVM kernel work. I hope that gets committed and merged back in time for 8.2-RELEASE. > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Wed Jan 26 23:18:29 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 E5B1B106566C for ; Wed, 26 Jan 2011 23:18:29 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id A54A48FC18 for ; Wed, 26 Jan 2011 23:18:29 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0QNIPH0043413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 23:18:26 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0QNIPH0043413 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296083907; x=1296688707; bh=fXUIvYyyrJ1ZI9UhfqiXGf6CV28WzrWNSdBoxxP8zcE=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=Hi+eltW9bRbEKTliXSYIp8TO0bI/S3HkDRCMlhQrEYgHmtjKYfQR2TUG1aVoP0G10 esdgM4GiWys1RlZgPdQdRllODcrPcMPJcJbFZQLbS26yzuhkmqjuLoIRCkgTIhgpMj InXMBckE/FEqVuoGB646JEoHecJdDTl8DFeMW5LU= Date: Wed, 26 Jan 2011 23:18:24 +0000 (UTC) From: Janne Snabb To: Alex In-Reply-To: <4D408984.3030502@joovke.com> Message-ID: References: <4D408984.3030502@joovke.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1852024168-1521991802-1296083907=:20212" X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Wed, 26 Jan 2011 23:18:27 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: Help! Network issue with freebsd + Xen 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: Wed, 26 Jan 2011 23:18:30 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1852024168-1521991802-1296083907=:20212 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 27 Jan 2011, Alex wrote: [..] > the HVM kernel just panics and I remember seeing something along the lines of > "do something smart?" > > does this patch you mention fix that? Yes. See http://www.freebsd.org/cgi/query-pr.cgi?pr=154302 The patch is also attached to this mail. Best Regards, -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ --1852024168-1521991802-1296083907=:20212 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=do-something-smart.patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=do-something-smart.patch LS0tIHN5cy9kZXYveGVuL25ldGZyb250L25ldGZyb250LmMub3JpZwkyMDEw LTEyLTIxIDE3OjA5OjI1LjAwMDAwMDAwMCArMDAwMA0KKysrIHN5cy9kZXYv eGVuL25ldGZyb250L25ldGZyb250LmMJMjAxMS0wMS0xNyAxMDoxMTowNi4w MDAwMDAwMDAgKzAwMDANCkBAIC00MDEsMTMgKzQwMSwxNCBAQA0KIHhlbl9u ZXRfcmVhZF9tYWMoZGV2aWNlX3QgZGV2LCB1aW50OF90IG1hY1tdKQ0KIHsN CiAJaW50IGVycm9yLCBpOw0KIAljaGFyICpzLCAqZSwgKm1hY3N0cjsNCiAN Ci0JZXJyb3IgPSB4c19yZWFkKFhTVF9OSUwsIHhlbmJ1c19nZXRfbm9kZShk ZXYpLCAibWFjIiwgTlVMTCwNCi0JICAgICh2b2lkICoqKSAmbWFjc3RyKTsN Ci0JaWYgKGVycm9yKQ0KKwlpZiAoKGVycm9yID0geHNfcmVhZChYU1RfTklM LCB4ZW5idXNfZ2V0X25vZGUoZGV2KSwgIm1hYyIsIE5VTEwsDQorCSAgICAo dm9pZCAqKikgJm1hY3N0cikpICE9IDAgJiYNCisJICAgIChlcnJvciA9IHhz X3JlYWQoWFNUX05JTCwgeGVuYnVzX2dldF9vdGhlcmVuZF9wYXRoKGRldiks IA0KKwkgICAgIm1hYyIsIE5VTEwsICh2b2lkICoqKSAmbWFjc3RyKSkgIT0g MCkNCiAJCXJldHVybiAoZXJyb3IpOw0KIA0KIAlzID0gbWFjc3RyOw0KIAlm b3IgKGkgPSAwOyBpIDwgRVRIRVJfQUREUl9MRU47IGkrKykgew0KIAkJbWFj W2ldID0gc3RydG91bChzLCAmZSwgMTYpOw0K --1852024168-1521991802-1296083907=:20212-- From owner-freebsd-xen@FreeBSD.ORG Thu Jan 27 09:43:22 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 6B7DF1065693 for ; Thu, 27 Jan 2011 09:43:22 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.freebsd.org (Postfix) with ESMTP id BE2C48FC19 for ; Thu, 27 Jan 2011 09:43:21 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0R9hHSp011689 for ; Thu, 27 Jan 2011 20:43:18 +1100 Message-ID: <4D413E35.9030107@joovke.com> Date: Thu, 27 Jan 2011 20:43:17 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> In-Reply-To: <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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: Thu, 27 Jan 2011 09:43:22 -0000 I've applied this patch, I now get past the ethernet issue, and have run into another problem, see screenshot: http://ahhyes.net/xen1.jpg any ideas? From owner-freebsd-xen@FreeBSD.ORG Thu Jan 27 14:32:55 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 4404B1065674 for ; Thu, 27 Jan 2011 14:32:55 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 0B84A8FC12 for ; Thu, 27 Jan 2011 14:32:54 +0000 (UTC) Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 4FF35ED0418; Thu, 27 Jan 2011 14:01:13 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Carsten Heesch In-Reply-To: Date: Thu, 27 Jan 2011 14:01:25 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <0F524D72-3752-47FD-9234-ED009009B0A0@ossafe.org> References: <1295969742.3187.48.camel@pow> To: Janne Snabb X-Mailer: Apple Mail (2.1082) Cc: freebsd-xen@freebsd.org, luke@hybrid-logic.co.uk Subject: Re: 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: Thu, 27 Jan 2011 14:32:55 -0000 >> int max =3D 24 /* MAX_SKB_FRAGS + (rx->status <=3D = RX_COPY_THRESHOLD) */; I've just recompiled XENHVM setting this for a quick test: > int max =3D MAX_SKB_FRAGS; Before, I was receiving said error message a lot; now it's gone. Also, = throughput has massively increased! My test setup was: 2x FreeBSD/amd64 8.2-RC2 (compiled about a week ago), XENHVM kernel. Both DomU's were running on the same physical machine (CentOS 5.5 x86_64 = with Xen 4.3.3 on Intel i7), their xn0 NICs are using the same bridge on = Dom0. I was able to trigger the error message on the receiving side by doing a = simple "scp test.bin :/dev/null" from one DomU to the other. = Throughput dropped within seconds from ~40MB/sec below 2MB/sec. Now, with that change in place, throughput remains well above 50MB/sec! = (approximates actual disk read speed minus SSH compression/encryption = overhead)=20 Which would be the right value for max? This was obviously only a quick, = dirty test. I haven't got a clue either, where the max=3D5 came from, = but it doesn't seem to be a reasonable value. Cheers Carsten From owner-freebsd-xen@FreeBSD.ORG Thu Jan 27 19:29:54 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 ED109106564A for ; Thu, 27 Jan 2011 19:29:54 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:e09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5D28FC16 for ; Thu, 27 Jan 2011 19:29:54 +0000 (UTC) Received: from nsayer-osx.silverspringnet.com (soi.silverspringnet.com [74.121.22.10]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0RJToYC069684 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 27 Jan 2011 11:29:53 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0RJToYC069684 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296156593; bh=BE4vDxZORRfBNJEcTVrvZA9bKcFcO3H76200uen/BOw=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=UG4GbcFqAUNKG7uw5oP7EVsz/9cJM/1aoN2xESRpemCy59IAaqXYaZcyfLi4gBure Gr4KWCgNDDzGMW78Vt0B+3Yv1tzhtGpSTeVuO+WVuydnUAON9sjt4s26z3JYkd+08N C8VTUARJHuVWl988nEsF7PF74AHxBcayKcCGZJmU= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Nick Sayer In-Reply-To: <4D413E35.9030107@joovke.com> Date: Thu, 27 Jan 2011 11:29:45 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Thu, 27 Jan 2011 11:29:53 -0800 (PST) Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] 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: Thu, 27 Jan 2011 19:29:55 -0000 On Jan 27, 2011, at 1:43 AM, Alex wrote: > I've applied this patch, I now get past the ethernet issue, and have = run into another problem, see screenshot: >=20 > http://ahhyes.net/xen1.jpg >=20 > any ideas? >=20 The disk geometry differs from the PV device and the emulated hardware, = I suspect. I was using GPT when I migrated, so I suspect that the issue was moot. = What is your partitioning schema for this disk? Can you switch over to = GPT... uh... somehow?= From owner-freebsd-xen@FreeBSD.ORG Thu Jan 27 21:29:53 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 A65DA106567A for ; Thu, 27 Jan 2011 21:29:53 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 447258FC1F for ; Thu, 27 Jan 2011 21:29:52 +0000 (UTC) Received: from [172.16.0.242] (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0RLToCb006466 for ; Fri, 28 Jan 2011 08:29:51 +1100 Message-ID: <4D41E3D1.7040100@joovke.com> Date: Fri, 28 Jan 2011 08:29:53 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> In-Reply-To: <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: xenbusb_nop_confighook_cb timeout 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: Thu, 27 Jan 2011 21:29:53 -0000 I've had that geom warning before on real hardware and it's never stopped it from working. In my screenshot, it appears the time out is originating from: xenbusb.c:xenbusb_nop_confighook_cb xenbusb_nop_confighook_cb(void *arg __unused) { } called in xenbusb_attach(device_t dev, char *bus_node, u_int id_components) /* * Since XenBus busses are attached to the XenStore, and * the XenStore does not probe children until after interrupt * services are available, this config hook is used solely * to ensure that the remainder of the boot process (e.g. * mount root) is deferred until child devices are adequately * probed. We unblock the boot process as soon as the * connecting child count in our softc goes to 0. */ xbs->xbs_attach_ch.ich_func = xenbusb_nop_confighook_cb; Regarding the partitioning, I am not sure what you mean. I have this configured as a VPS so I want to avoid doing anything that may destroy data on the disk. On 28/01/11 06:29, Nick Sayer wrote: > On Jan 27, 2011, at 1:43 AM, Alex wrote: > >> I've applied this patch, I now get past the ethernet issue, and have run into another problem, see screenshot: >> >> http://ahhyes.net/xen1.jpg >> >> any ideas? >> > The disk geometry differs from the PV device and the emulated hardware, I suspect. > > I was using GPT when I migrated, so I suspect that the issue was moot. What is your partitioning schema for this disk? Can you switch over to GPT... uh... somehow?_______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Thu Jan 27 22:41:08 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 F38A8106564A for ; Thu, 27 Jan 2011 22:41:07 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:e09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6357A8FC12 for ; Thu, 27 Jan 2011 22:41:07 +0000 (UTC) Received: from nsayer-osx.silverspringnet.com (edge-gw-rwc.silverspringnet.com [74.121.22.10]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0RMf31C072089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 27 Jan 2011 14:41:06 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0RMf31C072089 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296168066; bh=LvCZYSnlkaKwqkN338NVEhXitAn0c3rF2/nSZ2nVWLs=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=N5rSEu1kFgNVjC0OIMme22GHdVMOoYisTIX2VOAR+hNj4RCLTRF8rP1rJtc1ABl8a GMcKD/kAgRgoTbJ2cNyqd8sDJGsSVGnmFSF1/uYOCvWpHFqxIliqwumvXX9DBdiEMY MKCxe6trM0E1OobJ93K2W53B3x60UoOXn590gElo= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Nick Sayer In-Reply-To: <4D41E3D1.7040100@joovke.com> Date: Thu, 27 Jan 2011 14:40:58 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> To: freebsd-xen@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Thu, 27 Jan 2011 14:41:06 -0800 (PST) Subject: Re: xenbusb_nop_confighook_cb timeout 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: Thu, 27 Jan 2011 22:41:08 -0000 On Jan 27, 2011, at 1:29 PM, Alex wrote: > I've had that geom warning before on real hardware and it's never = stopped it from working. Ah, well, then never mind. I thought maybe it was germane to the hang. I don't know which differences we might have between us that would = account for it working for me, but not for you. My machine is GPT+ZFS = and it had no trouble transitioning to XENHVT once the "do something = smart" panic went away. From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 01:20:20 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 2C7D2106564A for ; Fri, 28 Jan 2011 01:20:20 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from one.digitalpacific.com.au (one.digitalpacific.com.au [203.19.59.9]) by mx1.freebsd.org (Postfix) with ESMTP id B83BC8FC15 for ; Fri, 28 Jan 2011 01:20:19 +0000 (UTC) X-ClientAddr: 150.101.205.12 Received: from [127.0.0.1] (eth525.nsw.adsl.internode.on.net [150.101.205.12]) (authenticated bits=0) by one.digitalpacific.com.au (8.13.8/8.13.8) with ESMTP id p0S0T8mf001287 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 28 Jan 2011 11:29:10 +1100 Message-ID: <4D420D46.2060600@joovke.com> Date: Fri, 28 Jan 2011 11:26:46 +1100 From: Alex User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DigitalPacific-MailScanner-Information: Please contact support@digitalpacific.com.au for more information X-DigitalPacific-MailScanner-ID: p0S0T8mf001287 X-DigitalPacific-MailScanner: Found to be clean X-DigitalPacific-MailScanner-From: joovke@joovke.com X-Spam-Status: No Subject: Re: xenbusb_nop_confighook_cb timeout 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: Fri, 28 Jan 2011 01:20:20 -0000 Hi Nick, Would you mind showing me a copy of your dmesg for the XENHVM kernel? I just want to make a comparison with mine. Perhaps this subject may get someone else's attention, otherwise I'll file a PR. :) On 28/01/2011 9:40 AM, Nick Sayer wrote: > On Jan 27, 2011, at 1:29 PM, Alex wrote: > >> I've had that geom warning before on real hardware and it's never stopped it from working. > Ah, well, then never mind. I thought maybe it was germane to the hang. > > I don't know which differences we might have between us that would account for it working for me, but not for you. My machine is GPT+ZFS and it had no trouble transitioning to XENHVT once the "do something smart" panic went away. > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 04:24:20 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 4BD50106564A for ; Fri, 28 Jan 2011 04:24:20 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0C5B28FC0A for ; Fri, 28 Jan 2011 04:24:19 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0S4OIbZ017315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jan 2011 04:24:18 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0S4OIbZ017315 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1296188659; x=1296793459; bh=x+rr38jE5QcPp+ev5uTx8jT2/Kfxbsaq4ZV9v+r1Uck=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=ZSn99QbQsYmDxeI+kWz0UF284WtuHEYgbGRpjZHTdT9LuSZBMTSiMSYfxG/AAk+9A z/bRy6Izh/SRXJvNmkp8YFn5t6Is4L1gv3nMqVeaWx8UwNh5WFDG0JB+/hD9YlLfkH yssUGBe9w5jpg2Bblw7a6cRCZQfRfKA877psX2Tw= Date: Fri, 28 Jan 2011 04:24:18 +0000 (UTC) From: Janne Snabb To: Carsten Heesch In-Reply-To: <0F524D72-3752-47FD-9234-ED009009B0A0@ossafe.org> Message-ID: References: <1295969742.3187.48.camel@pow> <0F524D72-3752-47FD-9234-ED009009B0A0@ossafe.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Fri, 28 Jan 2011 04:24:19 +0000 (UTC) Cc: freebsd-xen@freebsd.org, luke@hybrid-logic.co.uk Subject: Re: 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: Fri, 28 Jan 2011 04:24:20 -0000 On Thu, 27 Jan 2011, Carsten Heesch wrote: > >> int max = 24 /* MAX_SKB_FRAGS + (rx->status <= RX_COPY_THRESHOLD) */; > > I've just recompiled XENHVM setting this for a quick test: > > > int max = MAX_SKB_FRAGS; > > Before, I was receiving said error message a lot; now it's gone. > Also, throughput has massively increased! Good :). > Which would be the right value for max? This was obviously only > a quick, dirty test. I haven't got a clue either, where the max=5 > came from, but it doesn't seem to be a reasonable value. Could you, Luke or Grzegorz send-pr this, and include the following links in the PR? Evidence of several people having this problem and that the problem is indeed caused by incorrect "max" value or the "if (frags > max)" check: http://lists.freebsd.org/pipermail/freebsd-xen/2011-January/000779.html http://lists.freebsd.org/pipermail/freebsd-xen/2011-January/000783.html http://lists.freebsd.org/pipermail/freebsd-xen/2011-January/000784.html Some analysis of the relevant code by myself: http://lists.freebsd.org/pipermail/freebsd-xen/2011-January/000782.html http://lists.freebsd.org/pipermail/freebsd-xen/2011-January/000784.html It looks like all the FreeBSD Xen gurus/committers are busy/quiet currently. It would be good to have a PR on this so that someone who understands this "max" thing could have a look at it at some point even if they do not notice this discussion on this mailing list. The solution is likely to be simple, but it should be made/verified by someone who understands the code and its history. (Removing the "if (frags > max)" check altogether might be the correct solution, but it could also cause panics or other issues under heavy network load in case it is actually something that is needed.) PS. I think the 8.2 release is waiting for Xen fixes before being released. I think the release will not be as good as it could be on Xen. We are a bit late in the release cycle spotting all these problems... probably not enough time to correctly fix all of them given that some of the relevant people are currently busy/inactive. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 04:25:11 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 409D1106564A for ; Fri, 28 Jan 2011 04:25:11 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (kfu-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:e09::2]) by mx1.freebsd.org (Postfix) with ESMTP id D77608FC0C for ; Fri, 28 Jan 2011 04:25:10 +0000 (UTC) Received: from [192.168.5.199] (c-98-234-64-122.hsd1.ca.comcast.net [98.234.64.122]) (authenticated bits=0) by quack.kfu.com (8.14.4/8.14.4) with ESMTP id p0S4P6e4076582 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 27 Jan 2011 20:25:09 -0800 (PST) (envelope-from nsayer@kfu.com) X-DKIM: Sendmail DKIM Filter v2.8.3 quack.kfu.com p0S4P6e4076582 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kfu.com; s=KFU; t=1296188710; bh=tTk+wGeCws1mJrezaZkgrJtA2fsiHP+rXAKxq2XbSR4=; h=From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To: References:Message-Id; b=HoXAiBKfjQK/PxmtI4b+MUcjr8MEfVsioyiyjMfa3BIoamqDkBb8j7UwMcoxptQ+G ATRVxRwoJrAn/hMFb2AmL6CBhd+Y4VHpxwTq6ii7QOBVE6j4MLNG3yyL79q0io5jfo xarAu2BQ8sR3ZmiKbW5AGDIjif6HKWRAtAfpELdc= From: Nick Sayer Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: multipart/mixed; boundary=Apple-Mail-5-53926292 Date: Thu, 27 Jan 2011 20:25:06 -0800 In-Reply-To: <4D420D46.2060600@joovke.com> To: freebsd-xen@freebsd.org References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> <4D420D46.2060600@joovke.com> Message-Id: X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (quack.kfu.com [204.109.60.138]); Thu, 27 Jan 2011 20:25:10 -0800 (PST) Subject: Re: xenbusb_nop_confighook_cb timeout 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: Fri, 28 Jan 2011 04:25:11 -0000 --Apple-Mail-5-53926292 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii NP. It's attached. I have rootbsd's "Omicron" level of VPS. --Apple-Mail-5-53926292 Content-Disposition: attachment; filename=dmesg.txt Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: quoted-printable Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RC2 #7: Fri Jan 21 21:49:44 PST 2011 root@quack.kfu.com:/usr/obj/usr/src/sys/QUACK amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2394.02-MHz = K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x206c2 Family =3D 6 Model =3D 2c = Stepping =3D 2 = Features=3D0x1781fbff Features2=3D0x80982201> AMD Features=3D0x20100800 AMD Features2=3D0x1 TSC: P-state invariant real memory =3D 805306368 (768 MB) avail memory =3D 757047296 (721 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc320-0xc32f at device 1.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] uhci0: port 0xc300-0xc31f irq 23 = at device 1.2 on pci0 uhci0: [ITHREAD] usbus0: controller did not stop usbus0: on uhci0 intsmb0: irq 20 at device 1.3 on pci0 intsmb0: intr IRQ 9 enabled revision 0 intsmb0: [ITHREAD] smbus0: on intsmb0 vgapci0: mem = 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem = 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xs_probe: Probe retuns 0 xenstore0: on xenpci0 atrtc0: port 0x70-0x71 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppc0: [ITHREAD] ppbus0: on ppc0 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 qpi0: on motherboard orm0: at iomem 0xc9000-0xc97ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable = behavior. Consider tuning vm.kmem_size and vm.kmem_size_max in /boot/loader.conf. ZFS filesystem version 4 ZFS storage pool version 15 Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 xenbusb_front0: on xenstore0 ugen0.1: at usbus0 uhub0: on usbus0 xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:2d:5c:32 xn1: at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:67:42:78 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xbd0: 40960MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 SMP: AP CPU #1 Launched! Root mount waiting for: usbus0 uhub0: 2 ports with 2 removable, self powered Root mount waiting for: usbus0 ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=3D0 Trying to mount root from zfs:tank xn0: 2 link states coalesced ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based = forwarding disabled, default to deny, logging disabled load_dn_sched dn_sched FIFO loaded load_dn_sched dn_sched QFQ loaded load_dn_sched dn_sched RR loaded load_dn_sched dn_sched WF2Q+ loaded load_dn_sched dn_sched PRIO loaded --Apple-Mail-5-53926292 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jan 27, 2011, at 4:26 PM, Alex wrote: > Hi Nick, >=20 > Would you mind showing me a copy of your dmesg for the XENHVM kernel? = I just want to make a comparison with mine. >=20 > Perhaps this subject may get someone else's attention, otherwise I'll = file a PR. >=20 > :) > On 28/01/2011 9:40 AM, Nick Sayer wrote: >> On Jan 27, 2011, at 1:29 PM, Alex wrote: >>=20 >>> I've had that geom warning before on real hardware and it's never = stopped it from working. >> Ah, well, then never mind. I thought maybe it was germane to the = hang. >>=20 >> I don't know which differences we might have between us that would = account for it working for me, but not for you. My machine is GPT+ZFS = and it had no trouble transitioning to XENHVT once the "do something = smart" panic went away. >>=20 >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to = "freebsd-xen-unsubscribe@freebsd.org" >>=20 >=20 > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" --Apple-Mail-5-53926292-- From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 07:30:19 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A39A106566C for ; Fri, 28 Jan 2011 07:30:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6FFE48FC1A for ; Fri, 28 Jan 2011 07:30:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0S7UJvE035558 for ; Fri, 28 Jan 2011 07:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0S7UJQv035550; Fri, 28 Jan 2011 07:30:19 GMT (envelope-from gnats) Date: Fri, 28 Jan 2011 07:30:19 GMT Message-Id: <201101280730.p0S7UJQv035550@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Janne Snabb Cc: Subject: Re: kern/154302: First patch is not good X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Janne Snabb 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: Fri, 28 Jan 2011 07:30:19 -0000 The following reply was made to PR kern/154302; it has been noted by GNATS. From: Janne Snabb To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/154302: First patch is not good Date: Fri, 28 Jan 2011 07:26:05 +0000 (UTC) I wanted to add that the 1st patch I provided is not a good idea. It does not take into account that some other error than ENOENT could be returned. The 2nd patch is better. Alternatively it could be split to 2 separate if clauses. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 10:26:58 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 7B289106566B for ; Fri, 28 Jan 2011 10:26:58 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 3516B8FC08 for ; Fri, 28 Jan 2011 10:26:57 +0000 (UTC) Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 84AF4ED0418 for ; Fri, 28 Jan 2011 10:26:43 +0000 (GMT) From: Carsten Heesch Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Jan 2011 10:26:55 +0000 Message-Id: <11769353-E8AD-4CDA-B051-03B156EE6587@ossafe.org> To: freebsd-xen@FreeBSD.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Cc: Subject: Sync performance HAST and ggate/gmirror on Xen 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: Fri, 28 Jan 2011 10:26:58 -0000 Hi guys, Is anybody else using HAST or ggate/gmirror within Xen DomU's?=20 I'm experiencing dreadful performance (sync throughput less than = 1MB/sec) with both replication options, and am not quite sure how to = troubleshoot that, because the network speed between two DomU's is = otherwise well beyond 50MB/sec.=20 Logfiles and dmesg don't give any pointers, tcpdump looks clean (no = bouncing packets, wrong order etc), no collisions or packet loss either = (according to netstat). Anyone else experiencing similar problems? Test setup: 2x FreeBSD/amd64 8.2-RC2 (compiled about a week ago), XENHVM kernel = (with Janne's patch). Both DomU's are running on the same physical machine (CentOS 5.5 x86_64 = with Xen 4.3.3 on Intel i7), their NICs are using the same isolated = bridge on Dom0. Cheers Carsten Regards, Carsten Heesch carsten@heesch.me.uk mob: +44 7889 129998 From owner-freebsd-xen@FreeBSD.ORG Fri Jan 28 10:37:37 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 3BA09106566B for ; Fri, 28 Jan 2011 10:37:37 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 081DF8FC16 for ; Fri, 28 Jan 2011 10:37:36 +0000 (UTC) Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id AC358ED0418; Fri, 28 Jan 2011 10:37:22 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Carsten Heesch In-Reply-To: <11769353-E8AD-4CDA-B051-03B156EE6587@ossafe.org> Date: Fri, 28 Jan 2011 10:37:34 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <9D076804-6466-4302-B8FD-2176486AE763@ossafe.org> References: <11769353-E8AD-4CDA-B051-03B156EE6587@ossafe.org> To: Carsten Heesch X-Mailer: Apple Mail (2.1082) Cc: freebsd-xen@FreeBSD.org Subject: Re: Sync performance HAST and ggate/gmirror on Xen 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: Fri, 28 Jan 2011 10:37:37 -0000 >=20 > Both DomU's are running on the same physical machine (CentOS 5.5 = x86_64 with Xen 4.3.3 on Intel i7), [...] sorry, typo: Xen 3.4.3, not 4.3.3. Cheers C. From owner-freebsd-xen@FreeBSD.ORG Sat Jan 29 00:03:10 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 63E7C1065672 for ; Sat, 29 Jan 2011 00:03:10 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id F3CD18FC15 for ; Sat, 29 Jan 2011 00:03:09 +0000 (UTC) Received: from [192.168.4.138] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p0SNR2pi052536 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 28 Jan 2011 16:27:03 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D4350C2.6050806@FreeBSD.org> Date: Fri, 28 Jan 2011 16:26:58 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110123 Thunderbird/3.1.8 MIME-Version: 1.0 To: Alex References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> In-Reply-To: <4D41E3D1.7040100@joovke.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Fri, 28 Jan 2011 16:27:03 -0700 (MST) Cc: freebsd-xen@FreeBSD.org Subject: Re: xenbusb_nop_confighook_cb timeout X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org 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: Sat, 29 Jan 2011 00:03:10 -0000 On 1/27/2011 2:29 PM, Alex wrote: > I've had that geom warning before on real hardware and it's never > stopped it from working. > > In my screenshot, it appears the time out is originating from: > > xenbusb.c:xenbusb_nop_confighook_cb This means that one of the PV devices is not transitioning into either the Connected or Closed state. Can you provide the output of "xenstore-ls" from your DOM0 to me privately so I can help you track this down? Thanks, Justin From owner-freebsd-xen@FreeBSD.ORG Sat Jan 29 19:59:24 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 6F050106566B for ; Sat, 29 Jan 2011 19:59:24 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 380BC8FC0C for ; Sat, 29 Jan 2011 19:59:23 +0000 (UTC) Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id DF74EED0418; Sat, 29 Jan 2011 19:59:08 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Carsten Heesch In-Reply-To: <11769353-E8AD-4CDA-B051-03B156EE6587@ossafe.org> Date: Sat, 29 Jan 2011 19:59:21 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <0C44C35C-6D64-4E37-BBEA-DB3BC63CC465@ossafe.org> References: <11769353-E8AD-4CDA-B051-03B156EE6587@ossafe.org> To: Carsten Heesch X-Mailer: Apple Mail (2.1082) Cc: freebsd-xen@FreeBSD.org Subject: Re: Sync performance HAST and ggate/gmirror on Xen 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: Sat, 29 Jan 2011 19:59:24 -0000 > I'm experiencing dreadful performance (sync throughput less than = 1MB/sec) with both replication options, and am not quite sure how to = troubleshoot that, because the network speed between two DomU's is = otherwise well beyond 50MB/sec.=20 Have done some further testing. This only happens with amd64/XENHVM (xen = network driver). Generic amd64 kernels (re network driver) work just = fine, although the network driver seems to be a little bit slower.=20 Cheers C.