From owner-freebsd-virtualization@freebsd.org Sun Apr 10 21:00:26 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 6CCCBB0B82E for ; Sun, 10 Apr 2016 21:00:26 +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 4BB861974 for ; Sun, 10 Apr 2016 21:00:26 +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 u3AL01Se070502 for ; Sun, 10 Apr 2016 21:00:26 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604102100.u3AL01Se070502@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, 10 Apr 2016 21:00:26 +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, 10 Apr 2016 21:00:26 -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 11 05:28: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 9837EAECD41 for ; Mon, 11 Apr 2016 05:28:46 +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 591871FA0 for ; Mon, 11 Apr 2016 05:28:46 +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 0C09E20B4B44 for ; Mon, 11 Apr 2016 15:28:44 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 011DB280983 for ; Mon, 11 Apr 2016 15:28:43 +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 Za6bg1GAgS4I for ; Mon, 11 Apr 2016 15:28:43 +1000 (AEST) Received: from Peters-MacBook-Pro.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id D3FF028095E; Mon, 11 Apr 2016 15:28:40 +1000 (AEST) Subject: Re: -current host, 10.1 client loops To: Poul-Henning Kamp References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <723.1460154499@critter.freebsd.dk> Cc: "freebsd-virtualization@freebsd.org" From: Peter Grehan Message-ID: <570B3604.8020500@freebsd.org> Date: Sun, 10 Apr 2016 22:28:36 -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: <723.1460154499@critter.freebsd.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=H7R7u7si c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=EA5itrwUPoEA:10 a=N659UExz7-8A:10 a=kziv93cY1bsA:10 a=9gdpRLsQfFNrkPM0q98A: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: Mon, 11 Apr 2016 05:28:46 -0000 Hi Poul-Henning, > With the host now running: > > FreeBSD 11.0-CURRENT #0 r297514M > > And (another) i386 guest running: > > FreeBSD 11.0-CURRENT #3 r297721M > > I do not see the problem. > > I'm going to try the 10.1/i386 guest over the weekend. I've not yet been able to reproduce this. I've tried 2- and 3-vCPU 10.1/i386 guests on an Intel E3-1220 v3 (single and dual virtio-blk disks), and a 2 vCPU guest on an AMD Sempron 3850 APU. Buildworlds with -j set to the number of vCPUs have completed fine. The Intel system was using file-backed images on ZFS, while the AMD system was on UFS. The guests were UFS. The console was to stdout in a tmux session that was mostly backgrounded. Was there anything particular with your buildworld ? (-j settings, etc) Also, if the guest looks like it hangs, you can extract the RIPs with bhyvectl --get-rip --cpu=0 --vm= bhyvectl --get-rip --cpu=1 --vm= This might give a hint as to where the guest is spinning. later, Peter. From owner-freebsd-virtualization@freebsd.org Mon Apr 11 12:54:43 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 C2DD7B0C203 for ; Mon, 11 Apr 2016 12:54:43 +0000 (UTC) (envelope-from rodrigo.bahiense@controller.education) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0067.outbound.protection.outlook.com [157.56.111.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03C271CC6 for ; Mon, 11 Apr 2016 12:54:42 +0000 (UTC) (envelope-from rodrigo.bahiense@controller.education) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=escolavianet.onmicrosoft.com; s=selector1-controller-education; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2u+FUlcY1tZ8+cYJY2OseIjFrANKYxX8uf5ZsRaGUmQ=; b=fQOJo5WbciecjeZ59hAuAbLz0G3dkLk4jj43GQMfL8iJ6+s5W0l+selGVvRRbXS49eQ6SUlVIiUKanxAYNE1bZzNUDUKQqqf+ejxq1egeOhYU79JOYFOUBpLWchJf5WlCI+957sShaCHt9HsjtFv3ir8WchcZ1NuXKaHSBgtZE0= Received: from FR1PR80MB1489.lamprd80.prod.outlook.com (10.167.137.23) by FR1PR80MB1489.lamprd80.prod.outlook.com (10.167.137.23) with Microsoft SMTP Server (TLS) id 15.1.453.26; Mon, 11 Apr 2016 12:39:20 +0000 Received: from FR1PR80MB1489.lamprd80.prod.outlook.com ([10.167.137.23]) by FR1PR80MB1489.lamprd80.prod.outlook.com ([10.167.137.23]) with mapi id 15.01.0453.029; Mon, 11 Apr 2016 12:39:20 +0000 From: Rodrigo Bahiense To: "freebsd-virtualization@freebsd.org" Subject: 10.3-RELEASE on VMDepot? Thread-Topic: 10.3-RELEASE on VMDepot? Thread-Index: AdGT7lXezB9NrUOORTWGzC5maQq0QA== Date: Mon, 11 Apr 2016 12:39:18 +0000 Message-ID: Accept-Language: en-US, pt-BR Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=controller.education; x-originating-ip: [177.34.143.229] x-ms-office365-filtering-correlation-id: 0b99a3eb-72a1-4616-2ff8-08d362064dc0 x-microsoft-exchange-diagnostics: 1; FR1PR80MB1489; 5:rVewop+HDwvqcl4ryrj0rf6Fx9mowqaImV83Y4WsPw0Sb9UUeb6lbCRDEMx9S3zn4KpxmKYJZ+i6ghYuQSeyf9MImxzMdSUzgRYn8frc3Fgg71+UDbzq60kR0Hu+0fb8U2zWk/UHePJklc4gfSbe9w==; 24:4smWFZ2zG45ENcEYUZrbOd5eNbbJBDu1c2c5ANj5iBTlqVdR7Qsv0zgW6SbruPJZR8qzDCVLy/watOc8KEPrSWca0sbiHfRVrKn9TZPpOds= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:FR1PR80MB1489; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040074)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041046)(6043046)(6042046); SRVR:FR1PR80MB1489; BCL:0; PCL:0; RULEID:; SRVR:FR1PR80MB1489; x-forefront-prvs: 09090B6B69 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51874003)(3280700002)(54356999)(2900100001)(92566002)(16236675004)(3660700001)(86362001)(2351001)(50986999)(5002640100001)(81166005)(558084003)(5640700001)(5630700001)(9686002)(189998001)(586003)(87936001)(19300405004)(5003600100002)(2906002)(5004730100002)(66066001)(1220700001)(3846002)(5008740100001)(1096002)(790700001)(6116002)(102836003)(77096005)(122556002)(2501003)(33656002)(19580395003)(110136002)(229853001)(19625215002)(450100001)(107886002)(11100500001)(74316001)(10400500002)(76576001)(15975445007)(46492002); DIR:OUT; SFP:1101; SCL:1; SRVR:FR1PR80MB1489; H:FR1PR80MB1489.lamprd80.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: controller.education X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2016 12:39:18.9700 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ed829911-9e0b-4296-81bc-6a483a4aaa0e X-MS-Exchange-Transport-CrossTenantHeadersStamped: FR1PR80MB1489 Content-Type: text/plain; charset="us-ascii" 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: Mon, 11 Apr 2016 12:54:43 -0000 Hi! Are there any plans for the FreeBSD Release Engineering Team to publish the= 10.3-RELEASE image on VMDepot? If so, is there any scheduled date? If not so, is there any expected proble= m on upgrading 10.2-RELEASE to 10.3-RELEASE via freebsd-update? Thanks in advance! -- Rodrigo Bahiense From owner-freebsd-virtualization@freebsd.org Mon Apr 11 17:53: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 6A93BB0C455 for ; Mon, 11 Apr 2016 17:53:30 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 006B21122; Mon, 11 Apr 2016 17:53:29 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A8E084FB03; Mon, 11 Apr 2016 17:53:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u3BHrKMo016581; Mon, 11 Apr 2016 17:53:20 GMT (envelope-from phk@phk.freebsd.dk) To: Peter Grehan cc: "freebsd-virtualization@freebsd.org" Subject: Re: -current host, 10.1 client loops In-reply-to: <570B3604.8020500@freebsd.org> From: "Poul-Henning Kamp" References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16579.1460397200.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 11 Apr 2016 17:53:20 +0000 Message-ID: <16580.1460397200@critter.freebsd.dk> 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, 11 Apr 2016 17:53:30 -0000 -------- In message <570B3604.8020500@freebsd.org>, Peter Grehan writes: Ok, host is: 11.0-CURRENT #0 r297514M: Sun Apr 3 13:11:49 UTC 2016 CPU: AMD Athlon(tm) II X3 455 Processor (3311.19-MHz K8-class CPU) Origin=3D"AuthenticAMD" Id=3D0x100f53 Family=3D0x10 Model=3D0x5 Ste= pping=3D3 Features=3D0x178bfbff Features2=3D0x802009 AMD Features=3D0xee500800 AMD Features2=3D0x837ff SVM: NP,NRIP,NAsids=3D64 TSC: P-state invariant real memory =3D 17179869184 (16384 MB) avail memory =3D 16573874176 (15806 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <090712 APIC1033> FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs FreeBSD/SMP: 1 package(s) x 3 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 Guest is (still) 10.1-R Running with: sed 's/virtio-blk/ahci-hd/' \ /usr/share/examples/bhyve/vmrun.sh \ > vmrun_ada.sh sh vmrun_ada.sh \ -m 1G \ -c 3 \ -t ${VMN} \ -d ${P}.root.dd \ -d ${P}.swap.dd \ -d ${P}.tami_install.dd \ vm${VMU} || true Hanging now, trying to build some port. I may be able to find out which exact port later, but for now I'll leave it hanging, in case you have any ideas for pulling out more info. CTRL-T in the console works load: 10.99 cmd: sh 43413 [running] 22940.67r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22940.88r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.08r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.28r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.49r 0.00u 0.00s 100% 228k ^Z ^Z load: 10.29 cmd: sh 43413 [running] 22957.30r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.49r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.66r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.83r 0.00u 0.00s 100% 228k ^Z Suspended = root@:~ # = root@:~ # = root@:~ # = root@:~ # ps -axlwH load: 10.53 cmd: csh 669 [runnable] 29867.68r 0.02u 107.86s 0% 2392k load: 10.53 cmd: csh 669 [runnable] 29868.27r 0.02u 107.86s 0% 2392k load: 10.53 cmd: csh 669 [runnable] 29868.52r 0.02u 107.86s 0% 2392k [... 3 hours later still the same ...] > Also, if the guest looks like it hangs, you can extract the RIPs with > bhyvectl --get-rip --cpu=3D0 --vm=3D > bhyvectl --get-rip --cpu=3D1 --vm=3D > > This might give a hint as to where the guest is spinning. =3D=3D> _cpu_0 <=3D=3D rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14782 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 =3D=3D> _cpu_1 <=3D=3D rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14782 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 =3D=3D> _cpu_2 <=3D=3D rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb2 Any ideas ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-virtualization@freebsd.org Mon Apr 11 22:08:07 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 DE339B0C79F for ; Mon, 11 Apr 2016 22:08:07 +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 CE49C1249 for ; Mon, 11 Apr 2016 22:08:07 +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 u3BM868p040057 for ; Mon, 11 Apr 2016 22:08:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208246] [Hyper-V] FreeBSD 10.2 Disks not found on Hyper-V Windows Server 2008R2, preventing installation Date: Mon, 11 Apr 2016 22:08:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 11 Apr 2016 22:08:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208246 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 11 22:08:16 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 4AF57B0C7D4 for ; Mon, 11 Apr 2016 22:08:16 +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 3B69512DF for ; Mon, 11 Apr 2016 22:08:16 +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 u3BM8FSC040291 for ; Mon, 11 Apr 2016 22:08:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208241] [Hyper-V] VM network may not work over virtual switch based on wireless NIC Date: Mon, 11 Apr 2016 22:08:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 11 Apr 2016 22:08:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208241 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 11 22:08:27 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 1A209B0C824 for ; Mon, 11 Apr 2016 22:08:27 +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 08DD71395 for ; Mon, 11 Apr 2016 22:08:27 +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 u3BM8QUc040587 for ; Mon, 11 Apr 2016 22:08:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards" Date: Mon, 11 Apr 2016 22:08:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 11 Apr 2016 22:08:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208238 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 11 22:09:03 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 6A9DDB0C8C8 for ; Mon, 11 Apr 2016 22:09:03 +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 3B15D14DE for ; Mon, 11 Apr 2016 22:09:03 +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 u3BM92C1041525 for ; Mon, 11 Apr 2016 22:09:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 207885] HDD fail in Virtual Box machine for FreeBSD (ZFS; Unrecovered Read error) Date: Mon, 11 Apr 2016 22:09:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 11 Apr 2016 22:09:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207885 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 11 22:22: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 B9D54B0C4FA for ; Mon, 11 Apr 2016 22:22:54 +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 AA8291604 for ; Mon, 11 Apr 2016 22:22:54 +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 u3BMMsxR076783 for ; Mon, 11 Apr 2016 22:22:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208635] XEN DOM0 not start on CURRENT Date: Mon, 11 Apr 2016 22:22:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 11 Apr 2016 22:22:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208635 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 12 04:08: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 9C665B0CC64 for ; Tue, 12 Apr 2016 04:08:55 +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 5C866133E for ; Tue, 12 Apr 2016 04:08:55 +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 560AB20A40C7 for ; Tue, 12 Apr 2016 14:08:52 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 4F6DC280986 for ; Tue, 12 Apr 2016 14:08:52 +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 vqnvTxcmvV4a for ; Tue, 12 Apr 2016 14:08:52 +1000 (AEST) Received: from Peters-MacBook-Pro.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id D0DD4280985; Tue, 12 Apr 2016 14:08:49 +1000 (AEST) Subject: Re: -current host, 10.1 client loops To: Poul-Henning Kamp References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org> <16580.1460397200@critter.freebsd.dk> Cc: "freebsd-virtualization@freebsd.org" From: Peter Grehan Message-ID: <570C74CF.1080702@freebsd.org> Date: Mon, 11 Apr 2016 21:08:47 -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: <16580.1460397200@critter.freebsd.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=H7R7u7si c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=EA5itrwUPoEA:10 a=N659UExz7-8A:10 a=kziv93cY1bsA:10 a=BKiO_RQ3zAiDmoe8k6MA: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: Tue, 12 Apr 2016 04:08:55 -0000 > CTRL-T in the console works ... > ==> _cpu_0 <== > rip[0] 0x00000000c0b14780 > rip[0] 0x00000000c0b14782 There are the RIPs that show when the system is idle. > ==> _cpu_2 <== > rip[2] 0x00000000c100feb0 This is the TLB shootdown loop: (kgdb) x/i 0xc100feb0 0xc100feb0 : pause I'll try with a bit more CPU oversubscription and see if I can hit this. Thanks for the info - this should help track it down. later, Peter. From owner-freebsd-virtualization@freebsd.org Tue Apr 12 07:10:49 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 8F262B0CC68 for ; Tue, 12 Apr 2016 07:10:49 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 58E6C1E5C; Tue, 12 Apr 2016 07:10:49 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 14FC54FB03; Tue, 12 Apr 2016 07:10:46 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u3C7AjGb020380; Tue, 12 Apr 2016 07:10:46 GMT (envelope-from phk@phk.freebsd.dk) To: Peter Grehan cc: "freebsd-virtualization@freebsd.org" Subject: Re: -current host, 10.1 client loops In-reply-to: <570C74CF.1080702@freebsd.org> From: "Poul-Henning Kamp" References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org> <16580.1460397200@critter.freebsd.dk> <570C74CF.1080702@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20378.1460445045.1@critter.freebsd.dk> Date: Tue, 12 Apr 2016 07:10:45 +0000 Message-ID: <20379.1460445045@critter.freebsd.dk> 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, 12 Apr 2016 07:10:49 -0000 -------- In message <570C74CF.1080702@freebsd.org>, Peter Grehan writes: > I'll try with a bit more CPU oversubscription and see if I can hit >this. Thanks for the info - this should help track it down. For what its worth, I think the port being compiled was: /usr/ports/www/p5-Mozilla-CAnss Another possibly relevant datapoint: The actively being written to filesystem is UFS+SU+TRIM but no journal and I think fsck sees more and worse corruption than it should if writes happened in the order Kirk intended. Specifically it should never get fsck_ffs into the "please run fsck again" jungle. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-virtualization@freebsd.org Tue Apr 12 07:50: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 59036B0DBDC for ; Tue, 12 Apr 2016 07:50:20 +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 496D316FB for ; Tue, 12 Apr 2016 07:50:20 +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 u3C7oKYZ002464 for ; Tue, 12 Apr 2016 07:50:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208635] XEN DOM0 not start on CURRENT Date: Tue, 12 Apr 2016 07:50:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 12 Apr 2016 07:50:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208635 Roger Pau Monn=C3=83=C2=A9 changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed CC| |royger@freebsd.org --- Comment #1 from Roger Pau Monn=C3=83=C2=A9 --- Hello, You need to use r297242 or later, see: https://lists.freebsd.org/pipermail/freebsd-virtualization/2016-March/00424= 3.html For more information. Roger. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 12 08:34: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 A6310B0BB4F for ; Tue, 12 Apr 2016 08:34:12 +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 966961470 for ; Tue, 12 Apr 2016 08:34:12 +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 u3C8YCN3036720 for ; Tue, 12 Apr 2016 08:34:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards" Date: Tue, 12 Apr 2016 08:34:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 12 Apr 2016 08:34:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208238 --- Comment #2 from Dexuan Cui --- The tsc-calibration fix was temporarily taken back last Friday because we f= ound an interesting thing: with some kind of config, Xen can pretend to be Hyper= -V by mimicking the hypervisor CPUID signature (this is usually to make Window= s VM run better on Xen), but Xen doesn=E2=80=99t support Hyper-V timecounter, so= the fix causes an unexpected panic when FreeBSD VM runs on Xen in this case. We're making another patch to better detect if the underlying hypervisor supports Hyper-V timecounter or not: https://lists.freebsd.org/pipermail/freebsd-current/2016-April/060519.html --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 12 08:40: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 755A3B0C135 for ; Tue, 12 Apr 2016 08:40:31 +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 6223A173E for ; Tue, 12 Apr 2016 08:40:31 +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 u3C8eVCm046110 for ; Tue, 12 Apr 2016 08:40:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards" Date: Tue, 12 Apr 2016 08:40:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 12 Apr 2016 08:40:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208238 --- Comment #3 from Dexuan Cui --- The further patches on 11-CURRENT should fix the bug safely now: https://github.com/freebsd/freebsd/commit/297e2d2f528a41d9a9614e9b34049801f= 6935b31 https://github.com/freebsd/freebsd/commit/28d2243294e521bd34a063a402382b21a= d03b262 https://github.com/freebsd/freebsd/commit/dbf747e96c50495258170a73aa5a6ab28= 8b8b958 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 12 15:44:22 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 9CC10B0E380 for ; Tue, 12 Apr 2016 15:44:22 +0000 (UTC) (envelope-from lab@gta.com) Received: from mailgate.gta.com (gb-ha.orl.gta.com [209.208.105.194]) by mx1.freebsd.org (Postfix) with ESMTP id 8319917F8 for ; Tue, 12 Apr 2016 15:44:21 +0000 (UTC) (envelope-from lab@gta.com) Received: by mailgate.gta.com (Postfix, from userid 1002) id 3566D27306C; Tue, 12 Apr 2016 11:44:14 -0400 (EDT) Date: Tue, 12 Apr 2016 11:44:14 -0400 From: Larry Baird To: freebsd-virtualization@freebsd.org Subject: iocage no longer supported? Message-ID: <20160412154414.GA65809@gta.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) 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, 12 Apr 2016 15:44:22 -0000 I was beginning to look into a replacement for ezjail, mainly because ezjail doesn't use jail.conf. After vistiting lots of sites and doing some reading, I had about decided upon iocage. I am now convered about this decision. When I visit https://github.com/iocage/iocage is now says "**No longer supported. iocage is being rewritten in a differnt language." Does anybody have any details? Thanks, Larry -- ------------------------------------------------------------------------ Larry Baird Global Technology Associates, Inc. 1992-2012 | http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: lab@gta.com | TEL 407-380-0220 From owner-freebsd-virtualization@freebsd.org Tue Apr 12 20:19: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 1D204B0D499 for ; Tue, 12 Apr 2016 20:19:41 +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 0DCD61657 for ; Tue, 12 Apr 2016 20:19:41 +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 u3CKJeeI008336 for ; Tue, 12 Apr 2016 20:19:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 198344] [virtio] virtio-balloon does not work Date: Tue, 12 Apr 2016 20:19:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: brd@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-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, 12 Apr 2016 20:19:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198344 --- Comment #7 from Brad Davis --- It looks like this should be fixed in this MFC: https://svnweb.freebsd.org/base/stable/10/sys/dev/virtio/balloon/virtio_bal= loon.c?view=3Dlog Can someone test 10.3 and let us know? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Apr 13 04:06:34 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 9B791B0DBE0 for ; Wed, 13 Apr 2016 04:06:34 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id E1FB9154D for ; Wed, 13 Apr 2016 04:06:33 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 94010 invoked by uid 89); 13 Apr 2016 03:06:29 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 13 Apr 2016 03:06:29 -0000 Date: Tue, 12 Apr 2016 19:02:24 +0200 From: Michael Gmelin To: freebsd-virtualization@freebsd.org Subject: Re: iocage no longer supported? Message-ID: <20160412190224.051239ac@bsd64.grem.de> In-Reply-To: <20160412154414.GA65809@gta.com> References: <20160412154414.GA65809@gta.com> X-Mailer: Claws Mail 3.13.2-105-g3e2337 (GTK+ 2.24.29; amd64-unknown-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= 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: Wed, 13 Apr 2016 04:06:34 -0000 On Tue, 12 Apr 2016 11:44:14 -0400 Larry Baird wrote: > I was beginning to look into a replacement for ezjail, mainly because > ezjail doesn't use jail.conf. After vistiting lots of sites and doing > some reading, I had about decided upon iocage. I am now convered > about this decision. When I visit https://github.com/iocage/iocage is > now says "**No longer supported. iocage is being rewritten in a > differnt language." Does anybody have any details? > https://github.com/iocage/iocage/commit/3f394561a3dde55cd3ac7911be313c5df5865183 -- Michael Gmelin From owner-freebsd-virtualization@freebsd.org Wed Apr 13 10:44:23 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 629B7B0F478 for ; Wed, 13 Apr 2016 10:44:23 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 38A641A6A for ; Wed, 13 Apr 2016 10:44:22 +0000 (UTC) (envelope-from ifebi@schema31.it) Received: by mail-io0-x243.google.com with SMTP id u185so6178179iod.2 for ; Wed, 13 Apr 2016 03:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=schema31-it.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to; bh=f0n5qr1UEVJj3CcPhGv3IvaPYVxrhuOBvq8V4aPYw9Q=; b=HNJIgyojqrlt3UPF8Qe5R/F5pRe81azfC8qcgw/Cp3sD+v/PmyP2IZBX0pCJeZlMvQ mJ0aExS8Q5GxvcWebMyqaHpxSc5bExT94qx+8sahudgan4MyptUpBbuLIwc8QXnZ+/YD chA+rhBrWr2CnFtgS7lPPAkW7XlYN66d2NHgpm/ziPeQWIQR4FyPqXvd1KL2DUWvE1eG t1ePYRTyxGIOVUSP1HOxQatVq8MkiINhOf4H+hgxnPBj357AdP7iGkx0frRp9Hap8Xfp eR2HAWrGhscIwoOf/h9s2J3nKkscDhU21cCP/whwvne5JxowChkeF5bdPtd00v3WlV+x KBBQ== 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=f0n5qr1UEVJj3CcPhGv3IvaPYVxrhuOBvq8V4aPYw9Q=; b=AM0PkMAC+QW25Q63WkqzoWl9u87It3Yowwpd87RxdxksBFL+1h3tM3t2+nDj5V0uTo GiIRvkW7WMsgcUdoL18JV+BqnT+TFbNZonFBb/XKwULFEcxfkY+tt5ClBfnFN+ZuWuo9 jqOnuXO+q6m0V9NEG7ZByf2bjLDEbf8I3NNgnTP6Cmsg1GcD7EfaYow0uXOLF8sVGrB7 2cbEaM7apxvdpCkGuOyA7JQ7ezCcuVQ7lug3r9EE/wejjQiJE3PFXyzn4PXseT1CnTgP U4uZv8Z6590V7xgZAtCTOg9dYQZjZ/fdYXTDDycxM7rNpu89Ofutx7dzjSYPZhzYSrF4 0U/Q== X-Gm-Message-State: AOPr4FVRsb4DDyywhJmN4VA4PCW6zsHMkIUBDOAj7T6p1nfn5Y0vX1S7yW8RxaxV/KCUPn3MrS2MZEOvQhnZ/A== MIME-Version: 1.0 X-Received: by 10.107.26.201 with SMTP id a192mr9548411ioa.13.1460544262200; Wed, 13 Apr 2016 03:44:22 -0700 (PDT) Received: by 10.36.127.132 with HTTP; Wed, 13 Apr 2016 03:44:22 -0700 (PDT) X-Originating-IP: [2001:470:28:12b::7] Date: Wed, 13 Apr 2016 12:44:22 +0200 Message-ID: Subject: bhyve clock issue From: Ilario Febi 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, 13 Apr 2016 10:44:23 -0000 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. From owner-freebsd-virtualization@freebsd.org Wed Apr 13 10:55: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 9742BB0FA62 for ; Wed, 13 Apr 2016 10:55:28 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (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 28E41180A for ; Wed, 13 Apr 2016 10:55:28 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-lf0-x244.google.com with SMTP id e190so6658260lfe.1 for ; Wed, 13 Apr 2016 03:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=wk8KN/7nmGK/0/2Ndx4wVwE/ILtRqJ13VFl+ubbdnFE=; b=BJn0pibyo5tJKlIz3FgCvDTpIOqxiF/2t4wLxrvdVPjnSIEXnav86aICPZK/pbQDsp Dr9Nyd3Na61wQYmEURFHn0fy3IDhl/qCKDQl6CNviAAxYzc1oadUknCIy308PzIMsMxA iyw5cWlb9wVXgILLdOYwJIczkHkwqHjIFVZjYrPJdJ5OW7ZlGU6LUfN3WjJEr7kgmavc m4hC3qrA1R6B7VEDgib5sove3wwVDce2qtzjiU4u9CWM3SZHqDqOLH3Bje6LR3oihLPn ij5/5nRGDEePhnYEDYGXCQoWIGWMeGuLsnmWH0KJ4cpZ/LqJtdomty7sAJtaOtCxwshh Dzhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=wk8KN/7nmGK/0/2Ndx4wVwE/ILtRqJ13VFl+ubbdnFE=; b=iyj+nO7y9ZH30BKCWQ3i5uAyZ0LcT7Eh1hJxd42RhcjKJsRyQ31P3IRisR3rRroXOE EDNOwsRVED064UMGRywT63QvN3K8cXzZy45M0SqkHhRzAmXQqAQXzsy1IsnvP2oYo54E h6kfU3Zv5zl//Glz5Sx2rMrMgKCQhh/uGpBjb2v/stvqy52tX0kjNtef1lZJpluPUzWg 9LjaaOGKkggaL05QAbWXkgpcQ+BNoVtXvzF8V1S/FKAheWb/pIJq+Ljv/SYwZSZG0N0e wjDHYUOwj0VT+2fyQTJt8oqZl723LcKZwBKifxGN2jqW3w/4BP875TnLwjU93Q6VHIYx aIpQ== X-Gm-Message-State: AOPr4FUpefyCJUfVIPS3kLNTODs71MH1E0tghp6OszlGJNl1GzN+N3GJw5WseBswfuC41w== X-Received: by 10.25.149.144 with SMTP id x138mr3673735lfd.88.1460544926129; Wed, 13 Apr 2016 03:55:26 -0700 (PDT) Received: from dev.san.ru ([88.147.129.60]) by smtp.gmail.com with ESMTPSA id us9sm1883820lbc.24.2016.04.13.03.55.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Apr 2016 03:55:24 -0700 (PDT) Date: Wed, 13 Apr 2016 13:55:22 +0300 From: Roman Bogorodskiy To: freebsd-virtualization@FreeBSD.org Subject: Understanding Bhyve shutdown Message-ID: <20160413105520.GB84953@dev.san.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) 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, 13 Apr 2016 10:55:28 -0000 Hi, I was trying to get better understanding of how to properly shutdown VMs in bhyve, but unfortunately the documentation does not provide much details on that. Specifically, handbook [I] suggests to reboot a machine and then run bhyvectl --destroy on it. The bhyvectl(8) manpage mentions the '--force-reset' and '--force-poweroff' switches, but does not give details on those. I: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html I tried all the options I know and wrote down the results. I also have some questions, hopefully you'll be able to answer some of them. 1. bhyvectl --vm=$name --destroy * looks like hard poweroff in the guest * the corresponding bhyve(8) process goes away * /dev/vmm/ entry goes away In my experience, it's a dangerous way to shutdown a VM because sometimes it appears it damages the image and VM fails to boot with something like this: --- Starting devd. mode = 0100600, inum = 170269, fs = / panic: ffs_valloc: dup alloc cpuid = 0 KDB: stack backtrace: #0 0xffffffff80984e30 at kdb_backtrace+0x60 #1 0xffffffff809489e6 at vpanic+0x126 #2 0xffffffff809488b3 at panic+0x43 #3 0xffffffff80b74a6e at ffs_valloc+0x84e #4 0xffffffff80bb60ad at ufs_makeinode+0x7d #5 0xffffffff80bb24fd at ufs_create+0x2d #6 0xffffffff80e71841 at VOP_CREATE_APV+0xa1 #7 0xffffffff809cd9e6 at uipc_bindat+0x346 #8 0xffffffff809c5488 at kern_bindat+0x108 #9 0xffffffff809c52a7 at sys_bind+0x77 #10 0xffffffff80d4b3f7 at amd64_syscall+0x357 #11 0xffffffff80d30adb at Xfast_syscall+0xfb Uptime: 3s Dump failed. Partition too small. --- 2. kill -SIGTERM $bhyve_pid If guest supports ACPI shutdown: * guest shuts down cleanly * the corresponding bhyve(8) process terminates * /dev/vmm entry is still here, need bhyvectl --destroy for complete cleanup If guest does not support ACPI shutdown (such as doing sysctl hw.acpi.power_button_state=NONE): * Nothing happens Q1: Is there a way to know if a guest reacted to power button but waiting for the bhyve process to terminate? Q2: Why it's not done via bhyvectl (it seems that it's easier for users + don't have to overload a useful SIGTERM signal) 3. bhyvectl --vm=$name --force-poweroff * looks like hard poweroff in the guest * the corresponding bhyve(8) process goes away * /dev/vmm entry is still here, need bhyvectl --destroy for complete cleanup Q: what's the practical difference with just doing --destroy right away? 4. bhyvectl --vm=$name --force-reset Looks very similar to item #3 with just different exit code (reboot appears to be using 0, while shutdown and halt use 1 and 2). Q: what's the practical use of it? Would greatly appreciate if somebody could provide more details on that. I guess we'll need to update Handbook with this information as well because it needs to mention SIGTERM for ACPI shutdown at least. Roman Bogorodskiy From owner-freebsd-virtualization@freebsd.org Wed Apr 13 12:37:26 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 463B8B0E337 for ; Wed, 13 Apr 2016 12:37:26 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F17D1246 for ; Wed, 13 Apr 2016 12:37:25 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([91.140.61.167]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MXmpv-1bJl751GY3-00WqDj; Wed, 13 Apr 2016 14:37:16 +0200 Subject: Re: Understanding Bhyve shutdown To: Roman Bogorodskiy , freebsd-virtualization@FreeBSD.org References: <20160413105520.GB84953@dev.san.ru> From: Nikos Vassiliadis Message-ID: <570E3D59.5090609@gmx.com> Date: Wed, 13 Apr 2016 15:36:41 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160413105520.GB84953@dev.san.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0xLEs3NlbcVAkYhMF4Q0osMF7Rl3s+85kPzaTK10wJvsBjBc5+F wm1DNEeNzB4RGwyxT/1yUZWIO9HFuRRC5qBrbPW7tkk7QQXjgPXkHcOLDOEugjb9eLw/9kz 1EE6fIZuF7v85qsUm/Gn8oVXgYd3KwB20fcL2rpZIw9mWsf/ybhi0p+4Dxi4gfYZqc8F8u8 xJUtp7AuiDkkDN6R885Yw== X-UI-Out-Filterresults: notjunk:1;V01:K0:KL0W+QPajMs=:6jvAXD656NSaZClRnVBCBM LdfXd9sZdCvyVIWZBj/J/8T4zmJN4NGLHml3okdAhie4yrcDuEk44gQpu8GmJynmv1K2qP+HB PP1FrujQB+Ud4Vcl/NE5FTQuXDI5/BFvJihRKYTuSafkcc3B0lkCrbe+H/uVrsYqe/FQCdrqE ub16SVMH473QFJ04ZaOnjTyvc6YSPJSw4ik4Wzvi9no4UwXYWPh6y9NH5AYH4gBWR53kcwfQE 1JzhPn26JP4yVG0BttrHRer1H2qrh9KBhHd13+Vg7Kp+QFTPAdjsfByHd4ISWCpJ+M+QTTRT3 YqgpzdFwPHiY4SsjfNCSQEJghKksAzaweFXIo3d3RfOvcWSt3ilfseJ7kJdF08UWItmcUhLk0 A18rIgRgBG7osDnESfgjvzk+rMb1KSjLSgBGVlxoevEIL/AXwR7dHUWXY6TtNoMjMnOOD73U2 /fM2uu8pFw8Dv02TmBJRIo340oPeY8ZN1NV/NEA/r3bOCZPTXkNMmvM+wC/Zn1dKXRPShOjqE uVHn7xfC2g7F6ID+PjVBrnrfifR85fVPppUDjOHg18GRo0lA7SJepk6jV+XYhThUt6JEQTDhk FBqNNhNjZrp8zGP9KCkvY9rOrEp+ncv/lta47wSmlVrDbBatctY7Rzzdm3Jmv/qJKFB8SUVU7 otfpA8QMUpWX9nzUQTOKDhQ9DDW5nZZ3pv3F+wF6M0ZzKcpJCsTvu5oqRg4mK5UOQHPz9mwPF 9nTOeboo/Qm58bj0KvUIqrXUKeE5Cw/3hej7t9NfRl3PW0O+HZm71r1BohDdqYPaVX9IMe8nH S6xkRez 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, 13 Apr 2016 12:37:26 -0000 Hi Roman, On 04/13/16 13:55, Roman Bogorodskiy wrote: > Q1: Is there a way to know if a guest reacted to power button but > waiting for the bhyve process to terminate? I just signal repeatedly $bhyve_pid until it's gone. For what it's worth, I use this /etc/rc.shutdown.local: PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin # shutdown VMs for sig in TERM KILL; do for f in 1 2 3 4 5 6 7 8 9 10; do cmds=`killall -${sig} -q -s bhyve | sed 's/$/;/'` test -z "$cmds" && exit sh -c "$cmds" sleep 1 done done When a VM is hang, it won't respond to TERM, so you might want to use something like, 'for sig in TERM HUP KILL'. It works ok in my experience and I do have some VMs running Java which take a while to shutdown. Our VMs usually shut down within one or two seconds, the Java ones need more but still within ten seconds everything is gone. Experiment a bit and give it enough time to shutdown gracefully and if it's still alive SIGHUP $bhyve_pid. HTH, Nikos From owner-freebsd-virtualization@freebsd.org Wed Apr 13 14:15:33 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 633B0B0EBF5 for ; Wed, 13 Apr 2016 14:15:33 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1588A1775 for ; Wed, 13 Apr 2016 14:15:32 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id u3DEFG5h091864 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Apr 2016 15:15:17 +0100 (BST) (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1460556919; bh=GTJB8VNwGaHpoi9j5aE/ZBGqGB1J/8saNZNuyuz4IXk=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=WBmqzCtdhcICHhLDyA1JUhWiBFW4yU+s+lQQh/69D9JgWnC6oQ/bSNffMMpeE7k88 nqsd/Ne16MslRYMzp7OvNNS+kLmmKdGpvjbDeRkV0ttN+gQWpOojE2ehEkv8adrsIB /8hbdwutBXNx4hyXTOgjxs/A7cbFivZ1WqgCE3zE= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 13 Apr 2016 15:15:11 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Wed, 13 Apr 2016 15:15:10 +0100 From: Matt Churchyard To: Roman Bogorodskiy CC: FreeBSD virtualization Subject: RE: Understanding Bhyve shutdown Thread-Topic: Understanding Bhyve shutdown Thread-Index: AQHRlXMDYRnGHYTzkkieaIiropecY5+H6fIQ Date: Wed, 13 Apr 2016 14:15:10 +0000 Message-ID: <548d6c81c4784447b91f6f1459863eed@SERVER.ad.usd-group.com> References: <20160413105520.GB84953@dev.san.ru> In-Reply-To: <20160413105520.GB84953@dev.san.ru> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] 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: Wed, 13 Apr 2016 14:15:33 -0000 As I understand it 1) shutdown from guest 2) 'kill ' -> pressing the power button once. 3) --force-poweroff -> holding power button in 4) --force-reset -> pressing the reset button 5) bhyvectl --destroy -> same as 3? (although vmm is destroyed as well) 1 or 2 are obviously preferred. I've found however that some guests don't r= espond that well to the apci event. CentOS 6 seems to need apci installing = and enabling?!, and my Win2012R2 machine will only shutdown if I send the s= ignal twice. The rest are all hard shutdowns that should not be seen as a way to stop th= e guest, just a last resort if it can't be stopped correctly. I don't know = the practical difference between poweroff&destroy vs just destroy. I see no reason why the documentation suggests reboot rather than shutdown.= Bhyve exits either way and the only difference is the exit code. When usin= g one of the bhyve management tools that support reboots (such as vmrun.sh/= vm-bhyve/iohyve) however, a "restart" exit code (0) will cause the guest to= restart automatically; If a guest is locked up for example, a --force-rese= t will cause it to immediately reboot. >From a host, the only safe choice is 'kill ' (possibly multiple times)= and wait for bhyve process to (hopefully) exit. If that doesn't work eithe= r the acpi issue needs fixing or ideally the guest needs to be stopped usin= g its built-in shutdown function. The devs will have to confirm why they're implemented the way they are. My = instinct is that bhyvectl works on the vmm device, and reset/poweroff are j= ust functions that are possible via that interface, and so have been expose= d. The ACPI shutdown event likely needs to be initiated by the bhyve proces= s itself, hence using a signal to it. /end-speculation I think most users will want to use a bhyve tool so the raw specifics of th= e bhyve/bhyvectl commands are glossed over, although that doesn't mean the = handbook documentation of the base commands shouldn't be as complete/correc= t as possible of course. Matt -----Original Message----- From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-virtua= lization@freebsd.org] On Behalf Of Roman Bogorodskiy Sent: 13 April 2016 11:55 To: freebsd-virtualization@FreeBSD.org Subject: Understanding Bhyve shutdown Hi, I was trying to get better understanding of how to properly shutdown VMs in= bhyve, but unfortunately the documentation does not provide much details o= n that. Specifically, handbook [I] suggests to reboot a machine and then run bhyvec= tl --destroy on it.=20 The bhyvectl(8) manpage mentions the '--force-reset' and '--force-poweroff'= switches, but does not give details on those.=20 I: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html I tried all the options I know and wrote down the results. I also have some= questions, hopefully you'll be able to answer some of them. 1. bhyvectl --vm=3D$name --destroy * looks like hard poweroff in the guest * the corresponding bhyve(8) process goes away * /dev/vmm/ entry goes away In my experience, it's a dangerous way to shutdown a VM because sometimes i= t appears it damages the image and VM fails to boot with something like thi= s: --- Starting devd. mode =3D 0100600, inum =3D 170269, fs =3D / panic: ffs_valloc: dup alloc cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff80984e30 at kdb_backtrace+0x60 #1 0xffffffff809489e6 at vpanic+0x126 #2 0xffffffff809488b3 at panic+0x43 #3 0xffffffff80b74a6e at ffs_valloc+0x84e #4 0xffffffff80bb60ad at ufs_makeinode+0x7d #5 0xffffffff80bb24fd at ufs_create+0x2d #6 0xffffffff80e71841 at VOP_CREATE_APV+0xa1 #7 0xffffffff809cd9e6 at uipc_bindat+0x346 #8 0xffffffff809c5488 at kern_bindat+0x108 #9 0xffffffff809c52a7 at sys_bind+0x77 #10 0xffffffff80d4b3f7 at amd64_syscall+0x357 #11 0xffffffff80d30adb at Xfast_syscall+0xfb Uptime: 3s Dump failed. Partition too small. --- 2. kill -SIGTERM $bhyve_pid If guest supports ACPI shutdown: * guest shuts down cleanly * the corresponding bhyve(8) process terminates * /dev/vmm entry is still here, need bhyvectl --destroy for complete cleanup If guest does not support ACPI shutdown (such as doing sysctl hw.acpi.power_button_state=3DNONE): * Nothing happens Q1: Is there a way to know if a guest reacted to power button but waiting for the bhyve process to terminate? =20 Q2: Why it's not done via bhyvectl (it seems that it's easier for users + don't have to overload a useful SIGTERM signal) 3. bhyvectl --vm=3D$name --force-poweroff * looks like hard poweroff in the guest * the corresponding bhyve(8) process goes away * /dev/vmm entry is still here, need bhyvectl --destroy for complete cleanup Q: what's the practical difference with just doing --destroy right away? 4. bhyvectl --vm=3D$name --force-reset Looks very similar to item #3 with just different exit code (reboot appears to be using 0, while shutdown and halt use 1 and 2). =20 Q: what's the practical use of it? Would greatly appreciate if somebody could provide more details on that. I guess we'll need to update Handbook with this information as well because= it needs to mention SIGTERM for ACPI shutdown at least.=20 Roman Bogorodskiy _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/m= ailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" From owner-freebsd-virtualization@freebsd.org Thu Apr 14 06:03:36 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 AE39EB10E8F for ; Thu, 14 Apr 2016 06:03:36 +0000 (UTC) (envelope-from abrancatelli@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 2E81419CF for ; Thu, 14 Apr 2016 06:03:35 +0000 (UTC) (envelope-from abrancatelli@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 u3BJZpRc082107; Mon, 11 Apr 2016 21:35:53 +0200 (CEST) (envelope-from abrancatelli@schema31.it) MIME-Version: 1.0 Date: Mon, 11 Apr 2016 21:35:50 +0200 From: Andrea Brancatelli To: freebsd-virtualization@freebsd.org Cc: Ilario Febi Subject: bhyve clock jitter Organization: Schema31 s.r.l. Message-ID: <3d1e9bbda3b402e8b185fd27cc4dceee@schema31.it> X-Sender: abrancatelli@schema31.it User-Agent: Roundcube Webmail/1.1.4 Content-Type: text/plain; charset=UTF-8 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: Thu, 14 Apr 2016 06:03:36 -0000 Hi ... 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. -- Andrea Brancatelli Schema31 S.p.a. Responsabile IT ROMA - BO - FI - PA ITALY Tel: +39.06.98.358.472 Cell: +39.331.2488468 Fax: +39.055.71.880.466 Società del Gruppo SC31 ITALIA From owner-freebsd-virtualization@freebsd.org Thu Apr 14 06:03:35 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 8F7ECB10E89 for ; Thu, 14 Apr 2016 06:03:35 +0000 (UTC) (envelope-from abrancatelli@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 285A619CD for ; Thu, 14 Apr 2016 06:03:33 +0000 (UTC) (envelope-from abrancatelli@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 u3DAa6aA022418; Wed, 13 Apr 2016 12:36:06 +0200 (CEST) (envelope-from abrancatelli@schema31.it) Subject: Fwd: bhyve clock jitter References: <3d1e9bbda3b402e8b185fd27cc4dceee@schema31.it> From: Andrea Brancatelli Mime-Version: 1.0 (1.0) X-Mailer: iPad Mail (13E238) Message-Id: <0D35099D-C959-4713-999D-2E5F2AD3A7C9@schema31.it> Date: Wed, 13 Apr 2016 12:36:01 +0200 Cc: Ilario Febi 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: Thu, 14 Apr 2016 06:03:35 -0000 Hi ... I have a strange issue about the clock of some FreeBSD Bhyve guests, maybe s= omeone of you can help me to diagnose it and work on a solution. In detail, sometimes (without an apparent regularity) one of four bhyve gues= t'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 int= ervention, 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=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" @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 noquer= y [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 noquer= y [og-test] out: restrict 127.0.0.1 [og-test] out: restrict -6 ::1 [og-test] out: restrict 127.127.1.0 Some observation:=20 * 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 $mach= ine /usr/sbin/bhyve -c 2 -m 2048 -A -H -P -s 0,hostbridge -s 2,ahci-hd,/san_stor= age/VMfs/$machine/$machine.img -s 4,virtio-net,$tap -s 31,lpc -l com1,stdio $= machine Thanks in advance. =20 --=20 Andrea Brancatelli Schema31 S.p.a. Responsabile IT ROMA - BO - FI - PA=20 ITALY Tel: +39.06.98.358.472 Cell: +39.331.2488468 Fax: +39.055.71.880.466 Societ=C3=A0 del Gruppo SC31 ITALIA From owner-freebsd-virtualization@freebsd.org Thu Apr 14 06:24:47 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 68F8FB0F3E9 for ; Thu, 14 Apr 2016 06:24:47 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 36D7410C2 for ; Thu, 14 Apr 2016 06:24:47 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-io0-x231.google.com with SMTP id 2so94600025ioy.1 for ; Wed, 13 Apr 2016 23:24:47 -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=lvqGRVh9uEmuuFyyz9ex34o3S44NtuzxWAS6WQZQ8oQ=; b=eETsTDWPsTw8baTajfpEF7kT4BKIk/a7fy08Nw6CNmjZKjJegwH9fqqWN5O0ptRHE+ PgvC8S1MkLvhe35bNrTefGyY7DuMZ4WABQSfseM2kQBYFyvovNoa3mYiqKjo7AnINTtR /mGwX848k7xgm7FOaDTmcopPIUzjHhmxtIsPKSbeu7Y9xHCBKQUYoWeD7pHcJAPOcAQY +YzXs5vq22zvgCeJpa5lgpMvoVZ41Pbt6JZnzz33V/D7wMEEWhydyIqyQoXt5a6v9eBF 1pd6aGEsxyoz1NgpNJuRZAnLzwGZPEVbrHIi3DGWNJkQsKSnjQEFYgdzqSy7W4UqPPTl O+YQ== 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=lvqGRVh9uEmuuFyyz9ex34o3S44NtuzxWAS6WQZQ8oQ=; b=ZGYgbG+W07CT1vZYABa0Ll7NtqyAGkTWN4rqxS3G4CWP/U51fE7xoqXjczWQi1uM3I l+tKLdxvXd2lUEIvVc3VF6fP21njlSf2DEITYI4O9hMuW/Bl0umtvjcNFMRg+A7oedh/ YPX00yDHAtGMLKfXPNTTLsbQEqa0gYj30jv67nG6t6bgcuZkJRrBAtOgJQP6jkZqqIhO tPO1fZFkK7n+wfbX8Gx9XCOkr6ALbt7rzLrGTEN/extBkxThN0tZSCATyd5aHrv+evOn xIp/iFcrCyavw4Db7CV+7hauxZHr/KKGiggUUW5AMf/Eq2BRdkjVuHRIUN0+dQ+XT2ph ZwPw== X-Gm-Message-State: AOPr4FULVU3dDRofgs2XWn9wpoXG6ShCA4JPEyeqhty4g0jRoPDomSaVlRpfOQwmo4LVQ/+cS56Y+Z8pURoc9A== MIME-Version: 1.0 X-Received: by 10.107.168.233 with SMTP id e102mr15980389ioj.55.1460615086638; Wed, 13 Apr 2016 23:24:46 -0700 (PDT) Received: by 10.107.156.132 with HTTP; Wed, 13 Apr 2016 23:24:46 -0700 (PDT) Date: Thu, 14 Apr 2016 01:24:46 -0500 Message-ID: Subject: Xen from ports won't boot using -CURRENT From: Dustin Marquess 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: Thu, 14 Apr 2016 06:24:47 -0000 Hello! I'm using a -CURRENT install from a couple of weeks ago: FreeBSD 11.0-CURRENT #0 r297495: Fri Apr 1 21:24:26 UTC 2016 I installed xen from ports and followed the instructions on setting up: /etc/sysctl.conf /etc/ttys /boot/loader.conf /boot/menu.rc.local However after rebooting, booting fails with: don't know how to load module '/boot/xen' I'm guessing it's because for some reason it got compiled as 32-bit: /boot/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped I assume on amd64 it should be 64-bit? Thanks! -Dustin From owner-freebsd-virtualization@freebsd.org Thu Apr 14 09:59:18 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 CBC34B0F189 for ; Thu, 14 Apr 2016 09:59:18 +0000 (UTC) (envelope-from prvs=90533d348=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 9094618B5 for ; Thu, 14 Apr 2016 09:59:18 +0000 (UTC) (envelope-from prvs=90533d348=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,484,1454976000"; d="scan'208";a="347041033" Date: Thu, 14 Apr 2016 11:59:09 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Dustin Marquess CC: Subject: Re: Xen from ports won't boot using -CURRENT Message-ID: <20160414095901.smr5pwye7tznjnmg@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: 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: Thu, 14 Apr 2016 09:59:18 -0000 On Thu, Apr 14, 2016 at 01:24:46AM -0500, Dustin Marquess wrote: > Hello! > > I'm using a -CURRENT install from a couple of weeks ago: > > FreeBSD 11.0-CURRENT #0 r297495: Fri Apr 1 21:24:26 UTC 2016 > > I installed xen from ports and followed the instructions on setting up: > > /etc/sysctl.conf > > /etc/ttys > > /boot/loader.conf > > /boot/menu.rc.local > > > However after rebooting, booting fails with: > > > don't know how to load module '/boot/xen' > > > I'm guessing it's because for some reason it got compiled as 32-bit: > > > /boot/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), > statically linked, stripped Xen is always going to present itself as a 32-bit executable, although it's only the entry point that runs in 32bit mode, then it jumps into long mode by itself. Are you maybe trying to boot it from UEFI? (using the UEFI loader) Roger. From owner-freebsd-virtualization@freebsd.org Thu Apr 14 16:13: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 E8B5DB0F10A for ; Thu, 14 Apr 2016 16:13:32 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::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 AFF4214B8 for ; Thu, 14 Apr 2016 16:13:32 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-pa0-x230.google.com with SMTP id ot11so46178376pab.1 for ; Thu, 14 Apr 2016 09:13:32 -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=Key+BaEmrtqraOGdwYv0ozDPOvUjYw+isc272eCat4Y=; b=qvQqafE52FZC1R2U0nQ9L+zJYxW5lLuQRxR4nQdFFNxWb/h5sJq3FH00F/qn3xYvi+ Km8niSeB5xGBx+pvw4SfS8rAJ2GRgyQSWFUl/OI/O7MkxE+2+BleuGuqXD/9Fl2OZH6r B+kcuvLSkGD/pfM7FHA4zSOPdSr7c3zbanKEB8EXCtBV6y1CoCZbnUp1LudsU3SBIyl5 hk9y6xwl284TRYbtVBwJZVYY6rIHyI+KZlP6KcAHBGGQV2U11zu/eEWts6cWzD1EQ4L4 C28CeUzn7jC+siY/rF4XVL+YZ9xCBQFAFsY9US/I3p+INXb+B6aPFvcRepdYRyCc89d0 24JQ== 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=Key+BaEmrtqraOGdwYv0ozDPOvUjYw+isc272eCat4Y=; b=HOKO+4putVuGyt/ad6g6FyekdYcLH+PYTN9GH2TWsAvjLlo9T1aRDJ1hPWHDlow2Dx vg9X1AsKZ74FQ7ikOOjaqjJ8ZpfxHIpHorXbNvEP2ZseSOxJKgaLgI49SUoxplrI03DW hhOl0ayuWltfFjv5Z9eag/jgIShyHFxBTVLnWmt9E7rDLwysVbVqz/adFrxy9qT7WSRI /02iTzfUnysps2gDLzKJh5USOScSy1EKwLSa4wHTKyPlGUKEgYqy1Erfzud9YNtLwcKG qo1Ag0kWFObgk+AsAkJPavWxpzUXaepNGTfPqcD1/hN8kw5Q/fp7oNt7+dp08erfq5ny 90kA== X-Gm-Message-State: AOPr4FWfW+Bhk5fQdUb6304AHzqwt+xTRbG2Rm7J27TCFZ+RwHZevBvvV8qPSL/xk6sKJg== X-Received: by 10.66.66.198 with SMTP id h6mr22102603pat.112.1460650412066; Thu, 14 Apr 2016 09:13:32 -0700 (PDT) Received: from ?IPv6:2602:306:ce40:d9e0:9559:faaa:281a:19e7? ([2602:306:ce40:d9e0:9559:faaa:281a:19e7]) by smtp.gmail.com with ESMTPSA id g28sm58940548pfd.25.2016.04.14.09.13.30 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2016 09:13:30 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <8EE098BA-6C8F-41F4-B9CD-88F3D587B10F@gmail.com> Cc: "freebsd-virtualization@freebsd.org" X-Mailer: iPhone Mail (11D257) From: Neel Natu Subject: Re: bhyve clock issue Date: Thu, 14 Apr 2016 09:13:26 -0700 To: Ilario Febi 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, 14 Apr 2016 16:13:33 -0000 Hi, Did you see anything interesting in the ntpd log file around the time the la= rge skew happened? Best Neel > 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 is= : >=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 'ou= t: #' > [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 noqu= ery > [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 noquer= y > [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 noquer= y > [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 noquery= > [og-test] out: restrict -6 default limited kod nomodify notrap nopeer noqu= ery > [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 on= e). > * 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 $ma= chine > /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@freeb= sd.org" From owner-freebsd-virtualization@freebsd.org Thu Apr 14 17:25:42 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 31917ADABD5 for ; Thu, 14 Apr 2016 17:25:42 +0000 (UTC) (envelope-from dmarquess@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 F04DC1CDE for ; Thu, 14 Apr 2016 17:25:41 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-ig0-x236.google.com with SMTP id gy3so154091671igb.0 for ; Thu, 14 Apr 2016 10:25:41 -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=i8v29FxXyDhUY9XxnvdNLmdsB+dBejMaULvJ6FtzjrY=; b=SDfHRAw9A322vS2vuCq57H3BQeIxWn4OM7CSmXYHf93IeHpJ3iI9SluU7RgWSO4gWt Hq3cDK+CveiB77cHCdIbcR/TMvMvEgjWyPr9cFRcdQkjKCwYiVIjkLN//HJQV06+yODU UcjN9CUfqN7wiAPxd/zL15IMGrKq5bqlM0wQRD1Zc6eGVMoC/u1YCVepyhwccCGrkoV3 t7Lrh5e/XgsC1r0JhrExEmr//aNkdWkWZcIdlUCYRAIIs1HQ/HrAsYBZe3duKRWcrsLU nJY3iAI2Lnx62FUK3gts4riQLAZcYawhA5IWYQruWM4+hyVgSz3Mps3bsOb7ArUa3X/Z bUBw== 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=i8v29FxXyDhUY9XxnvdNLmdsB+dBejMaULvJ6FtzjrY=; b=H0XyTUBj8aOx/XhkgEnRC3ORgrdlmyGHtnKfOrn6CGblT1Q52PjJVZHSihL88TjlsG D63BFTNGMUUbXZcANrsSLpjj4Li0rs6GUc26MuSHVmfFTXB7ez1RmL9N/gpsafoFbFBW zpAQlB25TPjDMcpTftGfYIuyQQLAAbWm4na1Y0bQkGv5oYwZaVFbzsPHPL9fbOK7WO7l ht/QnqQT+nfR//UzCYbwebBPiCIwkZNFzY1YG5Y03S3+9TJ4SJ3sP094BU+rqmHsaIgn IJ2UF3mZJu/nvRoJBDm/hgXLR3nqTjAOS2xf8OOLHuD1fPe2C4eO176eEY1K/4J29Uu6 BfzA== X-Gm-Message-State: AOPr4FW0xHqDurF1AI0/MopyUUIPiBB5C7ppXEJxCHKorWHU00EYoIriyzJAbmYmPshdhk+GUbF7TXwY4YUqAQ== MIME-Version: 1.0 X-Received: by 10.50.92.41 with SMTP id cj9mr18333008igb.38.1460654741434; Thu, 14 Apr 2016 10:25:41 -0700 (PDT) Received: by 10.107.156.132 with HTTP; Thu, 14 Apr 2016 10:25:41 -0700 (PDT) In-Reply-To: <20160414095901.smr5pwye7tznjnmg@mac> References: <20160414095901.smr5pwye7tznjnmg@mac> Date: Thu, 14 Apr 2016 12:25:41 -0500 Message-ID: Subject: Re: Xen from ports won't boot using -CURRENT From: Dustin Marquess To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= 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: Thu, 14 Apr 2016 17:25:42 -0000 AH-HA! Indeed I am. Is UEFI not supported? -Dustin On Thu, Apr 14, 2016 at 4:59 AM, Roger Pau Monn=C3=A9 wrote: > On Thu, Apr 14, 2016 at 01:24:46AM -0500, Dustin Marquess wrote: > > Hello! > > > > I'm using a -CURRENT install from a couple of weeks ago: > > > > FreeBSD 11.0-CURRENT #0 r297495: Fri Apr 1 21:24:26 UTC 2016 > > > > I installed xen from ports and followed the instructions on setting up: > > > > /etc/sysctl.conf > > > > /etc/ttys > > > > /boot/loader.conf > > > > /boot/menu.rc.local > > > > > > However after rebooting, booting fails with: > > > > > > don't know how to load module '/boot/xen' > > > > > > I'm guessing it's because for some reason it got compiled as 32-bit: > > > > > > /boot/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), > > statically linked, stripped > > Xen is always going to present itself as a 32-bit executable, although it= 's > only the entry point that runs in 32bit mode, then it jumps into long mod= e > by itself. > > Are you maybe trying to boot it from UEFI? (using the UEFI loader) > > Roger. > From owner-freebsd-virtualization@freebsd.org Thu Apr 14 18:34:48 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 D2F1EAECA6B for ; Thu, 14 Apr 2016 18:34:48 +0000 (UTC) (envelope-from prvs=90533d348=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 77B281CD5 for ; Thu, 14 Apr 2016 18:34:48 +0000 (UTC) (envelope-from prvs=90533d348=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,485,1454976000"; d="scan'208";a="347158276" Date: Thu, 14 Apr 2016 20:34:22 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Dustin Marquess CC: Subject: Re: Xen from ports won't boot using -CURRENT Message-ID: <20160414183422.tkognsxajalx26fv@mac> References: <20160414095901.smr5pwye7tznjnmg@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: Thu, 14 Apr 2016 18:34:48 -0000 On Thu, Apr 14, 2016 at 12:25:41PM -0500, Dustin Marquess wrote: > AH-HA! Indeed I am. Is UEFI not supported? Not at the moment, I'm sorry. I simply haven't got the time to look into what's needed to boot FreeBSD + Xen using UEFI (since multiboot is not suitable in that case IIRC). If you want to use a FreeBSD Dom0 you will have to switch to legacy BIOS for the time being. Roger