From owner-freebsd-virtualization@freebsd.org Sun Apr 24 11:33:21 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D649B1B5C2 for ; Sun, 24 Apr 2016 11:33:21 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id E31161A12 for ; Sun, 24 Apr 2016 11:33:20 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 56544C448; Sun, 24 Apr 2016 11:33:20 +0000 (UTC) Date: Sun, 24 Apr 2016 11:33:20 +0000 To: freebsd-virtualization@freebsd.org From: "kristof (Kristof Provost)" Reply-to: D1944+333+b09c6235d993877b@reviews.freebsd.org Subject: [Differential] D1944: PF and VIMAGE fixes Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D1944: PF and VIMAGE fixes X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NDc2NzM0MzY4OTdiYThiNTU1MjY2ZDZmMTJiIFccrwA= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 11:33:21 -0000 kristof added inline comments. INLINE COMMENTS sys/netpfil/pf/pf_if.c:130 I don't understand why this is required. Surely if an ifnet lives in V_ifnet (so, lives in the current vnet) ifp->if_vnet is always going to be curvnet? sys/netpfil/pf/pf_if.c:141 Why add curvnet here? pfi_attach_ifnet_event doesn't use its argument. sys/netpfil/pf/pf_if.c:143 Same as above. sys/netpfil/pf/pf_if.c:151 Same as above. sys/netpfil/pf/pf_if.c:814 I believe this is correct, but should probably include adding an __unused annotation to arg, and removing the 'curvnet' argument from the EVENTHANDLER_REGISTER() call. REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, trociny, kristof, gnn, zec, rodrigc, glebius, eri Cc: ryan_timewasted.me, mmoll, javier_ovi_yahoo.com, farrokhi, julian, robak, freebsd-virtualization-list, freebsd-pf-list, freebsd-net-list From owner-freebsd-virtualization@freebsd.org Sun Apr 24 17:49:45 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1091B1B6EE; Sun, 24 Apr 2016 17:49:45 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv157.fwdcdn.com (frv157.fwdcdn.com [212.42.77.157]) (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 7F44918AB; Sun, 24 Apr 2016 17:49:45 +0000 (UTC) (envelope-from fidaj@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=Bs3U2Y6W5u2sXIbjLcko7zYE7DsQ0WNAcXpkpOQh+sY=; b=iRPWARgwU1NwK8sojk18H7DVNs2xQh2K8TkreiJJeyqz4ZkuyXrZnHioi9Sl/8QD8C+43rPZORbiHM/YikbinPEOint2xB8LMmA/o+LIb25Yb7fMQvsD1zXGHrBPspeXlQek8jJluq++kesp/5hA0d2AghZqlxRIZokOkT0fAgI=; Received: from [37.229.193.176] (helo=nonamehost.local) by frv157.fwdcdn.com with esmtpsa ID 1auOA3-00018Z-GW ; Sun, 24 Apr 2016 20:49:35 +0300 Date: Sun, 24 Apr 2016 20:49:34 +0300 From: Ivan Klymenko To: Warner Losh Cc: FreeBSD Current , freebsd-virtualization@freebsd.org Subject: Re: Heads up Message-ID: <20160424204934.46eebae8@nonamehost.local> In-Reply-To: <20160415114443.660453cb@nonamehost.local> References: <20160415114443.660453cb@nonamehost.local> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=37.229.193.176; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 17:49:45 -0000 On Fri, 15 Apr 2016 11:44:43 +0300 Ivan Klymenko wrote: > On Thu, 14 Apr 2016 16:42:33 -0600 > Warner Losh wrote: > > > The CAM I/O scheduler has been committed to current. This work is > > described in > > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the > > default scheduler doesn't change the default (old) behavior. > > > > One possible issue, however, is that it also enables NCQ Trims on > > ada SSDs. There are a few rogue drives that claim support for this > > feature, but actually implement data corrupt instead of queued > > trims. The list of known rogues is believed to be complete, but > > some caution is in order. > > > > Warner > > Hi. > Thanks for you work. > But i have problem with VirtualBox if i use the kernel with option > CAM_NETFLIX_IOSCHED > http://imgur.com/JpcfW1h This problem is not over. After the update on other hardware from r296979 to r298512 (!!! without option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual machine to a virtual disk I lost completely virtual machine with permanent damage to the integrity of the file system in the inside of the virtual machine. This is a serious bug! Who cares not to fall into the same situation - is testing yourself and needed more testers. Because there is a suspicion that the problem is also relevant for bhyve VM. With me on this no more neither the strength nor the desire nor time. Thanks. From owner-freebsd-virtualization@freebsd.org Sun Apr 24 18:31:20 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71D14B1B0E3 for ; Sun, 24 Apr 2016 18:31:20 +0000 (UTC) (envelope-from v.mirewski@bugsys.org) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 4E6191D8C for ; Sun, 24 Apr 2016 18:31:20 +0000 (UTC) (envelope-from v.mirewski@bugsys.org) Received: by mail-io0-x233.google.com with SMTP id u185so164722270iod.3 for ; Sun, 24 Apr 2016 11:31:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bugsys-org.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to; bh=Bw71CzkIbpbUE47sgl9e13iBA0JA3lFa5yzIl6NtzyY=; b=NP4Ox4SGvSfxAi8O1aqpkya0SHD9YzQyLRmd4/Lkz0ZT/zFwA5YkoBkruXm22B7QjH Rr2bSzy49U6O+tG35VQEdIgdE5r0e8+y6ILMpUWzYLC1auQZUkfFsWZne0TA4aLHQue5 MvwlKQORvUthfWaBqcj/63vNSK/VzlWBaFhorCXg0gDQgoY92eabqztbSrobsvpFBbt0 LtwjHiWHPe5nGBH8StJEPmTLBNKil4fRGMwJGlG/2OM9opTH+xdUROw6gNvOh4SBK7ye v/Y5FQtu/YHVCUzm5D7UGTp7eceArYkdWssKJDb2efaMp4doo730Jv9UMKkh7vx7gzDX oRCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Bw71CzkIbpbUE47sgl9e13iBA0JA3lFa5yzIl6NtzyY=; b=iHwn8XHK6VF32a5dUW0AcgDINjoJMtbjbsBawjIHupeZ3FWav4OepwOUXotAZOBblg PlQsiPzxt8zc3o7gYXGiZonKErd5R7R6TV9RFHEjU/6vieOQuIVSQqaUWzSoh29os1qp JG2bYkR/zBYBrsZLnknM8XCSyZHYll3IRn56GJTk+dvm7e2ZHj3xM/0p1GvA2sqZ8MHH KjgNTSeWOsIQFI8rNZOYyTMLDg/Irl1r99gJJbyDvhRSAtgSGW0zFJwpWyhXIBcYq2BY qfgRrUU7Rdfy8Okg+S6LoKDpg5tGbHfMz3PeksrepTqMvpycL6HgsU0yaqom9Z1ay++b ucCg== X-Gm-Message-State: AOPr4FU4PVmr8KzdjAzNlvvhTVXOkzDTg9WwrlgfjzinvYRSDkIr0PqizPSzc4+5NzwjBZ6p8YXYMt9CIlXTIg== MIME-Version: 1.0 X-Received: by 10.107.137.19 with SMTP id l19mr23640601iod.177.1461522679659; Sun, 24 Apr 2016 11:31:19 -0700 (PDT) Received: by 10.36.133.215 with HTTP; Sun, 24 Apr 2016 11:31:19 -0700 (PDT) X-Originating-IP: [95.87.204.121] Date: Sun, 24 Apr 2016 21:31:19 +0300 Message-ID: Subject: pptdevs option crashes system From: Vesselin Mirewski To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 18:31:20 -0000 Hi, I'm trying to bring up an excellent PCIe Fusion board which has no driver for FreeBSD. I used bhyve to bring up an ubuntu server ( which has an original driver by the manufacturer ) All went just fine, till I tried to pass through the board to the linux. My CPUs support all that's needed by bhyve: Xeon X5675. The board ( pciconf -lv ) : none3@pci0:11:0:0: class=3D0x018000 card=3D0x178d103c chip=3D0x10051aed rev= =3D0x01 hdr=3D0x00 vendor =3D 'Fusion-io' device =3D 'ioDimm3' class =3D mass storage none4@pci0:12:0:0: class=3D0x018000 card=3D0x178d103c chip=3D0x10051aed rev= =3D0x01 hdr=3D0x00 vendor =3D 'Fusion-io' device =3D 'ioDimm3' class =3D mass storage my /boot/loader.conf has ( bhyve part ): vmm_load=3D"YES" nmdm_load=3D"YES" *pptdevs=3D"11/0/0 12/0/0"* The last line crashes the system - "Interrupt trap" and the system starts to shutdown the cpus ( which gets an ugly loop till it finally reboots ) Then single user, set pptdevs=3D"" , boot and everything is fine again. The board is an HP accelerator board with 2x160GB SLC SSDs with ( according to specifications ) 150PB lifetime and the amazing 230,000 IOPs - I'm dying to do some benchmarks with PostgreSQL ... Any advice will be highly appreciated. Thanks in advance for your time. --=20 ------------------------------------------------------ =D0=92. =D0=9C=D0=B8=D1=80=D0=B5=D0=B2=D1=81=D0=BA=D0=B8 +359 884 63 74 64 From owner-freebsd-virtualization@freebsd.org Sun Apr 24 18:57:55 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EECD7B1B3FD for ; Sun, 24 Apr 2016 18:57:55 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 A8CC81652 for ; Sun, 24 Apr 2016 18:57:55 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id f89so133552684ioi.0 for ; Sun, 24 Apr 2016 11:57:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=g/ueHMPirNCOVaiQJMWulK+1sYKtCDdSyBnH5HvnquE=; b=Wu7LiyEELvr0PNmEzkl3JRBV2zOXu/cajAvEaHiRJ43F3YE5X1Y8B35ER+Syh3PC2h MNGCl1P7lav+JVfXtLC92902rB/IfmZH75LhUZVTZ88HAB2/qdYx8nwLyWjE7555EjGt I9pHRY2vDArSlPNS2aA1fUwBpgZ0giAqdEIkscZGHSvCS8ignTAqxTUWdZsKcv9fz1XW ei34xfXb4zOldu4xIpiYD04Ngu12iPJRomdMfPhYvd6ag86+31blBiHnUfvO0NLmBPEa J1J2mkBMYweTBNPsuY7R0gyWWFGEZQX1cdDJSHbplqpy3xOW1fYAgiq3HF485PSnPH0w /DNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=g/ueHMPirNCOVaiQJMWulK+1sYKtCDdSyBnH5HvnquE=; b=PYdeejKxJ5yJQSOiXbZ0jT02r2lyTsOJIcYm4fItmNTPg38xfdF7EkcSrzUTh4kxjw 0g2jfApjvHJav/w1B3ocrVuuyRhfbiAAPKOOOSuTPK20rfz4w0uVbeNOjzmeTfq8LtJ8 9pnpaw5zGkzY6yHLEuYtiLx/ExHyaGWNuwSdSB7fCrBkHUBkPABM0e+qDgRbMMye+wrw igQnRYg4S2sCD30+NoLugmn0UWVEp2CRaA30M4xDU5+cHR35RwfWHKL75MytnYwPkUEX SR70WmT06C8CPQxudBbC5hmJVd0/kw6iIWywMFuCgliLQA2O/y9Wx4IHo6Fks7hD+LHL Xk0Q== X-Gm-Message-State: AOPr4FV9BBH3p1HTVQR0HW/wyRz7gnZp/+hVxqm7lc+2O+XUzohN7Ia/q7HzbednQ5EHwIKHwUWE7wXLfTFqwg== MIME-Version: 1.0 X-Received: by 10.107.162.17 with SMTP id l17mr38580583ioe.42.1461524275222; Sun, 24 Apr 2016 11:57:55 -0700 (PDT) Received: by 10.79.137.195 with HTTP; Sun, 24 Apr 2016 11:57:55 -0700 (PDT) In-Reply-To: References: Date: Sun, 24 Apr 2016 11:57:55 -0700 Message-ID: Subject: Re: pptdevs option crashes system From: David Ehrmann To: Vesselin Mirewski Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 18:57:56 -0000 It sounds like the bug I reported a while ago, but on a different chip family: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207602 On Sunday, April 24, 2016, Vesselin Mirewski wrote: > Hi, > I'm trying to bring up an excellent PCIe Fusion board which has no driver > for FreeBSD. I used bhyve to bring up an ubuntu server ( which has an > original driver by the manufacturer ) > All went just fine, till I tried to pass through the board to the linux. > My CPUs support all that's needed by bhyve: Xeon X5675. > > The board ( pciconf -lv ) : > > none3@pci0:11:0:0: class=3D0x018000 card=3D0x178d103c chip=3D0x10051aed r= ev=3D0x01 > hdr=3D0x00 > vendor =3D 'Fusion-io' > device =3D 'ioDimm3' > class =3D mass storage > none4@pci0:12:0:0: class=3D0x018000 card=3D0x178d103c chip=3D0x10051aed r= ev=3D0x01 > hdr=3D0x00 > vendor =3D 'Fusion-io' > device =3D 'ioDimm3' > class =3D mass storage > > my /boot/loader.conf has ( bhyve part ): > vmm_load=3D"YES" > nmdm_load=3D"YES" > > *pptdevs=3D"11/0/0 12/0/0"* > > The last line crashes the system - "Interrupt trap" and the system starts > to shutdown the cpus ( which gets an ugly loop till it finally reboots ) > > Then single user, set pptdevs=3D"" , boot and everything is fine again. > > The board is an HP accelerator board with 2x160GB SLC SSDs with ( accordi= ng > to specifications ) 150PB lifetime and the amazing 230,000 IOPs - I'm dyi= ng > to do some benchmarks with PostgreSQL ... > > Any advice will be highly appreciated. Thanks in advance for your time. > > -- > ------------------------------------------------------ > =D0=92. =D0=9C=D0=B8=D1=80=D0=B5=D0=B2=D1=81=D0=BA=D0=B8 > +359 884 63 74 64 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org " From owner-freebsd-virtualization@freebsd.org Sun Apr 24 21:00:28 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A294FB1B180 for ; Sun, 24 Apr 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) 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 819CF143B for ; Sun, 24 Apr 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3OL01ab027824 for ; Sun, 24 Apr 2016 21:00:28 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604242100.u3OL01ab027824@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 24 Apr 2016 21:00:28 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 21:00:28 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 202321 | [bhyve,patch] More verbose error reporting in bhy New | 202322 | [bhyve,patch] add option to have bhyve write its 2 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon Apr 25 03:31:41 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A128B1BAE7 for ; Mon, 25 Apr 2016 03:31:41 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 0C4971655 for ; Mon, 25 Apr 2016 03:31:41 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x234.google.com with SMTP id o66so185610382ywc.3 for ; Sun, 24 Apr 2016 20:31:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:cc; bh=CNX/Yq+uoV7hEVjEa0Z16Su4TQDn9HKwRo6VJGp6XHE=; b=NoX5RFLYOHDzzHz0FJcUz67jZG46et4yMjsKVxHoKLyxX/wLRfrP9hnwaRvMBCGrBS WXHACIE6q1ZMK3A9dbQUJrhINVQlsN4B/h4XGxQG5h+xvGb0Re57lsoejzE+lo+TkZ/C 4jpxSmd8m8u4z51NJBGWPJoPsZFBVhYmx2kAg61eM5Wv5rvw125unpvWT8zGIj4F5Jcs oZXEKZ1gDL9F+unteMpyw1iE+R8IB8DGyEGaE/PmmE+T6QY9WAPvE/G+qQ+48oNm/sxW qhUTM93uHFmXHoipHIFJDcHuJz8d1llsXxrmBgJQvStf/E5psRK1JAywcgrtg8/qRRLc BDQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:cc; bh=CNX/Yq+uoV7hEVjEa0Z16Su4TQDn9HKwRo6VJGp6XHE=; b=AGsYOkRqm6wphjbCX1kPo0IkSwk4PGzkK3Du3Cbd1wcHHe0W8NK3LYDP9dAX8MgXkj vlBsi5HanHlyGMocN3fzVFL91zfZL5/RxZM9c7qmU2LBDCr/H27AK+dxrArwjMg9vo/G MFwadllu86bfz7ElEvzAtHFYdS3zFsqBZJgBKLY5U3aDe9rRaPGCACK9F4xsVfSMLHAL 0YFW4LXaET1D0pAueawNyrziaUZU0FcdSj1mAWQroBMjOtYfDoINUSH1S45Lv93p0KV5 wH3d8L6j4KqT1/ApvXlL6+CJWkaMAHOOM7D+9y7V00v9Kkxc2bl14xxJbOOxDtonjrVP Iwxw== X-Gm-Message-State: AOPr4FUeNlHnhhjAC9j8gg2Kk79rO6ZCXEgOdio232pXO47OtqIrLRmB1Y1xr3YYg+INmbz/bEOxyWn2kAg1OQ== MIME-Version: 1.0 X-Received: by 10.37.224.133 with SMTP id x127mt20981267ybg.141.1461555100235; Sun, 24 Apr 2016 20:31:40 -0700 (PDT) Received: by 10.129.5.216 with HTTP; Sun, 24 Apr 2016 20:31:40 -0700 (PDT) Date: Sun, 24 Apr 2016 23:31:40 -0400 Message-ID: Subject: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100) From: Ultima Cc: freebsd-current@freebsd.org, freebsd-virtualization@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 03:31:41 -0000 The sr-iov vf driver is failing to attach. # pciconf -lv: (filtered to only relevant output) ix0@pci0:129:0:0: class=0x020000 card=0x00001458 chip=0x15288086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Controller 10-Gigabit X540-AT2' class = network subclass = ethernet ix1@pci0:129:0:1: class=0x020000 card=0x00001458 chip=0x15288086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Controller 10-Gigabit X540-AT2' class = network subclass = ethernet none155@pci0:129:0:129: class=0x020000 card=0x00001458 chip=0x15158086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'X540 Ethernet Controller Virtual Function' class = network subclass = ethernet none156@pci0:129:0:131: class=0x020000 card=0x00001458 chip=0x15158086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'X540 Ethernet Controller Virtual Function' class = network subclass = ethernet # devctl attach pci0:129:0:129 devctl: Failed to attach pci0:129:0:129: Input/output error # dmesg ixv0: at device 0.129 numa-domain 1 on pci12 ixv0: Using MSIX interrupts with 2 vectors ixv0: ixgbe_reset_hw() failed with error -100 device_attach: ixv0 attach returned 5 # cat /etc/iovctl.conf PF { device : ix1; num_vfs : 31; } DEFAULT { passthrough : true; } VF-0 { passthrough : false; } VF-1 { passthrough : false; } Any ideas? Ultima From owner-freebsd-virtualization@freebsd.org Mon Apr 25 04:15:46 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92761B1B40C for ; Mon, 25 Apr 2016 04:15:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::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 637D91A12 for ; Mon, 25 Apr 2016 04:15:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id u185so172274136iod.3 for ; Sun, 24 Apr 2016 21:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=c38JuefBOOUsBNrB9H/XZ3B6T0EbUOGjHHmi5U3TxIs=; b=RjtlOfnSmKrxg81ITFAX6cKGAeivJuISj4d3Nj/KnTwRFsbbDCa1KA5UazB3cNs/T1 8G+OmpIRrQCHCxHpR394ke6+77RC7a+juHvlJMJ4JZIdmnXQOa31WAdrrsR2R6tlxs2L Tux1ITJnzLqhkGvOKYYMwrViYmi0wtyyapjrA2x6VoxUfo0zcOPzXTEZL+mi9oNVnJDA CUoMAWn1NwvOvvdEkHGXaG5I0DL+zMLJQLO7KRE4zD58Ec+vES+3ejA/kZ9trXMj1Ql2 HtRnoETzKw4DQ/5gIGMluwyh+FJ6nmVIYMPw8quTJj+KZxAQT4bN3gpoS3bDBcKLoIQR kWpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=c38JuefBOOUsBNrB9H/XZ3B6T0EbUOGjHHmi5U3TxIs=; b=ApNA/oyaOJtanB+PeCpufafMSTFoMPceOamGnllEJ9Wjp1rdPUGkTveyClBg6NO6Jr JXPKUO49Jkj/sSXwNxk+tc+ZEIss87Mhy0E1PMGd8EXCeGV4zUcu5z+7QGdABZhVI8lM 1iAhvn9Etqc2MrgexnNirjIZJSACzMkcLB8Q2dPZ+xI9L3Z8dskYXXZNAMTejjyFxkOm AaIImbyuHKKjRuIMUlnmJn2rKVuyohHCNRNqYu0mmJdgWSumbIZDxrUTsW86LLWqq/+Q v5M0YeE75k3+yP5t+KsbwYDv/Rn+G9B6PwDmsE9Oa3upDOa3JINjVS4TE3f5aY055Bah gOkQ== X-Gm-Message-State: AOPr4FX2Y+Skf55EEx6fJn/3IuxIavgAasKJW+4SOqm/NAPP7CL0pvX7sPhoYQqCV5yWNDWR6I+FuyP4qzGyeA== MIME-Version: 1.0 X-Received: by 10.107.133.229 with SMTP id p98mr7555952ioi.16.1461557745593; Sun, 24 Apr 2016 21:15:45 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Sun, 24 Apr 2016 21:15:45 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20160424204934.46eebae8@nonamehost.local> References: <20160415114443.660453cb@nonamehost.local> <20160424204934.46eebae8@nonamehost.local> Date: Sun, 24 Apr 2016 22:15:45 -0600 X-Google-Sender-Auth: RI13Xh1IOK9QxJcIGHye4YCUp8E Message-ID: Subject: Re: Heads up From: Warner Losh To: Ivan Klymenko Cc: FreeBSD Current , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 04:15:46 -0000 I'll try virtualbox again, but it booted fine when I tried it before. I'll give bhyve a sping. I haven't tried it in quite some time, but it worked about 9 months ago. But since I don't even know what the errors you are seeing are, I can't tell you that it is similar to some other error reports or something completely new. Warner On Sun, Apr 24, 2016 at 11:49 AM, Ivan Klymenko wrote: > On Fri, 15 Apr 2016 11:44:43 +0300 > Ivan Klymenko wrote: > > > On Thu, 14 Apr 2016 16:42:33 -0600 > > Warner Losh wrote: > > > > > The CAM I/O scheduler has been committed to current. This work is > > > described in > > > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the > > > default scheduler doesn't change the default (old) behavior. > > > > > > One possible issue, however, is that it also enables NCQ Trims on > > > ada SSDs. There are a few rogue drives that claim support for this > > > feature, but actually implement data corrupt instead of queued > > > trims. The list of known rogues is believed to be complete, but > > > some caution is in order. > > > > > > Warner > > > > Hi. > > Thanks for you work. > > But i have problem with VirtualBox if i use the kernel with option > > CAM_NETFLIX_IOSCHED > > http://imgur.com/JpcfW1h > > This problem is not over. > After the update on other hardware from r296979 to r298512 (!!! without > option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual > machine to a virtual disk I lost completely virtual machine with > permanent damage to the integrity of the file system in the inside of > the virtual machine. > > This is a serious bug! > > Who cares not to fall into the same situation - is testing yourself > and needed more testers. > Because there is a suspicion that the problem is also relevant for > bhyve VM. > With me on this no more neither the strength nor the desire nor > time. > > Thanks. > From owner-freebsd-virtualization@freebsd.org Mon Apr 25 08:47:32 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97FDFB11CB4 for ; Mon, 25 Apr 2016 08:47:32 +0000 (UTC) (envelope-from prvs=916a2d648=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 636A71F89 for ; Mon, 25 Apr 2016 08:47:32 +0000 (UTC) (envelope-from prvs=916a2d648=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,532,1454976000"; d="scan'208";a="356159660" Date: Mon, 25 Apr 2016 10:47:23 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? Message-ID: <20160425084714.64ejioyqgquwu4gw@mac> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA2 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 08:47:32 -0000 On Sat, Apr 23, 2016 at 10:40:20PM +0000, Marcin Cieslak wrote: > On a freshly installed (via upgrade from 10.3 from source) > -CURRENT on this machine: > > FreeBSD 11.0-CURRENT #0 r298488: Sat Apr 23 11:10:01 UTC 2016 > root@o.saper.info:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) > WARNING: WITNESS option enabled, expect reduced performance. > VT(vga): resolution 640x480 > CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.09-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 > Features=0xbfebfbff > Features2=0x1fbae3ff > AMD Features=0x28100800 > AMD Features2=0x1 > XSAVE Features=0x1 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory = 17179869184 (16384 MB) > avail memory = 16475140096 (15711 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads > random: unblocking device. > ioapic0 irqs 0-23 on motherboard > > ... i am trying to boot the system as Dom0 under Xen (4.5.2_2 > installed via pkg install). > > The kernel boots in one of four cases, mostly > though I don't get a block cursor after Xen messages > and the machine sits and waits. > > > After trying Xen suddenly the system no longer > boots again: > > Booting from local disk... > PXE-M0F: Existing Intel Boot Agent. > > ZFS: i/o error - all block copies unavailable > ZFS: i/o error - all block copies unavailable > ZFS: i/o error - all block copies unavailable > > Can't find /boot/zfsloader > > FreeBSD/x86 boot > Default: zroot:/boot/kernel/kernel > boot: > ZFS: i/o error - all block copies unavailable I'm currently running a r298464 world+kernel with ZFS on root and have seen no issues so far. > (...) > > The zpool imports without problems when > booting from the rescue mfsbsd (10.3): > > pool: zroot > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > ada0p3 ONLINE 0 0 0 > ada1p3 ONLINE 0 0 0 > > errors: No known data errors > > gpart layout: > > => 34 5860533101 ada0 GPT (2.7T) > 34 1024 1 freebsd-boot (512K) > 1058 4194304 2 freebsd-swap (2.0G) > 4195362 5856337773 3 freebsd-zfs (2.7T) > > => 34 5860533101 ada1 GPT (2.7T) > 34 1024 1 freebsd-boot (512K) > 1058 4194304 2 freebsd-swap (2.0G) > 4195362 5856337773 3 freebsd-zfs (2.7T) > > I have managed to make zpool boot again by doing voodoo > similar to this one: > > [root@rescue ~]# zpool import -R /mnt zroot > [root@rescue ~]# mount -t devfs devfs /mnt/dev > [root@rescue ~]# chroot /mnt /bin/tcsh > > (... Running make install in /usr/src/sys/boot ...) > > root@rescue:/ # gpart bootcode -p /boot/gptzfsboot -i 1 ada0 > partcode written to ada0p1 > root@rescue:/ # gpart bootcode -p /boot/gptzfsboot -i 1 ada1 > partcode written to ada1p1 > root@rescue:/ # exit > [root@rescue ~]# umount /mnt/dev > [root@rescue ~]# zpool export zroot > [root@rescue ~]# reboot > > Why zpool metadata get corrupted? TBH, I have no idea. Can you also paste the log of the system (Xen + FreeBSD) when it fails to boot? If that's not possible, can you at least paste the output of `xl dmesg` when booted correctly under Xen? What operations did you perform when the system booted correctly using FreeBSD/Xen? Does the disk get corrupted even if the system fails to boot? AFAICT, it seems like it's only the bootcode that gets corrupted, is that right? Roger. From owner-freebsd-virtualization@freebsd.org Mon Apr 25 19:14:39 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B260B1C498 for ; Mon, 25 Apr 2016 19:14:39 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 037761C6C for ; Mon, 25 Apr 2016 19:14:38 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3PJERhB075874 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Apr 2016 19:14:27 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461611667; bh=CdG8w9+CGEczMYhmpWL9i0tVuJZp+ECu3DvXRjiBgwI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=TpoLSqgcdFTgmgRiWX5YLiAi9MWFH1ZgvVwAE2Jw5TuiKsDeD/a6VL8SzzIdPtQ2/ 1I5615hbqPvUWlj+Qbxcy+8lZYnl5RRtbWiJvRRg+mcfmfL+YWvw/0duMfX5p8yD97 2yzqAamO/NBIp5OB3fvH/Nft2pyrOauYPISx9abg= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3PJEP2s075871; Mon, 25 Apr 2016 19:14:25 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 25 Apr 2016 19:14:25 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: <20160425084714.64ejioyqgquwu4gw@mac> Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 19:14:39 -0000 On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > I have managed to make zpool boot again by doing voodoo > > similar to this one: > > > > [root@rescue ~]# zpool import -R /mnt zroot > > [root@rescue ~]# mount -t devfs devfs /mnt/dev > > [root@rescue ~]# chroot /mnt /bin/tcsh > > > > (... Running make install in /usr/src/sys/boot ...) > > > > root@rescue:/ # gpart bootcode -p /boot/gptzfsboot -i 1 ada0 > > partcode written to ada0p1 > > root@rescue:/ # gpart bootcode -p /boot/gptzfsboot -i 1 ada1 > > partcode written to ada1p1 > > root@rescue:/ # exit > > [root@rescue ~]# umount /mnt/dev > > [root@rescue ~]# zpool export zroot > > [root@rescue ~]# reboot > > > > Why zpool metadata get corrupted? > > TBH, I have no idea. Can you also paste the log of the system (Xen + > FreeBSD) when it fails to boot? If that's not possible, can you at least > paste the output of `xl dmesg` when booted correctly under Xen? I am using a VGA-emulating console attached by my friendly hosting provider (Hetzner) and it does not give me the terminal-like output, only VGA. From the quickly scrolling Xen kernel messages I am getting to the stage where it is "scrubbing" and hands over to the kernel. > What operations did you perform when the system booted correctly using > FreeBSD/Xen? Nothing in particular. It seems it succeeds every other time. > Does the disk get corrupted even if the system fails to boot? AFAICT, it > seems like it's only the bootcode that gets corrupted, is that right? I am not sure what really gets corrupted - once I noticed that just rewriting bootcode (without "make install") didn't help (at least once). Maybe this is some leftover from the 10.3 -> 11 upgrade? It's hard to install 11 clean on the rented server.... But no idea how would *that* affect booting. I also have two drives on the controller, maybe something is not in sync there? Marcin From owner-freebsd-virtualization@freebsd.org Mon Apr 25 20:02:31 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C79AB1CD6E for ; Mon, 25 Apr 2016 20:02:31 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 80F7D10DB for ; Mon, 25 Apr 2016 20:02:30 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3PK2Np9076241 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Apr 2016 20:02:23 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461614543; bh=ZHakwDLEqMlasqxeSPOqQ++iyeCDFPFjV8Myi7NGe7I=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=L2TFBMmobwuxvNq9aE5InW6zNgvW4+eCZj124JoSQUuyO9cADPH/f9eJGNkOuJ0Cm uQMh0XLCSLUtuSk7jVzFw6MzlvDzlo5qBClCWlmI2ql+TvaG9TewXAqvUttfUAn16S uWbE5t5erde48eVPnMIUpog+p5CNykRmkwaJKSxc= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3PK2MW7076238; Mon, 25 Apr 2016 20:02:22 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 25 Apr 2016 20:02:22 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 20:02:31 -0000 On Mon, 25 Apr 2016, Marcin Cieslak wrote: > On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > TBH, I have no idea. Can you also paste the log of the system (Xen + > > FreeBSD) when it fails to boot? If that's not possible, can you at least > > paste the output of `xl dmesg` when booted correctly under Xen? I managed to boot it again... root@o:~ # xl dmesg xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory also: # w 8:01PM up 5 mins, 1 users, load averages: 0.10, 0.25, 0.15 w: kvm_getprocs: Cannot allocate memory: Cannot allocate memory xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0pvh=1 com1=115200,8n1 guest_loglvl=all loglvl=all" I am running a plain GENERIC kernel. Marcin From owner-freebsd-virtualization@freebsd.org Mon Apr 25 20:51:00 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 267E9B1C853 for ; Mon, 25 Apr 2016 20:51:00 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 94AD317C4 for ; Mon, 25 Apr 2016 20:50:59 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3PKos7W076631 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Apr 2016 20:50:54 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461617454; bh=2ZnXC2MZ22m0kp5uxOSMMuwa4kDctGLu7MgQtczCuTY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=MQc9wZ1a0J7j2sNKWNJn8U7HVCV/e3y2lxAzg1DP2mfvANzkQMD6PSb7av+1A4M/z Zf9aGO0STfgRw1YdPJgRVEBySZpDhWcSc2qeRFnIfkkOF7bKaTsC60/SCFuAaS47zZ 8AxkXPnQBMe9AAUCfNbmPqOULzVRRHs7gzOogbjs= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3PKorGj076628; Mon, 25 Apr 2016 20:50:54 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 25 Apr 2016 20:50:53 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 20:51:00 -0000 On Mon, 25 Apr 2016, Marcin Cieslak wrote: > On Mon, 25 Apr 2016, Marcin Cieslak wrote: > > > On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > > TBH, I have no idea. Can you also paste the log of the system (Xen + > > > FreeBSD) when it fails to boot? If that's not possible, can you at least > > > paste the output of `xl dmesg` when booted correctly under Xen? > > I managed to boot it again... > > root@o:~ # xl dmesg > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory It seems that my problem was ... vm.max_wired=1 in /boot/loader.conf instead of vm.max_wired=-1 Marcin From owner-freebsd-virtualization@freebsd.org Tue Apr 26 07:11:54 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3C6FB1C282 for ; Tue, 26 Apr 2016 07:11:54 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 777071897 for ; Tue, 26 Apr 2016 07:11:53 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="356410305" Date: Tue, 26 Apr 2016 09:11:51 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? Message-ID: <20160426071151.ctzdaehgfhzij6q3@mac> References: <20160425084714.64ejioyqgquwu4gw@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 07:11:54 -0000 On Mon, Apr 25, 2016 at 08:50:53PM +0000, Marcin Cieslak wrote: > On Mon, 25 Apr 2016, Marcin Cieslak wrote: > > > On Mon, 25 Apr 2016, Marcin Cieslak wrote: > > > > > On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > > > TBH, I have no idea. Can you also paste the log of the system (Xen + > > > > FreeBSD) when it fails to boot? If that's not possible, can you at least > > > > paste the output of `xl dmesg` when booted correctly under Xen? > > > > I managed to boot it again... > > > > root@o:~ # xl dmesg > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > > libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory > > It seems that my problem was ... > > vm.max_wired=1 > > in /boot/loader.conf > > instead of > > vm.max_wired=-1 And this also caused the ZFS corruption? Roger. From owner-freebsd-virtualization@freebsd.org Tue Apr 26 07:16:39 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37D42B1C44C for ; Tue, 26 Apr 2016 07:16:39 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C9DEC1AA7 for ; Tue, 26 Apr 2016 07:16:38 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3Q7GPAN082924 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Apr 2016 07:16:25 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461654985; bh=tjJWuAlsOUiALlrRQj5PswCLdQSjQeharQUvIry4lBc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=WsB7RmtSnxAfrblDGiR7F8Wk5t3HzqN9FKeDvhixP+dlrn6mumSV0CkkKEeSFH8ag MUHMh0toYK07Wz4DCT+9k12N7DURIqyNZhuqsQZkICTwwEIzQ/KkdyMYDR29Ir0LZh WkB2rNkh06YOjAV7t5K55berTDhhjE6U+SW/AYis= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3Q7GP9e082921; Tue, 26 Apr 2016 07:16:25 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Tue, 26 Apr 2016 07:16:25 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: <20160426071151.ctzdaehgfhzij6q3@mac> Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 07:16:39 -0000 On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory > > > > It seems that my problem was ... > > > > vm.max_wired=1 > > > > in /boot/loader.conf > > > > instead of > > > > vm.max_wired=-1 > > And this also caused the ZFS corruption? Looks like it to me... Pretty strange. Btw. is there any way to boot UEFI Windows partition under Xen? (it works fine under bhyve) Marcin From owner-freebsd-virtualization@freebsd.org Tue Apr 26 07:44:14 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9425B1CB5C for ; Tue, 26 Apr 2016 07:44:14 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69E06184C for ; Tue, 26 Apr 2016 07:44:13 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="349777681" Date: Tue, 26 Apr 2016 09:43:02 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? Message-ID: <20160426074302.4i3rv7wd5ogg7ful@mac> References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA2 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 07:44:14 -0000 On Tue, Apr 26, 2016 at 07:16:25AM +0000, Marcin Cieslak wrote: > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > > > libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory > > > > > > It seems that my problem was ... > > > > > > vm.max_wired=1 > > > > > > in /boot/loader.conf > > > > > > instead of > > > > > > vm.max_wired=-1 > > > > And this also caused the ZFS corruption? > > Looks like it to me... Pretty strange. I thought the max_wired sysctl node only affected the usage of wired memory by userspace applications, but it may have also prevented ZFS from using memory. > Btw. is there any way to boot UEFI Windows partition under Xen? > (it works fine under bhyve) You will have to boot it using OVMF, which is not compiled with Xen by default. I will try to add an OVMF package (like the SeaBIOS one that we already have), and wire it into the xen-tools package. If you want to try it yourself, you can add "--enable-ovmf" to the xen-tools package configure and see what breaks ;). Roger. From owner-freebsd-virtualization@freebsd.org Tue Apr 26 08:12:39 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75EEEAAB484 for ; Tue, 26 Apr 2016 08:12:39 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12DA81710 for ; Tue, 26 Apr 2016 08:12:38 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3Q8CX8a083496 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Apr 2016 08:12:33 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461658353; bh=3C1FdS34ZoOs1JAEZPu1UKOr0F4rafmHYoR75Eb/lNo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=hunKlcbhPRUEcUAGBh7jCBrPGhYeg0KVVxq73xVnl3pa6NNTw99i0TInsxyqWbqIQ qEHFgOtOek2YUGTW249pCHXS8U9UISP5+p1DSUXR+5wOy17KCSfdTJNKTEADHvoyfG 1YBY/l9/9jBAskDzviWGTrahJ23L6NTCZEkUoI+U= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3Q8CW8e083493; Tue, 26 Apr 2016 08:12:32 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Tue, 26 Apr 2016 08:12:32 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: <20160426074302.4i3rv7wd5ogg7ful@mac> Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 08:12:39 -0000 On Tue, 26 Apr 2016, Roger Pau Monné wrote: > You will have to boot it using OVMF, which is not compiled with Xen by > default. I will try to add an OVMF package (like the SeaBIOS one that we > already have), and wire it into the xen-tools package. > > If you want to try it yourself, you can add "--enable-ovmf" to the xen-tools > package configure and see what breaks ;). Thanks, lots of bad Linux-only scripts (#!/bin/bash and the like), will try! Marcin From owner-freebsd-virtualization@freebsd.org Tue Apr 26 09:24:37 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AD27AAC96B for ; Tue, 26 Apr 2016 09:24:37 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F159C18E0 for ; Tue, 26 Apr 2016 09:24:36 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3Q9OVgb083992 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Apr 2016 09:24:31 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461662671; bh=6A5Dir/KK2MEKMpAaaO4OVt7Smz1aRKcNUOXN9d7FNo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=I5BHMMQ1PQWAwwcyKh5jbqlgA55DidjQm4K8md2zDnHZ6O1X5kogRiorod6+4pB2n FKiw4E/CC2HEQT/M8aSjqUKuPzOPunNd2HbCRCW6licTrlq6qWx+ZjrdmjxJSL3qcA S+dmjDpLVeQ6OQ4F8FrcvmK7ryt9oGNrNrhh/UrU= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3Q9OUjP083989; Tue, 26 Apr 2016 09:24:30 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Tue, 26 Apr 2016 09:24:30 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) In-Reply-To: Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 09:24:37 -0000 On Tue, 26 Apr 2016, Marcin Cieslak wrote: > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > You will have to boot it using OVMF, which is not compiled with Xen by > > default. I will try to add an OVMF package (like the SeaBIOS one that we > > already have), and wire it into the xen-tools package. > > > > If you want to try it yourself, you can add "--enable-ovmf" to the xen-tools > > package configure and see what breaks ;). > > Thanks, lots of bad Linux-only scripts (#!/bin/bash and the like), will try! I got lazy and I have downloaded https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download recompiled xen-tools by adding to xen-tools/Makefile CONFIGURE_ARGS+= --enable-ovmf CONFIGURE_ARGS+= --with-system-ovmf=/root/xen/OVMF.fd and worked pretty much out of the box. This is Windows Server 2016 Technical Preview 2016, with GPL PV drivers added to get networking. My config: builder = "hvm" memory = 4096 vcpus = 2 name = "Windows" disk = [ '/dev/zvol/zroot/windows0,raw,hda,w','/root/fat.bin,raw,hdb,w' ] boot = "c" # Boot to hard disk image vnc = 2 vnclisten = "0.0.0.0" usbdevice = 'tablet' on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' acpi = 1 bios = 'ovmf' vif = [ 'bridge=bridge0' ] /root/fat.bin is a little partitioned "hard drive" with FAT16 partition used to provide GPL drivers. Marcin From owner-freebsd-virtualization@freebsd.org Tue Apr 26 09:36:05 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9503DAACC1D for ; Tue, 26 Apr 2016 09:36:05 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 545751D22 for ; Tue, 26 Apr 2016 09:36:04 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="356435101" Date: Tue, 26 Apr 2016 11:35:56 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) Message-ID: <20160426093556.oxeh5qyafe3ro6xy@mac> References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA2 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 09:36:05 -0000 On Tue, Apr 26, 2016 at 09:24:30AM +0000, Marcin Cieslak wrote: > I got lazy and I have downloaded > > https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download > > recompiled xen-tools by adding to xen-tools/Makefile > > CONFIGURE_ARGS+= --enable-ovmf > CONFIGURE_ARGS+= --with-system-ovmf=/root/xen/OVMF.fd > > and worked pretty much out of the box. Oh, thanks for the info, I didn't know OVMF provided pre-compiled binaries. This should make adding a OVMF port trivial. Would you like to take a stab at adding such a port and wiring it into the xen-tools package? Roger. From owner-freebsd-virtualization@freebsd.org Tue Apr 26 10:39:14 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D75DB1CAAF for ; Tue, 26 Apr 2016 10:39:14 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DFF541A2E for ; Tue, 26 Apr 2016 10:39:13 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3QAd78x084540 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Apr 2016 10:39:07 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461667147; bh=9aFgiHay3DlYaEDNvhl2in+/gv/Qv+d1Vx/n2lQCaFs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=hhE5RJDSN4c+2eaaQcg11jzRzsAHg1U8gniE2WpkaZ2djwNCpA4Qg2v9RmNMoF6l6 T+JR69cvr5H9bM+FjqN9wthBKnt7C0hjbcPbbxHXh05J7tQusazYl38oRlLiUNTLGT xXsiPQrFVlp460RBXVfMV+nWhUpE1VPrQB6BZSx4= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3QAd6Aa084537; Tue, 26 Apr 2016 10:39:06 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Tue, 26 Apr 2016 10:39:06 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) In-Reply-To: <20160426093556.oxeh5qyafe3ro6xy@mac> Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 10:39:14 -0000 On Tue, 26 Apr 2016, Roger Pau Monné wrote: > On Tue, Apr 26, 2016 at 09:24:30AM +0000, Marcin Cieslak wrote: > > I got lazy and I have downloaded > > > > https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download > > > > recompiled xen-tools by adding to xen-tools/Makefile > > > > CONFIGURE_ARGS+= --enable-ovmf > > CONFIGURE_ARGS+= --with-system-ovmf=/root/xen/OVMF.fd > > > > and worked pretty much out of the box. > > Oh, thanks for the info, I didn't know OVMF provided pre-compiled binaries. > This should make adding a OVMF port trivial. Would you like to take a stab > at adding such a port and wiring it into the xen-tools package? Yes, should be easy. Will try to plug a binary port in. By the way, I just managed to crash a whole machine by trying to boot Solaris 11.3: # builder = "hvm" memory = 2048 vcpus = 1 name = "Solaris0" disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ] kernel = "/root/xen/solaris/unix" ramdisk = "/root/xen/solaris/boot_archive" extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" #boot = "c" usbdevice = 'tablet' vnc = 1 vnclisten = '0.0.0.0' vif = [ 'bridge=bridge0' ] /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso ("Intel text-only image"). Marcin From owner-freebsd-virtualization@freebsd.org Tue Apr 26 11:29:29 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC982B1B34F for ; Tue, 26 Apr 2016 11:29:29 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5479A1DD4 for ; Tue, 26 Apr 2016 11:29:28 +0000 (UTC) (envelope-from prvs=917dd492e=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="356459031" Date: Tue, 26 Apr 2016 13:29:25 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) Message-ID: <20160426112925.hmijqrxt52kyswfg@mac> References: <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 11:29:29 -0000 On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote: > Yes, should be easy. Will try to plug a binary port in. Thanks :). > By the way, I just managed to crash a whole machine by trying to > boot Solaris 11.3: > > # builder = "hvm" > memory = 2048 > vcpus = 1 > name = "Solaris0" > disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ] > kernel = "/root/xen/solaris/unix" > ramdisk = "/root/xen/solaris/boot_archive" > extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" > #boot = "c" > usbdevice = 'tablet' > vnc = 1 > vnclisten = '0.0.0.0' > vif = [ 'bridge=bridge0' ] > > /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso > ("Intel text-only image"). I don't think you can boot Solaris as a PV guest anymore, you should instead boot it as a HVM guest. You will have to remove the kernel and ramdisk options and instead add builder="hvm" (that you have left commented out). Roger. From owner-freebsd-virtualization@freebsd.org Tue Apr 26 13:50:57 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5F33B1D76B for ; Tue, 26 Apr 2016 13:50:57 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: from stricnina.roma.schema31.it (stricnina.schema31.it [2.228.74.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "stricnina.roma.schema31.it", Issuer "stricnina.roma.schema31.it" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 562D310EF for ; Tue, 26 Apr 2016 13:50:56 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: from smtp.schema31.it (localhost [127.0.0.1]) by stricnina.roma.schema31.it (8.14.9/8.14.9) with ESMTP id u3QDkNgU098819; Tue, 26 Apr 2016 15:46:24 +0200 (CEST) (envelope-from ifebi@schema31.it) Subject: Re: bhyve clock issue To: Neel Natu References: <8EE098BA-6C8F-41F4-B9CD-88F3D587B10F@gmail.com> Cc: abrancatelli@schema31.it, "freebsd-virtualization@freebsd.org" From: Ilario Febi Message-ID: <571F7127.1050100@schema31.it> Date: Tue, 26 Apr 2016 15:46:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <8EE098BA-6C8F-41F4-B9CD-88F3D587B10F@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 13:50:57 -0000 Yes, I found errors in /var/log/messages and fix adding: kern.timecounter.hardware=TSC-low into /etc/sysctl.conf file Thanks for support. Il 14/04/16 18:13, Neel Natu ha scritto: > Hi, > > Did you see anything interesting in the ntpd log file around the time the large skew happened? > > Best > Neel > >> On Apr 13, 2016, at 3:44 AM, Ilario Febi wrote: >> >> Hi All >> >> I have a strange issue about the clock of some FreeBSD Bhyve guests, >> maybe someone of you can help me to diagnose it and work on a >> solution. >> >> In detail, sometimes (without an apparent regularity) one of four >> bhyve guest's clock goes exactly 7 minutes and 10 seconds in the >> future. >> >> This clock stays unaligned for about 20 minutes, then, without any >> human intervention, the clock realign to proper condition. >> >> My configuration is: >> >> envrm02 (bhyve HOST, 10.2-RELEASE-p14) >> -> og-qa (bhyve guest - 10.2-RELEASE-p14) >> -> og-ci (bhyve guest - 10.2-RELEASE-p14) >> -> og-test (bhyve guest - 10.2-RELEASE-p14) >> -> og-prod-rm (bhyve guest - 10.2-RELEASE-p14) >> All the og-* machines just have a running copy of tomcat. >> >> I built a simple test to catch the error with python/fabric... the test is: >> >> fab -R ENV,OG,OG-PROD -- date | awk -F ': ' '/2016/{print $2, $1}' >> >> which simply run the command "date" on all hosts. >> >> So, the result is: >> @Mac-mini ~/p/f/> ./check_clock.sh >> Thu Apr 7 17:38:00 CEST 2016 [envrm02] out >> Thu Apr 7 17:38:00 CEST 2016 [og-qa] out >> Thu Apr 7 17:38:00 CEST 2016 [og-ci] out >> Thu Apr 7 17:38:00 CEST 2016 [og-test] out >> Thu Apr 7 17:38:00 CEST 2016 [og-prod-rm] out >> >> @Mac-mini ~/p/f/> ./check_clock.sh >> Thu Apr 7 18:38:00 CEST 2016 [envrm02] out >> Thu Apr 7 18:45:10 CEST 2016 [og-qa] out >> Thu Apr 7 18:38:00 CEST 2016 [og-ci] out >> Thu Apr 7 18:38:00 CEST 2016 [og-test] out >> Thu Apr 7 18:38:00 CEST 2016 [og-prod-rm] out >> >> @Mac-mini ~/p/f/> ./check_clock.sh >> Thu Apr 7 18:41:05 CEST 2016 [envrm02] out >> Thu Apr 7 18:48:15 CEST 2016 [og-qa] out >> Thu Apr 7 18:41:05 CEST 2016 [og-ci] out >> Thu Apr 7 18:41:05 CEST 2016 [og-test] out >> Thu Apr 7 18:41:05 CEST 2016 [og-prod-rm] out >> >> @Mac-mini ~/p/f/> ./check_clock.sh >> Thu Apr 7 18:46:51 CEST 2016 [envrm02] out >> Thu Apr 7 18:46:52 CEST 2016 [og-qa] out >> Thu Apr 7 18:46:52 CEST 2016 [og-ci] out >> Thu Apr 7 18:46:53 CEST 2016 [og-test] out >> Thu Apr 7 18:46:53 CEST 2016 [og-prod-rm] out >> >> The configuration is the same for all hosts and is this: >> @Mac-mini ~/p/f/> fab -R ENV,OG,OG-PROD -- cat /etc/rc.conf | grep ntpd >> [envrm02] out: ntpd_enable="YES" >> [og-qa] out: ntpd_enable="YES" >> [og-qa] out: ntpd_sync_on_start="YES" >> [og-ci] out: ntpd_enable="YES" >> [og-ci] out: ntpd_sync_on_start="YES" >> [og-test] out: ntpd_enable="YES" >> [og-test] out: ntpd_sync_on_start="YES" >> [og-prod-rm] out: ntpd_enable="YES" >> [og-prod-rm] out: ntpd_sync_on_start="YES" >> >> @Mac-mini ~/p/f/> fab -R ENV,OG,OG-PROD -- cat /etc/ntp.conf | grep -v 'out: #' >> [envrm02] Executing task '' >> [envrm02] run: cat /etc/ntp.conf >> [envrm02] out: >> [envrm02] out: server 0.freebsd.pool.ntp.org iburst >> [envrm02] out: server 1.freebsd.pool.ntp.org iburst >> [envrm02] out: server 2.freebsd.pool.ntp.org iburst >> [envrm02] out: >> [envrm02] out: restrict default limited kod nomodify notrap nopeer noquery >> [envrm02] out: restrict -6 default limited kod nomodify notrap nopeer noquery >> [envrm02] out: restrict 127.0.0.1 >> [envrm02] out: restrict -6 ::1 >> [envrm02] out: restrict 127.127.1.0 >> >> [og-qa] Executing task '' >> [og-qa] run: cat /etc/ntp.conf >> [og-qa] out: >> [og-qa] out: server 0.freebsd.pool.ntp.org iburst >> [og-qa] out: server 1.freebsd.pool.ntp.org iburst >> [og-qa] out: server 2.freebsd.pool.ntp.org iburst >> [og-qa] out: >> [og-qa] out: restrict default limited kod nomodify notrap nopeer noquery >> [og-qa] out: restrict -6 default limited kod nomodify notrap nopeer noquery >> [og-qa] out: restrict 127.0.0.1 >> [og-qa] out: restrict -6 ::1 >> [og-qa] out: restrict 127.127.1.0 >> >> [og-ci] Executing task '' >> [og-ci] run: cat /etc/ntp.conf >> [og-ci] out: >> [og-ci] out: server 0.freebsd.pool.ntp.org iburst >> [og-ci] out: server 1.freebsd.pool.ntp.org iburst >> [og-ci] out: server 2.freebsd.pool.ntp.org iburst >> [og-ci] out: >> [og-ci] out: restrict default limited kod nomodify notrap nopeer noquery >> [og-ci] out: restrict -6 default limited kod nomodify notrap nopeer noquery >> [og-ci] out: restrict 127.0.0.1 >> [og-ci] out: restrict -6 ::1 >> [og-ci] out: restrict 127.127.1.0 >> >> [og-test] Executing task '' >> [og-test] run: cat /etc/ntp.conf >> [og-test] out: >> [og-test] out: server 0.freebsd.pool.ntp.org iburst >> [og-test] out: server 1.freebsd.pool.ntp.org iburst >> [og-test] out: server 2.freebsd.pool.ntp.org iburst >> [og-test] out: >> [og-test] out: restrict default limited kod nomodify notrap nopeer noquery >> [og-test] out: restrict -6 default limited kod nomodify notrap nopeer noquery >> [og-test] out: restrict 127.0.0.1 >> [og-test] out: restrict -6 ::1 >> [og-test] out: restrict 127.127.1.0 >> >> Some observation: >> * The clock of envrm02 (the HOST) always seems to be correct. >> * The issue happens on a (apparently) random guest (not always the same one). >> * The issue happens always on one host at a time. >> >> The bhyve command line is, roughly, this one: >> >> /usr/sbin/bhyveload -m 2048 -d /san_storage/VMfs/$machine/$machine.img $machine >> /usr/sbin/bhyve -c 2 -m 2048 -A -H -P -s 0,hostbridge -s >> 2,ahci-hd,/san_storage/VMfs/$machine/$machine.img -s 4,virtio-net,$tap >> -s 31,lpc -l com1,stdio $machine >> >> Thanks in advance. >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" -- *Ing. Ilario Febi Schema 31 S.p.a. Socio Unico* *System Administrator *BO - FI - ROMA - PA ITALY Tel: +39. 06.98.358.472 Cell: +39. 366.69.45.384 Fax: +39. 055.71.880.466 Societŕ del Gruppo *SC31 ITALIA* From owner-freebsd-virtualization@freebsd.org Tue Apr 26 14:51:05 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB5ADB1C7CE for ; Tue, 26 Apr 2016 14:51:05 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 B9F211D04 for ; Tue, 26 Apr 2016 14:51:05 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-pf0-x234.google.com with SMTP id c189so7757878pfb.3 for ; Tue, 26 Apr 2016 07:51:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=HUsdCvya0fD6ZZ7RhWqmjBEAI3Y7gOWW9JKqkrg5esc=; b=cSovj48Is81GyT6z93C/5bYB6CaltjKMJLxubGhUH03VcLSHqEJckOPGuKijlsIqQ8 mBbXSqTSNW5KeAMn9ovuBbm9FD6CR7dUhOr9ncoFzAXPZLg/wrdtqV3cZ5gMNTDsXBWJ F8rkMagobB2pQFlYTFX00wFs1OwdaSAEfgA7+heSyu8iZd3vgG/Z0BrhXNi0UI9aG9kZ QE7ydaP+2IjjyhWpWMUrO1I31p0UoIeJVuZ/iOiXJdKF3vdhUibrUn7JyjdRC8E/eR3I SqBVhZ5RRLvAGbFddetpxW6kFSwT8RRd7B10dQ4m3Z0rXjg2tsBp+h0SOi4sU2VvE0NP zGLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=HUsdCvya0fD6ZZ7RhWqmjBEAI3Y7gOWW9JKqkrg5esc=; b=dE3GG7Sq0zqg17oqgeOSZi1Tdcnur6WUQSqfhyJ7gMgr4oBPC/nyL4dmFxebNWroc8 B6b8hstkHsfdut8id60zkAmv5ItdtwnZrHdJEa1y2dcbN9oXEGWJiEFuFQmNPoMNc3Zi 60K56yjBvPRul8gSytXuWL1zFFhkaVBdmrgT7fg7KO9ZL5nTH1HLRy5uRpVdJ5hdaTPT hma+/UjmafDmWDuUO9UWXyO5Dho9/dlwTVua8f4XF3TJXiqYeBT/CI8cDsyLk1kAIJ5F fzeNv2+g7grUrK1FDFJHPxhdi1ZlxYJ8zcTOJKRslt0J+z6XXTbFsjXmMsntdfENHH0d nvyg== X-Gm-Message-State: AOPr4FXeV8Mvef/WocGqmX569+Ph90xkCdcQcPl1EJslsORD5AbKjh6IoyuVXGFeKDPNcQ== X-Received: by 10.98.49.134 with SMTP id x128mr4157184pfx.45.1461682265211; Tue, 26 Apr 2016 07:51:05 -0700 (PDT) Received: from ?IPv6:2602:306:ce40:d9e0:202a:8fdf:ec12:4557? ([2602:306:ce40:d9e0:202a:8fdf:ec12:4557]) by smtp.gmail.com with ESMTPSA id h88sm5906287pfd.10.2016.04.26.07.51.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2016 07:51:03 -0700 (PDT) References: <8EE098BA-6C8F-41F4-B9CD-88F3D587B10F@gmail.com> <571F7127.1050100@schema31.it> Mime-Version: 1.0 (1.0) In-Reply-To: <571F7127.1050100@schema31.it> Message-Id: <647BCA7C-B915-4FAE-870F-CA914B38B8B5@gmail.com> Cc: "abrancatelli@schema31.it" , "freebsd-virtualization@freebsd.org" X-Mailer: iPhone Mail (11D257) From: Neel Natu Subject: Re: bhyve clock issue Date: Tue, 26 Apr 2016 07:50:59 -0700 To: Ilario Febi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 14:51:06 -0000 What was the timecounter being used when you were seeing the time skew? Best Neel > On Apr 26, 2016, at 6:46 AM, Ilario Febi wrote: >=20 > Yes,=20 >=20 > I found errors in /var/log/messages and fix adding:=20 >=20 > kern.timecounter.hardware=3DTSC-low > into /etc/sysctl.conf file >=20 > Thanks for support. >=20 >=20 >=20 > Il 14/04/16 18:13, Neel Natu ha scritto: >> Hi, >>=20 >> Did you see anything interesting in the ntpd log file around the time the= large skew happened? >>=20 >> Best >> Neel >>=20 >>> On Apr 13, 2016, at 3:44 AM, Ilario Febi wrote: >>>=20 >>> Hi All >>>=20 >>> I have a strange issue about the clock of some FreeBSD Bhyve guests, >>> maybe someone of you can help me to diagnose it and work on a >>> solution. >>>=20 >>> In detail, sometimes (without an apparent regularity) one of four >>> bhyve guest's clock goes exactly 7 minutes and 10 seconds in the >>> future. >>>=20 >>> This clock stays unaligned for about 20 minutes, then, without any >>> human intervention, the clock realign to proper condition. >>>=20 >>> My configuration is: >>>=20 >>> envrm02 (bhyve HOST, 10.2-RELEASE-p14) >>> -> og-qa (bhyve guest - 10.2-RELEASE-p14) >>> -> og-ci (bhyve guest - 10.2-RELEASE-p14) >>> -> og-test (bhyve guest - 10.2-RELEASE-p14) >>> -> og-prod-rm (bhyve guest - 10.2-RELEASE-p14) >>> All the og-* machines just have a running copy of tomcat. >>>=20 >>> I built a simple test to catch the error with python/fabric... the test i= s: >>>=20 >>> fab -R ENV,OG,OG-PROD -- date | awk -F ': ' '/2016/{print $2, $1}' >>>=20 >>> which simply run the command "date" on all hosts. >>>=20 >>> So, the result is: >>> @Mac-mini ~/p/f/> ./check_clock.sh >>> Thu Apr 7 17:38:00 CEST 2016 [envrm02] out >>> Thu Apr 7 17:38:00 CEST 2016 [og-qa] out >>> Thu Apr 7 17:38:00 CEST 2016 [og-ci] out >>> Thu Apr 7 17:38:00 CEST 2016 [og-test] out >>> Thu Apr 7 17:38:00 CEST 2016 [og-prod-rm] out >>>=20 >>> @Mac-mini ~/p/f/> ./check_clock.sh >>> Thu Apr 7 18:38:00 CEST 2016 [envrm02] out >>> Thu Apr 7 18:45:10 CEST 2016 [og-qa] out >>> Thu Apr 7 18:38:00 CEST 2016 [og-ci] out >>> Thu Apr 7 18:38:00 CEST 2016 [og-test] out >>> Thu Apr 7 18:38:00 CEST 2016 [og-prod-rm] out >>>=20 >>> @Mac-mini ~/p/f/> ./check_clock.sh >>> Thu Apr 7 18:41:05 CEST 2016 [envrm02] out >>> Thu Apr 7 18:48:15 CEST 2016 [og-qa] out >>> Thu Apr 7 18:41:05 CEST 2016 [og-ci] out >>> Thu Apr 7 18:41:05 CEST 2016 [og-test] out >>> Thu Apr 7 18:41:05 CEST 2016 [og-prod-rm] out >>>=20 >>> @Mac-mini ~/p/f/> ./check_clock.sh >>> Thu Apr 7 18:46:51 CEST 2016 [envrm02] out >>> Thu Apr 7 18:46:52 CEST 2016 [og-qa] out >>> Thu Apr 7 18:46:52 CEST 2016 [og-ci] out >>> Thu Apr 7 18:46:53 CEST 2016 [og-test] out >>> Thu Apr 7 18:46:53 CEST 2016 [og-prod-rm] out >>>=20 >>> The configuration is the same for all hosts and is this: >>> @Mac-mini ~/p/f/> fab -R ENV,OG,OG-PROD -- cat /etc/rc.conf | grep ntpd >>> [envrm02] out: ntpd_enable=3D"YES" >>> [og-qa] out: ntpd_enable=3D"YES" >>> [og-qa] out: ntpd_sync_on_start=3D"YES" >>> [og-ci] out: ntpd_enable=3D"YES" >>> [og-ci] out: ntpd_sync_on_start=3D"YES" >>> [og-test] out: ntpd_enable=3D"YES" >>> [og-test] out: ntpd_sync_on_start=3D"YES" >>> [og-prod-rm] out: ntpd_enable=3D"YES" >>> [og-prod-rm] out: ntpd_sync_on_start=3D"YES" >>>=20 >>> @Mac-mini ~/p/f/> fab -R ENV,OG,OG-PROD -- cat /etc/ntp.conf | grep -v '= out: #' >>> [envrm02] Executing task '' >>> [envrm02] run: cat /etc/ntp.conf >>> [envrm02] out: >>> [envrm02] out: server 0.freebsd.pool.ntp.org iburst >>> [envrm02] out: server 1.freebsd.pool.ntp.org iburst >>> [envrm02] out: server 2.freebsd.pool.ntp.org iburst >>> [envrm02] out: >>> [envrm02] out: restrict default limited kod nomodify notrap nopeer noque= ry >>> [envrm02] out: restrict -6 default limited kod nomodify notrap nopeer no= query >>> [envrm02] out: restrict 127.0.0.1 >>> [envrm02] out: restrict -6 ::1 >>> [envrm02] out: restrict 127.127.1.0 >>>=20 >>> [og-qa] Executing task '' >>> [og-qa] run: cat /etc/ntp.conf >>> [og-qa] out: >>> [og-qa] out: server 0.freebsd.pool.ntp.org iburst >>> [og-qa] out: server 1.freebsd.pool.ntp.org iburst >>> [og-qa] out: server 2.freebsd.pool.ntp.org iburst >>> [og-qa] out: >>> [og-qa] out: restrict default limited kod nomodify notrap nopeer noquery= >>> [og-qa] out: restrict -6 default limited kod nomodify notrap nopeer noqu= ery >>> [og-qa] out: restrict 127.0.0.1 >>> [og-qa] out: restrict -6 ::1 >>> [og-qa] out: restrict 127.127.1.0 >>>=20 >>> [og-ci] Executing task '' >>> [og-ci] run: cat /etc/ntp.conf >>> [og-ci] out: >>> [og-ci] out: server 0.freebsd.pool.ntp.org iburst >>> [og-ci] out: server 1.freebsd.pool.ntp.org iburst >>> [og-ci] out: server 2.freebsd.pool.ntp.org iburst >>> [og-ci] out: >>> [og-ci] out: restrict default limited kod nomodify notrap nopeer noquery= >>> [og-ci] out: restrict -6 default limited kod nomodify notrap nopeer noqu= ery >>> [og-ci] out: restrict 127.0.0.1 >>> [og-ci] out: restrict -6 ::1 >>> [og-ci] out: restrict 127.127.1.0 >>>=20 >>> [og-test] Executing task '' >>> [og-test] run: cat /etc/ntp.conf >>> [og-test] out: >>> [og-test] out: server 0.freebsd.pool.ntp.org iburst >>> [og-test] out: server 1.freebsd.pool.ntp.org iburst >>> [og-test] out: server 2.freebsd.pool.ntp.org iburst >>> [og-test] out: >>> [og-test] out: restrict default limited kod nomodify notrap nopeer noque= ry >>> [og-test] out: restrict -6 default limited kod nomodify notrap nopeer no= query >>> [og-test] out: restrict 127.0.0.1 >>> [og-test] out: restrict -6 ::1 >>> [og-test] out: restrict 127.127.1.0 >>>=20 >>> Some observation: >>> * The clock of envrm02 (the HOST) always seems to be correct. >>> * The issue happens on a (apparently) random guest (not always the same o= ne). >>> * The issue happens always on one host at a time. >>>=20 >>> The bhyve command line is, roughly, this one: >>>=20 >>> /usr/sbin/bhyveload -m 2048 -d /san_storage/VMfs/$machine/$machine.img $= machine >>> /usr/sbin/bhyve -c 2 -m 2048 -A -H -P -s 0,hostbridge -s >>> 2,ahci-hd,/san_storage/VMfs/$machine/$machine.img -s 4,virtio-net,$tap >>> -s 31,lpc -l com1,stdio $machine >>>=20 >>> Thanks in advance. >>> _______________________________________________ >>> freebsd-virtualization@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fre= ebsd.org" >=20 > --=20 > Ing. Ilario Febi >=20 > Schema 31 S.p.a. Socio Unico > System Administrator >=20 > BO - FI - ROMA - PA=20 > ITALY > Tel: +39. 06.98.358.472 > Cell: +39. 366.69.45.384 > Fax: +39. 055.71.880.466 > Societ=C3=A0 del Gruppo SC31 ITALIA From owner-freebsd-virtualization@freebsd.org Tue Apr 26 15:01:13 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CB92B1CAA5 for ; Tue, 26 Apr 2016 15:01:13 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: from stricnina.roma.schema31.it (stricnina.schema31.it [2.228.74.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "stricnina.roma.schema31.it", Issuer "stricnina.roma.schema31.it" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CEA9C12FA for ; Tue, 26 Apr 2016 15:01:11 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: from smtp.schema31.it (localhost [127.0.0.1]) by stricnina.roma.schema31.it (8.14.9/8.14.9) with ESMTP id u3QF161r002432; Tue, 26 Apr 2016 17:01:09 +0200 (CEST) (envelope-from ifebi@schema31.it) Subject: Re: bhyve clock issue To: Neel Natu References: <8EE098BA-6C8F-41F4-B9CD-88F3D587B10F@gmail.com> <571F7127.1050100@schema31.it> <647BCA7C-B915-4FAE-870F-CA914B38B8B5@gmail.com> Cc: abrancatelli@schema31.it, "freebsd-virtualization@freebsd.org" From: Ilario Febi Message-ID: <571F82B2.2030207@schema31.it> Date: Tue, 26 Apr 2016 17:01:06 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <647BCA7C-B915-4FAE-870F-CA914B38B8B5@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2016 15:01:13 -0000 Il 26/04/16 16:50, Neel Natu ha scritto: > What was the timecounter being used when you were seeing the time skew? HPET -- *Ing. Ilario Febi Schema 31 S.p.a. Socio Unico* *System Administrator *BO - FI - ROMA - PA ITALY Tel: +39. 06.98.358.472 Cell: +39. 366.69.45.384 Fax: +39. 055.71.880.466 SocietĂ  del Gruppo *SC31 ITALIA* From owner-freebsd-virtualization@freebsd.org Wed Apr 27 13:33:41 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 650F3B1EAD8 for ; Wed, 27 Apr 2016 13:33:41 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::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 3254B1468 for ; Wed, 27 Apr 2016 13:33:41 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-ig0-x230.google.com with SMTP id c3so12734528igl.0 for ; Wed, 27 Apr 2016 06:33:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=0t02a2vtyrDLpud1+7vfDQq8x4Q7upOC5/r/s4uvk04=; b=EE1preVPT84hbGO9W2FdIP7W9HIqrQ//f+GHg5G6qjT2zJM8L7QJA3Kx5juCC5DS9U RQFp6thiPQd6Ubsr8PjqwSdC4AnBYM51rUOTNFP4k0YmQIM+kTnI9NoMcn2G0mkE5TIK ttE5LQn3wIEBStlyeXyV0o8ZOF3JUJLZf/lZSvXe9IbHlC8GZ+waccG4cwnjnGFN5ryi 2OuiO+lDqY9ec0JBxQpwaO//UsJUMx/JTb+bB78ECjya/HNPx4R2egpkh+/gJxIR7fcq X6F4qawdgQRM0BiAqNtWRC8cq/I1DW/w3neTvJ9eLTj3muUef4UnXCZXknRHTfHqjo8R NjIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=0t02a2vtyrDLpud1+7vfDQq8x4Q7upOC5/r/s4uvk04=; b=WcPIZzGXLgHf3DEiAvUyFMNWaJnaZCFONEuSwXkqCARjvE1fM4lMu3QoQPkRy1is2I uoQKUwz3Iuu0Q+CErijIeL8UKTI1nRMJHgYHlZIGkrS7FAhzvbiHkzo9Hx0pRj/4/O+o to3ohXF8Ir3q37F4GdsF2l0gwZdU6cAZfYZLuixc8QnpBCTCR08tFknbLEtJd5AXxj9F xPwrzrOBz6w4CPjnWCIsYHN1RFNFkKCodYt7Nmy6Y7QpXev0WIrQHrI1lGvfRkOJ4KYf T7y6gJa38JcEHoYdMX9TBHpDstcKQhJb17f+yKDoIdZiSTLZtsPjVS9Jzp0FcqSsIbvq 1t3g== X-Gm-Message-State: AOPr4FVVDDhMpF6FFDgMkkxW2neCPr+zHIYhffQIgj4X5g/aDGkpD8n/nvkE0GBtCjSVCj6F4573kNdVORNjBw== MIME-Version: 1.0 X-Received: by 10.50.180.202 with SMTP id dq10mr10891260igc.37.1461764020664; Wed, 27 Apr 2016 06:33:40 -0700 (PDT) Received: by 10.36.36.193 with HTTP; Wed, 27 Apr 2016 06:33:40 -0700 (PDT) Date: Wed, 27 Apr 2016 09:33:40 -0400 Message-ID: Subject: does FreeBSD 10.3 bhyve support windows guests? From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2016 13:33:41 -0000 Or is this support only in -CURRENT? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@freebsd.org Thu Apr 28 08:14:06 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CA83B1F669 for ; Thu, 28 Apr 2016 08:14:06 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail1.yamagi.org (yugo.yamagi.org [212.48.122.103]) (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 261DE16AF for ; Thu, 28 Apr 2016 08:14:05 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from [192.168.100.101] (helo=aka) by mail1.yamagi.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1avghf-0007al-7x; Thu, 28 Apr 2016 09:49:41 +0200 Date: Thu, 28 Apr 2016 09:49:33 +0200 From: Yamagi Burmeister To: aryeh.friedman@gmail.com Cc: freebsd-virtualization@freebsd.org Subject: Re: does FreeBSD 10.3 bhyve support windows guests? Message-Id: <20160428094933.de5b99b937488fa2bb791ef8@yamagi.org> In-Reply-To: References: X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 08:14:06 -0000 It was merged to 10.2-STABLE in r295124 and was releases as part of FreeBSD 10.3-RELEASE. On Wed, 27 Apr 2016 09:33:40 -0400 Aryeh Friedman wrote: > Or is this support only in -CURRENT? > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB From owner-freebsd-virtualization@freebsd.org Thu Apr 28 20:01:37 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46A01B20F6A for ; Thu, 28 Apr 2016 20:01:37 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B446D1D8F for ; Thu, 28 Apr 2016 20:01:36 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3SK1OlN073978 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Apr 2016 20:01:24 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461873685; bh=558EKuFO4o3IHnDZPRDF/mY7W+IB/+v0innisEErRzE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=d2WDpwtIkKA9kxMuCp/lJ+RiYbr/mjlUPXWJ0mdSiEMt9PwXeZH6xL5oM1B9ZryY9 3UbDj7/QJ1J5j91sOWEvQjRNYsFn9OpL4m2gn33biCEp1mSwPBYeNuT/zat8QyvV8C hoJOgzi4NBPv4wbMJbqFgX0ObF+VkdljyI7u6HuU= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3SK1Nn9073975; Thu, 28 Apr 2016 20:01:23 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Thu, 28 Apr 2016 20:01:23 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) In-Reply-To: <20160426112925.hmijqrxt52kyswfg@mac> Message-ID: References: <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> <20160426112925.hmijqrxt52kyswfg@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 20:01:37 -0000 On Tue, 26 Apr 2016, Roger Pau Monné wrote: > On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote: > > By the way, I just managed to crash a whole machine by trying to > > boot Solaris 11.3: > > > > # builder = "hvm" > > memory = 2048 > > vcpus = 1 > > name = "Solaris0" > > disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ] > > kernel = "/root/xen/solaris/unix" > > ramdisk = "/root/xen/solaris/boot_archive" > > extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" > > #boot = "c" > > usbdevice = 'tablet' > > vnc = 1 > > vnclisten = '0.0.0.0' > > vif = [ 'bridge=bridge0' ] > > > > /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso > > ("Intel text-only image"). > > I don't think you can boot Solaris as a PV guest anymore, you should instead > boot it as a HVM guest. You will have to remove the kernel and ramdisk > options and instead add builder="hvm" (that you have left commented out). However supported or not, I think it should not crash a whole host system?... Marcin From owner-freebsd-virtualization@freebsd.org Thu Apr 28 20:36:12 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C22BFB1F764; Thu, 28 Apr 2016 20:36:12 +0000 (UTC) (envelope-from cramerj@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.freebsd.org (Postfix) with ESMTP id 948FA127F; Thu, 28 Apr 2016 20:36:12 +0000 (UTC) (envelope-from cramerj@intel.com) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 28 Apr 2016 13:36:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,548,1455004800"; d="scan'208";a="955072668" Received: from orsmsx102.amr.corp.intel.com ([10.22.225.129]) by fmsmga001.fm.intel.com with ESMTP; 28 Apr 2016 13:36:10 -0700 Received: from orsmsx155.amr.corp.intel.com (10.22.240.21) by ORSMSX102.amr.corp.intel.com (10.22.225.129) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 28 Apr 2016 13:36:10 -0700 Received: from orsmsx112.amr.corp.intel.com ([169.254.3.229]) by ORSMSX155.amr.corp.intel.com ([169.254.7.253]) with mapi id 14.03.0248.002; Thu, 28 Apr 2016 13:36:09 -0700 From: cramerj To: Ultima CC: "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" , "freebsd-hardware@freebsd.org" Subject: RE: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100) Thread-Topic: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100) Thread-Index: AQHRnqMQZnyHMV17gky4xGYv8b9bOZ+f3arw Date: Thu, 28 Apr 2016 20:36:08 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjFiYTFkZDAtZjVkMy00ZGMzLWIxNjgtNTVhMzFiZjExYWRhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoickxLdk41QWtVTFZBdHhvbjVrNitHSlFPRUpQektlQVlBdTV3QU5NTG50WT0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 20:36:12 -0000 Yeah, we're running into some issues with our implementation. I'm working = on the VF driver now and hope to get some of these bugs fixed within the ne= xt couple weeks. Thanks, -Jeb -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of Ultima Sent: Sunday, April 24, 2016 8:32 PM Cc: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org; freebs= d-hardware@freebsd.org Subject: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, rese= t_hw() failed with error -100) The sr-iov vf driver is failing to attach. # pciconf -lv: (filtered to only relevant output) ix0@pci0:129:0:0: class=3D0x020000 card=3D0x00001458 chip=3D0x15288086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ethernet Controller 10-Gigabit X540-AT2' class =3D network subclass =3D ethernet ix1@pci0:129:0:1: class=3D0x020000 card=3D0x00001458 chip=3D0x15288086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ethernet Controller 10-Gigabit X540-AT2' class =3D network subclass =3D ethernet none155@pci0:129:0:129: class=3D0x020000 card=3D0x00001458 chip=3D0x1515808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'X540 Ethernet Controller Virtual Function' class =3D network subclass =3D ethernet none156@pci0:129:0:131: class=3D0x020000 card=3D0x00001458 chip=3D0x1515808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'X540 Ethernet Controller Virtual Function' class =3D network subclass =3D ethernet # devctl attach pci0:129:0:129 devctl: Failed to attach pci0:129:0:129: Input/output error # dmesg ixv0: at device 0.129 numa-domain 1 on pci12 ixv0: Using MSIX interrupts with 2 vectors ixv0: ixgbe_reset_hw() failed with error -100 device_attach: ixv0 attach returned 5 # cat /etc/iovctl.conf PF { device : ix1; num_vfs : 31; } DEFAULT { passthrough : true; } VF-0 { passthrough : false; } VF-1 { passthrough : false; } Any ideas? Ultima _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Thu Apr 28 22:55:30 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C873B1D6BE; Thu, 28 Apr 2016 22:55:30 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 2AA8E18A9; Thu, 28 Apr 2016 22:55:30 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x22a.google.com with SMTP id o66so151318556ywc.3; Thu, 28 Apr 2016 15:55:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=PwrSPDwCJNfhr5QgLhsdCHh2ICT35eWDkatEQywhmZ0=; b=e+6Dto8uXJT2So6GbF6MGgEekrTmti+IbGkXPPez4dXLg9E82+Yqdxz/bF5HotD5Q8 iH81hjgQda01hJ14bcIkL1yUSae77yNaV975WzPGKdoRtm65eC8W8/IRbcb62CijN1k1 Wq9YgzUhOybaqpwd5KXN7L+oPPcbaGp1eE6ZWqFLd6bei0TmN9On1hJqcWg7r52U8r3S r1l7ByPUbHolL68JPXv73WACUV8SW2OCk6t0kBxyu3AN06HrvGWoXqvlZeotVTdSTMKY 83EzdKoR1Sxlpp7IUtV1YjS1CzQwftEMwfFR/Yw39GRX3UkS+dJbmkDDXnJ1vzHX1S8L A8Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=PwrSPDwCJNfhr5QgLhsdCHh2ICT35eWDkatEQywhmZ0=; b=EZer4EHx5/51Spc/em4VuFJE6xRZadyMJmw446BTIeYsanlite1J+lBJFK9rdjSCqV dT2FuySsgi/YswQiawg74aigNFU6d/CMh+Wp0HCuXGCV03vmZTtFUG2gW9/o/Gmk/dvI ASNR6rxbsqJQ9wqez6sCu+TV7XAv7spxoQw7iery2pLE9cvxaB6eRkkScE9kZ/JKP7Va bTbIglaaSTupkIY4GGj+7McY5qSoc3u4wo3CmRfWFDrdvvM50wagC/MlzZ+f87YeOkff wPkesTxUMeAgibfvZhqbAly0QjI4yD41YrXRUMrmt6evhOMD2XiEXBB5ODC8WHsFj3/8 q4Ag== X-Gm-Message-State: AOPr4FXw+EJcXq1y4TWnbEuBIgYcL38X6W9FS3vCh6t03kKvmXpg/F0Jy/nlJlBK+LIBpJqbftTed0DXase0Mw== MIME-Version: 1.0 X-Received: by 10.129.2.66 with SMTP id 63mr9457347ywc.250.1461884129278; Thu, 28 Apr 2016 15:55:29 -0700 (PDT) Received: by 10.129.5.216 with HTTP; Thu, 28 Apr 2016 15:55:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2016 18:55:29 -0400 Message-ID: Subject: Re: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100) From: Ultima To: cramerj Cc: "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" , "freebsd-hardware@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 22:55:30 -0000 Jeb, Okay, just wanted to make sure it was known. =] Ultima On Thu, Apr 28, 2016 at 4:36 PM, cramerj wrote: > Yeah, we're running into some issues with our implementation. I'm working > on the VF driver now and hope to get some of these bugs fixed within the > next couple weeks. > > Thanks, > -Jeb > > -----Original Message----- > From: owner-freebsd-current@freebsd.org [mailto: > owner-freebsd-current@freebsd.org] On Behalf Of Ultima > Sent: Sunday, April 24, 2016 8:32 PM > Cc: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org; > freebsd-hardware@freebsd.org > Subject: ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, > reset_hw() failed with error -100) > > The sr-iov vf driver is failing to attach. > > > # pciconf -lv: (filtered to only relevant output) > ix0@pci0:129:0:0: class=0x020000 card=0x00001458 chip=0x15288086 rev=0x01 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Controller 10-Gigabit X540-AT2' > class = network > subclass = ethernet > ix1@pci0:129:0:1: class=0x020000 card=0x00001458 chip=0x15288086 rev=0x01 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Controller 10-Gigabit X540-AT2' > class = network > subclass = ethernet > none155@pci0:129:0:129: class=0x020000 card=0x00001458 chip=0x15158086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = 'X540 Ethernet Controller Virtual Function' > class = network > subclass = ethernet > none156@pci0:129:0:131: class=0x020000 card=0x00001458 chip=0x15158086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = 'X540 Ethernet Controller Virtual Function' > class = network > subclass = ethernet > > # devctl attach pci0:129:0:129 > devctl: Failed to attach pci0:129:0:129: Input/output error > > # dmesg > ixv0: 1.4.6-k> at device 0.129 numa-domain 1 on pci12 > ixv0: Using MSIX interrupts with 2 vectors > ixv0: ixgbe_reset_hw() failed with error -100 > device_attach: ixv0 attach returned 5 > > # cat /etc/iovctl.conf > PF { > device : ix1; > num_vfs : 31; > } > > DEFAULT { > passthrough : true; > } > VF-0 { > passthrough : false; > } > VF-1 { > passthrough : false; > } > > > Any ideas? > > Ultima > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Fri Apr 29 01:36:04 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94B66B20235 for ; Fri, 29 Apr 2016 01:36:04 +0000 (UTC) (envelope-from James@Lodge.me.uk) Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0147.outbound.protection.outlook.com [157.56.112.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA4AC128F for ; Fri, 29 Apr 2016 01:36:03 +0000 (UTC) (envelope-from James@Lodge.me.uk) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gavinlodge.onmicrosoft.com; s=selector1-Lodge-me-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zTvBGZHKQ1yxukXYK8GLJhiSTyEOwQQF3osoNBW2ieg=; b=FcZk2V6vXwrlCryI2F17CLvLu1mUghhe7+O+BImYTEcteGF5MTZ9vBqcoDm4eOMgBLr3lkXeD9VjkW/rjF8TrD8ouKRWvhOF5IO2tpvM6HiJEj9H9l/B5wm+1ppYDhNOBLnvEMwAGrp9Ry5NKZWJbNPNykE5SpZYuED/ooZhhD8= Received: from DB5PR06MB1718.eurprd06.prod.outlook.com (10.165.213.16) by DB5PR06MB1719.eurprd06.prod.outlook.com (10.165.213.17) with Microsoft SMTP Server (TLS) id 15.1.466.19; Thu, 28 Apr 2016 08:55:19 +0000 Received: from DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) by DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) with mapi id 15.01.0485.005; Thu, 28 Apr 2016 08:55:19 +0000 From: James Lodge To: Yamagi Burmeister CC: "aryeh.friedman@gmail.com" , "freebsd-virtualization@freebsd.org" Subject: Re: does FreeBSD 10.3 bhyve support windows guests? Thread-Topic: does FreeBSD 10.3 bhyve support windows guests? Thread-Index: AQHRoIlyenKeV43asEKPoav46Gk2XZ+fA+6AgAASYVM= Date: Thu, 28 Apr 2016 08:55:19 +0000 Message-ID: References: , <20160428094933.de5b99b937488fa2bb791ef8@yamagi.org> In-Reply-To: <20160428094933.de5b99b937488fa2bb791ef8@yamagi.org> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: yamagi.org; dkim=none (message not signed) header.d=none;yamagi.org; dmarc=none action=none header.from=Lodge.me.uk; x-originating-ip: [213.205.251.250] x-ms-office365-filtering-correlation-id: 80b7c0ae-a194-40b3-1ab6-08d36f42d3ad x-microsoft-exchange-diagnostics: 1; DB5PR06MB1719; 5:BjJPy3VIzq9wJTQ9vVsAAE1sqdBPXgozUJ6yRKVfhgC1aHXYmQcXmPtMUVfuT31uBIYmTd0JbeW0Wi8cE8FtOrtNzDfJTWb4D8lBJNFvIv4GOKdw2QlCvPVzdv9epSlVj3z+aU0uBd4XK4DrqnnSpud8XFV/nik05oEbQ8PyrXESYo/pAf+CsywFIuzSwguB; 24:OyyP0IyJ4plTOBFhcz+ByjeAHaGT36l9cCAsf8H6SeG7XGZnjA+bDWdX3Lqr28wiZ95Q49RnRz+kMb0koDKFlPOucv66NwIXymjK+5WLBLw=; 7:JllmE0LpW3Ed8Qxh0poRJX/U0fNLpqjmd6Ar806qA9RAWN7E3XYjj67XIUTRnhInMJ4d5EGq9zjAGGECCioGGKDAkGayPU6rTJpDn6ynkRPngGx77yju6UyyL3ODCXm7YDvFSvxTyOPbSwt9TJRXshKtYSPWGL4M06tlTQgEia4tsT89P/Wl4IFhVsL2mhCZXmYylizoAtTxqdjpFFa8t7rgsNEgXnoYxCBnb6p1t44=; 23:Jc02kwRNAobjeQ9FGuUVdU3KEd6d9cmUxCBsmBxU/NdCDLQlCI57dXD06LmxAB9KVTECrQ+NkrbWvhjYK30tDDKdaOUmFDtdpjlN4YTWCN+4/XLbw4CVBZne7R7/jhq04AU1q1d3HD58yo8eQJxaDvASb/F4SVxI4jP29456QVEbQRVk46KUQ+66CI2ExQL6; 23:T/J2NDPUFnimghhTn1WjRVPCFMt3e1bYc9Sf6BJRJkWnPvTiS6ud63o4AiAt3AlJLaVCaubBD40ZDzIXGp8RvNwx5RsL1Ynle+Yc3RHIUdRmbFX+XurLfCtTiNfwJ98piwDhj6wd+vi1j/A+kro5wzK6heBgWenC5WHCkYFfGXTuFswFEqVPm7GyJxpV2M0l x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB1719; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(6040130)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041072)(6043046); SRVR:DB5PR06MB1719; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB1719; x-forefront-prvs: 0926B0E013 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(122556002)(16601075003)(5002640100001)(92566002)(74482002)(106116001)(110136002)(189998001)(80792005)(4326007)(76176999)(19580395003)(66066001)(86362001)(19580405001)(82746002)(33656002)(54356999)(83716003)(15974865002)(50986999)(87936001)(2900100001)(3846002)(5004730100002)(81166005)(2950100001)(3280700002)(11100500001)(10400500002)(2906002)(3660700001)(15975445007)(77096005)(586003)(6116002)(102836003)(5008740100001)(1220700001)(1096002)(36756003)(104396002)(564094006); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR06MB1719; H:DB5PR06MB1718.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2016 08:55:19.6108 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ded56ae9-7c77-4cf6-bbfd-39e6a505742d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR06MB1719 X-OriginatorOrg: Lodge.me.uk X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 01:36:04 -0000 > On 28 Apr 2016, at 09:14, Yamagi Burmeister wrote: >=20 > It was merged to 10.2-STABLE in r295124 and was releases as part of > FreeBSD 10.3-RELEASE. >=20 > On Wed, 27 Apr 2016 09:33:40 -0400 > Aryeh Friedman wrote: >=20 >> Or is this support only in -CURRENT? >>=20 >> --=20 >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fre= ebsd.org" >=20 >=20 > --=20 > Homepage: www.yamagi.org > XMPP: yamagi@yamagi.org > GnuPG/GPG: 0xEFBCCBCB > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org"=20 Not self promoting but I wrote this blog post that might help=20 https://jameslodge.com/freebsd-bhyve-hypervisor-running-windows-server-2012= -r2-standard/ From owner-freebsd-virtualization@freebsd.org Fri Apr 29 07:57:25 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8E55B2032B for ; Fri, 29 Apr 2016 07:57:25 +0000 (UTC) (envelope-from prvs=9202e7170=roger.pau@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7128A1AC2 for ; Fri, 29 Apr 2016 07:57:24 +0000 (UTC) (envelope-from prvs=9202e7170=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,550,1454976000"; d="scan'208";a="357307682" Date: Fri, 29 Apr 2016 09:57:16 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak CC: Subject: Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) Message-ID: <20160429075716.5mykxirogrlvc5pq@mac> References: <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> <20160426112925.hmijqrxt52kyswfg@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA2 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 07:57:25 -0000 On Thu, Apr 28, 2016 at 08:01:23PM +0000, Marcin Cieslak wrote: > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote: > > > By the way, I just managed to crash a whole machine by trying to > > > boot Solaris 11.3: > > > > > > # builder = "hvm" > > > memory = 2048 > > > vcpus = 1 > > > name = "Solaris0" > > > disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ] > > > kernel = "/root/xen/solaris/unix" > > > ramdisk = "/root/xen/solaris/boot_archive" > > > extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" > > > #boot = "c" > > > usbdevice = 'tablet' > > > vnc = 1 > > > vnclisten = '0.0.0.0' > > > vif = [ 'bridge=bridge0' ] > > > > > > /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso > > > ("Intel text-only image"). > > > > I don't think you can boot Solaris as a PV guest anymore, you should instead > > boot it as a HVM guest. You will have to remove the kernel and ramdisk > > options and instead add builder="hvm" (that you have left commented out). > > However supported or not, I think it should not crash a whole host system?... Certainly. I assumed that you meant it crashed the VM, not the whole host. Can you please provide the trace of the crash? Roger. From owner-freebsd-virtualization@freebsd.org Fri Apr 29 18:32:55 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 763D1B20D86 for ; Fri, 29 Apr 2016 18:32:55 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (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 415191036; Fri, 29 Apr 2016 18:32:55 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by mail-ig0-x236.google.com with SMTP id u10so30908651igr.1; Fri, 29 Apr 2016 11:32:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc; bh=+D6V7GhIWI6r2yhgOzZRIdo8p8lB95IUmu4G8DssDT0=; b=WHQdelO4KF4uRJbMF3vJ9y/SCJbeYzS+aaHsWGDuwnBa1GX68UAwIX0ZtREWhxCSiQ uoZsucgOZLSUT/ONa3CcEFvJkmWo6ky4trOjm2OoHHBzsgio0XuhgRUDSpf9O+7KNHW/ AzBBCzvOK5b/BMFdymtN6IQVU1fKr4/slge1PkZmPnkQ7wIaYc93cVywBLhc5snb4wxP R/mSKI3fpljkXnqMNT2IbKhJCt1Re7cu/fNMyvzmqq2Dn5JtyEc5UMfTI8PncdyH7t8g we+p2gT1C9QiL5/6Kuf/DgDawSJe7NEsW8uWwQImgWwl25va7Zp434zp++CnqO7kcDUo HYXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc; bh=+D6V7GhIWI6r2yhgOzZRIdo8p8lB95IUmu4G8DssDT0=; b=jzwLOOUbkYqS1v333eQOWtSM/YsTsKo/ikEwTIkLwyqz3RbHZjjuGVYRX6QQKKpx4r ibO0vco4xGkgPs75KA1U1im+wtSz94Qwyy2N3SvzeLa6NZhjYVMBVlu1pZGfr2LeO5AS pCSei608bHJyr8/8cYXpiT05pbEHs/P8rmn3k3Ni9uhufogIq9GngIUl9pKQgLl2x3k5 rDJ6+W3wkSrNrZQIE5uuL1hNDchU6GayyBSxwfkJhxUS79N2i0Z+Qj/FPcDExtSHxGpI 0H0s/sEyZkZ8FndR7XQUKZkGPDDfgmEfcIMAZSAvw2pkbYsMrSTjghzmVqxI2LscYs3Q yjHQ== X-Gm-Message-State: AOPr4FX5pJkR+P2aqOTdq4b+ixKglNx5amd/mUPtbJzalmpihZwIwGZFdFay6DFN/ALYlc5k9v+WxT1Kkqlc3g== MIME-Version: 1.0 X-Received: by 10.50.49.15 with SMTP id q15mr6002649ign.73.1461954774506; Fri, 29 Apr 2016 11:32:54 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.50.225.172 with HTTP; Fri, 29 Apr 2016 11:32:54 -0700 (PDT) Date: Fri, 29 Apr 2016 11:32:54 -0700 X-Google-Sender-Auth: jPdGZNHEKE9hf9ZeHzn-mePOCAI Message-ID: Subject: bhyve: unhandled inl 0x402 From: Craig Rodrigues To: "freebsd-virtualization@freebsd.org" Cc: "jenkins-admin@freebsd.org" , Alan Somers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 18:32:55 -0000 Hi, I am seeing this errors in in the latest bhyve code in CURRENT: acpi0: on motherboard Unhandled inl 0x0402 at 0xffffffff8039c2bd This is from: https://jenkins.freebsd.org/job/FreeBSD_HEAD/219/console -- Craig From owner-freebsd-virtualization@freebsd.org Fri Apr 29 19:06:40 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FDC1B2143D for ; Fri, 29 Apr 2016 19:06:40 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 209EA1F9A for ; Fri, 29 Apr 2016 19:06:39 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 93A3920A40D1 for ; Sat, 30 Apr 2016 05:06:29 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 8A65A280A16 for ; Sat, 30 Apr 2016 05:06:29 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id R5d0CmCSeWHn for ; Sat, 30 Apr 2016 05:06:29 +1000 (AEST) Received: from Peters-MacBook-Pro.local (unknown [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 390282804D7; Sat, 30 Apr 2016 05:06:27 +1000 (AEST) Subject: Re: bhyve: unhandled inl 0x402 To: Craig Rodrigues , "freebsd-virtualization@freebsd.org" References: Cc: "jenkins-admin@freebsd.org" , Alan Somers From: Peter Grehan Message-ID: <5723B0B0.9070103@freebsd.org> Date: Fri, 29 Apr 2016 12:06:24 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=NYhGrz34 c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=kziv93cY1bsA:10 a=BKbfozSbJ5E7PHxnPYMA:9 a=pILNOxqGKmIA:10 a=Yhro_1J1t60A:10 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 19:06:40 -0000 Hi Craig, > I am seeing this errors in in the latest bhyve code in CURRENT: > > acpi0: on motherboard > Unhandled inl 0x0402 at 0xffffffff8039c2bd Hmmm, that's a 4-byte read from the ACPI PM1 control register, which is advertized as being size 2 in the FADT table :( The recent acpica import might be doing this. I'll look into it. later, Peter. From owner-freebsd-virtualization@freebsd.org Fri Apr 29 20:11:50 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66644B210D2 for ; Fri, 29 Apr 2016 20:11:50 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0357E148D; Fri, 29 Apr 2016 20:11:49 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3TKBlNH096300 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Apr 2016 20:11:47 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461960707; bh=BsEcq//entQ20OI16DLunbCHKI3AuT8nbfbBVUIo9Fs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Z4NyBRDK2JaKZMZuCyaxgLkht1kfeVlBhtbC8dX4y0XxtoRCSC6SLBI4iLP043SjM Ak9La087xHZrCckee+nOwH2Dm4e7a3gJvJzsoxkRB2dpn6pNc6e3hKxxzrg8ox5/S6 Fi71zO3Tx3XW14OgBnM+9Goqk4QSdYcAIZH1v1FI= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3TKBlAU096297; Fri, 29 Apr 2016 20:11:47 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Fri, 29 Apr 2016 20:11:47 +0000 From: Marcin Cieslak To: Peter Grehan cc: Craig Rodrigues , "freebsd-virtualization@freebsd.org" , "jenkins-admin@freebsd.org" , Alan Somers Subject: Re: bhyve: unhandled inl 0x402 In-Reply-To: <5723B0B0.9070103@freebsd.org> Message-ID: References: <5723B0B0.9070103@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 20:11:50 -0000 On Fri, 29 Apr 2016, Peter Grehan wrote: > Hi Craig, > > > I am seeing this errors in in the latest bhyve code in CURRENT: > > > > acpi0: on motherboard > > Unhandled inl 0x0402 at 0xffffffff8039c2bd > > Hmmm, that's a 4-byte read from the ACPI PM1 control register, which is > advertized as being size 2 in the FADT table :( The recent acpica import might > be doing this. Isn't 0x402 used also as the qemu default debug port? Marcin From owner-freebsd-virtualization@freebsd.org Fri Apr 29 21:21:50 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0BD9B21434 for ; Fri, 29 Apr 2016 21:21:50 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7EC33104B for ; Fri, 29 Apr 2016 21:21:50 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 3E4A820B57A6 for ; Sat, 30 Apr 2016 07:21:47 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 369A1280A1F for ; Sat, 30 Apr 2016 07:21:47 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id LVBRsHFnRAfJ for ; Sat, 30 Apr 2016 07:21:47 +1000 (AEST) Received: from Peters-MacBook-Pro.local (unknown [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id C0FBA2804D7; Sat, 30 Apr 2016 07:21:43 +1000 (AEST) Subject: Re: bhyve: unhandled inl 0x402 To: Marcin Cieslak References: <5723B0B0.9070103@freebsd.org> Cc: Craig Rodrigues , "freebsd-virtualization@freebsd.org" , "jenkins-admin@freebsd.org" , Alan Somers From: Peter Grehan Message-ID: <5723D064.7040702@freebsd.org> Date: Fri, 29 Apr 2016 14:21:40 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=NYhGrz34 c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=kziv93cY1bsA:10 a=8NvtLmsQGQ7ztagzRq4A:9 a=pILNOxqGKmIA:10 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 21:21:50 -0000 >>> acpi0: on motherboard >>> Unhandled inl 0x0402 at 0xffffffff8039c2bd >> >> Hmmm, that's a 4-byte read from the ACPI PM1 control register, which is >> advertized as being size 2 in the FADT table :( The recent acpica import might >> be doing this. > > Isn't 0x402 used also as the qemu default debug port? The default value for that (isa-debugcon) is 0xe9. Not sure why most o doc on the web overrides that with "iobase=0x402", but in any case, the inl is from a FreeBSD guest so qemu isn't involved. later, Peter. From owner-freebsd-virtualization@freebsd.org Fri Apr 29 21:34:17 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B0D4B218F0 for ; Fri, 29 Apr 2016 21:34:17 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::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 104DE1C1E; Fri, 29 Apr 2016 21:34:17 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by mail-ig0-x230.google.com with SMTP id bi2so35461621igb.0; Fri, 29 Apr 2016 14:34:17 -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; bh=AzvcUj0Vb7q/1lZv8yPpdtA9xFK/hQ1vU3/CazafrMc=; b=MgtE8v159JBwYbOH6ORW6cbg9vRwNm3fI6zER5NBLg2TKXYCtv8nms27mfbxV+aj88 UUZFCvn9lncHA5gaRZQg6vcQf8E7Gj5Jcg1tBpphcGzgVO0XV84+gXj1L2y2cFv8PNCn XL+ipnmOdv9UTVTLFD62/de/IWpQM7UXUkfin1uNllrnhUPk3OOQwtAXdUSpDSaYaYwy p9Q4VEDS+EN/2It/aCwIb1H1/pNgcmzTYfFUiyuiAh0swgVeU4hNYGwm630wd3CyEpGa tIF4yKLopRoobCc2JM3L8kgkV2v4BOU1c5qKuAoiRs9XjpQhjpmOEMhgW2aqgvVxFd/c lqzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=AzvcUj0Vb7q/1lZv8yPpdtA9xFK/hQ1vU3/CazafrMc=; b=dWFmSDS1WbVjdU1qb4ZK6fVIQzch3buekG5FS5qDupoNcgBJOzoAY+mSVZ5z+sI6VY dcQsZP3pJbOClSpMLbYQ8KurBSl6eOopRIY5bhR+yOFO47isKAVxujd2599BW5TmM/f5 X/qIGPstOKyYIoQyyuKkhVQgJyEjqI8ytnoKVus78DFkiRnI06R2zgZJTqnB/C9uC97y Xlj7H5EXHYzNsNN4VpZzDG7bOeXiKwtE6Cla9GEdvaLoS9h5zLbTcYkhCho8ZjX6gDg5 hYmeFyg59dlBgihXTAjn2L0ziFVs+oDd1bc1rxzDFZk0u5/cv3HwpkFWa/GiuSjkYJHP C7tw== X-Gm-Message-State: AOPr4FU/gYKeOLuUXtp7MjxNQSGAM4SPk8y8quhVpfgVf5Udr9CYSkPhXqrN7yg6sgl4qSVgiVkvj8isLukgAw== MIME-Version: 1.0 X-Received: by 10.50.33.176 with SMTP id s16mr6778637igi.86.1461965656586; Fri, 29 Apr 2016 14:34:16 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.50.225.172 with HTTP; Fri, 29 Apr 2016 14:34:16 -0700 (PDT) In-Reply-To: <5723B0B0.9070103@freebsd.org> References: <5723B0B0.9070103@freebsd.org> Date: Fri, 29 Apr 2016 14:34:16 -0700 X-Google-Sender-Auth: VX4N7lToWt1Ies2UU-ZEp9DIJMI Message-ID: Subject: Re: bhyve: unhandled inl 0x402 From: Craig Rodrigues To: Peter Grehan Cc: "freebsd-virtualization@freebsd.org" , "jenkins-admin@freebsd.org" , Alan Somers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 21:34:17 -0000 On Fri, Apr 29, 2016 at 12:06 PM, Peter Grehan wrote: > Hi Craig, > > I am seeing this errors in in the latest bhyve code in CURRENT: >> >> acpi0: on motherboard >> Unhandled inl 0x0402 at 0xffffffff8039c2bd >> > > Hmmm, that's a 4-byte read from the ACPI PM1 control register, which is > advertized as being size 2 in the FADT table :( The recent acpica import > might be doing this. > > John and Jung-uk are investigating, so you may wish to collaborate: https://lists.freebsd.org/pipermail/freebsd-current/2016-April/060933.html -- Craig From owner-freebsd-virtualization@freebsd.org Sat Apr 30 19:45:50 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B33A4B222C1 for ; Sat, 30 Apr 2016 19:45:50 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B7A81A01 for ; Sat, 30 Apr 2016 19:45:49 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3UJjh39009541 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Apr 2016 19:45:43 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1462045543; bh=4MJ/pfJX7EZvpTCpl73039GvF/sL4gATS1MV+/8wRyU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=k204AfAnqSt0LqrTFuWPYL94VMLvBsJmxYdmiHcr32dBKXWduZsJAhYg5pZ8iw3vo 7jD19NQT2ntvg9enurw6Ri3cR0MF8FPk6JP9EB09TNWTG8pBJKr5Ko6mOSXAWgSE9w yipLz4jObPZS3EBuLg3JvW6k0pPCt+woQNwS7OhU= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3UJjfMp009538; Sat, 30 Apr 2016 19:45:42 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Sat, 30 Apr 2016 19:45:41 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) In-Reply-To: <20160429075716.5mykxirogrlvc5pq@mac> Message-ID: References: <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> <20160426112925.hmijqrxt52kyswfg@mac> <20160429075716.5mykxirogrlvc5pq@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2016 19:45:50 -0000 On Fri, 29 Apr 2016, Roger Pau Monné wrote: > > > > ("Intel text-only image"). > > > > > > I don't think you can boot Solaris as a PV guest anymore, you should instead > > > boot it as a HVM guest. You will have to remove the kernel and ramdisk > > > options and instead add builder="hvm" (that you have left commented out). > > > > However supported or not, I think it should not crash a whole host system?... > > Certainly. I assumed that you meant it crashed the VM, not the whole host. > Can you please provide the trace of the crash? So, I tried it again ... it just quietly rebooted. No panic. During the boot I got the well-known ZFS: i/o error - all block copies unavailable ZFS: i/o error - all block copies unavailable ZFS: i/o error - all block copies unavailable Can't find /boot/zfsloader ... Marcin From owner-freebsd-virtualization@freebsd.org Sat Apr 30 20:57:05 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99C96B22E63 for ; Sat, 30 Apr 2016 20:57:05 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4762916D6 for ; Sat, 30 Apr 2016 20:57:04 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3UKutP5010033 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Apr 2016 20:56:55 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1462049816; bh=SE5ajKVuXWN0pp5RmbVyEVDg4xP0CDSqkSd2iFlBBkY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=eHnY+rku7wKAt2M4+WqQki93pDkei0KTVPYloGHnVELfW2AUn8bTuHbUC4teuvLN8 ku8SFpbx1VpdgMFfebpq5ewaY3VpWF+Z8nhK3opLJnmIA18MAqWUXF+uemt1fwBfhH RCaEK4wr24oepASBeHpe51gVK8ygBetgXLiqvZmo= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3UKus7X010030; Sat, 30 Apr 2016 20:56:55 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Sat, 30 Apr 2016 20:56:54 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?) In-Reply-To: <20160429075716.5mykxirogrlvc5pq@mac> Message-ID: References: <20160426071151.ctzdaehgfhzij6q3@mac> <20160426074302.4i3rv7wd5ogg7ful@mac> <20160426093556.oxeh5qyafe3ro6xy@mac> <20160426112925.hmijqrxt52kyswfg@mac> <20160429075716.5mykxirogrlvc5pq@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2016 20:57:05 -0000 On Fri, 29 Apr 2016, Roger Pau Monné wrote: > On Thu, Apr 28, 2016 at 08:01:23PM +0000, Marcin Cieslak wrote: > > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > > > On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote: > > > > By the way, I just managed to crash a whole machine by trying to > > > > boot Solaris 11.3: > > > > > > > > # builder = "hvm" > > > > memory = 2048 > > > > vcpus = 1 > > > > name = "Solaris0" > > > > disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ] > > > > kernel = "/root/xen/solaris/unix" > > > > ramdisk = "/root/xen/solaris/boot_archive" > > > > extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text" > > > > #boot = "c" > > > > usbdevice = 'tablet' > > > > vnc = 1 > > > > vnclisten = '0.0.0.0' > > > > vif = [ 'bridge=bridge0' ] > > > > > > > > /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso > > > > ("Intel text-only image"). > > > > > > I don't think you can boot Solaris as a PV guest anymore, you should instead > > > boot it as a HVM guest. You will have to remove the kernel and ramdisk > > > options and instead add builder="hvm" (that you have left commented out). > > > > However supported or not, I think it should not crash a whole host system?... > > Certainly. I assumed that you meant it crashed the VM, not the whole host. > Can you please provide the trace of the crash? Apologies, forgot to let Xen keep VGA: http://marcincieslak.com/tmp/xencrash.png Manual OCR: FreeBSD/amd64 (o.saper.info) (xc0) login: (XEN) vmx.c:2464:d0v0 EPT violation 0x182 (-w-/---), gpa 0x0000010178f000 (XEN) p2m-ept.c:916:d0v0 Walking EPT tables for domain 0 gfn 10178f (XEN) p2m-ept.c:922:d0v0 gfn exceeds max_mapped_pfn 10178e (XEN) vmx.c:2469:d0v0 --- GLA 0x809f18000 (XEN) domain_crash called from vmx.c:2471 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.5.2 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0043:[<000000080147bb94)] (XEN) RFLAGS: 0000000000010206 CONTEXT: hvm guest (d0v0) (XEN) rax: 0000000000000000 rbx: 0000000010f18000 rcx: 0000000002000000 (XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000809f18000 (XEN) rbp: 00007fffffffe100 rsi: 00007fffffffe0a8 r8: 0000000010f18000 (XEN) r9: 00007fffffffdfc0 r10: 000000080170058e r11: 0000000809000000 (XEN) r12: 000000080286a2d8 r13: 0000000000010f18 r14: 0000000801700a3b (XEN) r15: 000000080286a000 cr0: 0000000080050033 cr4: 00000000000406e0 (XEN) cr3: 000000000fa21000 cr2: 0000000809f18000 (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 003b cs: 0043 (XEN) Guest stack trace from rsp=00007fffffffe0a8: (XEN) Fault while accessing guest memory. (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.