From owner-freebsd-xen@FreeBSD.ORG Mon May 18 13:07:00 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F35C870 for ; Mon, 18 May 2015 13:07:00 +0000 (UTC) Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mx144.netapp.com", Issuer "VeriSign Class 3 International Server CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B0CB1546 for ; Mon, 18 May 2015 13:07:00 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,453,1427785200"; d="asc'?scan'208";a="43513595" Received: from hioexcmbx06-prd.hq.netapp.com ([10.122.105.39]) by mx144-out.netapp.com with ESMTP; 18 May 2015 06:04:13 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx06-prd.hq.netapp.com (10.122.105.39) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 18 May 2015 06:04:13 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com ([fe80::7ce8:9818:3705:3318]) by hioexcmbx07-prd.hq.netapp.com ([fe80::7ce8:9818:3705:3318%21]) with mapi id 15.00.1076.000; Mon, 18 May 2015 06:04:13 -0700 From: "Eggert, Lars" To: "freebsd-xen@freebsd.org" Subject: Xen dom0 crash Thread-Topic: Xen dom0 crash Thread-Index: AQHQkWsjcu7mjDGrw0On15/NPp9POg== Date: Mon, 18 May 2015 13:04:13 +0000 Message-ID: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.2100) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.122.56.79] Content-Type: multipart/signed; boundary="Apple-Mail=_F5F43370-B0F4-4E59-B81A-9A156F6420C5"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 13:07:00 -0000 --Apple-Mail=_F5F43370-B0F4-4E59-B81A-9A156F6420C5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen = crashes when starting the kernel. Log below; any ideas? Thanks, Lars = B2 ______ ____ _____ _____ | ____| | _ \ / ____| __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | | | | | __/ __/| |_) |____) | |__| | | | | | | | || | | |_| |_| \___|\___||____/|_____/|_____/ ``` = ` s` `.....---.......--.``` = -/ + Welcome to FreeBSD +4H+ .--` /y:` = +. /boot/kernel/cc_vegas.ko size 0x30d0 at 0x1068000:. :o = `+- Booting...el/cc_hd.ko size 0x2c00 at 0x1062000000 -/` = -o/ Xen 4.6-unstabletcp.ko size 0x2f90 at 0x1065000 = ::/sy+:. (XEN) Xen version 4.6-unstable (root@netapp.com) (gcc47 (FreeBSD Ports = Collection) 4.7.4) debug=3Dy Mon May 18 14:50:17 CEST 2015 = :` (XEN) Latest ChangeSet: | `: = :` (XEN) Bootloader: FreeBSD Loader | / = / (XEN) Command line: dom0_mem=3D4096M dom0pvh=3D1 com1=3D115200,8n1 = console=3Dcom1. (XEN) Video information:]ptions... | -- = -. (XEN) VGA is text mode 80x25, font 8x16 | `:` `:` (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds `--. (XEN) EDID info not retrieved because no DDC retrieval method = detected=3D=3D=3D=3D=3D=3D=3D=3D=3D(XEN) Disc = information:=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (XEN) Found 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) Xen-e820 RAM map:+0x50db0 - (XEN) 0000000000000000 - 000000000008b800 (usable) (XEN) 000000000008b800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007cb09000 (usable) (XEN) 000000007cb09000 - 000000007cb39000 (reserved) (XEN) 000000007cb39000 - 000000007cc52000 (ACPI data) (XEN) 000000007cc52000 - 000000007d4b0000 (ACPI NVS) (XEN) 000000007d4b0000 - 000000007eafb000 (reserved) (XEN) 000000007eafb000 - 000000007eafc000 (usable) (XEN) 000000007eafc000 - 000000007eb82000 (ACPI NVS) (XEN) 000000007eb82000 - 000000007f000000 (usable) (XEN) 0000000080000000 - 0000000090000000 (reserved) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000002080000000 (usable) (XEN) ACPI: RSDP 000F04A0, 0024 (r2 FTS ) (XEN) ACPI: XSDT 7CB71090, 00A4 (r1 FTS D2939-B1 1072009 AMI = 10013) (XEN) ACPI: FACP 7CB7FAA8, 010C (r5 FTS D2939-B1 1072009 AMI = 10013) (XEN) ACPI: DSDT 7CB711C8, E8DD (r2 FTS D2939-B1 114 INTL = 20091112) (XEN) ACPI: FACS 7D4A7080, 0040 (XEN) ACPI: APIC 7CB7FBB8, 0294 (r3 FTS D2939-B1 1072009 AMI = 10013) (XEN) ACPI: FPDT 7CB7FE50, 0044 (r1 FTS D2939-B1 1072009 AMI = 10013) (XEN) ACPI: MCFG 7CB7FE98, 003C (r1 FTS OEMMCFG. 1072009 MSFT = 97) (XEN) ACPI: SRAT 7CB7FED8, 0530 (r1 A M I AMI SRAT 1 AMI. = 0) (XEN) ACPI: SLIT 7CB80408, 0030 (r1 A M I AMI SLIT 0 AMI. = 0) (XEN) ACPI: HPET 7CB80438, 0038 (r1 FTS D2939-B1 1072009 AMI. = 5) (XEN) ACPI: PRAD 7CB80470, 00BE (r2 PRADID PRADTID 1 MSFT = 3000001) (XEN) ACPI: SPMI 7CB80530, 0040 (r5 A M I OEMSPMI 0 AMI. = 0) (XEN) ACPI: SSDT 7CB80570, D0CB0 (r2 INTEL CpuPm 4000 INTL = 20051117) (XEN) ACPI: SPCR 7CC51220, 0050 (r1 A M I APTIO4 1072009 AMI. = 5) (XEN) ACPI: EINJ 7CC51270, 0130 (r1 AMI AMI EINJ 0 = 0) (XEN) ACPI: ERST 7CC513A0, 0230 (r1 AMIER AMI ERST 0 = 0) (XEN) ACPI: HEST 7CC515D0, 00A8 (r1 AMI AMI HEST 0 = 0) (XEN) ACPI: BERT 7CC51678, 0030 (r1 AMI AMI BERT 0 = 0) (XEN) ACPI: DMAR 7CC516A8, 0110 (r1 A M I OEMDMAR 1 INTL = 1) (XEN) System RAM: 131023MB (134167628kB) (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 2 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 3 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 4 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 5 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 6 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 7 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 8 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 9 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 16 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 17 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 18 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 19 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 20 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 21 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 22 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 23 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 24 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 25 -> Node 0 (XEN) SRAT: PXM 1 -> APIC 32 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 33 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 34 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 35 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 36 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 37 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 38 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 39 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 40 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 41 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 48 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 49 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 50 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 51 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 52 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 53 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 54 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 55 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 56 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 57 -> Node 1 (XEN) SRAT: Node 0 PXM 0 0-80000000 (XEN) SRAT: Node 0 PXM 0 100000000-1080000000 (XEN) SRAT: Node 1 PXM 1 1080000000-2080000000 (XEN) NUMA: Allocated memnodemap from 207f338000 - 207f339000 (XEN) NUMA: Using 19 for the hash shift. (XEN) Domain heap initialised DMA width 32 bits (XEN) found SMP MP-table at 000fdbe0 (XEN) DMI 2.7 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x408 (XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0] (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - = 7d4a7080/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[7d4a708c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) Processor #2 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) (XEN) Processor #4 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled) (XEN) Processor #6 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled) (XEN) Processor #8 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x10] enabled) (XEN) Processor #16 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x12] enabled) (XEN) Processor #18 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x14] enabled) (XEN) Processor #20 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x16] enabled) (XEN) Processor #22 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x18] enabled) (XEN) Processor #24 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x20] enabled) (XEN) Processor #32 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x22] enabled) (XEN) Processor #34 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x24] enabled) (XEN) Processor #36 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x26] enabled) (XEN) Processor #38 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x28] enabled) (XEN) Processor #40 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x30] enabled) (XEN) Processor #48 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x32] enabled) (XEN) Processor #50 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x22] lapic_id[0x34] enabled) (XEN) Processor #52 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x24] lapic_id[0x36] enabled) (XEN) Processor #54 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x26] lapic_id[0x38] enabled) (XEN) Processor #56 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) (XEN) Processor #3 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) (XEN) Processor #5 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) (XEN) Processor #7 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled) (XEN) Processor #9 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x11] enabled) (XEN) Processor #17 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x13] enabled) (XEN) Processor #19 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x15] enabled) (XEN) Processor #21 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x17] enabled) (XEN) Processor #23 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x19] enabled) (XEN) Processor #25 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x21] enabled) (XEN) Processor #33 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x23] enabled) (XEN) Processor #35 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x25] enabled) (XEN) Processor #37 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x27] enabled) (XEN) Processor #39 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x29] enabled) (XEN) Processor #41 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x31] enabled) (XEN) Processor #49 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x21] lapic_id[0x33] enabled) (XEN) Processor #51 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x23] lapic_id[0x35] enabled) (XEN) Processor #53 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x25] lapic_id[0x37] enabled) (XEN) Processor #55 7:14 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x27] lapic_id[0x39] enabled) (XEN) Processor #57 7:14 APIC version 21 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1c] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1e] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x20] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x22] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x24] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x26] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1d] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x1f] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x21] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x23] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x25] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x27] high edge lint[0x1]) (XEN) Overriding APIC driver with bigsmp (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x02] address[0xfec01000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47 (XEN) ACPI: IOAPIC (id[0x03] address[0xfec40000] gsi_base[48]) (XEN) IOAPIC[2]: apic_id 3, version 32, address 0xfec40000, GSI 48-71 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) Xen ERST support is initialized. (XEN) HEST: Table parsing has been initialized (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 40 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 72 GSI, 7624 MSI/MSI-X (XEN) Switched to APIC driver x2apic_cluster. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2800.090 MHz processor. (XEN) Initing memory sharing. (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) mce_intel.c:735: MCA Capability: BCAST 1 SER 1 CMCI 1 firstbank 0 = extended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) alt table ffff82d0802deab0 -> ffff82d0802dfd40 (XEN) PCI: MCFG configuration 0: base 80000000 segment 0000 buses 00 - = ff (XEN) PCI: MCFG area at 80000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-ff (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=3D0xF0 apic1=3D0 pin1=3D2 apic2=3D-1 pin2=3D-1 (XEN) TSC deadline timer enabled (XEN) Platform timer is 14.318MHz HPET (XEN) Defaulting to alternative key handling; send 'A' to switch to = normal mode. (XEN) Allocated console ring of 512 KiB. (XEN) mwait-idle: MWAIT substates: 0x1120 (XEN) mwait-idle: v0.4 model 0x3e (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - APIC Register Virtualization (XEN) - Virtual Interrupt Delivery (XEN) - Posted Interrupt Processing (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Brought up 40 CPUs (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 1224 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=3D0xffffffff80200000 memsz=3D0x99d3f0 (XEN) elf_parse_binary: phdr: paddr=3D0xffffffff80d9d3f0 memsz=3D0x3d71f8 (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff811745e8 (XEN) elf_xen_parse_note: GUEST_OS =3D "FreeBSD" (XEN) elf_xen_parse_note: GUEST_VERSION =3D "0x10c929" (XEN) elf_xen_parse_note: XEN_VERSION =3D "xen-3.0" (XEN) elf_xen_parse_note: VIRT_BASE =3D 0xffffffff80000000 (XEN) elf_xen_parse_note: PADDR_OFFSET =3D 0xffffffff80000000 (XEN) elf_xen_parse_note: ENTRY =3D 0xffffffff80854000 (XEN) elf_xen_parse_note: HYPERCALL_PAGE =3D 0xffffffff80853000 (XEN) elf_xen_parse_note: HV_START_LOW =3D 0xffff800000000000 (XEN) elf_xen_parse_note: FEATURES =3D = "writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel= |hvm_callback_vector" (XEN) elf_xen_parse_note: PAE_MODE =3D "yes" (XEN) elf_xen_parse_note: unknown xen elf note (0xd) (XEN) elf_xen_parse_note: LOADER =3D "generic" (XEN) elf_xen_parse_note: SUSPEND_CANCEL =3D 0x0 (XEN) elf_xen_parse_note: BSD_SYMTAB =3D "yes" (XEN) elf_xen_parse: using notes from SHT_NOTE section (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base =3D 0xffffffff80000000 (XEN) elf_paddr_offset =3D 0xffffffff80000000 (XEN) virt_offset =3D 0x0 (XEN) virt_kstart =3D 0xffffffff80200000 (XEN) virt_kend =3D 0xffffffff8135e110 (XEN) virt_entry =3D 0xffffffff80854000 (XEN) p2m_base =3D 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0xffffffff80200000 -> = 0xffffffff811745e8 (XEN) Dom0 symbol map 0xffffffff811745e8 -> 0xffffffff8135e110 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000001030000000->0000001032000000 (1040320 pages = to be allocated) (XEN) Init. ramdisk: 000000207ffc0000->0000002080000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff8135e110 (XEN) Init. ramdisk: ffffffff8135f000->ffffffff8139f000 (XEN) Phys-Mach map: ffffffff8139f000->ffffffff81b9f000 (XEN) Start info: ffffffff81b9f000->ffffffff81ba04b4 (XEN) Page tables: ffffffff81ba1000->ffffffff81bb4000 (XEN) Boot stack: ffffffff81bb4000->ffffffff81bb5000 (XEN) TOTAL: ffffffff80000000->ffffffff82000000 (XEN) ENTRY ADDRESS: ffffffff80854000 (XEN) Dom0 has maximum 40 VCPUs (XEN) elf_load_binary: phdr 2 at 0xffffffff80200000 -> = 0xffffffff80b9d3f0 (XEN) elf_load_binary: phdr 3 at 0xffffffff80d9d3f0 -> = 0xffffffff80e487b8 (XEN) elf_load_bsdsyms: shdr 4 at 0xffff83207f3a4b70 -> = 0xffffffff81174f70 (XEN) elf_load_bsdsyms: shdr 34 at 0xffff83207fe11b65 -> = 0xffffffff811b0c48 (XEN) elf_load_bsdsyms: shdr 35 at 0xffff83207fe12670 -> = 0xffffffff811b0e10 (XEN) elf_load_bsdsyms: shdr 36 at 0xffff83207feeb4c8 -> = 0xffffffff81289c68 (XEN) Masked VT-d error signaling on 0000:00:05.0 (XEN) Masked VT-d error signaling on 0000:80:05.0 (XEN) Scrubbing Free RAM on 2 nodes using 20 CPUs (XEN) .....................................................done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch = input to Xen) (XEN) Freed 304kB init memory. (XEN) error code 7 (XEN) domain_crash_sync called from vmcs.c:1547 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.6-unstable x86_64 debug=3Dy Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0000:[] (XEN) RFLAGS: 0000000000000200 CONTEXT: hvm guest (d0v0) (XEN) rax: 0000000000000000 rbx: ffff82d0802e8000 rcx: = ffff82d0802eff80 (XEN) rdx: ffff82d0801e1500 rsi: 0000000000000000 rdi: = ffff82d0801ed77c (XEN) rbp: ffff82d0801061d2 rsp: ffffffff81bb5000 r8: = ffff83103ff00000 (XEN) r9: ffff82d08010623f r10: ffff82d0802eff70 r11: = 0000000000000000 (XEN) r12: ffff82d0802eff50 r13: ffff831033ae7000 r14: = ffff83103ff00000 (XEN) r15: ffff82d08018eae3 cr0: 0000000080000011 cr4: = 0000000000000020 (XEN) cr3: 0000000001ba1000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000 (XEN) Guest stack trace from rsp=3Dffffffff81bb5000: (XEN) Fault while accessing guest memory. (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. --Apple-Mail=_F5F43370-B0F4-4E59-B81A-9A156F6420C5 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlVZ40wACgkQIWcjmsUTWRrjXACgqcrfehr6rVypCM384IdhCX7D 6VMAniH+N5Gk1yUMau7LUHyixy8CsGbN =hyMI -----END PGP SIGNATURE----- --Apple-Mail=_F5F43370-B0F4-4E59-B81A-9A156F6420C5-- From owner-freebsd-xen@FreeBSD.ORG Mon May 18 13:07:00 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5375386F for ; Mon, 18 May 2015 13:07:00 +0000 (UTC) Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mx144.netapp.com", Issuer "VeriSign Class 3 International Server CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 076B01543 for ; Mon, 18 May 2015 13:06:59 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,453,1427785200"; d="asc'?scan'208";a="43512995" Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx144-out.netapp.com with ESMTP; 18 May 2015 06:01:42 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 18 May 2015 06:01:42 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com ([fe80::7ce8:9818:3705:3318]) by hioexcmbx07-prd.hq.netapp.com ([fe80::7ce8:9818:3705:3318%21]) with mapi id 15.00.1076.000; Mon, 18 May 2015 06:01:42 -0700 From: "Eggert, Lars" To: =?utf-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Topic: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Index: AQHQjVWqWfmhKLLkCEyxYLJkTsnG9Z16D22AgABSLoCAABHdgIAC8pqAgAAB7QCAAAZOAIAAH08AgAAEc4CAAAFDAIAAAhCAgAAdtwCABH0lgA== Date: Mon, 18 May 2015 13:01:42 +0000 Message-ID: References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <5553651D.3000400@citrix.com> <5555DFBC.9030306@citrix.com> <683335F9-E04E-4F8C-B1EF-0047E63E00AD@netapp.com> <5555FF4A.8010702@citrix.com> <126FDC37-2822-45DB-9AA6-3C9A03D89959@netapp.com> <55560414.1040002@citrix.com> <91758942-3683-42E5-9B39-66775E48D4DF@netapp.com> <55561EBC.8080901@citrix.com> In-Reply-To: <55561EBC.8080901@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.2100) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.122.56.79] Content-Type: multipart/signed; boundary="Apple-Mail=_709C820E-8519-42EF-9311-89D121691A54"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 13:07:00 -0000 --Apple-Mail=_709C820E-8519-42EF-9311-89D121691A54 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Unfortunately, the storm is still there with this patch. On 2015-5-15, at 18:28, Roger Pau Monn=C3=A9 = wrote: >=20 > El 15/05/15 a les 16.42, Eggert, Lars ha escrit: >> On 2015-5-15, at 16:35, Roger Pau Monn=C3=A9 = wrote: >>>=20 >>> Yes, but I've realized that isci for example passes an uint32_t = instead >>> of an int, so it might be best to set it to 0. >>=20 >> Here is what I see now: >>=20 >> isci0: port = 0x6000-0x60ff mem 0xde07c000-0xde07ffff,0xddc00000-0xddffffff irq 16 at = device 0.0 on pci10 >> isci0: attempting to allocate 2 MSI-X vectors (2 supported) >> ISCI: isci->num_interrupts: 2 max_msix_messages: 2 >> isci: 1:000089 ISCI bus_alloc_resource failed >>=20 >> The storm is still there. >=20 > Yes, after looking at the code, isci really needs to check for the > return value of pci_alloc_msix, because num_interrupts is not updated > if the allocation fails. Following patch should hopefully fix it, > please give it a try. >=20 > Roger. > --- > diff --git a/sys/dev/isci/isci_interrupt.c = b/sys/dev/isci/isci_interrupt.c > index 52c64f7..f331f3c 100644 > --- a/sys/dev/isci/isci_interrupt.c > +++ b/sys/dev/isci/isci_interrupt.c > @@ -128,6 +128,7 @@ isci_interrupt_setup(struct isci_softc *isci) > isci->controller_count; > BOOL use_msix =3D FALSE; > uint32_t force_legacy_interrupts =3D 0; > + int rc; >=20 > TUNABLE_INT_FETCH("hw.isci.force_legacy_interrupts", > &force_legacy_interrupts); > @@ -136,8 +137,8 @@ isci_interrupt_setup(struct isci_softc *isci) > pci_msix_count(isci->device) >=3D max_msix_messages) { >=20 > isci->num_interrupts =3D max_msix_messages; > - pci_alloc_msix(isci->device, &isci->num_interrupts); > - if (isci->num_interrupts =3D=3D max_msix_messages) > + rc =3D pci_alloc_msix(isci->device, = &isci->num_interrupts); > + if (rc =3D=3D 0 && isci->num_interrupts =3D=3D = max_msix_messages) > use_msix =3D TRUE; > } >=20 >=20 --Apple-Mail=_709C820E-8519-42EF-9311-89D121691A54 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlVZ4rUACgkQIWcjmsUTWRpazQCg6Uj2qikfibX7reKmSLK1y/72 +MAAoMKpl+R6KkQXCs6w8fQSnALz4QFt =0UeO -----END PGP SIGNATURE----- --Apple-Mail=_709C820E-8519-42EF-9311-89D121691A54-- From owner-freebsd-xen@FreeBSD.ORG Mon May 18 13:38:33 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B4D51E5 for ; Mon, 18 May 2015 13:38:33 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E30B31951 for ; Mon, 18 May 2015 13:38:31 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,453,1427760000"; d="scan'208";a="263623593" Message-ID: <5559EB2E.6080609@citrix.com> Date: Mon, 18 May 2015 15:37:50 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Eggert, Lars" , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> In-Reply-To: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 13:38:33 -0000 El 18/05/15 a les 15.04, Eggert, Lars ha escrit: > Hi, > > I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen crashes when starting the kernel. Log below; any ideas? > > Thanks, > Lars > > > B2 > ______ ____ _____ _____ > | ____| | _ \ / ____| __ \ > | |___ _ __ ___ ___ | |_) | (___ | | | | > | ___| '__/ _ \/ _ \| _ < \___ \| | | | > | | | | | __/ __/| |_) |____) | |__| | > | | | | | | || | | > |_| |_| \___|\___||____/|_____/|_____/ ``` ` > s` `.....---.......--.``` -/ > + Welcome to FreeBSD +4H+ .--` /y:` +. > /boot/kernel/cc_vegas.ko size 0x30d0 at 0x1068000:. :o `+- > Booting...el/cc_hd.ko size 0x2c00 at 0x1062000000 -/` -o/ > Xen 4.6-unstabletcp.ko size 0x2f90 at 0x1065000 ::/sy+:. > (XEN) Xen version 4.6-unstable (root@netapp.com) (gcc47 (FreeBSD Ports Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015 :` > (XEN) Latest ChangeSet: | `: :` > (XEN) Bootloader: FreeBSD Loader | / / > (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1. > (XEN) Video information:]ptions... | -- -. > (XEN) VGA is text mode 80x25, font 8x16 | `:` `:` > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds `--. > (XEN) EDID info not retrieved because no DDC retrieval method detected=========(XEN) Disc information:==================== > (XEN) Found 0 MBR signatures > (XEN) Found 0 EDD information structures > (XEN) Xen-e820 RAM map:+0x50db0 - > (XEN) 0000000000000000 - 000000000008b800 (usable) > (XEN) 000000000008b800 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007cb09000 (usable) > (XEN) 000000007cb09000 - 000000007cb39000 (reserved) > (XEN) 000000007cb39000 - 000000007cc52000 (ACPI data) > (XEN) 000000007cc52000 - 000000007d4b0000 (ACPI NVS) > (XEN) 000000007d4b0000 - 000000007eafb000 (reserved) > (XEN) 000000007eafb000 - 000000007eafc000 (usable) > (XEN) 000000007eafc000 - 000000007eb82000 (ACPI NVS) > (XEN) 000000007eb82000 - 000000007f000000 (usable) > (XEN) 0000000080000000 - 0000000090000000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000002080000000 (usable) > (XEN) ACPI: RSDP 000F04A0, 0024 (r2 FTS ) > (XEN) ACPI: XSDT 7CB71090, 00A4 (r1 FTS D2939-B1 1072009 AMI 10013) > (XEN) ACPI: FACP 7CB7FAA8, 010C (r5 FTS D2939-B1 1072009 AMI 10013) > (XEN) ACPI: DSDT 7CB711C8, E8DD (r2 FTS D2939-B1 114 INTL 20091112) > (XEN) ACPI: FACS 7D4A7080, 0040 > (XEN) ACPI: APIC 7CB7FBB8, 0294 (r3 FTS D2939-B1 1072009 AMI 10013) > (XEN) ACPI: FPDT 7CB7FE50, 0044 (r1 FTS D2939-B1 1072009 AMI 10013) > (XEN) ACPI: MCFG 7CB7FE98, 003C (r1 FTS OEMMCFG. 1072009 MSFT 97) > (XEN) ACPI: SRAT 7CB7FED8, 0530 (r1 A M I AMI SRAT 1 AMI. 0) > (XEN) ACPI: SLIT 7CB80408, 0030 (r1 A M I AMI SLIT 0 AMI. 0) > (XEN) ACPI: HPET 7CB80438, 0038 (r1 FTS D2939-B1 1072009 AMI. 5) > (XEN) ACPI: PRAD 7CB80470, 00BE (r2 PRADID PRADTID 1 MSFT 3000001) > (XEN) ACPI: SPMI 7CB80530, 0040 (r5 A M I OEMSPMI 0 AMI. 0) > (XEN) ACPI: SSDT 7CB80570, D0CB0 (r2 INTEL CpuPm 4000 INTL 20051117) > (XEN) ACPI: SPCR 7CC51220, 0050 (r1 A M I APTIO4 1072009 AMI. 5) > (XEN) ACPI: EINJ 7CC51270, 0130 (r1 AMI AMI EINJ 0 0) > (XEN) ACPI: ERST 7CC513A0, 0230 (r1 AMIER AMI ERST 0 0) > (XEN) ACPI: HEST 7CC515D0, 00A8 (r1 AMI AMI HEST 0 0) > (XEN) ACPI: BERT 7CC51678, 0030 (r1 AMI AMI BERT 0 0) > (XEN) ACPI: DMAR 7CC516A8, 0110 (r1 A M I OEMDMAR 1 INTL 1) > (XEN) System RAM: 131023MB (134167628kB) > (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 2 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 3 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 4 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 5 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 6 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 7 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 8 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 9 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 16 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 17 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 18 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 19 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 20 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 21 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 22 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 23 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 24 -> Node 0 > (XEN) SRAT: PXM 0 -> APIC 25 -> Node 0 > (XEN) SRAT: PXM 1 -> APIC 32 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 33 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 34 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 35 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 36 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 37 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 38 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 39 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 40 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 41 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 48 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 49 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 50 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 51 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 52 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 53 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 54 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 55 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 56 -> Node 1 > (XEN) SRAT: PXM 1 -> APIC 57 -> Node 1 > (XEN) SRAT: Node 0 PXM 0 0-80000000 > (XEN) SRAT: Node 0 PXM 0 100000000-1080000000 > (XEN) SRAT: Node 1 PXM 1 1080000000-2080000000 > (XEN) NUMA: Allocated memnodemap from 207f338000 - 207f339000 > (XEN) NUMA: Using 19 for the hash shift. > (XEN) Domain heap initialised DMA width 32 bits > (XEN) found SMP MP-table at 000fdbe0 > (XEN) DMI 2.7 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x408 > (XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0] > (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0] > (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7d4a7080/0000000000000000, using 32 > (XEN) ACPI: wakeup_vec[7d4a708c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > (XEN) Processor #0 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > (XEN) Processor #2 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) > (XEN) Processor #4 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled) > (XEN) Processor #6 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled) > (XEN) Processor #8 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x10] enabled) > (XEN) Processor #16 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x12] enabled) > (XEN) Processor #18 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x14] enabled) > (XEN) Processor #20 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x16] enabled) > (XEN) Processor #22 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x18] enabled) > (XEN) Processor #24 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x20] enabled) > (XEN) Processor #32 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x22] enabled) > (XEN) Processor #34 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x24] enabled) > (XEN) Processor #36 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x26] enabled) > (XEN) Processor #38 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x28] enabled) > (XEN) Processor #40 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x30] enabled) > (XEN) Processor #48 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x32] enabled) > (XEN) Processor #50 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x22] lapic_id[0x34] enabled) > (XEN) Processor #52 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x24] lapic_id[0x36] enabled) > (XEN) Processor #54 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x26] lapic_id[0x38] enabled) > (XEN) Processor #56 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > (XEN) Processor #1 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) > (XEN) Processor #3 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) > (XEN) Processor #5 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) > (XEN) Processor #7 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled) > (XEN) Processor #9 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x11] enabled) > (XEN) Processor #17 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x13] enabled) > (XEN) Processor #19 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x15] enabled) > (XEN) Processor #21 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x17] enabled) > (XEN) Processor #23 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x19] enabled) > (XEN) Processor #25 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x21] enabled) > (XEN) Processor #33 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x23] enabled) > (XEN) Processor #35 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x25] enabled) > (XEN) Processor #37 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x27] enabled) > (XEN) Processor #39 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x29] enabled) > (XEN) Processor #41 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x31] enabled) > (XEN) Processor #49 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x21] lapic_id[0x33] enabled) > (XEN) Processor #51 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x23] lapic_id[0x35] enabled) > (XEN) Processor #53 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x25] lapic_id[0x37] enabled) > (XEN) Processor #55 7:14 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x27] lapic_id[0x39] enabled) > (XEN) Processor #57 7:14 APIC version 21 > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1c] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1e] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x20] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x22] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x24] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x26] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1d] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x1f] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x21] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x23] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x25] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x27] high edge lint[0x1]) > (XEN) Overriding APIC driver with bigsmp > (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: IOAPIC (id[0x02] address[0xfec01000] gsi_base[24]) > (XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47 > (XEN) ACPI: IOAPIC (id[0x03] address[0xfec40000] gsi_base[48]) > (XEN) IOAPIC[2]: apic_id 3, version 32, address 0xfec40000, GSI 48-71 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs > (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 > (XEN) Xen ERST support is initialized. > (XEN) HEST: Table parsing has been initialized > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) SMP: Allowing 40 CPUs (0 hotplug CPUs) > (XEN) IRQ limits: 72 GSI, 7624 MSI/MSI-X > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2800.090 MHz processor. > (XEN) Initing memory sharing. > (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 > (XEN) mce_intel.c:735: MCA Capability: BCAST 1 SER 1 CMCI 1 firstbank 0 extended MCE MSR 0 > (XEN) Intel machine check reporting enabled > (XEN) alt table ffff82d0802deab0 -> ffff82d0802dfd40 > (XEN) PCI: MCFG configuration 0: base 80000000 segment 0000 buses 00 - ff > (XEN) PCI: MCFG area at 80000000 reserved in E820 > (XEN) PCI: Using MCFG for segment 0000 bus 00-ff > (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. > (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. > (XEN) Intel VT-d Snoop Control enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Shared EPT tables enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Interrupt remapping enabled > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) TSC deadline timer enabled > (XEN) Platform timer is 14.318MHz HPET > (XEN) Defaulting to alternative key handling; send 'A' to switch to normal mode. > (XEN) Allocated console ring of 512 KiB. > (XEN) mwait-idle: MWAIT substates: 0x1120 > (XEN) mwait-idle: v0.4 model 0x3e > (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) - APIC Register Virtualization > (XEN) - Virtual Interrupt Delivery > (XEN) - Posted Interrupt Processing > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > (XEN) Brought up 40 CPUs > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) Dom0 has maximum 1224 PIRQs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x99d3f0 > (XEN) elf_parse_binary: phdr: paddr=0xffffffff80d9d3f0 memsz=0x3d71f8 > (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff811745e8 > (XEN) elf_xen_parse_note: GUEST_OS = "FreeBSD" > (XEN) elf_xen_parse_note: GUEST_VERSION = "0x10c929" > (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" > (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 > (XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000 > (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80854000 > (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80853000 > (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 > (XEN) elf_xen_parse_note: FEATURES = "writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel|hvm_callback_vector" > (XEN) elf_xen_parse_note: PAE_MODE = "yes" > (XEN) elf_xen_parse_note: unknown xen elf note (0xd) > (XEN) elf_xen_parse_note: LOADER = "generic" > (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x0 > (XEN) elf_xen_parse_note: BSD_SYMTAB = "yes" > (XEN) elf_xen_parse: using notes from SHT_NOTE section > (XEN) elf_xen_addr_calc_check: addresses: > (XEN) virt_base = 0xffffffff80000000 > (XEN) elf_paddr_offset = 0xffffffff80000000 > (XEN) virt_offset = 0x0 > (XEN) virt_kstart = 0xffffffff80200000 > (XEN) virt_kend = 0xffffffff8135e110 > (XEN) virt_entry = 0xffffffff80854000 > (XEN) p2m_base = 0xffffffffffffffff > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0xffffffff80200000 -> 0xffffffff811745e8 > (XEN) Dom0 symbol map 0xffffffff811745e8 -> 0xffffffff8135e110 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000001030000000->0000001032000000 (1040320 pages to be allocated) > (XEN) Init. ramdisk: 000000207ffc0000->0000002080000000 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff8135e110 > (XEN) Init. ramdisk: ffffffff8135f000->ffffffff8139f000 > (XEN) Phys-Mach map: ffffffff8139f000->ffffffff81b9f000 > (XEN) Start info: ffffffff81b9f000->ffffffff81ba04b4 > (XEN) Page tables: ffffffff81ba1000->ffffffff81bb4000 > (XEN) Boot stack: ffffffff81bb4000->ffffffff81bb5000 > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > (XEN) ENTRY ADDRESS: ffffffff80854000 > (XEN) Dom0 has maximum 40 VCPUs > (XEN) elf_load_binary: phdr 2 at 0xffffffff80200000 -> 0xffffffff80b9d3f0 > (XEN) elf_load_binary: phdr 3 at 0xffffffff80d9d3f0 -> 0xffffffff80e487b8 > (XEN) elf_load_bsdsyms: shdr 4 at 0xffff83207f3a4b70 -> 0xffffffff81174f70 > (XEN) elf_load_bsdsyms: shdr 34 at 0xffff83207fe11b65 -> 0xffffffff811b0c48 > (XEN) elf_load_bsdsyms: shdr 35 at 0xffff83207fe12670 -> 0xffffffff811b0e10 > (XEN) elf_load_bsdsyms: shdr 36 at 0xffff83207feeb4c8 -> 0xffffffff81289c68 > (XEN) Masked VT-d error signaling on 0000:00:05.0 > (XEN) Masked VT-d error signaling on 0000:80:05.0 > (XEN) Scrubbing Free RAM on 2 nodes using 20 CPUs > (XEN) .....................................................done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) > (XEN) Freed 304kB init memory. > (XEN) error code 7 > (XEN) domain_crash_sync called from vmcs.c:1547 > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-4.6-unstable x86_64 debug=y Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: 0000:[] > (XEN) RFLAGS: 0000000000000200 CONTEXT: hvm guest (d0v0) > (XEN) rax: 0000000000000000 rbx: ffff82d0802e8000 rcx: ffff82d0802eff80 > (XEN) rdx: ffff82d0801e1500 rsi: 0000000000000000 rdi: ffff82d0801ed77c > (XEN) rbp: ffff82d0801061d2 rsp: ffffffff81bb5000 r8: ffff83103ff00000 > (XEN) r9: ffff82d08010623f r10: ffff82d0802eff70 r11: 0000000000000000 > (XEN) r12: ffff82d0802eff50 r13: ffff831033ae7000 r14: ffff83103ff00000 > (XEN) r15: ffff82d08018eae3 cr0: 0000000080000011 cr4: 0000000000000020 > (XEN) cr3: 0000000001ba1000 cr2: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000 > (XEN) Guest stack trace from rsp=ffffffff81bb5000: > (XEN) Fault while accessing guest memory. > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. Hello, This looks very similar to the crash reported at: https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html Which was also reported at xen-devel, but nobody seems to have looked into it. Could you send a bug report to xen-devel with the following trace (please make sure to mention PVH in the subject line) CCing the Intel VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen source tree). Thanks, Roger. From owner-freebsd-xen@FreeBSD.ORG Mon May 18 13:39:47 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 133DD2EC for ; Mon, 18 May 2015 13:39:47 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B72731959 for ; Mon, 18 May 2015 13:39:46 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,453,1427760000"; d="scan'208";a="266085914" Message-ID: <5559EB96.4040006@citrix.com> Date: Mon, 18 May 2015 15:39:34 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Eggert, Lars" CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <5553651D.3000400@citrix.com> <5555DFBC.9030306@citrix.com> <683335F9-E04E-4F8C-B1EF-0047E63E00AD@netapp.com> <5555FF4A.8010702@citrix.com> <126FDC37-2822-45DB-9AA6-3C9A03D89959@netapp.com> <55560414.1040002@citrix.com> <91758942-3683-42E5-9B39-66775E48D4DF@netapp.com> <55561EBC.8080901@citrix.com> In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 13:39:47 -0000 El 18/05/15 a les 15.01, Eggert, Lars ha escrit: > Unfortunately, the storm is still there with this patch. I guess you will have to resort to using hw.isci.force_legacy_interrupts=1 until I get around to implement MSI-X support for Xen Dom0, sorry for the trouble. Roger. From owner-freebsd-xen@FreeBSD.ORG Mon May 18 13:53:19 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 516D9A28 for ; Mon, 18 May 2015 13:53:19 +0000 (UTC) Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mx143.netapp.com", Issuer "VeriSign Class 3 International Server CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1ED581BEA for ; Mon, 18 May 2015 13:53:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,453,1427785200"; d="asc'?scan'208";a="42729505" Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx143-out.netapp.com with ESMTP; 18 May 2015 06:52:26 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 18 May 2015 06:52:25 -0700 Received: from HIOEXCMBX07-PRD.hq.netapp.com ([fe80::7ce8:9818:3705:3318]) by hioexcmbx07-prd.hq.netapp.com ([fe80::7ce8:9818:3705:3318%21]) with mapi id 15.00.1076.000; Mon, 18 May 2015 06:52:25 -0700 From: "Eggert, Lars" To: =?utf-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Topic: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Index: AQHQjVWqWfmhKLLkCEyxYLJkTsnG9Z16D22AgABSLoCAABHdgIAC8pqAgAAB7QCAAAZOAIAAH08AgAAEc4CAAAFDAIAAAhCAgAAdtwCABH0lgIAACpYAgAADlQA= Date: Mon, 18 May 2015 13:52:25 +0000 Message-ID: References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <5553651D.3000400@citrix.com> <5555DFBC.9030306@citrix.com> <683335F9-E04E-4F8C-B1EF-0047E63E00AD@netapp.com> <5555FF4A.8010702@citrix.com> <126FDC37-2822-45DB-9AA6-3C9A03D89959@netapp.com> <55560414.1040002@citrix.com> <91758942-3683-42E5-9B39-66775E48D4DF@netapp.com> <55561EBC.8080901@citrix.com> <5559EB96.4040006@citrix.com> In-Reply-To: <5559EB96.4040006@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.2100) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.122.56.79] Content-Type: multipart/signed; boundary="Apple-Mail=_1DCDE5FD-DBF9-48C4-AE5B-DCD75507966F"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 13:53:19 -0000 --Apple-Mail=_1DCDE5FD-DBF9-48C4-AE5B-DCD75507966F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 2015-5-18, at 15:39, Roger Pau Monn=C3=A9 = wrote: > I guess you will have to resort to using > hw.isci.force_legacy_interrupts=3D1 until I get around to implement = MSI-X > support for Xen Dom0, sorry for the trouble. No worries, that's a fine workaround. Thanks for all the help! Lars --Apple-Mail=_1DCDE5FD-DBF9-48C4-AE5B-DCD75507966F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlVZ7pgACgkQIWcjmsUTWRoVtQCdGP9nkWKelkPHkD/B5qtlgwLN RZ4An1WO3pXaltC5wucXT2QiXFIimljD =Om9m -----END PGP SIGNATURE----- --Apple-Mail=_1DCDE5FD-DBF9-48C4-AE5B-DCD75507966F-- From owner-freebsd-xen@FreeBSD.ORG Mon May 18 17:34:17 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 126B9D82 for ; Mon, 18 May 2015 17:34:17 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0BA918CD for ; Mon, 18 May 2015 17:34:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4IHYG6e086529 for ; Mon, 18 May 2015 17:34:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 154428] [xen] xn0 network interface and PF - Massive performance drop Date: Mon, 18 May 2015 17:34:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bdrewery@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 17:34:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Bryan Drewery changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bdrewery@FreeBSD.org --- Comment #11 from Bryan Drewery --- I just hit this on 10.1-GENERIC on EC2. Empty pf.conf with pf enabled = horrible performance. Disabling pf or TSO with pf fixes it. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Mon May 18 17:40:01 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31FE712E for ; Mon, 18 May 2015 17:40:01 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C6F9192B for ; Mon, 18 May 2015 17:40:01 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4IHe0PU088859 for ; Mon, 18 May 2015 17:40:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled Date: Mon, 18 May 2015 17:40:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bdrewery@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 17:40:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 Bryan Drewery changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bdrewery@FreeBSD.org --- Comment #4 from Bryan Drewery --- This wasn't fixed, see Bug #192013 and Bug #154428. I'm having this exact issue on EC2 10.1-GENERIC. Even with an empty pf.conf just enabling pf kills performance outbound and causes massive hangs. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Mon May 18 17:44:35 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DA232F5 for ; Mon, 18 May 2015 17:44:35 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 478361A69 for ; Mon, 18 May 2015 17:44:35 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4IHiZP8096069 for ; Mon, 18 May 2015 17:44:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled Date: Mon, 18 May 2015 17:44:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 17:44:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D135178 --- Comment #5 from Roger Pau Monn=C3=83=C2=A9 --- This bug is not about TSO + PF, just about TSO, which seems to work fine now (when not used in conjunction with PF). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@FreeBSD.ORG Mon May 18 17:45:52 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A35C6424 for ; Mon, 18 May 2015 17:45:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8DD561A85 for ; Mon, 18 May 2015 17:45:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4IHjqUv096853 for ; Mon, 18 May 2015 17:45:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled Date: Mon, 18 May 2015 17:45:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bdrewery@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 17:45:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D135178 --- Comment #6 from Bryan Drewery --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #5) > This bug is not about TSO + PF, just about TSO, which seems to work fine = now > (when not used in conjunction with PF). Ah. Sounds suspicious though. If PF is using TSO wrong why is it only causi= ng problems with the Xen interface and not all? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@FreeBSD.ORG Mon May 18 19:22:55 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F246E16 for ; Mon, 18 May 2015 19:22:55 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59A9E183B for ; Mon, 18 May 2015 19:22:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4IJMtGS095040 for ; Mon, 18 May 2015 19:22:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled Date: Mon, 18 May 2015 19:22:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cperciva@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 18 May 2015 19:22:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 Colin Percival changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cperciva@FreeBSD.org --- Comment #7 from Colin Percival --- PF is inserting bogus TCP checksums into TSO segments. Some interfaces say "gee, some idiot didn't read the spec" and ignore the checksums, while other interfaces say "hey, this is not a TSO packet" and drop it. The Xen network (at least as implemented in EC2) falls into the second category. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Tue May 19 06:05:05 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDC80FD9 for ; Tue, 19 May 2015 06:05:05 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7A261FAF for ; Tue, 19 May 2015 06:05:05 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4J655bh055654 for ; Tue, 19 May 2015 06:05:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Tue, 19 May 2015 06:05:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: raitech@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 19 May 2015 06:05:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 raitech@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |raitech@gmail.com --- Comment #6 from raitech@gmail.com --- (In reply to Sean Bruno from comment #4) Following Sean's idea, I was playing with the PV network frontend options, and got one FreeBSD 10.1 RELEASE to get its traffic routed by another FreeBSD 10.1 RELEASE, both within the same XenServer 6.5 host and both with xn1 over the same host-VLAN. router0# ifconfig xn1 -txcsum -tso4 -lro vm0# ifconfig xn1 -txcsum -tso4 -lro Without this config on both domUs, I can not do a: # fetch http://www.google.com/ (obs.: on success, result will be stored in fetch.out; needs two control-C to stop) But with the indicated configuration, I can exec the above command like a charm. I could even SSH into the vm0 from the Internet. Best regards, Raimundo Santos -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Wed May 20 08:19:12 2015 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4850C57E for ; Wed, 20 May 2015 08:19:12 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 335161202 for ; Wed, 20 May 2015 08:19:12 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4K8JCJ3033494 for ; Wed, 20 May 2015 08:19:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Wed, 20 May 2015 08:19:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kpielorz@tdx.co.uk X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 May 2015 08:19:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #7 from kpielorz@tdx.co.uk --- (In reply to raitech from comment #6) Hi, I've tested those options here - and they do work *for FreeBSD* boxes. However - if you set '-txcsum -tso4 -lro' on the FreeBSD box acting as a router - Windows machines still cannot pass traffic through it as a router :( [not tested Linux - but I'd guess from past experience a Linux PV instance will be the same] So whilst this is a work around (of sorts) for FreeBSD boxes using another FreeBSD box as a router - it's not usable in mixed platforms. There's obviously some weird interaction still going on with PV to PV network traffic involving FreeBSD when it's 'routing' things. -Karl -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-xen@FreeBSD.ORG Wed May 20 15:31:18 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FFB681E for ; Wed, 20 May 2015 15:31:18 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF09818FE for ; Wed, 20 May 2015 15:31:17 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,464,1427760000"; d="scan'208";a="266935304" Message-ID: <555CA899.1010704@citrix.com> Date: Wed, 20 May 2015 17:30:33 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "Eggert, Lars" CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <7C88785C-B4B0-4A2A-A77D-8AD56BC79E91@netapp.com> <555363DD.7080906@citrix.com> <38851CA4-57AA-4010-B741-0DB05E689975@netapp.com> In-Reply-To: <38851CA4-57AA-4010-B741-0DB05E689975@netapp.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 May 2015 15:31:18 -0000 El 15/05/15 a les 14.06, Eggert, Lars ha escrit: > On 2015-5-13, at 18:00, Eggert, Lars wrote: >> >> On 2015-5-13, at 16:46, Roger Pau Monné wrote: >>> I guess migration-rdma gets compiled because Qemu detects that you have >>> some library and assumes that you want it enabled. Did you install >>> something new between your previous build of Xen and this one? >> >> Yes, this box has world built with OFED. I'll try on a more standard world build Friday. > > Now building tools stops here: > > gmake[5]: Entering directory '/usr/home/elars/src/xen/tools/tests/x86_emulator' > [ -L x86_emulate ] || ln -sf /usr/home/elars/src/xen/tools/tests/x86_emulator/../../../xen/arch/x86/x86_emulate . > gcc47 -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -Wdeclaration-after-statement -I/usr/home/elars/src/xen/tools/tests/x86_emulator/../../../tools/include -c -g -o x86_emulate.o x86_emulate.c > x86_emulate.c:17:0: error: "__packed" redefined [-Werror] > In file included from /usr/include/assert.h:38:0, > from x86_emulate.c:1: > /usr/local/lib/gcc47/gcc/x86_64-portbld-freebsd11.0/4.7.4/include-fixed/sys/cdefs.h:244:0: note: this is the location of the previous definition > cc1: all warnings being treated as errors > Makefile:49: recipe for target 'x86_emulate.o' failed > gmake[5]: *** [x86_emulate.o] Error 1 > gmake[5]: Leaving directory '/usr/home/elars/src/xen/tools/tests/x86_emulator' > /usr/home/elars/src/xen/tools/tests/../../tools/Rules.mk:123: recipe for target 'subdir-all-x86_emulator' failed > gmake[4]: *** [subdir-all-x86_emulator] Error 2 > gmake[4]: Leaving directory '/usr/home/elars/src/xen/tools/tests' > /usr/home/elars/src/xen/tools/tests/../../tools/Rules.mk:118: recipe for target 'subdirs-all' failed > gmake[3]: *** [subdirs-all] Error 2 > gmake[3]: Leaving directory '/usr/home/elars/src/xen/tools/tests' > /usr/home/elars/src/xen/tools/../tools/Rules.mk:123: recipe for target 'subdir-all-tests' failed > gmake[2]: *** [subdir-all-tests] Error 2 > gmake[2]: Leaving directory '/usr/home/elars/src/xen/tools' > /usr/home/elars/src/xen/tools/../tools/Rules.mk:118: recipe for target 'subdirs-all' failed > gmake[1]: *** [subdirs-all] Error 2 > gmake[1]: Leaving directory '/usr/home/elars/src/xen/tools' > Makefile:53: recipe for target 'build-tools' failed > gmake: *** [build-tools] Error 2 Did you manage to get past this? TBH I don't know why Xen tries to build the tests, my build of tools doesn't even try to. Roger. From owner-freebsd-xen@FreeBSD.ORG Wed May 20 15:43:57 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30F77E75 for ; Wed, 20 May 2015 15:43:57 +0000 (UTC) Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mx141.netapp.com", Issuer "VeriSign Class 3 International Server CA - G3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB85B1A95 for ; Wed, 20 May 2015 15:43:56 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,465,1427785200"; d="asc'?scan'208";a="44728523" Received: from hioexcmbx08-prd.hq.netapp.com ([10.122.105.41]) by mx141-out.netapp.com with ESMTP; 20 May 2015 08:43:21 -0700 Received: from HIOEXCMBX01-PRD.hq.netapp.com (10.122.105.34) by hioexcmbx08-prd.hq.netapp.com (10.122.105.41) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 20 May 2015 08:43:21 -0700 Received: from HIOEXCMBX01-PRD.hq.netapp.com ([10.122.105.34]) by hioexcmbx01-prd.hq.netapp.com ([10.122.105.34]) with mapi id 15.00.1076.000; Wed, 20 May 2015 08:43:21 -0700 From: "Eggert, Lars" To: =?Windows-1252?Q?Roger_Pau_Monn=E9?= CC: "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Topic: Xen dom0 "interrupt storm detected on "irq16:"; throttling interrupt source" Thread-Index: AQHQjVWqWfmhKLLkCEyxYLJkTsnG9Z16D22AgABSLoCAAA5vgIAAAfCAgAAUmICAAuNBgIAIFKyAgAADlIA= Date: Wed, 20 May 2015 15:43:20 +0000 Message-ID: <4F264264-BF1D-4D34-AF1A-D6D22FACDAC4@netapp.com> References: <55531131.7040404@citrix.com> <65D7289A-9261-4F02-88E5-B2D137C268C1@netapp.com> <7C88785C-B4B0-4A2A-A77D-8AD56BC79E91@netapp.com> <555363DD.7080906@citrix.com> <38851CA4-57AA-4010-B741-0DB05E689975@netapp.com> <555CA899.1010704@citrix.com> In-Reply-To: <555CA899.1010704@citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.2100) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.122.56.79] Content-Type: multipart/signed; boundary="Apple-Mail=_F93BF52A-4FAD-4E95-9DEB-13D5FD2BA000"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 20 May 2015 15:43:57 -0000 --Apple-Mail=_F93BF52A-4FAD-4E95-9DEB-13D5FD2BA000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 2015-5-20, at 17:30, Roger Pau Monn=E9 wrote: >=20 > Did you manage to get past this? >=20 > TBH I don't know why Xen tries to build the tests, my build of tools > doesn't even try to. Yes, I think the issue was that I tried to build Xen 4.5-release. I'm = now building master without problems. Lars --Apple-Mail=_F93BF52A-4FAD-4E95-9DEB-13D5FD2BA000 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlVcq5kACgkQIWcjmsUTWRq6eQCghVm71QanbkIRhrQNkIDHjmRR fT8AoMQKpzFYHDKYbjVwv0g/gs6nOehM =Mi/D -----END PGP SIGNATURE----- --Apple-Mail=_F93BF52A-4FAD-4E95-9DEB-13D5FD2BA000-- From owner-freebsd-xen@FreeBSD.ORG Fri May 22 08:58:45 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B18EF142 for ; Fri, 22 May 2015 08:58:45 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 638791423 for ; Fri, 22 May 2015 08:58:44 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,474,1427760000"; d="scan'208";a="267661361" Message-ID: <555EEFBA.5080902@citrix.com> Date: Fri, 22 May 2015 10:58:34 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= , FreeBSD XEN Subject: Re: Porting the block-iscsi hotplug script References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> In-Reply-To: <5556F21D.2050005@entel.upc.edu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 08:58:45 -0000 El 16/05/15 a les 9.30, Gustau PĂ©rez ha escrit: > > > El 30/04/2015 a les 16:40, Roger Pau MonnĂ© ha escrit: >> Hello, >> >> El 30/04/15 a les 16.04, Gustau PĂ©rez ha escrit: >>> >>> El 30/04/2015 a les 11:57, Roger Pau MonnĂ© ha escrit: >>>> I've been digging into this, and it looks like it's going to be more >>>> complicated than what I thought. FreeBSD blkback is not prepared to work >>>> with hotplug scripts so we also need to modify it. >>>> >>>> I hope I'm going to have some time next week to prepare a patch to both >>>> the FreeBSD kernel and libxl, sorry for the delay. >>> > > Hi Roger, > > I was checking my pending stuff and I found this. I was wondering if > there was any progress on the blkback backend to support iscsi hotplug > scripts. I'm planing to move a bunch of vms to Xen and I'd be very > interested on using the FreeBSD iscsi hotplug script I created by using > the linux one as a guide. Hello, Sorry for the delay, I have patches ready now to enable disk hotplug scripts for FreeBSD. You will need to patch both Xen and the FreeBSD kernel in order to use them. The patch for the FreeBSD kernel is at: https://people.freebsd.org/~royger/freebsd-hotplug/ And the patches for Xen are at: https://people.freebsd.org/~royger/xen-hotplug/ Please note that Xen patches should be applied in the right order, or else you will get conflicts. Patch 4 in the Xen series contains a sample block hotplug script that you can probably use as the base for your iSCSI hotplug script. If something is not clear please drop me a line. Roger. From owner-freebsd-xen@FreeBSD.ORG Fri May 22 09:22:23 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BF499CB for ; Fri, 22 May 2015 09:22:23 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5240B1836 for ; Fri, 22 May 2015 09:22:21 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,474,1427760000"; d="scan'208";a="265143848" Message-ID: <555EF542.3090002@citrix.com> Date: Fri, 22 May 2015 11:22:10 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= , FreeBSD XEN Subject: Re: Porting the block-iscsi hotplug script References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> In-Reply-To: <555EEFBA.5080902@citrix.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 09:22:23 -0000 El 22/05/15 a les 10.58, Roger Pau MonnĂ© ha escrit: > And the patches for Xen are at: > > https://people.freebsd.org/~royger/xen-hotplug/ I had to upload the Xen patches again because the ones there missed a chunk, please fetch them again (if you have already done so). Roger. From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:11:38 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 717C954B for ; Fri, 22 May 2015 16:11:38 +0000 (UTC) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E84A319E6 for ; Fri, 22 May 2015 16:11:37 +0000 (UTC) Received: by lbbqq2 with SMTP id qq2so16177558lbb.3 for ; Fri, 22 May 2015 09:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=YO5WOSY5lhWR4T547QHrv7tbrcBxYugmuaAMtKfKrjg=; b=hZN9T6zoh7FkjIY+2L3Kdka6Eqc8L0mrL3FaWD5WZBtnEl1eDljHZ8FLtEjugq/spN 8sO8OOfGmh08S775WG60MpJU8uG/a9528ZDPNVli7qj4Q7Z0J086nzn6Tbmxh5jx/bt1 52CsA9gL5BQz9HMQRAAqS3bpLFj7rncnRMBwuR0vi5exQuSV5m/+cpslgoE+Ru+f4HWq qS18zq1U1HKiJKt9QSfRFqsZh92nYAKG1J48psQk8IL3VRS26sdsHQUJr1AQ4LVI8YCI BZXtTcK3RqLA9VJoxVU4xHUct3iR66RcgTz3WVad3zpj3AsFTQcdAJb7v6Fb4Xs0ziiK 5M2A== X-Received: by 10.152.19.198 with SMTP id h6mr7069162lae.62.1432311096034; Fri, 22 May 2015 09:11:36 -0700 (PDT) Received: from kloomba ([217.65.211.144]) by mx.google.com with ESMTPSA id j1sm585729lbc.15.2015.05.22.09.11.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 09:11:35 -0700 (PDT) Sender: Roman Bogorodskiy Date: Fri, 22 May 2015 19:11:19 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: "Eggert, Lars" , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash Message-ID: <20150522161117.GA59488@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <5559EB2E.6080609@citrix.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 16:11:38 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roger Pau Monn=E9 wrote: > El 18/05/15 a les 15.04, Eggert, Lars ha escrit: > > Hi, > >=20 > > I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xe= n crashes when starting the kernel. Log below; any ideas? > >=20 > > Thanks, > > Lars > > (XEN) ----[ Xen-4.6-unstable x86_64 debug=3Dy Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) RIP: 0000:[] > > (XEN) RFLAGS: 0000000000000200 CONTEXT: hvm guest (d0v0) > > (XEN) rax: 0000000000000000 rbx: ffff82d0802e8000 rcx: ffff82d0802e= ff80 > > (XEN) rdx: ffff82d0801e1500 rsi: 0000000000000000 rdi: ffff82d0801e= d77c > > (XEN) rbp: ffff82d0801061d2 rsp: ffffffff81bb5000 r8: ffff83103ff0= 0000 > > (XEN) r9: ffff82d08010623f r10: ffff82d0802eff70 r11: 000000000000= 0000 > > (XEN) r12: ffff82d0802eff50 r13: ffff831033ae7000 r14: ffff83103ff0= 0000 > > (XEN) r15: ffff82d08018eae3 cr0: 0000000080000011 cr4: 000000000000= 0020 > > (XEN) cr3: 0000000001ba1000 cr2: 0000000000000000 > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000 > > (XEN) Guest stack trace from rsp=3Dffffffff81bb5000: > > (XEN) Fault while accessing guest memory. > > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >=20 > Hello, >=20 > This looks very similar to the crash reported at: >=20 > https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html >=20 > Which was also reported at xen-devel, but nobody seems to have looked > into it. >=20 > Could you send a bug report to xen-devel with the following trace > (please make sure to mention PVH in the subject line) CCing the Intel > VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen > source tree). H, I'm observing a crash that looks similar to me: (XEN) ----[ Xen-4.5.0 x86_64 debug=3Dn Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0020:[] (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm guest (XEN) rax: fffff800d887c1b0 rbx: fffff8000ed85100 rcx: 0000000000000000 (XEN) rdx: ffffffff81788560 rsi: 0000000000000008 rdi: fffff8000ed85100 (XEN) rbp: fffffe023956a850 rsp: fffffe023956a850 r8: ffffffff815056f8 (XEN) r9: ffffffff8178857c r10: fffff8000ea9e0f0 r11: ffffffff81664200 (XEN) r12: 0000000000000004 r13: ffffffff80ee832b r14: fffff8000ed85118 (XEN) r15: fffff8000ed85100 cr0: 000000008005003b cr4: 00000000000406e0 (XEN) cr3: 0000000002cca000 cr2: 000000080a8da140 (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 0028 cs: 0020 (XEN) Guest stack trace from rsp=3Dfffffe023956a850: (XEN) Fault while accessing guest memory. (XEN) Domain 0 crashed: rebooting machine in 5 seconds. (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. I'm wondering if it's related to the same issue? It's triggered only when I try to reboot/poweroff the guest. Roman Bogorodskiy --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVX1UlAAoJEMltX/4IwiJqLLIH/3elbMEjmNSebPx/Uph1ryEn yYP4CwBQLPZY1t8LN9gpBFUeKOjDctVLJW1XcuX4nxlvvA8y0xrqUX+4TErvMya2 a0TjRtCK63YE656Zxda4tTkEEfQ2M9KpRIhHl8zsQdYO1CU0XKZIjYi8AVqL7QeE LhAST663wmeYAmZJo/sSHdxN0n87EISiRhKdTNcOAZMVg56JyXYGrRSstUDPfnsY lt/+h3ai6YmAe1p5Ctbr9y/qS9fHoexZPiv/5BY1Ua4PFkgd/2JxpfgRzYVUIkoL L2BvlmG5HioNEAzka6Pi5W7aNsME1SPQgTleBsPKHm3zH+5rpe00N6w6gUsB36w= =IRwS -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:26:41 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE4B5A21 for ; Fri, 22 May 2015 16:26:41 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F2FF1B4C for ; Fri, 22 May 2015 16:26:41 +0000 (UTC) Received: by lami4 with SMTP id i4so16183361lam.0 for ; Fri, 22 May 2015 09:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=yhD9cE4SfbInIkodYMUpfH/Go4p5vnBTGm+fKcZvWUo=; b=AKghwxMVGK41NaMPkPJG6VETWp1roVaPFLyD2prA2gIvkmEsJc+6ndKrUbpgCOcNj6 FpWLJCjoNXSNwYx1ePABsR6LiNzfuKbhw96h2CIxaR3wrvD2A4jrXOnOAoffxi7FKsiQ tFAmirPNDDDzu5+GuUUS97Gk92i3PApsPSfagzWLfl0/3w/y+xfbKM8DcZVmcvDrRFlu okN1/CgoC+JNoCw5KhmXwnva8K9sj8+JGTI3/e79cZ9TZ4BgmXshurMaQyqv0RW0dpBN asUPxNMBBJcIJcBjYZ86J8p5QIC/9GrdWuYgPpbZAPJtJKfieUyhNnG8g6ib8LcUTuKX c+9g== X-Received: by 10.152.42.164 with SMTP id p4mr7045590lal.3.1432311999280; Fri, 22 May 2015 09:26:39 -0700 (PDT) Received: from kloomba ([95.104.142.217]) by mx.google.com with ESMTPSA id a7sm585156lah.46.2015.05.22.09.26.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 09:26:38 -0700 (PDT) Sender: Roman Bogorodskiy Date: Fri, 22 May 2015 19:26:22 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: "Eggert, Lars" , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash Message-ID: <20150522162621.GA59587@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline In-Reply-To: <20150522161117.GA59488@kloomba> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 16:26:41 -0000 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roman Bogorodskiy wrote: > Roger Pau Monn=E9 wrote: >=20 > > El 18/05/15 a les 15.04, Eggert, Lars ha escrit: > > > Hi, > > >=20 > > > I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and = Xen crashes when starting the kernel. Log below; any ideas? > > >=20 > > > Thanks, > > > Lars > > > (XEN) ----[ Xen-4.6-unstable x86_64 debug=3Dy Not tainted ]---- > > > (XEN) CPU: 0 > > > (XEN) RIP: 0000:[] > > > (XEN) RFLAGS: 0000000000000200 CONTEXT: hvm guest (d0v0) > > > (XEN) rax: 0000000000000000 rbx: ffff82d0802e8000 rcx: ffff82d080= 2eff80 > > > (XEN) rdx: ffff82d0801e1500 rsi: 0000000000000000 rdi: ffff82d080= 1ed77c > > > (XEN) rbp: ffff82d0801061d2 rsp: ffffffff81bb5000 r8: ffff83103f= f00000 > > > (XEN) r9: ffff82d08010623f r10: ffff82d0802eff70 r11: 0000000000= 000000 > > > (XEN) r12: ffff82d0802eff50 r13: ffff831033ae7000 r14: ffff83103f= f00000 > > > (XEN) r15: ffff82d08018eae3 cr0: 0000000080000011 cr4: 0000000000= 000020 > > > (XEN) cr3: 0000000001ba1000 cr2: 0000000000000000 > > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000 > > > (XEN) Guest stack trace from rsp=3Dffffffff81bb5000: > > > (XEN) Fault while accessing guest memory. > > > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > > > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > >=20 > > Hello, > >=20 > > This looks very similar to the crash reported at: > >=20 > > https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html > >=20 > > Which was also reported at xen-devel, but nobody seems to have looked > > into it. > >=20 > > Could you send a bug report to xen-devel with the following trace > > (please make sure to mention PVH in the subject line) CCing the Intel > > VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen > > source tree). >=20 > H, >=20 > I'm observing a crash that looks similar to me: >=20 > (XEN) ----[ Xen-4.5.0 x86_64 debug=3Dn Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: 0020:[] > (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm guest > (XEN) rax: fffff800d887c1b0 rbx: fffff8000ed85100 rcx: 00000000000000= 00 > (XEN) rdx: ffffffff81788560 rsi: 0000000000000008 rdi: fffff8000ed851= 00 > (XEN) rbp: fffffe023956a850 rsp: fffffe023956a850 r8: ffffffff815056= f8 > (XEN) r9: ffffffff8178857c r10: fffff8000ea9e0f0 r11: ffffffff816642= 00 > (XEN) r12: 0000000000000004 r13: ffffffff80ee832b r14: fffff8000ed851= 18 > (XEN) r15: fffff8000ed85100 cr0: 000000008005003b cr4: 00000000000406= e0 > (XEN) cr3: 0000000002cca000 cr2: 000000080a8da140 > (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 0028 cs: 0020 > (XEN) Guest stack trace from rsp=3Dfffffe023956a850: > (XEN) Fault while accessing guest memory. > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >=20 > I'm wondering if it's related to the same issue? >=20 > It's triggered only when I try to reboot/poweroff the guest. >=20 > Roman Bogorodskiy And the full log from guest start to crash: https://dpaste.de/mWNu Roman Bogorodskiy --AqsLC8rIMeq19msA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVX1itAAoJEMltX/4IwiJq8Q0H/0308zPBnw7hKy6er9nx7C3a UI8w2WSl1h8iX54oqqlHEvooa+lQBLdTm2zL8t2662Qdp0gnz2Dm0euCXNSYVTfB kf73i3UeveT21vmFGrHCqz8K5oxK3nA/xlHhe50iipXcb0nwOD+fNN3GlJFqeOCA PvvNeNQnRZunNQ23J9wEIBTz4KngXPad+5MNsfwwOXjKmCuOzZ2DyOoYneYeOJDQ IQuuV5b9LXL3qgFFQ6Y91sMSRL/Uvsy9SNPOb46jgddUqrOHdM0PhETHdSrnZI75 O9j3pGeomHux2KUZ5ruXJnTTivahM+mm9sbuJFDRNezpGSUIsDuHjPpK0wKG4TU= =eut2 -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:27:16 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F7E3A50; Fri, 22 May 2015 16:27:16 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 40CC01B65; Fri, 22 May 2015 16:27:16 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,476,1427760000"; d="scan'208";a="267798384" Message-ID: <555F58DC.2040807@citrix.com> Date: Fri, 22 May 2015 18:27:08 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Roman Bogorodskiy CC: "Eggert, Lars" , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> In-Reply-To: <20150522161117.GA59488@kloomba> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 16:27:16 -0000 Hello, El 22/05/15 a les 18.11, Roman Bogorodskiy ha escrit: > H, > > I'm observing a crash that looks similar to me: > > (XEN) ----[ Xen-4.5.0 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: 0020:[] > (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm guest > (XEN) rax: fffff800d887c1b0 rbx: fffff8000ed85100 rcx: 0000000000000000 > (XEN) rdx: ffffffff81788560 rsi: 0000000000000008 rdi: fffff8000ed85100 > (XEN) rbp: fffffe023956a850 rsp: fffffe023956a850 r8: ffffffff815056f8 > (XEN) r9: ffffffff8178857c r10: fffff8000ea9e0f0 r11: ffffffff81664200 > (XEN) r12: 0000000000000004 r13: ffffffff80ee832b r14: fffff8000ed85118 > (XEN) r15: fffff8000ed85100 cr0: 000000008005003b cr4: 00000000000406e0 > (XEN) cr3: 0000000002cca000 cr2: 000000080a8da140 > (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 0028 cs: 0020 > (XEN) Guest stack trace from rsp=fffffe023956a850: > (XEN) Fault while accessing guest memory. > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > > I'm wondering if it's related to the same issue? The issue mentioned in this thread has been fixed in the xen-kernel port with the following commit: https://svnweb.freebsd.org/ports?view=revision&revision=386935 Not sure if binary packages in pkg have been updated or not. > It's triggered only when I try to reboot/poweroff the guest. I'm not sure if it's the same issue. In this case the crash happened when booting Dom0 (well even before booting Dom0). Can you please provide the full log (including Xen and FreeBSD boot output)? With just this chunk it's impossible to guess what's going on. Also, if I understand it correctly, the crash you are seeing happens when trying to shutdown/reboot a running DomU? Roger. From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:30:19 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C3507BE2; Fri, 22 May 2015 16:30:19 +0000 (UTC) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 893461B94; Fri, 22 May 2015 16:30:19 +0000 (UTC) Received: by oihd6 with SMTP id d6so17782461oih.2; Fri, 22 May 2015 09:30:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8eqrt1fOM+TKxmklhORAcCFxF+RPegSQ1BuSM9+CIr8=; b=uRSH3+27RwKvOwMdN5puaDyR5aMXnKDMYuUQlOVtOjdCTEZz2D1x3CMmm9YKz4b9Hs M5mvIJYuFFKB9nRMpO3bZcn8/WTJX1rx3meU8lQjXwuVtAICOJRtL65qHoNe8P2SF/dm tPL/vX8JBwkRXHcnCj1t2euivdPYHkBflSlQHni7NTvdiTPJV2mavCLvKmkl6VjvVQuW 0EFpZjG6XIw34D9U6hv/yE8YNWx+jEfrWMso47pi89Yj1Adj+gaPf5AhhprVLllil8vZ o3+UyBA2UQXQvXOhB7/GnXazO1OOJHxoA+hOsADibKYBy3dW/9KEc8q9neXQJsJ4lGpq 32jA== MIME-Version: 1.0 X-Received: by 10.60.223.193 with SMTP id qw1mr7339797oec.53.1432312218854; Fri, 22 May 2015 09:30:18 -0700 (PDT) Sender: royger@gmail.com Received: by 10.60.52.170 with HTTP; Fri, 22 May 2015 09:30:18 -0700 (PDT) In-Reply-To: <20150522162621.GA59587@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> <20150522162621.GA59587@kloomba> Date: Fri, 22 May 2015 18:30:18 +0200 X-Google-Sender-Auth: SrhynPyETKfgymL583EkXTpxVgc Message-ID: Subject: Re: Xen dom0 crash From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= To: Roman Bogorodskiy Cc: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 16:30:19 -0000 Hello, On Fri, May 22, 2015 at 6:26 PM, Roman Bogorodskiy wrote: > And the full log from guest start to crash: > > https://dpaste.de/mWNu Are you maybe trying to boot a FreeBSD i386 guest? There's an issue currently when using a 64bit FreeBSD blkback with a 32bit FreeBSD guest, which I hope I will solve shortly. Roger. From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:40:22 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08782F27; Fri, 22 May 2015 16:40:22 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7BFC61CA9; Fri, 22 May 2015 16:40:21 +0000 (UTC) Received: by laat2 with SMTP id t2so16385510laa.1; Fri, 22 May 2015 09:40:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+bdwD2ilptyR4VFxUxsX6ySLHDZcDEw8AkaK9bWAWog=; b=WLue8xt7lgI7J8X0INWTL5rv6x3F+tUPPkahk0/+e2AatQ+BCQoY5rAjR8ByP5pcHc PMlQOs+ElmagUDahzVheGp1sPzDq/cxMYUnnh5N6uQrBOrRUQxzo0vjCyqIH74ql1IF4 8Um/FR1kVyzslgVd/MLjBRK4ZwGnwRw1Iu9+Q71snouWWmr8KB16H8KSXZwqmthxEtLN 3OA3H+FCcTDVZRtxvKSWXgzEbcznb1XKGvlNVOoOfi/R8mDtbwEgQ+T2teIWDBNzL/+j Mg6y8OXPCXoAN/kEmeM4XvBR67Scmj20ixM7nUbgi//0IjJRRcQizDz4JkOwxz6+0szQ fDMg== X-Received: by 10.152.170.165 with SMTP id an5mr5085379lac.100.1432312819525; Fri, 22 May 2015 09:40:19 -0700 (PDT) Received: from kloomba ([95.104.142.217]) by mx.google.com with ESMTPSA id z7sm597696lal.33.2015.05.22.09.40.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 09:40:18 -0700 (PDT) Sender: Roman Bogorodskiy Date: Fri, 22 May 2015 19:40:05 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: Roger Pau =?iso-8859-1?Q?Monn=E9?= , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash Message-ID: <20150522164004.GB59587@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> <20150522162621.GA59587@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VrqPEDrXMn8OVzN4" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 16:40:22 -0000 --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roger Pau Monn=E9 wrote: > Hello, >=20 > On Fri, May 22, 2015 at 6:26 PM, Roman Bogorodskiy wr= ote: > > And the full log from guest start to crash: > > > > https://dpaste.de/mWNu >=20 > Are you maybe trying to boot a FreeBSD i386 guest? There's an issue > currently when using a 64bit FreeBSD blkback with a 32bit FreeBSD > guest, which I hope I will solve shortly. No, the guest is: FreeBSD 10.0-RELEASE amd64. Here's dmesg.boot from dom0: https://dpaste.de/ey7Q Config file for domU looks this way: builder =3D "hvm" name =3D "freebsd" memory =3D 512 vcpus =3D 4 vif =3D [ 'bridge=3Dbridge0' ] disk =3D [ '/home/novel/freebsd-xen.img,raw,hda,rw', ] vnc =3D 1 vnclisten =3D "0.0.0.0" serial=3D"pty" Packages versions: xen-4.5.0 xen-kernel-4.5.0_2 xen-tools-4.5.0_4 output of 'xl info': release : 11.0-CURRENT version : FreeBSD 11.0-CURRENT #0 r282110: Mon Apr 27 20:49:= 15 UTC 2015 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC machine : amd64 nr_cpus : 4 max_cpu_id : 3 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 3492 hw_caps : bfebfbff:2c100800:00000000:00007f00:77fafbff:00000= 000:00000021:00002fbb virt_caps : hvm hvm_directio total_memory : 16255 free_memory : 7273 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 5 xen_extra : .0 xen_version : 4.5.0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-= 3.0-x86_32p hvm-3.0-x86_64=20 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xffff800000000000 xen_changeset :=20 xen_commandline : dom0_mem=3D8192M dom0_max_vcpus=3D4 dom0pvh=3D1 co= m1=3D115200,8n1 guest_loglvl=3Dall loglvl=3Dall console=3Dcom1,vga cc_compiler : gcc48 (FreeBSD Ports Collection) 4.8.4 cc_compile_by : root cc_compile_domain :=20 cc_compile_date : Thu May 21 17:39:38 MSK 2015 xend_config_format : 4 Thanks, Roman Bogorodskiy --VrqPEDrXMn8OVzN4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVX1vkAAoJEMltX/4IwiJq848H/0WzGFqaoMJK2xNDlKeRc82/ a/KyWgYZZkUzeInWorKE0vcEn79jeWJXOJ/v/wECi8hfj4UAtl36uypkycBMN8Qa DRKU896ZqpshLbloF1GwC3HlemBNuFaGnbvIiODGIMP27nOOmbnP6oh4z5mU3aGg FPeD7/ZxoWwMTzZ3gmOtP7fFX8RqxmTJendu7IKzDzqIce9nDKUd3+C/uN5ELl4G qCmVJ4wnqQO6fenXCTHpGekHO5ubaL+4yb3Iy4P0edQnMSloSH9d8xZIdefxX5e4 Lbe+iKb19j1IVeyc5AzuvKPJNVzewp6mnI953UD05VxR8Z4TBKoBz7bWYNiaVC0= =q0e/ -----END PGP SIGNATURE----- --VrqPEDrXMn8OVzN4-- From owner-freebsd-xen@FreeBSD.ORG Fri May 22 17:40:32 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74B23FEA; Fri, 22 May 2015 17:40:32 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19E0E13F0; Fri, 22 May 2015 17:40:32 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so46386985wic.0; Fri, 22 May 2015 10:40:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=IEAyLX8FokvheadosxlBd6mN6acNgk21mbTJvL+a8EM=; b=UTojidd6zG+dfQ1mpGvFqhrT+cOMDy9KWP6ObopsGurH8mWfHnxWNyFoe2AMuaTFrM ex6dL8Le0BsP3eQINCr9Kx3RXW4ELTASk3KZ/cFIhMDDiy9kRumf+l6xurplKnmTWF/V 2Q3LG3xnGI6Z9kqJg8uGcmZVdO9q/6Z7RljzKNSjNdnbjnj9ksOQbPiElKuTwzJuwO9F FeVCxV7gx9andBnoLah7kFZzRghDP6lYDebwm356L6u8t5k5cZwwOD9oiZsx8PVLVCYy +B6ZEt64/brBA8tSD+FwE0bd8lrD/NrumEWXAcy6S+g8ai0uIsR2OHeuaX+OgmT0uV8/ RYtg== X-Received: by 10.180.99.2 with SMTP id em2mr1185684wib.59.1432316430638; Fri, 22 May 2015 10:40:30 -0700 (PDT) Received: from [172.16.1.30] (243.Red-2-136-43.dynamicIP.rima-tde.net. [2.136.43.243]) by mx.google.com with ESMTPSA id v3sm8471479wix.8.2015.05.22.10.40.28 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 10:40:29 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Message-ID: <555F6A04.3040907@FreeBSD.org> Date: Fri, 22 May 2015 19:40:20 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Roman Bogorodskiy CC: =?windows-1252?Q?Roger_Pau_Monn=E9?= , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> <20150522162621.GA59587@kloomba> <20150522164004.GB59587@kloomba> In-Reply-To: <20150522164004.GB59587@kloomba> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 17:40:32 -0000 El 22/05/15 a les 18.40, Roman Bogorodskiy ha escrit: > No, the guest is: > > FreeBSD 10.0-RELEASE amd64. > > Here's dmesg.boot from dom0: > > https://dpaste.de/ey7Q I think I know what's going on, you are using a rather old kernel (from 27/04/15) which doesn't contain r282634. Could you update your Dom0 kernel to recent HEAD and try again? Thanks, Roger. From owner-freebsd-xen@FreeBSD.ORG Fri May 22 18:25:46 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41BAFA51; Fri, 22 May 2015 18:25:46 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3CD41A2F; Fri, 22 May 2015 18:25:45 +0000 (UTC) Received: by lbbuc2 with SMTP id uc2so18512587lbb.2; Fri, 22 May 2015 11:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ZOchiLQX8nhwXkqzbBhenSHeotLuZn1WuXu0/R2GXFQ=; b=a4BtQ54Ww7WwDq4aHlkgblhNkwQPGcmgO1C4DMaN4RO6kQiOU8uUsugdXnLr1wrfKE XLwg8JmrLj3j9sGJD4hZAIEQlL9nPKxgSmlS2wBP5pU/46QRzEXfSrGUztNk2GrfmjSj o+xRi2+7QNCPiinJdzqJx0DmJu4z/xnYC0/25JR1+W4VhMid9/Pe5gElzV7n9Es67X0G T/jpQadZ6Wa6Mgj6XbQwm7u3I7FmXGGpHbuBI6a+8IRzsXaOf4pOYGg9Ht95pw2oTcZh P/9GqIG6OYt5JEgqxhx8Ma1lRiMFbAFNx7+8rNvpvUw/VdFhRkJUQJq3nvYIdoMelxM2 nCrw== X-Received: by 10.112.129.132 with SMTP id nw4mr7586651lbb.122.1432319143760; Fri, 22 May 2015 11:25:43 -0700 (PDT) Received: from kloomba ([95.104.142.217]) by mx.google.com with ESMTPSA id lf12sm649674lac.38.2015.05.22.11.25.42 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 11:25:42 -0700 (PDT) Sender: Roman Bogorodskiy Date: Fri, 22 May 2015 21:25:29 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: Roger Pau =?iso-8859-1?Q?Monn=E9?= , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash Message-ID: <20150522182527.GC59587@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> <20150522162621.GA59587@kloomba> <20150522164004.GB59587@kloomba> <555F6A04.3040907@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NKoe5XOeduwbEQHU" Content-Disposition: inline In-Reply-To: <555F6A04.3040907@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 18:25:46 -0000 --NKoe5XOeduwbEQHU Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roger Pau Monn=E9 wrote: > El 22/05/15 a les 18.40, Roman Bogorodskiy ha escrit: > > No, the guest is: > >=20 > > FreeBSD 10.0-RELEASE amd64. > >=20 > > Here's dmesg.boot from dom0: > >=20 > > https://dpaste.de/ey7Q >=20 > I think I know what's going on, you are using a rather old kernel (from > 27/04/15) which doesn't contain r282634. Could you update your Dom0 > kernel to recent HEAD and try again? That worked, thanks! Roman Bogorodskiy --NKoe5XOeduwbEQHU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVX3SXAAoJEMltX/4IwiJq3/8H/12xwK36reS8KCCOJMk010h5 SY/YUPXYxZrfnarBRnWA5SpsXAbxrSScjR5f0v0r86zCpD4iFX1DIIIMB7Pq3RSz JkFiVcm2U7CE7dc2PUtaaEkhXS3tgj26F41G6Aambj2Q5kBDr9j+fhII6cJ4tdaS yeO696lfuBBDvRFcOKXiv2KREvSX4or4TlFU0weIMBYlUpK4a7OhqxzQiV1rEh81 3VKQLlLfpquJFeTFyf/NlRjnpKJze+w4fgEX3CnfklmeJn4hrmn6WXdLJGNEdxfT kYYCD6w4JlbkIyRDM0AKMPeSu448/U1OI82w0ufcVY94kwkfOVdZ9E92a9MDC0I= =78HO -----END PGP SIGNATURE----- --NKoe5XOeduwbEQHU-- From owner-freebsd-xen@FreeBSD.ORG Fri May 22 21:10:41 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9174EE9A for ; Fri, 22 May 2015 21:10:41 +0000 (UTC) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "relay.upc.es", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C56D1DEF for ; Fri, 22 May 2015 21:10:40 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id t4MLAP6E007655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Fri, 22 May 2015 23:10:26 +0200 Received: from [192.168.2.134] (196.Red-79-154-48.dynamicIP.rima-tde.net [79.154.48.196]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id t4MLAOIC028627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 22 May 2015 23:10:25 +0200 Message-ID: <555F9B3F.1000600@entel.upc.edu> Date: Fri, 22 May 2015 23:10:23 +0200 From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= , FreeBSD XEN Subject: Re: Porting the block-iscsi hotplug script References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> <555EF542.3090002@citrix.com> In-Reply-To: <555EF542.3090002@citrix.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Greylist: ACL matched, not delayed by milter-greylist-4.4.3 (dash.upc.es [147.83.2.50]); Fri, 22 May 2015 23:10:26 +0200 (CEST) X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.4.3 (ackerman2.upc.es [147.83.2.244]); Fri, 22 May 2015 23:10:25 +0200 (CEST) X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 22 May 2015 21:10:41 -0000 El 22/05/2015 a les 11:22, Roger Pau MonnĂ© ha escrit: > El 22/05/15 a les 10.58, Roger Pau MonnĂ© ha escrit: >> And the patches for Xen are at: >> >> https://people.freebsd.org/~royger/xen-hotplug/ > I had to upload the Xen patches again because the ones there missed a > chunk, please fetch them again (if you have already done so). Hi Roger, I'll take a look at those patches. I'm not sure if I'll be able to test them this weekend. My current kernel is a bit old (r281759 as of April 21th), and I'm currently using the 0001-xen-introduce-a-newbus-function-to-allocate-unused-m.patch. Has this patch been integrated in HEAD? I'm considering rebuild everything and then try your patches. Thanks for your efforts, Gustau > Roger. > From owner-freebsd-xen@FreeBSD.ORG Sat May 23 06:58:31 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1172377 for ; Sat, 23 May 2015 06:58:31 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1D091950 for ; Sat, 23 May 2015 06:58:31 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.13,480,1427760000"; d="scan'208";a="267963589" Message-ID: <55602512.1090702@citrix.com> Date: Sat, 23 May 2015 08:58:26 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= , FreeBSD XEN Subject: Re: Porting the block-iscsi hotplug script References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> <555EF542.3090002@citrix.com> <555F9B3F.1000600@entel.upc.edu> In-Reply-To: <555F9B3F.1000600@entel.upc.edu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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, 23 May 2015 06:58:32 -0000 Hello, El 22/05/15 a les 23.10, Gustau PĂ©rez ha escrit: > I'll take a look at those patches. I'm not sure if I'll be able to > test them this weekend. No problem, I've already sent the patches upstream for review but I will make sure you can properly test them before they are committed. > My current kernel is a bit old (r281759 as of April 21th), and I'm > currently using the > 0001-xen-introduce-a-newbus-function-to-allocate-unused-m.patch. Has > this patch been integrated in HEAD? Yes, a proper fix for this issue was committed as r282634: https://svnweb.freebsd.org/base?view=revision&revision=282634 > I'm considering rebuild everything and then try your patches. > > Thanks for your efforts, Thanks for the testing, Roger.