From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 3 07:18:16 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F3D4CF91 for ; Sun, 3 Nov 2013 07:18:15 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC5B12100 for ; Sun, 3 Nov 2013 07:18:15 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id ma3so5939203pbc.18 for ; Sun, 03 Nov 2013 00:18:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=5/scjn3PtkiFNGjF4B/VLFAPUyOlK8EBm8TmHT+ZJnk=; b=KLgbWOQhEdJ+ggJfbKr5ejZAMa0zFiYFIaunYr7JVY2cv87wss3j6aka4Zx2OYW2HM 2yC1fas9Ea/eHwv3TpixuWsdMxbMqWfDOxQjLxYfPvzx8peUUFeMiEM9s6nziDsSOMXy yVqvpSUg2bmA1AE2RejRvxqT5hWvgKFY49jcKK+QifAJHB/KNmbZT5SKm/yPYunc3Z7y hQh6bA2X/Xgf7Ms9GX3vNPdH5cJI9j64stR2VHK0v9N9uiWtawL+yIYSEr2F/X/6NPxB qvATbA/0rD4p+CFKf6sx4t5YEu1AvjV+aF1SjXoLQJvd7YraFJxDJ9V/86KvWjNqGF5s WFZg== X-Gm-Message-State: ALoCoQlTNM4nV+3lDSPIzBJ2mY5KiFwaiCUihRTE8xCY01nomdASxkDZy+DelQphlHltZfWOWnFc X-Received: by 10.69.18.171 with SMTP id gn11mr11814274pbd.63.1383463088996; Sun, 03 Nov 2013 00:18:08 -0700 (PDT) Received: from Michaels-MacBook-Pro.local (50-0-18-32.dsl.static.sonic.net. [50.0.18.32]) by mx.google.com with ESMTPSA id hz10sm20623706pbc.36.2013.11.03.00.18.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Nov 2013 00:18:08 -0700 (PDT) Message-ID: <5275F8B1.105@callfortesting.org> Date: Sun, 03 Nov 2013 00:18:09 -0700 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: rc-style script for bhyve VM provisioning and management Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 03 Nov 2013 07:18:16 -0000 Hello all from the FreeBSD 20th Anniversary Party in San Francisco, I have published a bhyve virtual machine provisioning and management framework to simplify the building and deploying of bhyve VMs during the run-up to the FreeBSD 10.0 release. As you may know, bhyve is rapidly finalizing for release in FreeBSD 10.0 and most features are finally becoming stable enough to document in a canonical manner. These scripts demonstrate the many opportunities for customization of bhyve deployments and will embrace features like OpenBSD and Linux support as soon as key components like the userland grub* arrive (currently in final testing). It will also demonstrate the use of pf to allow bhyve networking on wireless interfaces. It can be downloaded from: http://bhyve.org/bhyve-script.tar It works like a rc script but does not comply with the FreeBSD way. I am working with several developers to determine to what degree it should be compatible with existing frameworks like ezjail. ./vm0 will give the usage: usage (start|stop|load|boot|destroy|restart|list|debug mount|umount|jail|format|fetch|install|provision|wipe) Some routines like "provision" include steps like fetch (distribution sets), format (disk images or volumes) and install them. The "jail" routine demonstrates how a virtual machine can be launched using the jail(8) command, because we can, given that bhyve FreeBSD VMs are simply instances of FreeBSD with the ABI limitations of different releases. bhyve will support any vision of FreeBSD with VirtIO, specifically FreeBSD 8.4 and 8-STABLE, 9.2 and 9-STABLE, and any recent version of 10 or 11. Detailed instructions are included in the vm0 script and it is designed to simply be copied to vm1, vm2 etc. with easily-configured global variables. While tmux(1) is optional and supports both captive and detached execution, a script is included to list and attach to running VMs/sessions. A script is also provided for the easy duplication of VMs and I have tested this with up to 15 X 16 vCPU instances though far more should work without issue. Please throw everything you can at bhyve to expose any remaining flaws prior to the FreeBSD 10.0 release. All the best, Michael Dexter From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 3 13:15:58 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ABCC72C8 for ; Sun, 3 Nov 2013 13:15:58 +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 EF6832E22 for ; Sun, 3 Nov 2013 13:15:57 +0000 (UTC) Received: (qmail 49435 invoked by uid 89); 3 Nov 2013 13:15:55 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.54) by mail.grem.de with ESMTPA; 3 Nov 2013 13:15:55 -0000 Date: Sun, 3 Nov 2013 14:15:58 +0100 From: Michael Gmelin To: Michael Dexter Subject: Re: rc-style script for bhyve VM provisioning and management Message-ID: <20131103141558.379dffa4@bsd64.grem.de> In-Reply-To: <5275F8B1.105@callfortesting.org> References: <5275F8B1.105@callfortesting.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 03 Nov 2013 13:15:58 -0000 On Sun, 03 Nov 2013 00:18:09 -0700 Michael Dexter wrote: > > Hello all from the FreeBSD 20th Anniversary Party in San Francisco, > > I have published a bhyve virtual machine provisioning and management > framework to simplify the building and deploying of bhyve VMs during > the run-up to the FreeBSD 10.0 release. As you may know, bhyve is > rapidly finalizing for release in FreeBSD 10.0 and most features are > finally becoming stable enough to document in a canonical manner. > These scripts demonstrate the many opportunities for customization of > bhyve deployments and will embrace features like OpenBSD and Linux > support as soon as key components like the userland grub* arrive > (currently in final testing). It will also demonstrate the use of pf > to allow bhyve networking on wireless interfaces. > > It can be downloaded from: > > http://bhyve.org/bhyve-script.tar > > It works like a rc script but does not comply with the FreeBSD way. I > am working with several developers to determine to what degree it > should be compatible with existing frameworks like ezjail. > > ./vm0 will give the usage: > > usage (start|stop|load|boot|destroy|restart|list|debug > mount|umount|jail|format|fetch|install|provision|wipe) > > Some routines like "provision" include steps like fetch (distribution > sets), format (disk images or volumes) and install them. > > The "jail" routine demonstrates how a virtual machine can be launched > using the jail(8) command, because we can, given that bhyve FreeBSD > VMs are simply instances of FreeBSD with the ABI limitations of > different releases. bhyve will support any vision of FreeBSD with > VirtIO, specifically FreeBSD 8.4 and 8-STABLE, 9.2 and 9-STABLE, and > any recent version of 10 or 11. > > Detailed instructions are included in the vm0 script and it is > designed to simply be copied to vm1, vm2 etc. with easily-configured > global variables. > > While tmux(1) is optional and supports both captive and detached > execution, a script is included to list and attach to running > VMs/sessions. A script is also provided for the easy duplication of > VMs and I have tested this with up to 15 X 16 vCPU instances though > far more should work without issue. > > Please throw everything you can at bhyve to expose any remaining flaws > prior to the FreeBSD 10.0 release. > > All the best, > > Michael Dexter Sounds similar to how I ran my VMs for a while (well, I ln -s from the original VM script instead of copying, so it's easier to update all at once). I finally changed the script to use profiles a few days ago, since it seemed much cleaner in general and better for automatic control and also complies to the FreeBSD way. I submitted a PR for sysutils/bhyve-rc literally hours before you released vm0 (http://www.freebsd.org/cgi/query-pr.cgi?pr=183604), great timing ;) It's only good for one use case, but does that very well. I like the idea of the script using the general structure of ezjail. I would also suggest to split this it two scripts, one rc script, that only provides non-destructive operations like (start|stop|restart|rcvar) and one called vm-admin which provides the provisions functions on top, e.g. service vm start vm0 # ok vm-admin start vm0 # ok service vm format vm0 ... # not ok vm-admin format vm0 ... # ok -- Michael Gmelin From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 08:23:26 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EC647E36; Mon, 4 Nov 2013 08:23:26 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C3E5123AA; Mon, 4 Nov 2013 08:23:26 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id q10so6394606pdj.41 for ; Mon, 04 Nov 2013 00:23:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=OmI1y5AuhUXeb4WFn5zQ65G6twwfjZUFRAyDPuUO0uE=; b=YAByOYrTx9przQitNJXwJyCjyhv36HHLKeDP1V3/n5G7HwQrlE+YxNmnfg9vGOaCDu dPu+vnPlwQ3mmjs0ugQBTiQWz7s6QKFpWct4FGzrpVFv8LzwA+xuSSSg81c0+8ZKuvSQ mjkgsVeOLAlbTZTmWOkt5jHjPMtZWGtkmMnB9rTDrzdUSIVWwX69yfEBG7VgwFJ+g+pB jrY4ndeVgVZKy8SO3t73KRjZQJIZW3CIQg8paWML6TgGxIfFUDNDr/y/DJi5aGw1wTlX bZ0pSCh/BZ+K3p/qktMhKUf7TIdPijvS0FCT8UySWMeq3jpunTstDn4y6umxkpVeKN87 f1iA== MIME-Version: 1.0 X-Received: by 10.66.67.6 with SMTP id j6mr457004pat.165.1383553402354; Mon, 04 Nov 2013 00:23:22 -0800 (PST) Received: by 10.68.185.130 with HTTP; Mon, 4 Nov 2013 00:23:22 -0800 (PST) Date: Mon, 4 Nov 2013 03:23:22 -0500 Message-ID: Subject: how is the MAC for tap(4) computed? From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" , FreeBSD Stable List Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 08:23:27 -0000 There seems to be a very high rate of MAC address collisions when tap is running on different machines.... is there anyway to make the selection of MAC more random From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 11:06:58 2013 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AD465788 for ; Mon, 4 Nov 2013 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A4D32C52 for ; Mon, 4 Nov 2013 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA4B6wok048567 for ; Mon, 4 Nov 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA4B6wWB048565 for freebsd-virtualization@FreeBSD.org; Mon, 4 Nov 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Nov 2013 11:06:58 GMT Message-Id: <201311041106.rA4B6wWB048565@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF + VIMAGE kernel opt a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail 7 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 14:26:09 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 47FF971B for ; Mon, 4 Nov 2013 14:26:09 +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 0A934288A for ; Mon, 4 Nov 2013 14:26:08 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 29223122BA; Tue, 5 Nov 2013 00:26:01 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BPP24388 (AUTH peterg@ptree32.com.au); Tue, 5 Nov 2013 00:26:00 +1000 Message-ID: <5277AE77.8050804@freebsd.org> Date: Mon, 04 Nov 2013 06:25:59 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: how is the MAC for tap(4) computed? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 14:26:09 -0000 Hi Aryeh, > There seems to be a very high rate of MAC address collisions when tap is > running on different machines.... is there anyway to make the selection of > MAC more random Do you mean, tap(4) when used with bhyve ? If so, bhyve calculates the MAC address for adapters based on an md5 hash of the PCI slot/function and VM name. If you use the same bhyve configuration on a different machine, the MAC address will be the same. If that's the problem, you may want to supply your own MAC address with the "mac=" parameter on the command line e.g. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 16:26:42 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8A732630 for ; Mon, 4 Nov 2013 16:26:42 +0000 (UTC) (envelope-from michael.berman@tidalscale.com) Received: from smtp141.ord.emailsrvr.com (smtp141.ord.emailsrvr.com [173.203.6.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61B242124 for ; Mon, 4 Nov 2013 16:26:41 +0000 (UTC) Received: from smtp22.relay.ord1a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp22.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 0242F2001E0; Mon, 4 Nov 2013 11:20:46 -0500 (EST) X-SMTPDoctor-Processed: csmtpprox 2.7.4 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp22.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id E8A9E2002EE; Mon, 4 Nov 2013 11:20:46 -0500 (EST) X-Virus-Scanned: OK Received: from smtp192.mex05.mlsrvr.com (unknown [184.106.31.85]) by smtp22.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTPS id 953BB2001E0; Mon, 4 Nov 2013 11:20:46 -0500 (EST) Received: from ORD2MBX05C.mex05.mlsrvr.com ([fe80::90e2:baff:fe30:7498]) by ORD2HUB17.mex05.mlsrvr.com ([fe80::be30:5bff:feee:e494%15]) with mapi id 14.03.0158.001; Mon, 4 Nov 2013 10:20:46 -0600 From: Michael Berman To: Peter Grehan Subject: Re: how is the MAC for tap(4) computed? Thread-Topic: how is the MAC for tap(4) computed? Thread-Index: AQHO2Tdq6yIx73mh6UyJrpKbCYa+LJoVhbaA//+7fPM= Date: Mon, 4 Nov 2013 16:20:45 +0000 Message-ID: <89C04F5A-A2E6-4738-AB0C-4DADDE8DCC58@tidalscale.com> References: , <5277AE77.8050804@freebsd.org> In-Reply-To: <5277AE77.8050804@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 16:26:42 -0000 Peter, lost the last part of your message ... An alternative would be hashing the vm name with the host name and host MAC= address. Sent from my iPhone > On Nov 4, 2013, at 6:26 AM, "Peter Grehan" wrote: >=20 > Hi Aryeh, >=20 >> There seems to be a very high rate of MAC address collisions when tap is >> running on different machines.... is there anyway to make the selection = of >> MAC more random >=20 > Do you mean, tap(4) when used with bhyve ? If so, bhyve calculates the MA= C address for adapters based on an md5 hash of the PCI slot/function and VM= name. If you use the same bhyve configuration on a different machine, the = MAC address will be the same. >=20 > If that's the problem, you may want to supply your own MAC address with t= he "mac=3D" parameter on the command line e.g. >=20 > later, >=20 > Peter. >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 16:35:15 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 96A28BD8 for ; Mon, 4 Nov 2013 16:35:15 +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 5836B21CC for ; Mon, 4 Nov 2013 16:35:15 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 13E3B12305; Tue, 5 Nov 2013 02:35:13 +1000 (EST) Received: from Peters-MacBook-Pro.local (50-197-184-177-static.hfc.comcastbusiness.net [50.197.184.177]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BPP28512 (AUTH peterg@ptree32.com.au); Tue, 5 Nov 2013 02:35:12 +1000 Message-ID: <5277CCB8.4010900@freebsd.org> Date: Mon, 04 Nov 2013 08:35:04 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Michael Berman Subject: Re: how is the MAC for tap(4) computed? References: , <5277AE77.8050804@freebsd.org> <89C04F5A-A2E6-4738-AB0C-4DADDE8DCC58@tidalscale.com> In-Reply-To: <89C04F5A-A2E6-4738-AB0C-4DADDE8DCC58@tidalscale.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 16:35:15 -0000 Hi Michael, > Peter, lost the last part of your message ... Doh: meant to say e.g. -s 5,virtio-net,tap0,mac=00:0c:29:3f:71:e2 > An alternative would be hashing the vm name with the host name and host MAC address. Yes, though in that case a VM will end up with a different MAC address if it's moved to a different host :( What we'll probably end up doing is to generate a UUID when a VM is created and hash off that. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 17:10:03 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A0BCFF43; Mon, 4 Nov 2013 17:10:03 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 667E0243E; Mon, 4 Nov 2013 17:10:02 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.5/8.14.5) with ESMTP id rA4H9tSu095479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Nov 2013 11:09:55 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.7/8.14.6) with ESMTP id rA4H9tSl033160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Nov 2013 11:09:55 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.7/8.14.7/Submit) id rA4H9tPA033157; Mon, 4 Nov 2013 11:09:55 -0600 (CST) (envelope-from dan) Date: Mon, 4 Nov 2013 11:09:55 -0600 From: Dan Nelson To: Aryeh Friedman Subject: Re: how is the MAC for tap(4) computed? Message-ID: <20131104170955.GH63947@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 9.1-STABLE User-Agent: Mutt/1.5.22 (2013-10-16) X-Virus-Scanned: clamav-milter 0.98 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (email2.allantgroup.com [172.17.19.78]); Mon, 04 Nov 2013 11:09:55 -0600 (CST) X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.73 Cc: FreeBSD Stable List , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 17:10:03 -0000 In the last episode (Nov 04), Aryeh Friedman said: > There seems to be a very high rate of MAC address collisions when tap is > running on different machines.... is there anyway to make the selection > of MAC more random It looks like it's generated based on the number of ticks since boot, plus the unit number of the tap device: http://fxr.watson.org/fxr/source/net/if_tap.c#L434 So if you have devices created on boot on a bunch of machines, chances are high that you'll get conflicts. Maybe instead of using the 'ticks' value, kern.hostid could be used instead? That has much better randomness than 'ticks'. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 4 21:08:34 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BBC0313A; Mon, 4 Nov 2013 21:08:34 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9147722ED; Mon, 4 Nov 2013 21:08:34 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id rp8so1521016pbb.3 for ; Mon, 04 Nov 2013 13:08:34 -0800 (PST) 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:content-type; bh=/lud48gHxhNycsnZAkWjTP9kr3w4uCGFHbQd2mkLFYY=; b=bZRlaLIP/uemmd6OLgZad6DC3nPBoRknNXiXF5O6226RWiETeDHCHBtKGOQL550D61 ejgOnvpNlxmm7fhc+PRRdMLHJMUopfsP18O11v7y9qw5IICyBW7ZM4gPL15O72FsGBqp y2wYUYPck5ZdF1AMVToCFuyzibkgNyvFl2TI8+ExQtSlRBVH1xoZSkFolP8svysrJlwC DWHXJ7r6bt17r7KgJSQk8toHys1ZMvbebQaXxwgJPxi2MZ+DgayXhlXKb+08f10wcGfe fgaQUk+AMcNO9IaJaUeh4O5qbHWOzcYjj/Zse7PNKQ4gDJKrRRvsHP4P73eirTTxAbnV 6Lfw== MIME-Version: 1.0 X-Received: by 10.68.254.105 with SMTP id ah9mr19703534pbd.87.1383599313931; Mon, 04 Nov 2013 13:08:33 -0800 (PST) Received: by 10.68.218.136 with HTTP; Mon, 4 Nov 2013 13:08:33 -0800 (PST) In-Reply-To: <20131104170955.GH63947@dan.emsphone.com> References: <20131104170955.GH63947@dan.emsphone.com> Date: Mon, 4 Nov 2013 16:08:33 -0500 Message-ID: Subject: Re: how is the MAC for tap(4) computed? From: "illoai@gmail.com" To: Dan Nelson Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Stable List , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Nov 2013 21:08:34 -0000 On 4 November 2013 12:09, Dan Nelson wrote: > In the last episode (Nov 04), Aryeh Friedman said: >> There seems to be a very high rate of MAC address collisions when tap is >> running on different machines.... is there anyway to make the selection >> of MAC more random > > It looks like it's generated based on the number of ticks since boot, plus > the unit number of the tap device: > > http://fxr.watson.org/fxr/source/net/if_tap.c#L434 > > So if you have devices created on boot on a bunch of machines, chances are > high that you'll get conflicts. Maybe instead of using the 'ticks' value, > kern.hostid could be used instead? That has much better randomness than > 'ticks'. With physical interfaces you can use something like ifconfig ath0 ether 00:2d:44:88:ff:00 (assuming the device & the driver support changing MAC addresses) I've never tried it with a virtual interface, but it should work if the device supports it. -- -- From owner-freebsd-virtualization@FreeBSD.ORG Tue Nov 5 07:13:30 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 144C121D for ; Tue, 5 Nov 2013 07:13:30 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CB3662143 for ; Tue, 5 Nov 2013 07:13:29 +0000 (UTC) Received: by mail-vc0-f177.google.com with SMTP id ib11so5194960vcb.8 for ; Mon, 04 Nov 2013 23:13:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gO30iXnbVt/pbUOgTS41RLMEyRktdyFA6VR+YXfwpL4=; b=hDmVOEx32YEAErh31CKlduIOlMTxbBcr3Dx2ZI8onM2Y0p0iZG3IYi1P51Zt6jskuT fmCbGwA2kFKcgenLXHiKJWTdy0idKN/pFRICmKEouyBrfVmiCQzu6XST89BBQaWvdfZe +g5FxuZYfGnd6c4Yq5e6NU5yayGgMeG4SlpzK+TDmCcf4RDObhADy0E/ZkqSl0v4VYcs vLEeqPc46QbuUio9ceEHpqedaBVIBHNV6n6gSD2rVOzkv2LbX1RTAz7zcmC2SOlh8g0b QakW+imQJ02lam5eCbRPQAvNBXf+YHKkKe3dtPtFnaaKVl9Ut17ufC9UDRknt6GsFvnK FCFw== MIME-Version: 1.0 X-Received: by 10.52.98.194 with SMTP id ek2mr12092916vdb.11.1383635608331; Mon, 04 Nov 2013 23:13:28 -0800 (PST) Received: by 10.52.168.106 with HTTP; Mon, 4 Nov 2013 23:13:28 -0800 (PST) Date: Tue, 5 Nov 2013 11:13:28 +0400 Message-ID: Subject: Hyper-V From: Pavel Timofeev To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 05 Nov 2013 07:13:30 -0000 Hi! I upgraded to 10.0-BETA3 but still see messages like Tue Nov 5 11:09:05 MSK 2013 calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 (zabbix_server) calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 (zabbix_server) calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 (zabbix_server) calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 (zabbix_server) calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 (zabbix_server) calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 (zabbix_server) calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 (zabbix_server) calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 (zabbix_server) calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 (zabbix_server) calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 (zabbix_server) calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 (cron) calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 (sendmail) calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 (sendmail) calcru: runtime went backwards from 4691 usec to 2735 usec for pid 1011 (sendmail) calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 (sendmail) calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 (httpd) calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 (httpd) calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 (httpd) calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 (httpd) calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 (httpd) calcru: runtime went backwards from 201793 usec to 102672 usec for pid 996 (httpd) calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 (sshd) calcru: runtime went backwards from 45196 usec to 23221 usec for pid 974 (zabbix_server) calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 (zabbix_server) calcru: runtime went backwards from 605 usec to 306 usec for pid 968 (zabbix_server) calcru: runtime went backwards from 626 usec to 316 usec for pid 967 (zabbix_server) calcru: runtime went backwards from 773 usec to 391 usec for pid 966 (zabbix_server) calcru: runtime went backwards from 663 usec to 335 usec for pid 965 (zabbix_server) calcru: runtime went backwards from 799 usec to 404 usec for pid 964 (zabbix_server) calcru: runtime went backwards from 37723 usec to 19422 usec for pid 963 (zabbix_server) calcru: runtime went backwards from 49425 usec to 26265 usec for pid 962 (zabbix_server) calcru: runtime went backwards from 38883 usec to 20993 usec for pid 961 (zabbix_server) calcru: runtime went backwards from 53478 usec to 27411 usec for pid 960 (zabbix_server) calcru: runtime went backwards from 40845 usec to 21750 usec for pid 959 (zabbix_server) calcru: runtime went backwards from 47835 usec to 24455 usec for pid 958 (zabbix_server) calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 (zabbix_server) calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 (zabbix_agentd) calcru: runtime went backwards from 32053 usec to 16204 usec for pid 928 (zabbix_server) calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 (sh) calcru: runtime went backwards from 1128021 usec to 868022 usec for pid 697 (sh) calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 (syslogd) calcru: runtime went backwards from 688 usec to 348 usec for pid 106 (adjkerntz) calcru: runtime went backwards from 12 usec to 6 usec for pid 3 (sctp_iterator) calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 (fdc0) calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 (rand_harvestq) calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 (geom) calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 (intr) calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 (init) calcru: runtime went backwards from 2340313 usec to 1226503 usec for pid 1 (init) calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 (kernel) Is it bad? Or I have to ignore them? From owner-freebsd-virtualization@FreeBSD.ORG Tue Nov 5 18:24:39 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B91FA49D; Tue, 5 Nov 2013 18:24:39 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73C2F2C64; Tue, 5 Nov 2013 18:24:39 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id rA5IOaeD054699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Nov 2013 10:24:36 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id rA5IOZjF054698; Tue, 5 Nov 2013 10:24:35 -0800 (PST) (envelope-from jmg) Date: Tue, 5 Nov 2013 10:24:35 -0800 From: John-Mark Gurney To: "illoai@gmail.com" Subject: Re: how is the MAC for tap(4) computed? Message-ID: <20131105182435.GT73243@funkthat.com> Mail-Followup-To: "illoai@gmail.com" , Dan Nelson , FreeBSD Stable List , Aryeh Friedman , "freebsd-virtualization@freebsd.org" References: <20131104170955.GH63947@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 05 Nov 2013 10:24:36 -0800 (PST) Cc: FreeBSD Stable List , Dan Nelson , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 05 Nov 2013 18:24:39 -0000 illoai@gmail.com wrote this message on Mon, Nov 04, 2013 at 16:08 -0500: > On 4 November 2013 12:09, Dan Nelson wrote: > > In the last episode (Nov 04), Aryeh Friedman said: > >> There seems to be a very high rate of MAC address collisions when tap is > >> running on different machines.... is there anyway to make the selection > >> of MAC more random > > > > It looks like it's generated based on the number of ticks since boot, plus > > the unit number of the tap device: > > > > http://fxr.watson.org/fxr/source/net/if_tap.c#L434 > > > > So if you have devices created on boot on a bunch of machines, chances are > > high that you'll get conflicts. Maybe instead of using the 'ticks' value, > > kern.hostid could be used instead? That has much better randomness than > > 'ticks'. > > With physical interfaces you can use something like > ifconfig ath0 ether 00:2d:44:88:ff:00 > (assuming the device & the driver support changing MAC > addresses) > > I've never tried it with a virtual interface, but it should work if the > device supports it. But remeber when choosing an address like that, that you set the second low bit of the first octect to one to designate that it's a locally administered address... See wikipedia for more info: https://en.wikipedia.org/wiki/MAC_address#Address_details -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-virtualization@FreeBSD.ORG Tue Nov 5 19:45:02 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CF4ADFD7 for ; Tue, 5 Nov 2013 19:45:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 956E121A9 for ; Tue, 5 Nov 2013 19:45:02 +0000 (UTC) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rA5Jj1ZD050291 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 5 Nov 2013 11:45:01 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52794AB7.80600@freebsd.org> Date: Tue, 05 Nov 2013 11:44:55 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Pavel Timofeev , "freebsd-virtualization@freebsd.org" Subject: Re: Hyper-V References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 05 Nov 2013 19:45:02 -0000 On 11/4/13, 11:13 PM, Pavel Timofeev wrote: > Hi! I upgraded to 10.0-BETA3 but still see messages like > > Tue Nov 5 11:09:05 MSK 2013 > calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 > (zabbix_server) > calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 > (zabbix_server) > calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 > (zabbix_server) > calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 > (zabbix_server) > calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 > (zabbix_server) > calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 > (zabbix_server) > calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 > (zabbix_server) > calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 > (zabbix_server) > calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 > (zabbix_server) > calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 > (zabbix_server) > calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 (cron) > calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 > (sendmail) > calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 (sendmail) > calcru: runtime went backwards from 4691 usec to 2735 usec for pid > 1011 (sendmail) > calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 > (sendmail) > calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 (httpd) > calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 (httpd) > calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 (httpd) > calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 (httpd) > calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 (httpd) > calcru: runtime went backwards from 201793 usec to 102672 usec for pid > 996 (httpd) > calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 (sshd) > calcru: runtime went backwards from 45196 usec to 23221 usec for pid > 974 (zabbix_server) > calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 > (zabbix_server) > calcru: runtime went backwards from 605 usec to 306 usec for pid 968 > (zabbix_server) > calcru: runtime went backwards from 626 usec to 316 usec for pid 967 > (zabbix_server) > calcru: runtime went backwards from 773 usec to 391 usec for pid 966 > (zabbix_server) > calcru: runtime went backwards from 663 usec to 335 usec for pid 965 > (zabbix_server) > calcru: runtime went backwards from 799 usec to 404 usec for pid 964 > (zabbix_server) > calcru: runtime went backwards from 37723 usec to 19422 usec for pid > 963 (zabbix_server) > calcru: runtime went backwards from 49425 usec to 26265 usec for pid > 962 (zabbix_server) > calcru: runtime went backwards from 38883 usec to 20993 usec for pid > 961 (zabbix_server) > calcru: runtime went backwards from 53478 usec to 27411 usec for pid > 960 (zabbix_server) > calcru: runtime went backwards from 40845 usec to 21750 usec for pid > 959 (zabbix_server) > calcru: runtime went backwards from 47835 usec to 24455 usec for pid > 958 (zabbix_server) > calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 > (zabbix_server) > calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 > (zabbix_agentd) > calcru: runtime went backwards from 32053 usec to 16204 usec for pid > 928 (zabbix_server) > calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 (sh) > calcru: runtime went backwards from 1128021 usec to 868022 usec for pid 697 (sh) > calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 (syslogd) > calcru: runtime went backwards from 688 usec to 348 usec for pid 106 (adjkerntz) > calcru: runtime went backwards from 12 usec to 6 usec for pid 3 (sctp_iterator) > calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 (fdc0) > calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 > (rand_harvestq) > calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 (geom) > calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 (intr) > calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 (init) > calcru: runtime went backwards from 2340313 usec to 1226503 usec for > pid 1 (init) > calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 (kernel) > > > Is it bad? Or I have to ignore them? I'm not talking authoratatively but in some virtualization systems, if the TSCs on the various processors are not sufficiently synchronized, then when the hypervisor switches you from one CPU to another, you can get odd (sometimes negative) time readings which give messages like this.. > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > > From owner-freebsd-virtualization@FreeBSD.ORG Tue Nov 5 22:18:34 2013 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41A8B74C; Tue, 5 Nov 2013 22:18:34 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 158552B76; Tue, 5 Nov 2013 22:18:33 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VdoxE-0009E9-T6; Tue, 05 Nov 2013 22:18:33 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id rA5MITwD062380; Tue, 5 Nov 2013 15:18:30 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+L3V4L71c3Q2PQ9Ds8/kEn Subject: Re: how is the MAC for tap(4) computed? From: Ian Lepore To: John-Mark Gurney In-Reply-To: <20131105182435.GT73243@funkthat.com> References: <20131104170955.GH63947@dan.emsphone.com> <20131105182435.GT73243@funkthat.com> Content-Type: text/plain; charset="us-ascii" Date: Tue, 05 Nov 2013 15:18:29 -0700 Message-ID: <1383689909.31172.169.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable List , Dan Nelson , "illoai@gmail.com" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 05 Nov 2013 22:18:34 -0000 On Tue, 2013-11-05 at 10:24 -0800, John-Mark Gurney wrote: > illoai@gmail.com wrote this message on Mon, Nov 04, 2013 at 16:08 -0500: > > On 4 November 2013 12:09, Dan Nelson wrote: > > > In the last episode (Nov 04), Aryeh Friedman said: > > >> There seems to be a very high rate of MAC address collisions when tap is > > >> running on different machines.... is there anyway to make the selection > > >> of MAC more random > > > > > > It looks like it's generated based on the number of ticks since boot, plus > > > the unit number of the tap device: > > > > > > http://fxr.watson.org/fxr/source/net/if_tap.c#L434 > > > > > > So if you have devices created on boot on a bunch of machines, chances are > > > high that you'll get conflicts. Maybe instead of using the 'ticks' value, > > > kern.hostid could be used instead? That has much better randomness than > > > 'ticks'. > > > > With physical interfaces you can use something like > > ifconfig ath0 ether 00:2d:44:88:ff:00 > > (assuming the device & the driver support changing MAC > > addresses) > > > > I've never tried it with a virtual interface, but it should work if the > > device supports it. > > But remeber when choosing an address like that, that you set the second > low bit of the first octect to one to designate that it's a locally > administered address... > > See wikipedia for more info: > https://en.wikipedia.org/wiki/MAC_address#Address_details > Several ethernet drivers for embedded systems have logic to cook up a random address (probably it should be commonized somewhere) in which they set the first 3 bytes to 'b','s','d' and the low bytes to a random number. The nifty thing about the value 62:73:64 (beside that it's bsd) is that it sets the locally-administered bit in the address. -- Ian From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 6 07:23:20 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 05C09AB7; Wed, 6 Nov 2013 07:23:20 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A6EAE2785; Wed, 6 Nov 2013 07:23:19 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id hu8so6512999vcb.0 for ; Tue, 05 Nov 2013 23:23:18 -0800 (PST) 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:content-type; bh=cLOrY4GzZcVMxFnbRZcWyErg5+1b5N2VNhuQN6SKEV8=; b=IWb2BVfNjOznNrkXMadljJjjltDyvS/2KHfcvpZvSi2vs+1G6CIQT7kaBpc4O6VyNI ea61VEPp4NecfLXuVotCmQ2JLoG9RJ0IZu5z43IbVYFws2zweyh/t1uV1fzbegblCrbo iNz/20G4My4L+MeS0YRREGuIpnR/1vDJf4A2uMfhajoOe1/JE4CDBx/4Zr/DpXRi7ht+ 8BG8gxXKhXGhi3HYuC/062K9nlacjgNQ4r6zi/P5ozirTXLnohiSGgxy7dWezwNxxslt 3kvDVoXpiBTyz34I6rY8JHPJkIIKJUN7+hlTudzlxCywDCBfsUK4jp2ylR3sdjk6W3+7 YqIg== MIME-Version: 1.0 X-Received: by 10.52.106.201 with SMTP id gw9mr83465vdb.49.1383722598723; Tue, 05 Nov 2013 23:23:18 -0800 (PST) Received: by 10.52.168.106 with HTTP; Tue, 5 Nov 2013 23:23:18 -0800 (PST) In-Reply-To: <52794AB7.80600@freebsd.org> References: <52794AB7.80600@freebsd.org> Date: Wed, 6 Nov 2013 11:23:18 +0400 Message-ID: Subject: Re: Hyper-V From: Pavel Timofeev To: Julian Elischer Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Nov 2013 07:23:20 -0000 Thank you very much! I started to dig, and found that I can reboot my server running under Hyper-V by doing 'sysctl -a'. Can anybody confirm same behavoiur? FreeBSD 10.0-BETA3, Win 2012 Datacenter 2013/11/5 Julian Elischer : > On 11/4/13, 11:13 PM, Pavel Timofeev wrote: >> >> Hi! I upgraded to 10.0-BETA3 but still see messages like >> >> Tue Nov 5 11:09:05 MSK 2013 >> calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 >> (zabbix_server) >> calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 >> (zabbix_server) >> calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 >> (zabbix_server) >> calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 >> (zabbix_server) >> calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 >> (zabbix_server) >> calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 >> (zabbix_server) >> calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 >> (zabbix_server) >> calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 >> (zabbix_server) >> calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 >> (zabbix_server) >> calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 >> (zabbix_server) >> calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 >> (cron) >> calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 >> (sendmail) >> calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 >> (sendmail) >> calcru: runtime went backwards from 4691 usec to 2735 usec for pid >> 1011 (sendmail) >> calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 >> (sendmail) >> calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 >> (httpd) >> calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 >> (httpd) >> calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 >> (httpd) >> calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 >> (httpd) >> calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 >> (httpd) >> calcru: runtime went backwards from 201793 usec to 102672 usec for pid >> 996 (httpd) >> calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 >> (sshd) >> calcru: runtime went backwards from 45196 usec to 23221 usec for pid >> 974 (zabbix_server) >> calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 >> (zabbix_server) >> calcru: runtime went backwards from 605 usec to 306 usec for pid 968 >> (zabbix_server) >> calcru: runtime went backwards from 626 usec to 316 usec for pid 967 >> (zabbix_server) >> calcru: runtime went backwards from 773 usec to 391 usec for pid 966 >> (zabbix_server) >> calcru: runtime went backwards from 663 usec to 335 usec for pid 965 >> (zabbix_server) >> calcru: runtime went backwards from 799 usec to 404 usec for pid 964 >> (zabbix_server) >> calcru: runtime went backwards from 37723 usec to 19422 usec for pid >> 963 (zabbix_server) >> calcru: runtime went backwards from 49425 usec to 26265 usec for pid >> 962 (zabbix_server) >> calcru: runtime went backwards from 38883 usec to 20993 usec for pid >> 961 (zabbix_server) >> calcru: runtime went backwards from 53478 usec to 27411 usec for pid >> 960 (zabbix_server) >> calcru: runtime went backwards from 40845 usec to 21750 usec for pid >> 959 (zabbix_server) >> calcru: runtime went backwards from 47835 usec to 24455 usec for pid >> 958 (zabbix_server) >> calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 >> (zabbix_server) >> calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 >> (zabbix_agentd) >> calcru: runtime went backwards from 32053 usec to 16204 usec for pid >> 928 (zabbix_server) >> calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 >> (sh) >> calcru: runtime went backwards from 1128021 usec to 868022 usec for pid >> 697 (sh) >> calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 >> (syslogd) >> calcru: runtime went backwards from 688 usec to 348 usec for pid 106 >> (adjkerntz) >> calcru: runtime went backwards from 12 usec to 6 usec for pid 3 >> (sctp_iterator) >> calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 >> (fdc0) >> calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 >> (rand_harvestq) >> calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 >> (geom) >> calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 >> (intr) >> calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 >> (init) >> calcru: runtime went backwards from 2340313 usec to 1226503 usec for >> pid 1 (init) >> calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 >> (kernel) >> >> >> Is it bad? Or I have to ignore them? > > > I'm not talking authoratatively but in some virtualization systems, if the > TSCs on the various processors are not sufficiently synchronized, then when > the hypervisor switches you from one CPU to another, you can get odd > (sometimes negative) time readings which give messages like this.. > >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to >> "freebsd-virtualization-unsubscribe@freebsd.org" >> >> > From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 6 11:08:03 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 704971CC; Wed, 6 Nov 2013 11:08:03 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2094A24EF; Wed, 6 Nov 2013 11:08:03 +0000 (UTC) Received: by mail-ve0-f175.google.com with SMTP id jz11so3420173veb.20 for ; Wed, 06 Nov 2013 03:08:02 -0800 (PST) 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:content-type; bh=qd5JJM++Pf7XfSRZzk7iANCc05WB1DqooqEzMEduz1o=; b=KYwrdgj7JpFZl/x1zYp78swDXh1rJkMwwojhrWWRPZjif+s4HOBGAu8J73U7RuFzXe icMq6sTaucyzsIYPLHH50POTg3fxbEgfhKOSOste8Vh51CNI7a3daXzPcWWf6GyRPhq1 7wyh+JYzWtka4iuv0c8EzkldtNpmVdJ6jefD2QeOReeBojQnUeEJ4PoQs9IO+pItF9lq Fp3+I+Gh4LS7HTerIbTszjcxrHcy4/jAC3cTUWugXqzUENSB3k5J6FYsSqLXAX6o4N3K B1lg7Pl0hR97/mmW2DAh7anzRxrf1b5uh68r0vIkG8F7NeFnT3AR+uf/EBuw0xZuF79k N2VQ== MIME-Version: 1.0 X-Received: by 10.58.46.18 with SMTP id r18mr1956932vem.4.1383736082255; Wed, 06 Nov 2013 03:08:02 -0800 (PST) Received: by 10.52.168.106 with HTTP; Wed, 6 Nov 2013 03:08:02 -0800 (PST) In-Reply-To: References: <52794AB7.80600@freebsd.org> Date: Wed, 6 Nov 2013 15:08:02 +0400 Message-ID: Subject: Re: Hyper-V From: Pavel Timofeev To: Julian Elischer Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Nov 2013 11:08:03 -0000 Does anybody know how to disable Hyper-v time syncing it guest FreeBSD OS? I'd like to try this one. 2013/11/6 Pavel Timofeev : > Thank you very much! > I started to dig, and found that I can reboot my server running under > Hyper-V by doing 'sysctl -a'. > Can anybody confirm same behavoiur? > > FreeBSD 10.0-BETA3, Win 2012 Datacenter > > 2013/11/5 Julian Elischer : >> On 11/4/13, 11:13 PM, Pavel Timofeev wrote: >>> >>> Hi! I upgraded to 10.0-BETA3 but still see messages like >>> >>> Tue Nov 5 11:09:05 MSK 2013 >>> calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 >>> (zabbix_server) >>> calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 >>> (zabbix_server) >>> calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 >>> (zabbix_server) >>> calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 >>> (zabbix_server) >>> calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 >>> (zabbix_server) >>> calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 >>> (zabbix_server) >>> calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 >>> (zabbix_server) >>> calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 >>> (zabbix_server) >>> calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 >>> (zabbix_server) >>> calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 >>> (zabbix_server) >>> calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 >>> (cron) >>> calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 >>> (sendmail) >>> calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 >>> (sendmail) >>> calcru: runtime went backwards from 4691 usec to 2735 usec for pid >>> 1011 (sendmail) >>> calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 >>> (sendmail) >>> calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 >>> (httpd) >>> calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 >>> (httpd) >>> calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 >>> (httpd) >>> calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 >>> (httpd) >>> calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 >>> (httpd) >>> calcru: runtime went backwards from 201793 usec to 102672 usec for pid >>> 996 (httpd) >>> calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 >>> (sshd) >>> calcru: runtime went backwards from 45196 usec to 23221 usec for pid >>> 974 (zabbix_server) >>> calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 >>> (zabbix_server) >>> calcru: runtime went backwards from 605 usec to 306 usec for pid 968 >>> (zabbix_server) >>> calcru: runtime went backwards from 626 usec to 316 usec for pid 967 >>> (zabbix_server) >>> calcru: runtime went backwards from 773 usec to 391 usec for pid 966 >>> (zabbix_server) >>> calcru: runtime went backwards from 663 usec to 335 usec for pid 965 >>> (zabbix_server) >>> calcru: runtime went backwards from 799 usec to 404 usec for pid 964 >>> (zabbix_server) >>> calcru: runtime went backwards from 37723 usec to 19422 usec for pid >>> 963 (zabbix_server) >>> calcru: runtime went backwards from 49425 usec to 26265 usec for pid >>> 962 (zabbix_server) >>> calcru: runtime went backwards from 38883 usec to 20993 usec for pid >>> 961 (zabbix_server) >>> calcru: runtime went backwards from 53478 usec to 27411 usec for pid >>> 960 (zabbix_server) >>> calcru: runtime went backwards from 40845 usec to 21750 usec for pid >>> 959 (zabbix_server) >>> calcru: runtime went backwards from 47835 usec to 24455 usec for pid >>> 958 (zabbix_server) >>> calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 >>> (zabbix_server) >>> calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 >>> (zabbix_agentd) >>> calcru: runtime went backwards from 32053 usec to 16204 usec for pid >>> 928 (zabbix_server) >>> calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 >>> (sh) >>> calcru: runtime went backwards from 1128021 usec to 868022 usec for pid >>> 697 (sh) >>> calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 >>> (syslogd) >>> calcru: runtime went backwards from 688 usec to 348 usec for pid 106 >>> (adjkerntz) >>> calcru: runtime went backwards from 12 usec to 6 usec for pid 3 >>> (sctp_iterator) >>> calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 >>> (fdc0) >>> calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 >>> (rand_harvestq) >>> calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 >>> (geom) >>> calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 >>> (intr) >>> calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 >>> (init) >>> calcru: runtime went backwards from 2340313 usec to 1226503 usec for >>> pid 1 (init) >>> calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 >>> (kernel) >>> >>> >>> Is it bad? Or I have to ignore them? >> >> >> I'm not talking authoratatively but in some virtualization systems, if the >> TSCs on the various processors are not sufficiently synchronized, then when >> the hypervisor switches you from one CPU to another, you can get odd >> (sometimes negative) time readings which give messages like this.. >> >>> _______________________________________________ >>> freebsd-virtualization@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>> To unsubscribe, send any mail to >>> "freebsd-virtualization-unsubscribe@freebsd.org" >>> >>> >> From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 6 11:37:31 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 75C60BAE for ; Wed, 6 Nov 2013 11:37:31 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 36E7A278F for ; Wed, 6 Nov 2013 11:37:31 +0000 (UTC) Received: by mail-vb0-f42.google.com with SMTP id p14so3322167vbm.15 for ; Wed, 06 Nov 2013 03:37:30 -0800 (PST) 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:cc :content-type; bh=QHZOHURRWr2fImdjYgU9Ip6xxeRMS/UwSVNuImp+DZk=; b=meUQgrxHg4OK4ufHXyK0X3lSyOP+yYF1riNSapKviZID/RwJ0wYnNll1l50QtWq85o DiJf8tdmX42BltTkdKCnF0j9eAw+bSIUWsqN4IIdW86RZHuAs6zUKA7li8AdmWj776eY wev1i+ggyNOgQYj7dh7ngab0jfV/7PbmuuZsQP+1C3a3iD12xVAqhjoYWbeeHPyyXdmg CQpCeFwPD5F5KjMWggWaJTtWScOpLZS+EnFLzX5fP2cawEYZY7jhPdlADIEBPV5zB9dK O5xtmVwSseRnMQ5mUe/sk4fP8MXrM+xJmuwXNGn4QzwaStmgVg9zaKnZjjvEwD8YtckL KVpA== MIME-Version: 1.0 X-Received: by 10.220.183.199 with SMTP id ch7mr1977282vcb.27.1383737849998; Wed, 06 Nov 2013 03:37:29 -0800 (PST) Received: by 10.52.168.106 with HTTP; Wed, 6 Nov 2013 03:37:29 -0800 (PST) In-Reply-To: References: <52794AB7.80600@freebsd.org> Date: Wed, 6 Nov 2013 15:37:29 +0400 Message-ID: Subject: Re: Hyper-V From: Pavel Timofeev Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Nov 2013 11:37:31 -0000 I already tried disabling Hyper-v time syncing, setting kern.timecounter.hardware to different type from kern.timecounter.choice, setting kern.hz to different values. But nothing helped. I'll try to install CentOS 6.4 on this machine and see what happens. 2013/11/6 Pavel Timofeev : > Does anybody know how to disable Hyper-v time syncing it guest FreeBSD > OS? I'd like to try this one. > > 2013/11/6 Pavel Timofeev : >> Thank you very much! >> I started to dig, and found that I can reboot my server running under >> Hyper-V by doing 'sysctl -a'. >> Can anybody confirm same behavoiur? >> >> FreeBSD 10.0-BETA3, Win 2012 Datacenter >> >> 2013/11/5 Julian Elischer : >>> On 11/4/13, 11:13 PM, Pavel Timofeev wrote: >>>> >>>> Hi! I upgraded to 10.0-BETA3 but still see messages like >>>> >>>> Tue Nov 5 11:09:05 MSK 2013 >>>> calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 >>>> (cron) >>>> calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 >>>> (sendmail) >>>> calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 >>>> (sendmail) >>>> calcru: runtime went backwards from 4691 usec to 2735 usec for pid >>>> 1011 (sendmail) >>>> calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 >>>> (sendmail) >>>> calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 >>>> (httpd) >>>> calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 >>>> (httpd) >>>> calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 >>>> (httpd) >>>> calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 >>>> (httpd) >>>> calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 >>>> (httpd) >>>> calcru: runtime went backwards from 201793 usec to 102672 usec for pid >>>> 996 (httpd) >>>> calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 >>>> (sshd) >>>> calcru: runtime went backwards from 45196 usec to 23221 usec for pid >>>> 974 (zabbix_server) >>>> calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 605 usec to 306 usec for pid 968 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 626 usec to 316 usec for pid 967 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 773 usec to 391 usec for pid 966 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 663 usec to 335 usec for pid 965 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 799 usec to 404 usec for pid 964 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 37723 usec to 19422 usec for pid >>>> 963 (zabbix_server) >>>> calcru: runtime went backwards from 49425 usec to 26265 usec for pid >>>> 962 (zabbix_server) >>>> calcru: runtime went backwards from 38883 usec to 20993 usec for pid >>>> 961 (zabbix_server) >>>> calcru: runtime went backwards from 53478 usec to 27411 usec for pid >>>> 960 (zabbix_server) >>>> calcru: runtime went backwards from 40845 usec to 21750 usec for pid >>>> 959 (zabbix_server) >>>> calcru: runtime went backwards from 47835 usec to 24455 usec for pid >>>> 958 (zabbix_server) >>>> calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 >>>> (zabbix_server) >>>> calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 >>>> (zabbix_agentd) >>>> calcru: runtime went backwards from 32053 usec to 16204 usec for pid >>>> 928 (zabbix_server) >>>> calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 >>>> (sh) >>>> calcru: runtime went backwards from 1128021 usec to 868022 usec for pid >>>> 697 (sh) >>>> calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 >>>> (syslogd) >>>> calcru: runtime went backwards from 688 usec to 348 usec for pid 106 >>>> (adjkerntz) >>>> calcru: runtime went backwards from 12 usec to 6 usec for pid 3 >>>> (sctp_iterator) >>>> calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 >>>> (fdc0) >>>> calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 >>>> (rand_harvestq) >>>> calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 >>>> (geom) >>>> calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 >>>> (intr) >>>> calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 >>>> (init) >>>> calcru: runtime went backwards from 2340313 usec to 1226503 usec for >>>> pid 1 (init) >>>> calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 >>>> (kernel) >>>> >>>> >>>> Is it bad? Or I have to ignore them? >>> >>> >>> I'm not talking authoratatively but in some virtualization systems, if the >>> TSCs on the various processors are not sufficiently synchronized, then when >>> the hypervisor switches you from one CPU to another, you can get odd >>> (sometimes negative) time readings which give messages like this.. >>> >>>> _______________________________________________ >>>> freebsd-virtualization@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>>> To unsubscribe, send any mail to >>>> "freebsd-virtualization-unsubscribe@freebsd.org" >>>> >>>> >>> From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 6 11:44:38 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 46E92115 for ; Wed, 6 Nov 2013 11:44:38 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 073A82810 for ; Wed, 6 Nov 2013 11:44:37 +0000 (UTC) Received: by mail-ve0-f174.google.com with SMTP id pa12so3410139veb.5 for ; Wed, 06 Nov 2013 03:44:37 -0800 (PST) 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:content-type; bh=TcuW9H19PMZ4Nbk58GEjfhD8PVXObZaNerOMlWCGXtw=; b=ca8MUe43U4AsTTNidl8hD5PozCbAKq3uSB4siG564QzC2e2wU64Pq9XyH7zQkaXSBk qDfZyA3iZyI7sR+42PqW+Cdta1OA1JxipR3XY6ZjS0mvYaDIY7g4nOho9OW5p4NIUgOZ pLPMHe8JJZE/FRpvkDTxJT0bzbGsoTZmSXClEaFaZm82PtV6JZNyybJn3VDCLWdjPl4X ZtnFCWaFinASgXvtpqM1ev89WIhtai6es0T50YyLxlKWPp5sypB5iHF64kPZb92FAiyR nhpvV65Is3lEK1DdrOe0vS23RiqUe55rYWK+eJKT5gOeOdcCW0kcaCWcNDObIEgukouB iXiA== MIME-Version: 1.0 X-Received: by 10.52.170.111 with SMTP id al15mr872231vdc.43.1383738277053; Wed, 06 Nov 2013 03:44:37 -0800 (PST) Received: by 10.52.168.106 with HTTP; Wed, 6 Nov 2013 03:44:36 -0800 (PST) In-Reply-To: References: <52794AB7.80600@freebsd.org> Date: Wed, 6 Nov 2013 15:44:36 +0400 Message-ID: Subject: Re: Hyper-V From: Pavel Timofeev To: Pavel Timofeev Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 06 Nov 2013 11:44:38 -0000 Small fix: kern.timecounter.hardware=TSC covered messages, but now it looks stange % time sleep 30 20.24 real 0.00 user 0.00 sys 2013/11/6 Pavel Timofeev : > I already tried disabling Hyper-v time syncing, setting > kern.timecounter.hardware to different type from > kern.timecounter.choice, setting kern.hz to different values. But > nothing helped. > I'll try to install CentOS 6.4 on this machine and see what happens. > > 2013/11/6 Pavel Timofeev : >> Does anybody know how to disable Hyper-v time syncing it guest FreeBSD >> OS? I'd like to try this one. >> >> 2013/11/6 Pavel Timofeev : >>> Thank you very much! >>> I started to dig, and found that I can reboot my server running under >>> Hyper-V by doing 'sysctl -a'. >>> Can anybody confirm same behavoiur? >>> >>> FreeBSD 10.0-BETA3, Win 2012 Datacenter >>> >>> 2013/11/5 Julian Elischer : >>>> On 11/4/13, 11:13 PM, Pavel Timofeev wrote: >>>>> >>>>> Hi! I upgraded to 10.0-BETA3 but still see messages like >>>>> >>>>> Tue Nov 5 11:09:05 MSK 2013 >>>>> calcru: runtime went backwards from 1728 usec to 889 usec for pid 981 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1229 usec to 703 usec for pid 976 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1019 usec to 595 usec for pid 978 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 3041 usec to 1611 usec for pid 969 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1078 usec to 595 usec for pid 975 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1114 usec to 617 usec for pid 980 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1086 usec to 602 usec for pid 977 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1195 usec to 782 usec for pid 970 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 3206 usec to 2157 usec for pid 979 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 2179 usec to 1542 usec for pid 972 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 1833 usec to 927 usec for pid 1026 >>>>> (cron) >>>>> calcru: runtime went backwards from 1091 usec to 551 usec for pid 1022 >>>>> (sendmail) >>>>> calcru: runtime went backwards from 823 usec to 416 usec for pid 1022 >>>>> (sendmail) >>>>> calcru: runtime went backwards from 4691 usec to 2735 usec for pid >>>>> 1011 (sendmail) >>>>> calcru: runtime went backwards from 1162 usec to 587 usec for pid 1011 >>>>> (sendmail) >>>>> calcru: runtime went backwards from 947 usec to 478 usec for pid 1010 >>>>> (httpd) >>>>> calcru: runtime went backwards from 895 usec to 452 usec for pid 1009 >>>>> (httpd) >>>>> calcru: runtime went backwards from 954 usec to 482 usec for pid 1008 >>>>> (httpd) >>>>> calcru: runtime went backwards from 909 usec to 459 usec for pid 1007 >>>>> (httpd) >>>>> calcru: runtime went backwards from 1214 usec to 653 usec for pid 1006 >>>>> (httpd) >>>>> calcru: runtime went backwards from 201793 usec to 102672 usec for pid >>>>> 996 (httpd) >>>>> calcru: runtime went backwards from 1105 usec to 1064 usec for pid 991 >>>>> (sshd) >>>>> calcru: runtime went backwards from 45196 usec to 23221 usec for pid >>>>> 974 (zabbix_server) >>>>> calcru: runtime went backwards from 2192 usec to 1436 usec for pid 973 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 605 usec to 306 usec for pid 968 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 626 usec to 316 usec for pid 967 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 773 usec to 391 usec for pid 966 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 663 usec to 335 usec for pid 965 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 799 usec to 404 usec for pid 964 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 37723 usec to 19422 usec for pid >>>>> 963 (zabbix_server) >>>>> calcru: runtime went backwards from 49425 usec to 26265 usec for pid >>>>> 962 (zabbix_server) >>>>> calcru: runtime went backwards from 38883 usec to 20993 usec for pid >>>>> 961 (zabbix_server) >>>>> calcru: runtime went backwards from 53478 usec to 27411 usec for pid >>>>> 960 (zabbix_server) >>>>> calcru: runtime went backwards from 40845 usec to 21750 usec for pid >>>>> 959 (zabbix_server) >>>>> calcru: runtime went backwards from 47835 usec to 24455 usec for pid >>>>> 958 (zabbix_server) >>>>> calcru: runtime went backwards from 2257 usec to 1612 usec for pid 957 >>>>> (zabbix_server) >>>>> calcru: runtime went backwards from 2361 usec to 1193 usec for pid 932 >>>>> (zabbix_agentd) >>>>> calcru: runtime went backwards from 32053 usec to 16204 usec for pid >>>>> 928 (zabbix_server) >>>>> calcru: runtime went backwards from 32517 usec to 19280 usec for pid 697 >>>>> (sh) >>>>> calcru: runtime went backwards from 1128021 usec to 868022 usec for pid >>>>> 697 (sh) >>>>> calcru: runtime went backwards from 9609 usec to 5601 usec for pid 601 >>>>> (syslogd) >>>>> calcru: runtime went backwards from 688 usec to 348 usec for pid 106 >>>>> (adjkerntz) >>>>> calcru: runtime went backwards from 12 usec to 6 usec for pid 3 >>>>> (sctp_iterator) >>>>> calcru: runtime went backwards from 5467 usec to 2853 usec for pid 2 >>>>> (fdc0) >>>>> calcru: runtime went backwards from 11306 usec to 8408 usec for pid 14 >>>>> (rand_harvestq) >>>>> calcru: runtime went backwards from 136242 usec to 76230 usec for pid 13 >>>>> (geom) >>>>> calcru: runtime went backwards from 156117 usec to 118882 usec for pid 12 >>>>> (intr) >>>>> calcru: runtime went backwards from 7820 usec to 4847 usec for pid 1 >>>>> (init) >>>>> calcru: runtime went backwards from 2340313 usec to 1226503 usec for >>>>> pid 1 (init) >>>>> calcru: runtime went backwards from 4114 usec to 2164 usec for pid 0 >>>>> (kernel) >>>>> >>>>> >>>>> Is it bad? Or I have to ignore them? >>>> >>>> >>>> I'm not talking authoratatively but in some virtualization systems, if the >>>> TSCs on the various processors are not sufficiently synchronized, then when >>>> the hypervisor switches you from one CPU to another, you can get odd >>>> (sometimes negative) time readings which give messages like this.. >>>> >>>>> _______________________________________________ >>>>> freebsd-virtualization@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>>>> To unsubscribe, send any mail to >>>>> "freebsd-virtualization-unsubscribe@freebsd.org" >>>>> >>>>> >>>> From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 7 12:21:39 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4D56CB69 for ; Thu, 7 Nov 2013 12:21:39 +0000 (UTC) (envelope-from mtetsuyah@gmail.com) Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2AB2329CD for ; Thu, 7 Nov 2013 12:21:39 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id g10so524348pdj.34 for ; Thu, 07 Nov 2013 04:21:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=4NJNH2npDxtf1Q3Tk+tueyAo64cZgutnnhW/hWDWoQc=; b=I4alWlSbTNQGhACqb7DUtL1igaCFMZI5qT0+tn+1s6x4XtsRsS3xqjFdiI8YRHNzgm XpBLqXUg/adwUQowv6aWVdjk3fdfB2lKwehcTAyZhJOLZipWaHnbRYSOVzuy3eIq+kEe i9rdx7wED/d4Xx3Sok+xtsyj8TKhTiaTrHM9ds9lsIeMojY++z3j7PtekwZbcRv6lKlJ AskfyuQy+M/4SaOdlbZ9MTnUH+0I4x+UZ1blFAskHnIo9zFu61+XsMp3RQgJn+1nMJUO 0MNaaTFLeIkd3cd0V1aHTeupXJ5vcre9QV6TGfnrHxseOs7xfMbG+JmI/xqlQKcElBtW +CjQ== MIME-Version: 1.0 X-Received: by 10.68.236.103 with SMTP id ut7mr8722980pbc.118.1383826898716; Thu, 07 Nov 2013 04:21:38 -0800 (PST) Received: by 10.70.5.164 with HTTP; Thu, 7 Nov 2013 04:21:38 -0800 (PST) Date: Thu, 7 Nov 2013 21:21:38 +0900 Message-ID: Subject: Bhyve virtio-net on Linux guest From: Tetsuya Mukawa To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Nov 2013 12:21:39 -0000 Hi folks, I want to run a Linux guest on Bhyve. It seems very recently Bhyve supports a linux guest, so I am a bit worry about I can use a virtio-net. Someone, could you please let me know is it possible to use a virtio-net on Linux guest? -- Tetsuya From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 7 12:26:43 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 52F47E59 for ; Thu, 7 Nov 2013 12:26:43 +0000 (UTC) (envelope-from krn@krn.dk) Received: from fjotte.krn.dk (fjotte.krn.dk [62.242.64.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E3B6C2A54 for ; Thu, 7 Nov 2013 12:26:42 +0000 (UTC) Received: from [127.0.0.1] (ip199.tdu.dk [62.242.64.199] (may be forged)) (authenticated bits=0) by fjotte.krn.dk (8.13.6/8.13.6) with ESMTP id rA7CQAx8013601; Thu, 7 Nov 2013 13:26:10 +0100 (CET) (envelope-from krn@krn.dk) Message-ID: <527B86E2.5020907@krn.dk> Date: Thu, 07 Nov 2013 13:26:10 +0100 From: Kristen Nielsen User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: FreeBSD 9.1-Rel: Jail-rc startup of vnet jails with new configuration syntax Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Nov 2013 12:26:43 -0000 Hi freebsd-virtualization list I am trying to figure out how to start configured jails within FreeBSD 9.1Release at boot time. I am using new C-style jail configuration syntax in /etc/jail.conf. all jail starts successfully when i do a jail -c from the commandline. I am trying to configure jails to start at boot time using the features in the /etc/rc.conf file. in /etc/rc.conf at base host i have jail_enable="YES" jail_list=" jail1 jail2 jail3 " and no more jail related lines, evereything else is placed into the jail configuration (C-style) file. running "service jail start": Configuring jails:. Starting jails:/etc/rc.d/jail: ERROR: jail: No hostname has been defined for jail1 Looking into the /etc/rc.d/jail script it seems it expects that the /etc/rc.conf contains old style jail configuration statement like jail__hostname="jail1" etc. I have looked at the patch at: http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet but it also uses the old style (rc.config) jail configuration format, but with extended number of parameters. The patch is dated before the 9-1 release where the C-style jail configuration syntax was taken into use. is there a patch for /etc/rc.d/jail script that make it handles the new style jail configuration file format (the C-style format). or am I doing this the wrong way. If you can point me into the right direction it will be very helpfull. Whishlist It would be great with something like a /etc/jail.d/ setup where each jail configuration file is contained in a separate file, the format is the same as the /etc/jail.conf, the latter fil just holds configurations for all jails. Both files with the C-style syntax. Regards Kristen Nielsen, Denmark. krn@krn.dk From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 7 12:44:36 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 27262A62 for ; Thu, 7 Nov 2013 12:44:36 +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 85C152BF0 for ; Thu, 7 Nov 2013 12:44:34 +0000 (UTC) Received: (qmail 21452 invoked by uid 89); 7 Nov 2013 12:44:33 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.77) by mail.grem.de with ESMTPA; 7 Nov 2013 12:44:33 -0000 Date: Thu, 7 Nov 2013 13:44:32 +0100 From: Michael Gmelin To: Kristen Nielsen Subject: Re: FreeBSD 9.1-Rel: Jail-rc startup of vnet jails with new configuration syntax Message-ID: <20131107134432.2530dce7@bsd64.grem.de> In-Reply-To: <527B86E2.5020907@krn.dk> References: <527B86E2.5020907@krn.dk> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Nov 2013 12:44:36 -0000 On Thu, 07 Nov 2013 13:26:10 +0100 Kristen Nielsen wrote: > Hi freebsd-virtualization list > > I am trying to figure out how to start configured jails within > FreeBSD 9.1Release at boot time. > I am using new C-style jail configuration syntax in /etc/jail.conf. > all jail starts successfully when i do a jail -c from the commandline. > > I am trying to configure jails to start at boot time using the > features in the /etc/rc.conf file. > > in /etc/rc.conf at base host i have > jail_enable="YES" > jail_list=" jail1 jail2 jail3 " > > and no more jail related lines, evereything else is placed into the > jail configuration (C-style) file. > > running "service jail start": > Configuring jails:. > Starting jails:/etc/rc.d/jail: ERROR: jail: No hostname has been > defined for jail1 > > Looking into the /etc/rc.d/jail script it seems it expects that the > /etc/rc.conf contains old style jail configuration statement like > > jail__hostname="jail1" > etc. > > I have looked at the patch at: > http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet > but it also uses the old style (rc.config) jail configuration format, > but with extended number of parameters. The patch is dated before the > 9-1 release where the C-style jail configuration syntax was taken > into use. > > is there a patch for /etc/rc.d/jail script that make it handles the > new style jail configuration file format (the C-style format). or am > I doing this the wrong way. > > If you can point me into the right direction it will be very helpfull. > > Whishlist > It would be great with something like a /etc/jail.d/ setup > where each jail configuration file is contained in a separate file, > the format is the same as the /etc/jail.conf, the latter fil just > holds configurations for all jails. Both files with the C-style > syntax. Have you considered using sysutils/ezjail (the de-facto standard for managing jails under FreeBSD right now) or a similar port (sysutils/jailrc, sysutils/qjail etc.)? -- Michael Gmelin From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 7 12:49:58 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8BD47DD1 for ; Thu, 7 Nov 2013 12:49:58 +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 E8BBD2C5A for ; Thu, 7 Nov 2013 12:49:57 +0000 (UTC) Received: (qmail 21485 invoked by uid 89); 7 Nov 2013 12:49:56 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.77) by mail.grem.de with ESMTPA; 7 Nov 2013 12:49:56 -0000 Date: Thu, 7 Nov 2013 13:49:55 +0100 From: Michael Gmelin To: Kristen Nielsen Subject: Re: FreeBSD 9.1-Rel: Jail-rc startup of vnet jails with new configuration syntax Message-ID: <20131107134955.734a474f@bsd64.grem.de> In-Reply-To: <20131107134432.2530dce7@bsd64.grem.de> References: <527B86E2.5020907@krn.dk> <20131107134432.2530dce7@bsd64.grem.de> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Nov 2013 12:49:58 -0000 On Thu, 7 Nov 2013 13:44:32 +0100 Michael Gmelin wrote: > > > On Thu, 07 Nov 2013 13:26:10 +0100 > Kristen Nielsen wrote: > > > Hi freebsd-virtualization list > > > > I am trying to figure out how to start configured jails within > > FreeBSD 9.1Release at boot time. > > I am using new C-style jail configuration syntax in /etc/jail.conf. > > all jail starts successfully when i do a jail -c from the > > commandline. > > > > I am trying to configure jails to start at boot time using the > > features in the /etc/rc.conf file. > > > > in /etc/rc.conf at base host i have > > jail_enable="YES" > > jail_list=" jail1 jail2 jail3 " > > > > and no more jail related lines, evereything else is placed into the > > jail configuration (C-style) file. > > > > running "service jail start": > > Configuring jails:. > > Starting jails:/etc/rc.d/jail: ERROR: jail: No hostname has been > > defined for jail1 > > > > Looking into the /etc/rc.d/jail script it seems it expects that the > > /etc/rc.conf contains old style jail configuration statement like > > > > jail__hostname="jail1" > > etc. > > > > I have looked at the patch at: > > http://wiki.polymorf.fr/index.php/Howto:FreeBSD_jail_vnet > > but it also uses the old style (rc.config) jail configuration > > format, but with extended number of parameters. The patch is dated > > before the 9-1 release where the C-style jail configuration syntax > > was taken into use. > > > > is there a patch for /etc/rc.d/jail script that make it handles the > > new style jail configuration file format (the C-style format). or am > > I doing this the wrong way. > > > > If you can point me into the right direction it will be very > > helpfull. > > > > Whishlist > > It would be great with something like a /etc/jail.d/ > > setup where each jail configuration file is contained in a separate > > file, the format is the same as the /etc/jail.conf, the latter fil > > just holds configurations for all jails. Both files with the C-style > > syntax. > > Have you considered using sysutils/ezjail (the de-facto standard for > managing jails under FreeBSD right now) or a similar port > (sysutils/jailrc, sysutils/qjail etc.)? > I missed the vnet requirement in my first reply. There has been a vnet patch for ezjail floating around a while ago, but I think it was never adopted to ezjail. Sorry for the noise. -- Michael Gmelin From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 7 13:35:51 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A84D09B9 for ; Thu, 7 Nov 2013 13:35:51 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 682632069 for ; Thu, 7 Nov 2013 13:35:51 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id F063128437; Thu, 7 Nov 2013 14:35:42 +0100 (CET) Received: from [192.168.1.2] (ip-89-177-49-222.net.upcbroadband.cz [89.177.49.222]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2E16A28422; Thu, 7 Nov 2013 14:35:42 +0100 (CET) Message-ID: <527B972E.7020900@quip.cz> Date: Thu, 07 Nov 2013 14:35:42 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Kristen Nielsen Subject: Re: FreeBSD 9.1-Rel: Jail-rc startup of vnet jails with new configuration syntax References: <527B86E2.5020907@krn.dk> In-Reply-To: <527B86E2.5020907@krn.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 Nov 2013 13:35:51 -0000 Kristen Nielsen wrote: > Hi freebsd-virtualization list > > I am trying to figure out how to start configured jails within FreeBSD > 9.1Release at boot time. > I am using new C-style jail configuration syntax in /etc/jail.conf. > all jail starts successfully when i do a jail -c from the commandline. [...] Take a look at sysutils/jail2. It is jail startup/shutdown script with jail.conf support. Miroslav Lachman