From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 07:25:34 2014 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 ESMTPS id 507DCEB8 for ; Sun, 9 Feb 2014 07:25:34 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e: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 18E931BFA for ; Sun, 9 Feb 2014 07:25:34 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so4852117pdj.15 for ; Sat, 08 Feb 2014 23:25:33 -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=QP2QUW7KLqdSkc2kftV0xa59J0KBNpaqVzGgPBX+sLk=; b=iYByLhrKgp3ZaRIp4QD1OigpWPBOQG3qBwZCHTjnuT0fdp1QwNyy4XY5lDsXSWrDUf S/E5iVsAmyD34VLbgNh31o9mGwBWsuHcKj7OTBq7ljgsSDd6HJfjuPwFLq0Dwjp6O6/F QWoFwOJEzvRvy7yBkWjLH89IYYg16qNPSsSPnyzNSe5362Aw8XNpOTUg5JndEmCvVvn0 MeYvNWRNTUwV0iVgTI17XSMAaEtr4K8GiXqMkEFW0ytKMuxDRogGRrz3r1kQxAUKCysk AB+Pn0jA+TKUxmeY331b2DP6z0V2qo3ArEuY1ormP6NrpCgU0cCWZxE7mf4OvRVAzHLB Zh3Q== MIME-Version: 1.0 X-Received: by 10.68.180.66 with SMTP id dm2mr1721195pbc.143.1391930733520; Sat, 08 Feb 2014 23:25:33 -0800 (PST) Received: by 10.70.127.142 with HTTP; Sat, 8 Feb 2014 23:25:33 -0800 (PST) Received: by 10.70.127.142 with HTTP; Sat, 8 Feb 2014 23:25:33 -0800 (PST) In-Reply-To: <52F6BD8B.7080205@callfortesting.org> References: <52F5363D.8040102@freebsd.org> <52F6BD8B.7080205@callfortesting.org> Date: Sun, 9 Feb 2014 09:25:33 +0200 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Sami Halabi To: Michael Dexter Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 07:25:34 -0000 As long as its practical and related to the virtualizationn I think its okay. At least he provides a lot of info through his discussions. Sami =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 9 =D7=91=D7=A4=D7=91=D7=A8 2014 01:28,= "Michael Dexter" =D7=9B=D7=AA=D7=91: > > For the curious, Aryeh posted 67 out of January's 276 messages to the > list with the next highest poster coming in at 21. > > This is not the proper use of this list. > > Michael Dexter > bhyve volunteer > _______________________________________________ > 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 Sun Feb 9 07:30:53 2014 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 ESMTPS id AC7CEF55 for ; Sun, 9 Feb 2014 07:30:53 +0000 (UTC) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63B941C72 for ; Sun, 9 Feb 2014 07:30:53 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id w8so7882104qac.28 for ; Sat, 08 Feb 2014 23:30:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mbM49ITZ4uDOEaTsnhjDnPowvC+oSxeiws2K1gNeMsE=; b=sPmDEgfR5/JWk/QfPFHfM7JzfYfKITsPy2b8Mrf/Wc6tyKXU5+PHeoHsiixChnE1ED VEMgkCewKdMJgEcjLvtpuY4eRlESki4TnumnsEIpjEJNTM+IK63PC/AlQQMn4tb9Zi0b fm8KfjdnediclqdN20eWUIe8WgJykwoC/5BR8z/87pJ9ODbHUcf7xeoe5S+ejnsf5Nsz 1svlFbg3rRoV894cU3+gqTuB07/o9qUU01E1rcyTj/yFh15qxzGp5IrZMckLQf0pdcyN gLAhQiZx6dMY6IIbsUv1UQANmEugUy1nfqpHu6ZKFGuMR6hxx1DzPO0ef0Fb1r2RiZ1k vMQg== MIME-Version: 1.0 X-Received: by 10.229.179.5 with SMTP id bo5mr19776195qcb.21.1391931052496; Sat, 08 Feb 2014 23:30:52 -0800 (PST) Sender: shteryana@gmail.com Received: by 10.224.128.69 with HTTP; Sat, 8 Feb 2014 23:30:52 -0800 (PST) In-Reply-To: <20140206201238.GA74665@enceladus10.kn-bremen.de> References: <20140206175919.GA67849@enceladus10.kn-bremen.de> <20140206201238.GA74665@enceladus10.kn-bremen.de> Date: Sun, 9 Feb 2014 09:30:52 +0200 X-Google-Sender-Auth: 8q1itI8XToAjvMJKOu573GkXUsM Message-ID: Subject: Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE ) From: Shteryana Shopova To: Juergen Lock Content-Type: multipart/mixed; boundary=001a11c2bccaefe7c104f1f433be Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: syrinx@FreeBSD.org List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 07:30:53 -0000 --001a11c2bccaefe7c104f1f433be Content-Type: text/plain; charset=UTF-8 Hi, Ok, I seem to have sent an earlier and not-well-though-out version of the patch - attaching the correct one now (I dug into this a couple of months ago and needed some time to remember the details). I tried it with your test setup and - module loads/unloads cleanly, but will freeze the vbox FreeBSD 10 host if I try to run openbsd 5.5 VM (my FreeBSD current host freezes too if I try to run a VirtualBox VM with vmm.ko and nmdm.ko modules loaded, not sure why). I tested it again on a FreeBSD current host running on real hardware with a number of VMs/OSes and the results I got are - * Ubuntu-12.04.4 both amd64 and i386 fail to boot from CD - get stuck somewhere after a purple screen * Debian 7.3.0 both amd64 and i386 boot and install fine from CD, booting from hard disk gets stuck at GRUB though * FreeBSD 10 i386 boots from CD and disk, however is very slow (installation took literally several hours) * pfSense 2.1 i386 works fine * OpenBSD 5.5 i386 boots and installs from CD, boots from disk after installation only when ACPI is disabled at boot * OpenBSD 5.5 amd64 boots and installs from CD, booting the installed OS from disk however crashes qemu late around starting sndiod with RAX=0000000000000000 RBX=00001a938686c340 RCX=00001a91832031e5 RDX=00001a938dc82b64 RSI=0000000000000012 RDI=00001a938686c350 RBP=00001a938dfb6f60 RSP=00007f7ffffebf30 R8 =00001a938dfb6f60 R9 =000000000000000d R10=0000000000000000 R11=0000000000000000 R12=00001a91832031e5 R13=0000000000000012 R14=00001a9392ff4000 R15=0000000000000000 RIP=00001a938db21c7d RFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 SMM=0 HLT=0 ES =0023 0000000000000000 ffffbfff 00aff300 DPL=3 DS16 [-WA] CS =002b 0000000000000000 ffffbfff 00affb00 DPL=3 CS64 [-RA] SS =0023 0000000000000000 ffffbfff 00aff300 DPL=3 DS16 [-WA] DS =0023 0000000000000000 ffffbfff 00aff300 DPL=3 DS16 [-WA] FS =0023 0000000000000000 ffffbfff 00aff300 DPL=3 DS16 [-WA] GS =0023 0000000000000000 ffffbfff 00aff300 DPL=3 DS16 [-WA] LDT=0000 0000000000000000 00000000 00008200 DPL=0 LDT TR =0030 ffff800000011000 00000067 00008900 DPL=0 TSS64-avl GDT= ffff800000011068 0000003f IDT= ffff800000010000 00000fff CR0=e001003b CR2=00001a938686c348 CR3=000000003f498000 CR4=000007b0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 Unsupported return value: 0xffffffff and kqemu: closed by pid=26323 kqemu: aborting: Unexpected exception 0x0d in monitor space in dmesg. This however looks like a problem with kqemu-kmod not related to the KPI changes. I tested this with kqemu-kmod-devel with the patch applied and qemu-0.11.1_13 since obviously KQEMU support was dropped in later versions. Considering that kqemu support was dropped in newer versions of qemu however, the patch is probably useless and kqemu-kmod ports should just be marked obsolete. cheers, Shteryana On Thu, Feb 6, 2014 at 10:12 PM, Juergen Lock wrote: > The commit does look relevant but testing your patch on a 10.0-RC1 > vbox guest (it's what I had available) with the RC1 iso like so: > > # kldload kqemu > % qemu-system-x86_64 -cdrom /dev/cd0 -m 512 -curses -enable-kqemu > > panics like this: > > ---------------------------------------------------------- > 10rc1amd64mbr2 dumped core - see /var/crash/vmcore.1 > --001a11c2bccaefe7c104f1f433be Content-Type: text/plain; charset=US-ASCII; name="kqemu-freebsd.c-20140208-01.diff" Content-Disposition: attachment; filename="kqemu-freebsd.c-20140208-01.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hrfznp8k0 LS0tIGtxZW11LWZyZWVic2QuY34JMjAxNC0wMi0wNyAyMDowMDozMy42NTYyNTUzOTUgKzAyMDAK KysrIGtxZW11LWZyZWVic2QuYwkyMDE0LTAyLTA4IDA4OjQzOjE5LjIwOTEwMDcwOCArMDIwMApA QCAtMTA1LDE3ICsxMDUsMjkgQEAKICAqLwogc3RydWN0IGtxZW11X3BhZ2UgKkNERUNMIGtxZW11 X2FsbG9jX3plcm9lZF9wYWdlKHVuc2lnbmVkIGxvbmcgKnBwYWdlX2luZGV4KQogeworI2lmIF9f RnJlZUJTRF92ZXJzaW9uIDwgMTAwMDAzMAogICAgIHBtYXBfdCBwbWFwOworI2VuZGlmCiAgICAg dm1fb2Zmc2V0X3QgdmE7CiAgICAgdm1fcGFkZHJfdCBwYTsKIAorI2lmIF9fRnJlZUJTRF92ZXJz aW9uID49IDEwMDAwMzAKKyAgICB2YSA9IGttZW1fbWFsbG9jKGtlcm5lbF9hcmVuYSwgUEFHRV9T SVpFLCBNX1pFUk8gfCBNX1dBSVRPSyk7CisjZWxzZQogICAgIHZhID0ga21lbV9hbGxvYyhrZXJu ZWxfbWFwLCBQQUdFX1NJWkUpOworI2VuZGlmCisKICAgICBpZiAodmEgPT0gMCkgewogCWtxZW11 X2xvZygia3FlbXVfYWxsb2NfemVyb2VkX3BhZ2U6IE5VTExcbiIpOwogCXJldHVybiBOVUxMOwog ICAgIH0KKworI2lmIF9fRnJlZUJTRF92ZXJzaW9uID49IDEwMDAwMzAKKyAgICBwYSA9IHZ0b3Bo eXModmEpOworI2Vsc2UKICAgICBwbWFwID0gdm1fbWFwX3BtYXAoa2VybmVsX21hcCk7CiAgICAg cGEgPSBwbWFwX2V4dHJhY3QocG1hcCwgdmEpOworI2VuZGlmCiAgICAgLyoga3FlbXVfbG9nKCJr cWVtdV9hbGxvY196ZXJvZWRfcGFnZTogJTA4eFxuIiwgcGEpOyAqLwogICAgICpwcGFnZV9pbmRl eCA9IHBhID4+IFBBR0VfU0hJRlQ7CiAgICAgcmV0dXJuIChzdHJ1Y3Qga3FlbXVfcGFnZSAqKXZh OwpAQCAtMTI1LDcgKzEzNywxMSBAQAogewogICAgIGlmIChrcWVtdV9kZWJ1ZyA+IDApCiAgICAg CWtxZW11X2xvZygia3FlbXVfZnJlZV9wYWdlKCVwKVxuIiwgcGFnZSk7CisjaWYgX19GcmVlQlNE X3ZlcnNpb24gPj0gMTAwMDAzMAorICAgIGttZW1fZnJlZShrZXJuZWxfYXJlbmEsICh2bV9vZmZz ZXRfdCkgcGFnZSwgUEFHRV9TSVpFKTsKKyNlbHNlCiAgICAga21lbV9mcmVlKGtlcm5lbF9tYXAs ICh2bV9vZmZzZXRfdCkgcGFnZSwgUEFHRV9TSVpFKTsKKyNlbmRpZgogfQogCiAvKiByZXR1cm4g a2VybmVsIGFkZHJlc3Mgb2YgdGhlIHBoeXNpY2FsIHBhZ2UgcGFnZV9pbmRleCAqLwo= --001a11c2bccaefe7c104f1f433be-- From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 07:58:43 2014 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 ESMTPS id 116D91F1 for ; Sun, 9 Feb 2014 07:58:43 +0000 (UTC) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C60571DA5 for ; Sun, 9 Feb 2014 07:58:42 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id y10so4818665pdj.26 for ; Sat, 08 Feb 2014 23:58:36 -0800 (PST) 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 :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xI0vA0vEWi8/vDMCSjiAQ3A8WjlNnH1qQ6uFe/Dnlbg=; b=dcV2O1YnezjXMn1r1B9bw84/Os2NMHKfKIHkSVif9IjiNOmYxbAt4ssvTJJGqCiSZV ePTcSvbIp5r1Fl4/5bE45SOM6miU2oPXRv4/ekaK09DMnnY2PoNWe7w4nsCWYAMHb/nN +VSRg2XEUnU8DJobJoB4X/pBzm60Zw6EuuiM5hXxX7itTQyD11cOicpEtsv5hBX8UzB4 tzASyi+iAi+MKBg0pPYrjPC808PLszyq7+GIab3eIGxoY5+/+zDGjCzF+xBogkrz9sBI l+8EkmYs5U95rIMA2sfm/an8/u73RT60lII3cqbxR/FhKgdiyxLWDeuCILqr9iU2PGYZ EX2Q== X-Gm-Message-State: ALoCoQkMwfbI6huE8CVGY2jRTwBzem5PH3Hx2z51DfdHwL4T51iO8plWcy27zV739jVtCwJ14oiL X-Received: by 10.68.170.66 with SMTP id ak2mr30133092pbc.5.1391932716074; Sat, 08 Feb 2014 23:58:36 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id c7sm30292847pbt.0.2014.02.08.23.58.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Feb 2014 23:58:35 -0800 (PST) Message-ID: <52F7352A.7010009@callfortesting.org> Date: Sat, 08 Feb 2014 23:58:34 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Sami Halabi Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve References: <52F5363D.8040102@freebsd.org> <52F6BD8B.7080205@callfortesting.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 07:58:43 -0000 On 2/8/14 11:25 PM, Sami Halabi wrote: > As long as its practical and related to the virtualizationn I think its > okay. Correct but this has unfortunately not been the case. > At least he provides a lot of info through his discussions. Off topic is off topic in accordance with the stated FreeBSD mailing list etiquette guidelines and you will find many corrections to his statements. Friend of yours? Michael Dexter bhyve volunteer From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 08:02:29 2014 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 ESMTPS id AC3A6263 for ; Sun, 9 Feb 2014 08:02:29 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e: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 736F31E16 for ; Sun, 9 Feb 2014 08:02:29 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id fa1so4944624pad.28 for ; Sun, 09 Feb 2014 00:02:29 -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=oYg9+JQBmodrODTY1y5Gju8R5spJer9C6fy7Xy2Sq7c=; b=E2yp8yiamT+vHzUxdFu7LWYn17st+zwnOze8OUCN5YzAbWg4Wq8XHdkxraGmxr767D rqXhJdFKNt+thYUeC4VvKMmibrkBvi5qcvcd4HC/4KzJHVKm21NcBu4//8kuZPG3XpOZ tMvX7z5PQ6ELq6cgczsvNs/QfD7ZbJ0HK0iy8ymQuUXQ08o48eiKh8c8khty3eiYpKfA RQMjEEzxosVNcUmOvh2xmAVe5idVquKxj2rfHIgzG8eMkhR7+QU7aoNqLBPo661bUqr8 nrAyU6wcTEhjdct64jMUokmal1aXdNFkd4SMtZB7T6j34U4yjxiz23UI49Uh54V7F54c DXNA== MIME-Version: 1.0 X-Received: by 10.66.192.162 with SMTP id hh2mr605835pac.150.1391932949150; Sun, 09 Feb 2014 00:02:29 -0800 (PST) Received: by 10.68.102.35 with HTTP; Sun, 9 Feb 2014 00:02:29 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> <52F6BD8B.7080205@callfortesting.org> Date: Sun, 9 Feb 2014 09:02:29 +0100 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Marie To: Sami Halabi Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 08:02:29 -0000 Trying this again. First attempt went only to Sami. I think it's awesome that there are projects using FreeBSD technology. However, this list is for discussions related to virtualization in FreeBSD. IMO, there has been a lot of off-topic posts on this list lately, mostly by Aryeh. If I wanted this level of information about Petitecloud, I'd subscribe to their list (now that they have one). And if I wanted to know about some persons plans which are not directly related to virtualization in FreeBSD, I'd ask them, or look at their blog. These things are not the reason I subscribed to this list, at least. _____________________ Marie Helene http://savagedlight.me/ On Sun, Feb 9, 2014 at 8:25 AM, Sami Halabi wrote: > As long as its practical and related to the virtualizationn I think its > okay. > At least he provides a lot of info through his discussions. > > Sami > =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A 9 =D7=91=D7=A4=D7=91=D7=A8 2014 01:2= 8, "Michael Dexter" > =D7=9B=D7=AA=D7=91: > > > > > For the curious, Aryeh posted 67 out of January's 276 messages to the > > list with the next highest poster coming in at 21. > > > > This is not the proper use of this list. > > > > Michael Dexter > > bhyve volunteer > > _______________________________________________ > > 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" > > > _______________________________________________ > 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 Sun Feb 9 18:33:49 2014 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 ESMTPS id 2ABAF110 for ; Sun, 9 Feb 2014 18:33:49 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D9AB41ADB for ; Sun, 9 Feb 2014 18:33:48 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 66FA41534C4; Sun, 9 Feb 2014 19:33:34 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1-AS7a-eU3o; Sun, 9 Feb 2014 19:33:31 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 0867F153448; Sun, 9 Feb 2014 19:33:31 +0100 (CET) Message-ID: <52F7C9FC.5070409@digiware.nl> Date: Sun, 09 Feb 2014 19:33:32 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Michael Dexter , "freebsd-virtualization@freebsd.org" Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> In-Reply-To: <52F6953D.2010400@callfortesting.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 18:33:49 -0000 On 8-2-2014 21:36, Michael Dexter wrote: > > Hello all, > > I have built and uploaded a bhyve SVM project branch snapshot of r261578 > (February 4th, 2014, MFC @ r259205) that can be found at: > > http://mirrors.nycbug.org/pub/bhyve/r261578-svm/ > > Those with Barcelona class (http://en.wikipedia.org/wiki/AMD_10h) AMD > hardware are invited to give this. So far I have had luck with my humble > Athlon(tm) II Neo N36L Dual-Core Processor (1297.87-MHz K8-class CPU). I was exactly looking for this information, since I upgraded to 10-Stable. And found no bhyve for AMD. Are there any (near future) plans to merge this with the regular stable branch? For now I'll give the above a testshot. Thanx, --WjW From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 20:59:21 2014 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 ESMTPS id A6620419 for ; Sun, 9 Feb 2014 20:59:21 +0000 (UTC) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e: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 7D37A16B5 for ; Sun, 9 Feb 2014 20:59:21 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id um1so5374609pbc.19 for ; Sun, 09 Feb 2014 12:59:21 -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=55JkLK+msbUDrwC4lBQtRF26ZaBl4A/hyAsS2R16bmc=; b=zA2p/GmVBYl2J5ixi6QpCrKYIgKxRdNSpHr2YNoXcme/MsbJY0V8OVz73a6CorNOXV GW2aM/cWUC9O6Qcelrzz47588Lmggxtmh4YKg8mrMOn4RN7mIrVGQB75wduXMU2dVosg KEdPQBAbwwt5k3Fd7h2Gpd1jc4NZO4YYoLLURt3qGJyRhaD/uqgjFRV4TfEL8re7Dp3r HqeLHaI78XblsxSM6OJkep7M9Rw24BeMt7QED26c2YwRdeCKG/SOT8LsefhcP0l5U0sx Yl69RdLQW4/Fp8ODSkkKmhrbZ1q+0oLXPUq3RgF2fybArt7ujJXw1Lw+I7EFc4WLWxCE CJwA== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr33328266pbc.42.1391979561087; Sun, 09 Feb 2014 12:59:21 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 9 Feb 2014 12:59:21 -0800 (PST) Date: Sun, 9 Feb 2014 15:59:21 -0500 Message-ID: Subject: are ahci-hd images the same as raw under bhyve From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 20:59:21 -0000 When I was playing with bhyve-grub a while ago I noticed there seemed to be little difference between ahci-hd and "raw" (if no format it given besides just naming a md file). Is it safe to treat the two formats interchangeably in bhyve (and bhyve-grub)? Can I do this to the point of mixing and matching them on instances created with both (i.e. boot with ahci on a raw image and vice versa)? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 21:11:02 2014 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 ESMTPS id BABA9D02 for ; Sun, 9 Feb 2014 21:11:02 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 414F11815 for ; Sun, 9 Feb 2014 21:11:02 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id hr17so4142713lab.20 for ; Sun, 09 Feb 2014 13:11:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=s5JC3NM9n7tPNbDasxm38bQFSZ4pAzmld+nBmW6hOKw=; b=vKJguwOEG8PZf9BZHSaF8g83doTfTHs+C6NC/QN9qwa3s+Jkf+fVOI78UyxT5PdN9q vCbT19Tf5VOD+ZvxvxCz4L2lmQDa+o7NAyazIKbAxEEAyHDjBZ4mXrYBnbln9dMeQs6A tz10V2FYkBOoDtfWqtvpSUctKnvNvmyTq5ybmYxOgwn43k0G28Il6+ptpMEpHhLA8uxT yuFi8NojeXanLw0OOxyEuNWuVVClfOvi3EwZBEppHAbKQgfLfgELli/3LqBda/9cGVlg vKNkpxTYYqkrJpSIZ2guc8489brdRVFiROetSxF2EuqIStjcxnvfb5OVF4UUWAlagfHV BebA== MIME-Version: 1.0 X-Received: by 10.153.8.225 with SMTP id dn1mr19175901lad.17.1391980260256; Sun, 09 Feb 2014 13:11:00 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Sun, 9 Feb 2014 13:11:00 -0800 (PST) Date: Sun, 9 Feb 2014 13:11:00 -0800 X-Google-Sender-Auth: h7lhIUB0XzVnHp2vas7gy8hC8v8 Message-ID: Subject: Detect of BHyve VM was powered off or rebooted? From: Craig Rodrigues To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 21:11:02 -0000 Hi, I posted some rc.d scripts that I am using to boot a BHyve VM and send the output to a serial console using the /dev/nmdm driver: http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html It works quite well. There is some things I would like to improve, and would like some advice on the best way to do it. (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, then I do not want to automatically restart the VM in the script. User should manually: service bhyvevm start (2) If the VM was powered down, via shutdown -p, or halt -p, then in my script I do not want to restart the VM in the script. User should manually: service bhyvevm start (3) If the VM was rebooted via "reboot" or "shutdown -r", then I *do* want the script to restart the VM. I think if I change my start_vm.sh script to do something like: ( while [ -e /dev/vmm/${VM} ]; do /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" done ) & then this might cover cases (1) and (3), but what will cover case (2)? Thanks for any advice. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 21:32:38 2014 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 ESMTPS id 065471F0; Sun, 9 Feb 2014 21:32:38 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e: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 CA1EE196D; Sun, 9 Feb 2014 21:32:37 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id fa1so5346013pad.14 for ; Sun, 09 Feb 2014 13:32: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=r6T/c6x5CnvM7EGmnoh73ZPUArjmLRDDyYGEw2X6Z2o=; b=kdsgHlNSjOKmOu/+0InRxqmrqZfA3FAtGfP4vOZn7UyB5J4aHqxNJxpZukjYUAr7oH 6XPM65NnlxiYLG3kDXlHDEyiu+ot3L2myg4VmdYca/TRQp5Kuua4l7CuTKjySOkXxj6l U4zyOEoryWRYQO++CnJnBaf2ew+v5IIPfL9QyJOJM6L+JqT1a8c7lyK8Lqo8lZRsfT6m +gzxM9WtNE/exqpJuC/GoWPn17K+DukUVAReME6MFrrjDu6KCF3tzHRN5eEp3V1FVCvj sST1UT8L2V1Hu1hENe5BCRNlEGoK1xnclh8Rk6bDZ5WI3LFsx6cX0Oh8qWvNhZ+37vyh pU9w== MIME-Version: 1.0 X-Received: by 10.66.121.234 with SMTP id ln10mr21631634pab.20.1391981557393; Sun, 09 Feb 2014 13:32:37 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 9 Feb 2014 13:32:37 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:32:37 -0500 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Aryeh Friedman To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 21:32:38 -0000 On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: > Hi, > > I posted some rc.d scripts that I am using to boot a BHyve VM > and send the output to a serial console using the /dev/nmdm > driver: > > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html > > It works quite well. There is some things I would like to improve, > and would like some advice on the best way to do it. > > (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, > then I do not want to automatically restart the VM in the script. > User should manually: service bhyvevm start > > (2) If the VM was powered down, via shutdown -p, or halt -p, > then in my script I do not want to restart the VM in the script. > User should manually: service bhyvevm start > > (3) If the VM was rebooted via "reboot" or "shutdown -r", > then I *do* want the script to restart the VM. > > I think if I change my start_vm.sh script to do something like: > > > > ( > while [ -e /dev/vmm/${VM} ]; do > /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc > -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" > done > > ) & > > > then this might cover cases (1) and (3), but what will cover > case (2)? > > Thanks for any advice. > The options you gave (which are really the only ones available) do not distinguish between the reason for the termination of the instance of bhyve pointing to /dev/vmm/XXX (it just does a normal termination). In my playing with this for almost a month the only solution seems to be put a trigger on instance shutdown via whatever method to leave a "cookie" file behind on the host (note I have not nor plan to do this in any of my own work). An other question is it wise to auto-reboot regardless of reason of the hypervisor termination? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 22:18:53 2014 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 ESMTPS id 9ADDD772 for ; Sun, 9 Feb 2014 22:18:53 +0000 (UTC) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0CAFF1CC9 for ; Sun, 9 Feb 2014 22:18:52 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id c6so4192524lan.38 for ; Sun, 09 Feb 2014 14:18:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ESayJ8CiBi47v/mZo1Wv62VcBwvjN9g3yiwtA6jUwP8=; b=mxrFfHhlJNE2NxTdHvExFJnUIwlIcV0v7m3+qYLx+ym+ZuVXX8KEgF9rMf60AALctP i3geop4mxxQtIDK92iB8B1K2QHhrWQm2zem8VoYLHdbCU+HwzJIDdj+o1Pm1LCDEPrN8 HCLPAF17O62YQyYBKaxtjZ+uS4I0/Yf7ryrlaAlMLmONnE7FdngZ5ioDQ+p6NdpAZ67V 0aABbpbdMeyVhVVJas6Soyyiks5IPRR1w3ZONPR1Wn7fnOvBCL3DQd86phe7WqbwR0NT F1RQi7icTtOWzGDvUUJqzuSNPDREgQGBKvTef9670yPMLuzXrIkUz4uYfEbOpn7EWreg tvAw== MIME-Version: 1.0 X-Received: by 10.152.27.100 with SMTP id s4mr19541468lag.18.1391984330916; Sun, 09 Feb 2014 14:18:50 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Sun, 9 Feb 2014 14:18:50 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 14:18:50 -0800 X-Google-Sender-Auth: O9wO8FvcAaF7Icj7_w37h7Ke7tg Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Craig Rodrigues To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 22:18:53 -0000 On Sun, Feb 9, 2014 at 1:32 PM, Aryeh Friedman wrote: > > > > On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: > >> Hi, >> >> I posted some rc.d scripts that I am using to boot a BHyve VM >> and send the output to a serial console using the /dev/nmdm >> driver: >> >> >> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html >> >> It works quite well. There is some things I would like to improve, >> and would like some advice on the best way to do it. >> >> (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, >> then I do not want to automatically restart the VM in the script. >> User should manually: service bhyvevm start >> >> (2) If the VM was powered down, via shutdown -p, or halt -p, >> then in my script I do not want to restart the VM in the script. >> User should manually: service bhyvevm start >> >> (3) If the VM was rebooted via "reboot" or "shutdown -r", >> then I *do* want the script to restart the VM. >> >> I think if I change my start_vm.sh script to do something like: >> >> >> >> ( >> while [ -e /dev/vmm/${VM} ]; do >> /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc >> -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" >> done >> >> ) & >> >> >> then this might cover cases (1) and (3), but what will cover >> case (2)? >> >> Thanks for any advice. >> > > The options you gave (which are really the only ones available) do not > distinguish between the reason for the termination of the instance of bhyve > pointing to /dev/vmm/XXX (it just does a normal termination). > Did you play with any of these flags to bhyvectl? [--get-vmcs-exit-ctls] [--get-vmcs-exit-reason] [--get-vmcs-exit-qualification] [--get-vmcs-exit-interruption-info] If I do: bhyvectl --get-vmcs-exit-reason --vm vm1 I get: vmcs_exit_reason[0] 0x000000000000001e If I look at: http://svnweb.freebsd.org/base/head/sys/amd64/vmm/intel/vmcs.h?view=markup#l310 we have: #define EXIT_REASON_INOUT 30 Linux has this stuff also: http://lxr.free-electrons.com/source/arch/x86/include/asm/vmx.h?v=3.1#L250 so I guess these values are defined in some Intel manual. > In my playing with this for almost a month the only solution seems to be > put a trigger on instance shutdown via whatever method to leave a "cookie" > file behind on the host (note I have not nor plan to do this in any of my > own work). > Yes, I can see why this might need to be done. I might need to do that myself. However, if bhyvectl can be used to provide adequate status information as to why the VM exited, I might be able to avoid this. It would be nicer though if /usr/sbin/bhyve returned the EXIT_REASON in its status code. > > An other question is it wise to auto-reboot regardless of reason of the > hypervisor termination? > I think the answer is "it depends". If someone does "reboot" or "shutdown -r", I think it is reasonable to restart the VM. If someone does "halt -p" or "shutdown -p", I think it is reasonable to not restart the VM. For any other error condition, I think it is reasonable to not restart the VM. I think that there is no single answer for all users and all applications. In my case, I am running BHyve VM's as "headless" which I access via the /dev/nmdm driver. If the VM reboots normally, I want it to restart. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 22:34:24 2014 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 ESMTPS id 133F2E2D; Sun, 9 Feb 2014 22:34:24 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D45191E24; Sun, 9 Feb 2014 22:34:23 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id z10so5292630pdj.19 for ; Sun, 09 Feb 2014 14:34:23 -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=5Aa9IafV0IthK8jIZMhWAm9CpW2I/mbiG77nm4lqLcc=; b=Oy7Ijf6JY69sjyLUrcFJI8l66mjOAyS8Dy1CcCycLEyiRTYpcDG7bFMixGh21HSszP VCj1Yl+11eGALI++OXm7qicVeOPUkQI+YkF7Emg3rFFjU/qqtPA5Q3HPYQn5zX5AUIqd RBeAgi1TUM3dlgUVZCWN89V+PIoUtkPcbgljyfKy6MOedO0GznEWWyMcnFRpO6mg1clO Q4Of/yS6dqQt3h2Vacn0wmtK31ueL+YmWB4aMODRaw6gf+g+hHp6Fu++rjXiXffzSCqb IsJstSnuxy5hgD7v57sQz2VqUh6wcKucErWG2yrGHCzIGlq4kaU4lS3YxUx1L1M2mJcY G8qA== MIME-Version: 1.0 X-Received: by 10.68.255.101 with SMTP id ap5mr33781623pbd.41.1391985263248; Sun, 09 Feb 2014 14:34:23 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 9 Feb 2014 14:34:23 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 17:34:23 -0500 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Aryeh Friedman To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 22:34:24 -0000 On Sun, Feb 9, 2014 at 5:18 PM, Craig Rodrigues wrote: > > > > On Sun, Feb 9, 2014 at 1:32 PM, Aryeh Friedman wrote: > >> >> >> >> On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: >> >>> Hi, >>> >>> I posted some rc.d scripts that I am using to boot a BHyve VM >>> and send the output to a serial console using the /dev/nmdm >>> driver: >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html >>> >>> It works quite well. There is some things I would like to improve, >>> and would like some advice on the best way to do it. >>> >>> (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, >>> then I do not want to automatically restart the VM in the script. >>> User should manually: service bhyvevm start >>> >>> (2) If the VM was powered down, via shutdown -p, or halt -p, >>> then in my script I do not want to restart the VM in the script. >>> User should manually: service bhyvevm start >>> >>> (3) If the VM was rebooted via "reboot" or "shutdown -r", >>> then I *do* want the script to restart the VM. >>> >>> I think if I change my start_vm.sh script to do something like: >>> >>> >>> >>> ( >>> while [ -e /dev/vmm/${VM} ]; do >>> /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s >>> 1:0,lpc >>> -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} >>> ${VM}" >>> done >>> >>> ) & >>> >>> >>> then this might cover cases (1) and (3), but what will cover >>> case (2)? >>> >>> Thanks for any advice. >>> >> >> The options you gave (which are really the only ones available) do not >> distinguish between the reason for the termination of the instance of bhyve >> pointing to /dev/vmm/XXX (it just does a normal termination). >> > > Did you play with any of these flags to bhyvectl? > > [--get-vmcs-exit-ctls] > [--get-vmcs-exit-reason] > [--get-vmcs-exit-qualification] > [--get-vmcs-exit-interruption-info] > > If I do: > bhyvectl --get-vmcs-exit-reason --vm vm1 > > I get: > vmcs_exit_reason[0] 0x000000000000001e > > If I look at: > > > http://svnweb.freebsd.org/base/head/sys/amd64/vmm/intel/vmcs.h?view=markup#l310 > > we have: > #define EXIT_REASON_INOUT 30 > You will likely need to detect the following ones also (all for different reasons that may or may not have anything to do with an issue with the VM instead of some host [OS or hardware] issue): #define EXIT_REASON_EXT_INTR 1 #define EXIT_REASON_INIT 3 #define EXIT_REASON_HLT 12 #define EXIT_REASON_CPUID 10 #define EXIT_REASON_VMLAUNCH 20 > Linux has this stuff also: > http://lxr.free-electrons.com/source/arch/x86/include/asm/vmx.h?v=3.1#L250 > > so I guess these values are defined in some Intel manual. > > > >> In my playing with this for almost a month the only solution seems to be >> put a trigger on instance shutdown via whatever method to leave a "cookie" >> file behind on the host (note I have not nor plan to do this in any of my >> own work). >> > > Yes, I can see why this might need to be done. I might need to do that > myself. However, if bhyvectl can be used to provide adequate status > information as to why the VM exited, I might be able to avoid this. > > It would be nicer though if /usr/sbin/bhyve returned > the EXIT_REASON in its status code. > > > >> >> An other question is it wise to auto-reboot regardless of reason of the >> hypervisor termination? >> > > I think the answer is "it depends". If someone > does "reboot" or "shutdown -r", I think it is reasonable to restart the > VM. If someone does "halt -p" or "shutdown -p", I think it is reasonable > to not restart the VM. For any other error condition, I think it is > reasonable to not restart the VM. > > I think that there is no single answer for all users and all applications. > In my case, I am running BHyve VM's as "headless" which > I access via the /dev/nmdm driver. If the VM reboots normally, I want it > to restart. > It seems almost any boot failure would be host side for example if there is no SSH access (which if the instance is never logged into then it is likely a host issue) then it is highly unlikely the VM is in bootable form (this is after a manual reboot of it)... an other reason (just learned the hardway) is the user uses a mismatch between backing file formats (my case using raw images with ahci-hd) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 22:41:44 2014 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 ESMTPS id 51D2224F for ; Sun, 9 Feb 2014 22:41:44 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA8A11FEF for ; Sun, 9 Feb 2014 22:41:43 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id w7so4226914lbi.35 for ; Sun, 09 Feb 2014 14:41:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8Yw6/aa3quko2w9tdqeP9PGDrI0MJHKpGBXDy97osB4=; b=hNacBQCnj1/ndgnCAlqwOUOprvbTPfqozKH74z49VO/UXfNu3lkcRGmAkiHqlM8QX9 fQ4CfmTS4aXhtLHqjtnjO/8VpBrFy4HbKSKgMIAhTr6VnRybpRNPl0fRGWnI0YrShSLe jFkiGdn65aFupCQZG0wWQLA1+GU2Nqcvj1a2fljOvZ3cvnV+NOb2ZBPGPC/6dhfO4s8Q SaJIuoHUdYLnjwb8gfPPKcuud+D5kGSHtn1Um3ARHeaIrpN+9p+H92TrtRfs/BaS//r/ LHmrgG19qyFZq+CqbnKWfAeUWoo5QZUsDXK0+EXMeOxifZmO5tDBSRi/5I6wr5wzeTbb AjAw== MIME-Version: 1.0 X-Received: by 10.152.120.37 with SMTP id kz5mr15911171lab.30.1391985701877; Sun, 09 Feb 2014 14:41:41 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Sun, 9 Feb 2014 14:41:41 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 14:41:41 -0800 X-Google-Sender-Auth: PYoq4SFTK7iITA800uSmn77fyhc Message-ID: Subject: Re: RFC: hyperv disk i/o performance vs. data integrity From: Craig Rodrigues To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 09 Feb 2014 22:41:44 -0000 On Sat, Feb 1, 2014 at 9:24 PM, Aryeh Friedman wrote: > > Craig Rodrigues and the FreeNAS team have done a fantastic job already (I > have not personally tried FreeNAS yet but I have heard nothing but good > things about it) and making it so it can run on a bhyve instance. Thanks for those kind words. At the 2013 FreeBSD Vendor Summit, I gave this presentation: http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/ which shows how I am using BHyve to test FreeNAS. BHyve is rough around the edges, but it works really well for testing. BHyve is improving every day. I encourage anyone in the BHyve community to download a FreeNAS 9.2.1 ISO and test booting it inside a BHyve VM. See this link for download details: http://forums.freenas.org/threads/announcing-freenas-9-2-1-release.18278/ Booting the FreeNAS ISO inside BHyve is a great way to test out BHyve (and FreeNAS). If you find FreeNAS-specific problems you can report them at: http://www.freenas.org/support/ That web page has links to our bugtracker and online forums. That way there is no need to clutter this mailing list with FreeNAS-specific stuff. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 00:03:42 2014 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 ESMTPS id E5BB4AD1; Mon, 10 Feb 2014 00:03:42 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CBF31602; Mon, 10 Feb 2014 00:03:42 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id k4so8636192qaq.15 for ; Sun, 09 Feb 2014 16:03:41 -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=zNhlXhLdz98Ljbw5Juny0AUjlKdR6nqBbGOXAi6VYbc=; b=T2kwib9IaQl2sNjRRAs+1icxKDF1RWk1xQUDnDTOT7Wjns/16klcNyrIPowiqn7QQ8 yFRjUpWXwhdclsRwVuz+nR9r8a524lgvOQzw9Gr1FOB8KTGF0jipuRgF+Bx7E8v3ecXI 87eW7XXh/lSB14WK94MvNUO1jKg/qx63vZGtqW8hcXN6+fFVlb9aMHC8GYmdIbw3azp4 AzXMd9ROOVLKYrx7gMe+5aG/4cMYY2HoUe0nWvNQ7zzlGHxtPsza2pOZK9xmAYhjJsLv 8m5OM+lm/9H0WtN7BQe8KKS0HBc02nwjuMksvsdQyQcDi3AocLgNA7WrMwq2fVmIj9bS jugw== MIME-Version: 1.0 X-Received: by 10.224.132.65 with SMTP id a1mr43406124qat.69.1391990621437; Sun, 09 Feb 2014 16:03:41 -0800 (PST) Received: by 10.140.87.71 with HTTP; Sun, 9 Feb 2014 16:03:41 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:03:41 -0800 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Neel Natu To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 00:03:43 -0000 Hi Craig, On Sun, Feb 9, 2014 at 1:11 PM, Craig Rodrigues wrote: > Hi, > > I posted some rc.d scripts that I am using to boot a BHyve VM > and send the output to a serial console using the /dev/nmdm > driver: > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html > > It works quite well. There is some things I would like to improve, > and would like some advice on the best way to do it. > > (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, > then I do not want to automatically restart the VM in the script. > User should manually: service bhyvevm start > > (2) If the VM was powered down, via shutdown -p, or halt -p, > then in my script I do not want to restart the VM in the script. > User should manually: service bhyvevm start > > (3) If the VM was rebooted via "reboot" or "shutdown -r", > then I *do* want the script to restart the VM. > > I think if I change my start_vm.sh script to do something like: > > > > ( > while [ -e /dev/vmm/${VM} ]; do > /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc > -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" > done > > ) & > > > then this might cover cases (1) and (3), but what will cover > case (2)? The exit code of the bhyve process will be 0 if it exited because the guest rebooted and will be non-zero if the guest did an acpi poweroff. You can use that to distinguish between cases (2) and (3). Having said that there are error conditions for which bhyve exits with a non-zero exit code. So, we'll need to explicitly define an exit code to distinguish between an acpi poweroff and these error conditions. best Neel > > Thanks for any advice. > > -- > Craig > _______________________________________________ > 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 Mon Feb 10 00:10:13 2014 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 ESMTPS id 57587B54; Mon, 10 Feb 2014 00:10:13 +0000 (UTC) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 01F721627; Mon, 10 Feb 2014 00:10:12 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id m20so9413243qcx.37 for ; Sun, 09 Feb 2014 16:10:12 -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=2yjSCy+KJEC0KzIry5DZusEf6zgJTdZUkYvt6w9ivNQ=; b=g8140UHppFgB/3B0i5+0n7U+DdoKlNvOL/KyP0jPKeLzDtlYm0h2HNmSNZupsMeAoV GKvQ4chW49qrtb8dOU8nsyke38UFzZ56lN23wEmziSLWzObKrvkfeDNWGnby5sIqotJV TAG/PRChPOjeqD55PgUyoebfikd3CPpKnk+iErKlU4rJAzr4HK2qa7CMgxTOlJvD+Ltk 9DybisSpQRw9XGxLpotjgl+C5EsQaibxIUUCRrcan5efsPVsX/6PWGi1UVj0iw92DzkP Ljzum9aLVzuEnj8Hwp8KJCpPJyHMJXfZeEX0SY/qdDCP6wr5hF1nDGHhE3sNau3YC1gZ U8/g== MIME-Version: 1.0 X-Received: by 10.224.113.204 with SMTP id b12mr42607341qaq.35.1391991012226; Sun, 09 Feb 2014 16:10:12 -0800 (PST) Received: by 10.140.87.71 with HTTP; Sun, 9 Feb 2014 16:10:12 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:10:12 -0800 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Neel Natu To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 00:10:13 -0000 Hi Craig, On Sun, Feb 9, 2014 at 2:18 PM, Craig Rodrigues wrote: > On Sun, Feb 9, 2014 at 1:32 PM, Aryeh Friedman wrote: > >> >> >> >> On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: >> >>> Hi, >>> >>> I posted some rc.d scripts that I am using to boot a BHyve VM >>> and send the output to a serial console using the /dev/nmdm >>> driver: >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html >>> >>> It works quite well. There is some things I would like to improve, >>> and would like some advice on the best way to do it. >>> >>> (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, >>> then I do not want to automatically restart the VM in the script. >>> User should manually: service bhyvevm start >>> >>> (2) If the VM was powered down, via shutdown -p, or halt -p, >>> then in my script I do not want to restart the VM in the script. >>> User should manually: service bhyvevm start >>> >>> (3) If the VM was rebooted via "reboot" or "shutdown -r", >>> then I *do* want the script to restart the VM. >>> >>> I think if I change my start_vm.sh script to do something like: >>> >>> >>> >>> ( >>> while [ -e /dev/vmm/${VM} ]; do >>> /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc >>> -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" >>> done >>> >>> ) & >>> >>> >>> then this might cover cases (1) and (3), but what will cover >>> case (2)? >>> >>> Thanks for any advice. >>> >> >> The options you gave (which are really the only ones available) do not >> distinguish between the reason for the termination of the instance of bhyve >> pointing to /dev/vmm/XXX (it just does a normal termination). >> > > Did you play with any of these flags to bhyvectl? > > [--get-vmcs-exit-ctls] > [--get-vmcs-exit-reason] > [--get-vmcs-exit-qualification] > [--get-vmcs-exit-interruption-info] > > If I do: > bhyvectl --get-vmcs-exit-reason --vm vm1 > > I get: > vmcs_exit_reason[0] 0x000000000000001e > > If I look at: > > http://svnweb.freebsd.org/base/head/sys/amd64/vmm/intel/vmcs.h?view=markup#l310 > > we have: > #define EXIT_REASON_INOUT 30 > > Linux has this stuff also: > http://lxr.free-electrons.com/source/arch/x86/include/asm/vmx.h?v=3.1#L250 > > so I guess these values are defined in some Intel manual. > Yes, but this an entirely different thing. The VMCS exit reason is used to inform the hypervisor what condition caused the guest to stop executing - e.g. a nested page fault. Please don't use it to infer whether the guest wanted to reboot or poweroff :-) > > >> In my playing with this for almost a month the only solution seems to be >> put a trigger on instance shutdown via whatever method to leave a "cookie" >> file behind on the host (note I have not nor plan to do this in any of my >> own work). >> > > Yes, I can see why this might need to be done. I might need to do that > myself. However, if bhyvectl can be used to provide adequate status > information as to why the VM exited, I might be able to avoid this. > > It would be nicer though if /usr/sbin/bhyve returned > the EXIT_REASON in its status code. > Agreed - see my reply to your original post. best Neel > > >> >> An other question is it wise to auto-reboot regardless of reason of the >> hypervisor termination? >> > > I think the answer is "it depends". If someone > does "reboot" or "shutdown -r", I think it is reasonable to restart the > VM. If someone does "halt -p" or "shutdown -p", I think it is reasonable > to not restart the VM. For any other error condition, I think it is > reasonable to not restart the VM. > > I think that there is no single answer for all users and all applications. > In my case, I am running BHyve VM's as "headless" which > I access via the /dev/nmdm driver. If the VM reboots normally, I want it > to restart. > > -- > Craig > _______________________________________________ > 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 Mon Feb 10 00:14:16 2014 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 ESMTPS id A1AC5DC7; Mon, 10 Feb 2014 00:14:16 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 48E48169A; Mon, 10 Feb 2014 00:14:16 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id j15so8473185qaq.25 for ; Sun, 09 Feb 2014 16:14:15 -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=M5z3qiNmfa0Ckeek4AX7faVghLlc8Z2+5Voz6Jezmgc=; b=YVeNpEwusnKGtZdeBQo9PjM+KWjPiIMJxobGgp931Yz/xk+R6I/ttAEicn+ijGwd8k 9SY//i7E+RRXrwELcMJQbmFUVRt58Qzkn4EO8lc/B4bu19v092uwid11ANEabzESPvn/ 3HLaSSIdg+zyTKPyACndLHCh9IFUkE+JveYZlVARRAYqB9opNSH6PfCcLeLGb0BLHd8j Vvx6GE68gwc+apt6dHYKchKY0BHGwvXDoHqhUX5g+AyvUrSebAkuA7i06EC9azkwdFf7 ahLcOZudBskyqwdVVktXX9QXTPLla0IgjWHuMwJW3W9Ww+4FdhRrlAM3tFvxWOO5ep4D GkEA== MIME-Version: 1.0 X-Received: by 10.224.113.204 with SMTP id b12mr42626776qaq.35.1391991255357; Sun, 09 Feb 2014 16:14:15 -0800 (PST) Received: by 10.140.87.71 with HTTP; Sun, 9 Feb 2014 16:14:15 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:14:15 -0800 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Neel Natu To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 00:14:16 -0000 Hi Aryeh, On Sun, Feb 9, 2014 at 2:34 PM, Aryeh Friedman wrote: > On Sun, Feb 9, 2014 at 5:18 PM, Craig Rodrigues wrote: > >> >> >> >> On Sun, Feb 9, 2014 at 1:32 PM, Aryeh Friedman wrote: >> >>> >>> >>> >>> On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: >>> >>>> Hi, >>>> >>>> I posted some rc.d scripts that I am using to boot a BHyve VM >>>> and send the output to a serial console using the /dev/nmdm >>>> driver: >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html >>>> >>>> It works quite well. There is some things I would like to improve, >>>> and would like some advice on the best way to do it. >>>> >>>> (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, >>>> then I do not want to automatically restart the VM in the script. >>>> User should manually: service bhyvevm start >>>> >>>> (2) If the VM was powered down, via shutdown -p, or halt -p, >>>> then in my script I do not want to restart the VM in the script. >>>> User should manually: service bhyvevm start >>>> >>>> (3) If the VM was rebooted via "reboot" or "shutdown -r", >>>> then I *do* want the script to restart the VM. >>>> >>>> I think if I change my start_vm.sh script to do something like: >>>> >>>> >>>> >>>> ( >>>> while [ -e /dev/vmm/${VM} ]; do >>>> /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s >>>> 1:0,lpc >>>> -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} >>>> ${VM}" >>>> done >>>> >>>> ) & >>>> >>>> >>>> then this might cover cases (1) and (3), but what will cover >>>> case (2)? >>>> >>>> Thanks for any advice. >>>> >>> >>> The options you gave (which are really the only ones available) do not >>> distinguish between the reason for the termination of the instance of bhyve >>> pointing to /dev/vmm/XXX (it just does a normal termination). >>> >> >> Did you play with any of these flags to bhyvectl? >> >> [--get-vmcs-exit-ctls] >> [--get-vmcs-exit-reason] >> [--get-vmcs-exit-qualification] >> [--get-vmcs-exit-interruption-info] >> >> If I do: >> bhyvectl --get-vmcs-exit-reason --vm vm1 >> >> I get: >> vmcs_exit_reason[0] 0x000000000000001e >> >> If I look at: >> >> >> http://svnweb.freebsd.org/base/head/sys/amd64/vmm/intel/vmcs.h?view=markup#l310 >> >> we have: >> #define EXIT_REASON_INOUT 30 >> > > You will likely need to detect the following ones also (all for different > reasons that may or may not have anything to do with an issue with the VM > instead of some host [OS or hardware] issue): > > #define EXIT_REASON_EXT_INTR 1 > #define EXIT_REASON_INIT 3 > #define EXIT_REASON_HLT 12 > #define EXIT_REASON_CPUID 10 > #define EXIT_REASON_VMLAUNCH 20 > These are VMCS exit reasons that have nothing to do whatsoever with the guest wanting to reboot or power itself off. best Neel > >> Linux has this stuff also: >> http://lxr.free-electrons.com/source/arch/x86/include/asm/vmx.h?v=3.1#L250 >> >> so I guess these values are defined in some Intel manual. >> >> >> >>> In my playing with this for almost a month the only solution seems to be >>> put a trigger on instance shutdown via whatever method to leave a "cookie" >>> file behind on the host (note I have not nor plan to do this in any of my >>> own work). >>> >> >> Yes, I can see why this might need to be done. I might need to do that >> myself. However, if bhyvectl can be used to provide adequate status >> information as to why the VM exited, I might be able to avoid this. >> >> It would be nicer though if /usr/sbin/bhyve returned >> the EXIT_REASON in its status code. >> >> >> >>> >>> An other question is it wise to auto-reboot regardless of reason of the >>> hypervisor termination? >>> >> >> I think the answer is "it depends". If someone >> does "reboot" or "shutdown -r", I think it is reasonable to restart the >> VM. If someone does "halt -p" or "shutdown -p", I think it is reasonable >> to not restart the VM. For any other error condition, I think it is >> reasonable to not restart the VM. >> >> I think that there is no single answer for all users and all applications. >> In my case, I am running BHyve VM's as "headless" which >> I access via the /dev/nmdm driver. If the VM reboots normally, I want it >> to restart. >> > > It seems almost any boot failure would be host side for example if there is > no SSH access (which if the instance is never logged into then it is likely > a host issue) then it is highly unlikely the VM is in bootable form (this > is after a manual reboot of it)... an other reason (just learned the > hardway) is the user uses a mismatch between backing file formats (my case > using raw images with ahci-hd) > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > 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 Mon Feb 10 01:18:03 2014 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 ESMTPS id 7A16AE4B for ; Mon, 10 Feb 2014 01:18:03 +0000 (UTC) Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F2CED1AA4 for ; Mon, 10 Feb 2014 01:18:02 +0000 (UTC) Received: by mail-qa0-f51.google.com with SMTP id f11so8564924qae.24 for ; Sun, 09 Feb 2014 17:18: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=vUu0ltiG3gpL5+l1rkhMNLRlrHIrMjTj7zKP6A1Hj0k=; b=GMQfxyB0esjgGfz/9PK26s2DqvtcQcZkpHFWiOHJ++mhyVj4wIrAIbwQnxOA01IwTJ r4V78DLzlOtPxmnBxIC6QCRLMd+w4fCqvF3hY2NO8w/MMDuxBpBXeyyLXNvabviNSKDQ Eyavn5F3kXepOqV/um88STm7WvS+djt8qExoceJIr3rKwiJCNhlTqx4CKqK0jc9IdfdN eTAd2vqhW3eDAoviTAt0lD1XI/Z7vkfKHwlg8eHky/3xwCVg6OVGd3ZGx385gjLP4HRc gLtloc+9fGgo/6COI31zpgE+gkJzZf1DytKou8PTwO9CbscDtyRE5BGNEGn1F0dvAGjg yeLw== MIME-Version: 1.0 X-Received: by 10.224.166.137 with SMTP id m9mr10222560qay.81.1391995082146; Sun, 09 Feb 2014 17:18:02 -0800 (PST) Received: by 10.140.87.71 with HTTP; Sun, 9 Feb 2014 17:18:02 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 17:18:02 -0800 Message-ID: Subject: Re: Networking issues From: Neel Natu To: ickler@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 01:18:03 -0000 Hi Sebastian, On Fri, Feb 7, 2014 at 12:03 PM, wrote: > Hello virtualization-lovers, > > I am very dedicated to FreeBSD since 7.2 and welcome the new bhyve > hypervisor. :) > > So I set everything up, launched the guest and set up the network. The > problem now is, I can reach the host IP, but not the default gateway. Did I > forget to set something up? > The system is a hosted root box. > > My current setup (i changed the IP's except the last octet): > ---snip--- > host: > # ifconfig > re0: flags=8943 metric 0 > mtu 1500 > > options=82099 > ether 30:85:a9:ed:01:22 > inet 192.168.0.137 netmask 0xffffffe0 broadcast 192.168.0.159 > inet6 fe80::3285:a9ff:feed:122%re0 prefixlen 64 scopeid 0x1 > nd6 options=29 > media: Ethernet autoselect (1000baseT ) > status: active > bridge0: flags=8843 metric 0 mtu > 1500 > ether 02:0d:2a:df:6e:00 > nd6 options=1 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap0 flags=143 > ifmaxaddr 0 port 4 priority 128 path cost 2000000 > member: re0 flags=143 > ifmaxaddr 0 port 1 priority 128 path cost 20000 > tap0: flags=8943 metric 0 > mtu 1500 > options=80000 > ether 00:bd:fe:79:0e:00 > nd6 options=29 > media: Ethernet autoselect > status: active > Opened by PID 16910 > > # netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 5.9.157.129 UGS 0 293321 re0 > 192.168.0.128/27 link#1 U 0 30 re0 > 192.168.0.137 link#1 UHS 0 0 lo0 > 127.0.0.1 link#2 UH 0 1606 lo0 > > ---snip--- > > ---snip--- > guest: > # ifconfig > vtnet0: flags=8943 metric 0 > mtu 1500 > options=80028 > ether 00:a0:98:18:c4:69 > inet 192.168.0.154 netmask 0xffffffe0 broadcast 192.168.0.159 > inet6 fe80::2a0:98ff:fe18:c469%vtnet0 prefixlen 64 scopeid 0x1 > nd6 options=29 > media: Ethernet 10Gbase-T > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > > # netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 5.9.157.129 UGS 0 418 vtnet0 > 192.168.0.128/27 link#1 U 0 24 vtnet0 > 192.168.0.154 link#1 UHS 0 0 lo0 > 127.0.0.1 link#2 UH 0 24 lo0 > > ---snip--- > > ping host -> guest works > > # ping 192.168.0.154 > PING 192.168.0.154 (192.168.0.154): 56 data bytes > 64 bytes from 192.168.0.154: icmp_seq=0 ttl=64 time=0.083 ms > 64 bytes from 192.168.0.154: icmp_seq=1 ttl=64 time=0.094 ms > > > ping guest -> host works > > # ping 192.168.0.137 > PING 192.168.0.137 (192.168.0.137): 56 data bytes > 64 bytes from 192.168.0.137: icmp_seq=0 ttl=64 time=0.398 ms > 64 bytes from 192.168.0.137: icmp_seq=1 ttl=64 time=0.069 ms > > > ping 173.194.70.102 (google.com) from guest - doesn't work... > # ping 173.194.70.102 > PING 173.194.70.102 (173.194.70.102): 56 data bytes > --- 173.194.70.102 ping statistics --- > 3 packets transmitted, 0 packets received, 100.0% packet loss > > tcpdump listening on the host: > > # tcpdump -N -vv -i bridge0 > tcpdump: WARNING: bridge0: no IPv4 address assigned > tcpdump: listening on bridge0, link-type EN10MB (Ethernet), capture size > 65535 bytes > 19:58:19.139767 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has static > tell 192.168.0.137, length 46 > > ---^ same on tap0 > > > What's wrong with that setup? Did I forget to set a proper route? Or is it > a MAC address issue? > Can you ping the default router from your guest? Also, I was bit puzzled that the default router is 5.9.157.129 on a 192.168.0.128/27 subnet. Should I read it as 192.168.0.129 instead? best Neel > Thanks in advance, > > Sebastian > _______________________________________________ > 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 Mon Feb 10 06:36:15 2014 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 ESMTPS id 898C44C3 for ; Mon, 10 Feb 2014 06:36:15 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57BCE1911 for ; Mon, 10 Feb 2014 06:36:13 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so5813542pab.38 for ; Sun, 09 Feb 2014 22:36:13 -0800 (PST) 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:references:in-reply-to:content-type :content-transfer-encoding; bh=EbL7zJZfJus2OIU/TJO2xvCz0s4td4VVFCVfqyFjI3A=; b=hEAlZrg36J2hGEsoXCKPKKRSthC/8DaKOh+BeyXSMf7zHVqhlBxvRyy1QmmV0m1vPf or+B9lwW2jp+mbGZQqZBjGilC6Ck2Ka3Ik6NxGql2wP0XegJufZrdS+ueVPccMzxTeiL rRMvC+2LrfnvQF72yJEbb0tBk+OvsViKa/N8+jxTojvIJYt0pNTizpV35ZKwsNq2IUAi 9AFpglXRSxf8k0OsB63jqBVi2JkYkC1eTAh89QKgzdMqWEwN/qdM8wVO/1NUbQxYsPib ajvizmKhkO2iXmF9p49i5i99Xszhwvdun5JYizGMq/ZxHzgntQDnWKONEKh7Qfwn2fNG kD+A== X-Gm-Message-State: ALoCoQneNPxKGk4u8zgqUuvbxrx5zWHnhe5SMhUZkMPVtC0GsyvMhLXBpw6hvqUcTvLK8AWkekA7 X-Received: by 10.69.0.10 with SMTP id au10mr36054117pbd.48.1392014173492; Sun, 09 Feb 2014 22:36:13 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id qf7sm102776487pac.14.2014.02.09.22.36.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Feb 2014 22:36:12 -0800 (PST) Message-ID: <52F8735E.8020701@callfortesting.org> Date: Sun, 09 Feb 2014 22:36:14 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Willem Jan Withagen , "freebsd-virtualization@freebsd.org" Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> In-Reply-To: <52F7C9FC.5070409@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 06:36:15 -0000 On 2/9/14 10:33 AM, Willem Jan Withagen wrote: > Are there any (near future) plans to merge this with the regular stable > branch? It just missed 10.0-RELEASE. :( There was a technical issue at the time and there are some performance patches on their way. Please do test! Michael From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 06:41:43 2014 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 ESMTPS id B76F55C2 for ; Mon, 10 Feb 2014 06:41:43 +0000 (UTC) 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 236EB198B for ; Mon, 10 Feb 2014 06:41:42 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id s1A6fSdR064662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 9 Feb 2014 22:41:32 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52F87493.7070607@freebsd.org> Date: Mon, 10 Feb 2014 14:41:23 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Olivier_Cochard-Labb=E9?= Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: FreeBSD virtualization mailing list X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 06:41:43 -0000 On 2/8/14, 2:35 AM, Olivier Cochard-Labbé wrote: > Hi, > > just a report of my migration to bhyve. > > I was using VirtualBox for generate full-meshed network lab of multiple VM > (essentially nanobsd based) and have migrated my script to bhyve. > > My original script is resumed to this kind of usage: > ./lab-script.sh -i FreeBSD-image-disk -n number-of-vm -l number-of-LAN > if you are doing network simulation why not just use vimage jails and/or the immunes framework? much easier on the resources.. From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 11:06:57 2014 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 ESMTPS id 9FD191A0 for ; Mon, 10 Feb 2014 11:06:57 +0000 (UTC) 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 88C301FF5 for ; Mon, 10 Feb 2014 11:06:57 +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 s1AB6v1p080244 for ; Mon, 10 Feb 2014 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AB6veo080242 for freebsd-virtualization@FreeBSD.org; Mon, 10 Feb 2014 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Feb 2014 11:06:57 GMT Message-Id: <201402101106.s1AB6veo080242@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.17 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, 10 Feb 2014 11:06:57 -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 Feb 10 15:14:26 2014 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 ESMTPS id 84AF8DB7 for ; Mon, 10 Feb 2014 15:14:26 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3FD8516D9 for ; Mon, 10 Feb 2014 15:14:21 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 42CC81534D1; Mon, 10 Feb 2014 16:14:17 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tE8GrEsahQbd; Mon, 10 Feb 2014 16:14:15 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:15f5:cdaf:d398:e69e] (unknown [IPv6:2001:4cb8:3:1:15f5:cdaf:d398:e69e]) by smtp.digiware.nl (Postfix) with ESMTP id 863F1153448; Mon, 10 Feb 2014 16:14:15 +0100 (CET) Message-ID: <52F8ECC2.2060805@digiware.nl> Date: Mon, 10 Feb 2014 16:14:10 +0100 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Michael Dexter , "freebsd-virtualization@freebsd.org" Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> In-Reply-To: <52F8735E.8020701@callfortesting.org> 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.17 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, 10 Feb 2014 15:14:26 -0000 On 2014-02-10 7:36, Michael Dexter wrote: > On 2/9/14 10:33 AM, Willem Jan Withagen wrote: >> Are there any (near future) plans to merge this with the regular stable >> branch? > > It just missed 10.0-RELEASE. :( > > There was a technical issue at the time and there are some performance > patches on their way. Please do test! I usually prefer to build my onw. So I tried that from a both basic 10-stable as well as the svn-url I got from Peter some time ago. But - building 10-stable did not give the amd svm stuff - building the previous svn-url on my 10-stable bombs out due to some missing net/.... files. Need to rerun, to get the exact error. But I'll download and try the pre-cooked iso's. And maybe it is just a matter of just loading the "other" kernel-module?? --WjW From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 15:39:56 2014 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 ESMTPS id B7E7A81E for ; Mon, 10 Feb 2014 15:39:56 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7639D18DD for ; Mon, 10 Feb 2014 15:39:56 +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 294BC11E4D; Tue, 11 Feb 2014 01:39:48 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRS30938 (AUTH peterg@ptree32.com.au); Tue, 11 Feb 2014 01:39:47 +1000 Message-ID: <52F8F2C1.9030505@freebsd.org> Date: Mon, 10 Feb 2014 07:39:45 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: are ahci-hd images the same as raw under bhyve 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.17 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, 10 Feb 2014 15:39:56 -0000 Hi Aryeh, > When I was playing with bhyve-grub a while ago I noticed there seemed to be > little difference between ahci-hd and "raw" (if no format it given besides > just naming a md file). Is it safe to treat the two formats > interchangeably in bhyve (and bhyve-grub)? Can I do this to the point of > mixing and matching them on instances created with both (i.e. boot with > ahci on a raw image and vice versa)? Not quite sure what you mean here: ahci-hd is a device emulation (as are ahci-cd and virtio-blk). The backend for these is either a disk image on a filesystem or a block device. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 15:46:58 2014 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 ESMTPS id E7D9EBAC for ; Mon, 10 Feb 2014 15:46:58 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id A452319A1 for ; Mon, 10 Feb 2014 15:46:58 +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 20C7012367; Tue, 11 Feb 2014 01:46:57 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRS30987 (AUTH peterg@ptree32.com.au); Tue, 11 Feb 2014 01:46:56 +1000 Message-ID: <52F8F46E.4060704@freebsd.org> Date: Mon, 10 Feb 2014 07:46:54 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Olivier_Cochard-Labb=E9?= Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve References: <52F5363D.8040102@freebsd.org> 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.17 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, 10 Feb 2014 15:46:59 -0000 Hi Olivier, > If you create a sparse file for the bhyve raw disk (e.g. with > truncate -s), du will show the actual blocks used rather than the > total size. > > > But can I truncate an already existing image disk (downloaded nanobsd > image as example) ? Not without some processing. One way to do it might be a downloaded -> qcow2 -> raw using qemu-img, which will create sparse files if possible. > There is an em(4) emulation slowly being worked on. It should also > be possible to add altq functionality to FreeBSD's virtio net driver. > > > Adding altq(4) to vtnet(4) should be a better idea. As bryanv@ mentioned, it's there with a conditional flag. > For internal-only networks, there will most likely be a user-space > ethernet switch (ala VDE) that bhyve network interfaces can be > pointed at. > > > Great: Why not the high-perf netmap VALE switch ? That's being worked on, but I think that requires root access. > Because with a dummy TCP iperf bench between bhyve guests report only > 254 Mbits/sec. Hmmm, I've seen better numbers than that. What's your host h/w, guest config and iperf params ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 01:19:04 2014 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 ESMTPS id 0B4C350E for ; Tue, 11 Feb 2014 01:19:04 +0000 (UTC) Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CB14F1FCF for ; Tue, 11 Feb 2014 01:19:02 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id y10so6832597pdj.32 for ; Mon, 10 Feb 2014 17:19:02 -0800 (PST) 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:references:in-reply-to:content-type :content-transfer-encoding; bh=XjUdtPg7Qe/QoXxKfy09DfOv7IM1HpkYw3wyBdbYURk=; b=l26iJTkn4EayejTQVYlUlMVXDKNisJJHZ7BtQHcJF1RrwKvRfNEgpryghFSZ6yFjen MwKymP0E+mZMUm3pSwXq6yUbz1Zo9mW5mNMGIRUnZiCUD/nUiCEqdX+DQpyctTE6ZRKj vywerAU0tiJ2nBDZgTYA0pdKDAtOSc4iXrJJM9Lr1GyOEZwm4ZzjOWFpqbaxZvbSTjrT qBgxn75C9pCYhUOnVMs6NgXw5BfqiynXCuvpp1AG/skcjmWQyOsGAp2DqkB3eD3trlVc 2C48rcIxbpmemNYkvDZrkmWFz3l8nZ8gcJiVtfvCPG+xyg9Ioj4g/t84FdMDhp6U+/Lr K2/Q== X-Gm-Message-State: ALoCoQkWiHYvdvT7UPs7HWqZt1DVOxf7xobrEurZeimS8knSHVhTpxP5+VUOC8utBlCAFsYcF3Se X-Received: by 10.67.8.102 with SMTP id dj6mr29065418pad.10.1392081542484; Mon, 10 Feb 2014 17:19:02 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id x5sm46828441pbw.26.2014.02.10.17.19.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Feb 2014 17:19:01 -0800 (PST) Message-ID: <52F97A84.90308@callfortesting.org> Date: Mon, 10 Feb 2014 17:19:00 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Willem Jan Withagen , "freebsd-virtualization@freebsd.org" Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> In-Reply-To: <52F8ECC2.2060805@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 01:19:04 -0000 Willem, On 2/10/14 7:14 AM, Willem Jan Withagen wrote: > I usually prefer to build my onw. So I tried that from a both basic > 10-stable as well as the svn-url I got from Peter some time ago. But > - building 10-stable did not give the amd svm stuff > - building the previous svn-url on my 10-stable bombs out due to some > missing net/.... files. Need to rerun, to get the exact error. The snapshot was built from the SVM projects branch: http://svnweb.freebsd.org/base/projects/bhyve_svm/ I opted to build world with -j4 and kernel on -j2 on a dual-core system as per Glen Barber's suggestion of how he is building the official releases. Michael From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 01:50:54 2014 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 ESMTPS id 0E1E5AF5 for ; Tue, 11 Feb 2014 01:50:54 +0000 (UTC) Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1FB71289 for ; Tue, 11 Feb 2014 01:50:53 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id up15so7049510pbc.14 for ; Mon, 10 Feb 2014 17:50:53 -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=4e712EnKv+KmZaEK8ik404FrSrvUXWZTveLvC2ggvhQ=; b=xRABJv3FzLgknTwHsWQwtxrmy3VRlGsbda5kPgJSWqWIo/PxZQsfwXA+uUYa0ZI+yb xXphzTTgr15I19S9iosEGLfOA0lIpPZIbURnA5HpNK8r32kUvwKxd6cjP8rjUd/7c0xR e6GaYpySAKiUaVuJTB+if86hvuudDwFp2WJcxPEx7zfd4dX3tKzKmAPHqfP4PkQwqV83 GsgoFdmixWbnvbqXypHBDJ0QvkAOpxeeM1LT51VoXXYC+LkEkb7PrR9qG2afiFiVsy8Y QbeE1aRJSYG9cUdblUfOD34zUlFtYhkiYM+925krVdrLbkgptdVjIOvww64U/1B5JhV1 1JzQ== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr40970145pbc.42.1392083453329; Mon, 10 Feb 2014 17:50:53 -0800 (PST) Received: by 10.68.155.38 with HTTP; Mon, 10 Feb 2014 17:50:53 -0800 (PST) In-Reply-To: <52F97A84.90308@callfortesting.org> References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> Date: Mon, 10 Feb 2014 20:50:53 -0500 Message-ID: Subject: Re: CFT: bhyve AMD snapshot From: Aryeh Friedman To: Michael Dexter Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 01:50:54 -0000 On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter wrote: > > Willem, > > On 2/10/14 7:14 AM, Willem Jan Withagen wrote: > > I usually prefer to build my onw. So I tried that from a both basic > > 10-stable as well as the svn-url I got from Peter some time ago. But > > - building 10-stable did not give the amd svm stuff > > - building the previous svn-url on my 10-stable bombs out due to some > > missing net/.... files. Need to rerun, to get the exact error. > > The snapshot was built from the SVM projects branch: > > http://svnweb.freebsd.org/base/projects/bhyve_svm/ > > I opted to build world with -j4 and kernel on -j2 on a dual-core system > as per Glen Barber's suggestion of how he is building the official > releases. > > Attempting to install this right now will let you know how it goes. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 04:35:46 2014 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 ESMTPS id 3FA9A60D for ; Tue, 11 Feb 2014 04:35:46 +0000 (UTC) Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 103CC12C8 for ; Tue, 11 Feb 2014 04:35:46 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id un15so7202505pbc.32 for ; Mon, 10 Feb 2014 20:35:45 -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=9BDN6/dxnAyowx16Quaj7saiJ3c0ochuCd6glSUGIns=; b=kNArtjBOksjcXvyhFqaT9QaCaE8Ge9yGI6iXi0ThQcyk/mX7Q60GxGsDkssiSXT6OS I4j8LI1P4+pOMlSEVGcd/3akKSI9M9JM8T1mMxdQpKVmbaBORIDNA3bmWaJKMArLR4xk bbYk84A/HuTtAvX8B0ShfFvpS/J1Bvxlf04E/xl2obbRw4PYpy6syErW+wEvv9SUb9sa OhsKOdzD2omc5e8hLh0VhKLuWarWUB8Dr7rzCh2dlj6sc+FSeQfif3NLZQS/ItmSpHA9 WvD651XQJr06YSmXQrdfGKTWQlOslEHJDTtOODey4gnguGPLwPy9N2eHGZxn96uunlKm SLPQ== MIME-Version: 1.0 X-Received: by 10.68.139.73 with SMTP id qw9mr41411343pbb.121.1392093345465; Mon, 10 Feb 2014 20:35:45 -0800 (PST) Received: by 10.68.155.38 with HTTP; Mon, 10 Feb 2014 20:35:45 -0800 (PST) In-Reply-To: References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> Date: Mon, 10 Feb 2014 23:35:45 -0500 Message-ID: Subject: Re: CFT: bhyve AMD snapshot From: Aryeh Friedman To: Michael Dexter Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 04:35:46 -0000 On Mon, Feb 10, 2014 at 8:50 PM, Aryeh Friedman wrote: > > > > On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter > wrote: > >> >> Willem, >> >> On 2/10/14 7:14 AM, Willem Jan Withagen wrote: >> > I usually prefer to build my onw. So I tried that from a both basic >> > 10-stable as well as the svn-url I got from Peter some time ago. But >> > - building 10-stable did not give the amd svm stuff >> > - building the previous svn-url on my 10-stable bombs out due to some >> > missing net/.... files. Need to rerun, to get the exact error. >> >> The snapshot was built from the SVM projects branch: >> >> http://svnweb.freebsd.org/base/projects/bhyve_svm/ >> >> I opted to build world with -j4 and kernel on -j2 on a dual-core system >> as per Glen Barber's suggestion of how he is building the official >> releases. >> >> > Attempting to install this right now will let you know how it goes. > Still setting things up but am noticing a significant number of lock reversals on your branch in areas that have nothing to do with virtualization (like building devel/subversion) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 08:15:48 2014 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 ESMTPS id C39EF331 for ; Tue, 11 Feb 2014 08:15:48 +0000 (UTC) Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7DF7715C7 for ; Tue, 11 Feb 2014 08:15:48 +0000 (UTC) Received: by mail-pb0-f48.google.com with SMTP id rr13so7369431pbb.21 for ; Tue, 11 Feb 2014 00:15:48 -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 :content-type; bh=ULgWRbTobVQHkJJ8TtqLdRB7HeB7hQ5RL7GiMhBGCF0=; b=XgcM4ksG25jJ/zCiF/2O6M/dfBybi/nssNJNVXjH2dGrOtPSGepgp0zz2h8ao4hYJ7 cLm0nUNcGQdAdx8X2RB/8MYmy+JIOej+h8Ip6az7P9TG7GBbbIO6tI7tvme47aj5CwQh uaycvvpSnl5i4jSkeCLjbdR+CjgAXU4YYddI/cImir5nE8FT1qSzwQTEVCdsTHt1MWuX 21y21/Hxmz6iVCQjR7y+5lyvZfnoZ9ei+xLkegjsMh59i/43YiSHal/inqdFCMMlDhub aGWtM7L++uGbYmOluImB5vL/m5iH4JtbJh3nKq8iLyMJOwNhz3v3/EaEm7SV8llL7KxT UaLg== MIME-Version: 1.0 X-Received: by 10.68.230.137 with SMTP id sy9mr42758488pbc.126.1392106548066; Tue, 11 Feb 2014 00:15:48 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 11 Feb 2014 00:15:47 -0800 (PST) In-Reply-To: References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> Date: Tue, 11 Feb 2014 03:15:47 -0500 Message-ID: Subject: Re: CFT: bhyve AMD snapshot From: Aryeh Friedman To: Michael Dexter , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 08:15:48 -0000 On Tue, Feb 11, 2014 at 3:07 AM, Aryeh Friedman wrote: > It seems like the patch fails to acquire a DHCP address (or use the net in > any other way with the following which works fine on intel): > > #!/bin/sh > # > # Generated by PetiteCloud 0.2.5 > # > > truncate -s 10G /vms/pri/nq6g103n9 > ifconfig tap1 destroy > ifconfig tap1 create > ifconfig tap1 up > sleep 5 > ifconfig bridge0 addm tap1 up > > /usr/sbin/bhyveload -m 512 -d > /vms/cds/FreeBSD-10.0-RELEASE-amd64-disc1.iso t4n1ustl23 > /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s > 1,virtio-net,tap1 -s 2,virtio-blk,/vms/pri/nq6g103n9 -s > 3,ahci-cd,/vms/cds/FreeBSD-10.0-RELEASE-amd64-disc1.iso -S 31,uart,stdio > t4n1ustl23 > echo $!>/var/run/petitecloud/t4n1ustl23 > ifconfig tap1 destroy > ifconfig tap1 create > ifconfig tap1 up > sleep 5 > ifconfig bridge0 addm tap1 up > > /usr/sbin/bhyveload -m 512 -d /vms/pri/nq6g103n9 t4n1ustl23 > /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s > 1,virtio-net,tap1 -s 2,virtio-blk,/vms/pri/nq6g103n9 -S 31,uart,stdio > t4n1ustl23 > echo $!>/var/run/petitecloud/t4n1ustl23 > > Booting... Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x300f10 Family = 0x12 Model = 0x1 Stepping = 0 Features=0x783ab7f Features2=0x80a02001 AMD Features=0xe6505880<,SYSCALL,,,NX,MMX+,FFXSR,Page1GB,LM,3DNow!+,3DNow!> AMD Features2=0x37ff TSC: P-state invariant real memory = 536870912 (512 MB) avail memory = 492273664 (469 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: random device not loaded; using insecure entropy ioapic0 irqs 0-23 on motherboard kbd0 at kbdmux0 random: initialized module_register_init: MOD_LOAD (vesa, 0xffffffff80cfa5e0, 0) error 19 Fatal trap 30: reserved (unknown) fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80d1d3af stack pointer = 0x28:0xffffffff817f6b10 frame pointer = 0x28:0xffffffff817f6b40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 0 (swapper) trap number = 30 panic: reserved (unknown) fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff808e7dd0 at kdb_backtrace+0x60 #1 0xffffffff808af8b5 at panic+0x155 #2 0xffffffff80c8e692 at trap_fatal+0x3a2 #3 0xffffffff80c8e2cf at trap+0x7bf #4 0xffffffff80c75392 at calltrap+0x8 #5 0xffffffff80d1e59e at vmbus_identify+0xe #6 0xffffffff808e02d7 at bus_generic_probe+0x77 #7 0xffffffff80c7314a at nexus_acpi_attach+0x1a #8 0xffffffff808df242 at device_attach+0x3a2 #9 0xffffffff808e07b9 at bus_generic_new_pass+0xe9 #10 0xffffffff808dd0af at bus_set_pass+0x8f #11 0xffffffff80c7472a at configure+0xa #12 0xffffffff80861238 at mi_startup+0x118 #13 0xffffffff802d3e0c at btext+0x2c Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Host: root@:/home/aryeh # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01 EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 CPU: AMD A6-3650 APU with Radeon(tm) HD Graphics (2595.33-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x300f10 Family = 0x12 Model = 0x1 Stepping = 0 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 7732641792 (7374 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 09:29:34 2014 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 ESMTPS id 0335EB27 for ; Tue, 11 Feb 2014 09:29:34 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE77C1B7D for ; Tue, 11 Feb 2014 09:29:33 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 2051E1534C4; Tue, 11 Feb 2014 10:29:25 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WaQXHgTTwcdj; Tue, 11 Feb 2014 10:29:23 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:15f5:cdaf:d398:e69e] (unknown [IPv6:2001:4cb8:3:1:15f5:cdaf:d398:e69e]) by smtp.digiware.nl (Postfix) with ESMTP id 04E191534C0; Tue, 11 Feb 2014 10:29:22 +0100 (CET) Message-ID: <52F9ED6C.3050604@digiware.nl> Date: Tue, 11 Feb 2014 10:29:16 +0100 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Michael Dexter Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> 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.17 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, 11 Feb 2014 09:29:34 -0000 > On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter > > wrote: > > > Willem, > > On 2/10/14 7:14 AM, Willem Jan Withagen wrote: > > I usually prefer to build my onw. So I tried that from a both > basic > > 10-stable as well as the svn-url I got from Peter some time > ago. But > > - building 10-stable did not give the amd svm stuff > > - building the previous svn-url on my 10-stable bombs out due > to some > > missing net/.... files. Need to rerun, to get the exact error. > > The snapshot was built from the SVM projects branch: > > http://svnweb.freebsd.org/base/projects/bhyve_svm/ > > I opted to build world with -j4 and kernel on -j2 on a dual-core > system > as per Glen Barber's suggestion of how he is building the > official releases. In my case it was a src.conf which contained WITHOUT_PF = true WITH_IPFW = true After which the buildworld breaks on building iipfw, because of missing pf files. Removing WITHOUT_PF lets me build world. --WjW From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 09:38:12 2014 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 ESMTPS id 73798E0D for ; Tue, 11 Feb 2014 09:38:12 +0000 (UTC) Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 312541C47 for ; Tue, 11 Feb 2014 09:38:11 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id f11so11202038qae.21 for ; Tue, 11 Feb 2014 01:38:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=SMSeAS8uNZ5jYRWlUqtQZ/HR9ks0R1U2lXz4WfE+Me4=; b=RU3EyNusTJqMVxU8ntGVIIhr3pJ+W6ESwndcmYrm9lM1ZTTSZwYwqVa0WY0rivM/co 7ft/MD8L1UmhcpX2IGt+MQD8T1iIcC55VO8sguRYBWOUNMb7h7wJPUQuzEguNXllOqsK KX6gS8v5uNV0a20qcDEucnzxD/7bBARcsAoDSBXM8XCCLt5IlEgMNztiJI7v5D77OZWK jxHY0jADCdxa+C0f2EQ+Jx4DB7qI5qFV30EkiNEstH1AtIxuxd8JGjS5jefIq18RANbf vlNcFja9A/TFrxu95pPxdShmA0FwMt/pRoPUxIbmXXJzUy0iX6SghUfWuk2vpoq9rzMW 97ig== X-Gm-Message-State: ALoCoQldZx0BrEslkB15RxD6YaNYLmoRhhcWR5itExrLF65waANT1/2B7yHINfdikts/3gFlXhdb MIME-Version: 1.0 X-Received: by 10.140.96.202 with SMTP id k68mr52714513qge.84.1392111490847; Tue, 11 Feb 2014 01:38:10 -0800 (PST) Received: by 10.140.80.45 with HTTP; Tue, 11 Feb 2014 01:38:10 -0800 (PST) X-Originating-IP: [2001:470:28:12b::3] Date: Tue, 11 Feb 2014 10:38:10 +0100 Message-ID: Subject: bhyve upgrade From: Andrea Brancatelli To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 09:38:12 -0000 Hello all, given that I'm not confortable with unofficial upgrades, I was wondering if, say, a 10-p1 would contain any new bhyve upgrade or should we wait for an official 10.1 ? --=20 *Andrea BrancatelliSchema 31 S.r.l. - Socio UnicoResponsabile ITROMA - FIRENZE - PALERMO ITALYTel: +39. 06.98.358.472* *Cell: +39 331.2488468Fax: +39. 055.71.880.466Societ=C3=A0 del Gruppo SC31 ITALIA* From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 09:38:21 2014 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 ESMTPS id 4EFAEE4C for ; Tue, 11 Feb 2014 09:38:21 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e: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 266B71C49 for ; Tue, 11 Feb 2014 09:38:21 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id fa1so7415166pad.14 for ; Tue, 11 Feb 2014 01:38:20 -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=R2dGgtpgliE0+m97FU8mVW2tihyOHbuohH4f7+/G0x0=; b=FiaaKccCk2rFhHx5AbnajbtRstRj+bNO9Z8QVG6uLkJSiHKDhP+QmT+CHqIqjiRKoI NJi1JOMU292akzck5tS+Yh9Yujb2hQyWDKJnKT6cX6OlkCyisnJLS+5VYd9CzcP8BIRZ W3VE41IH9PqMNTVzHL4nBWvlONUdYeT1iknrDj0Du69vxlBatiIC8pHuZlOqXDCwRYxw zSdqQfSL/mQ1CQTkfie6QYs5m/BazTxV4daTj1IkxM3wQ2lnxBUNb7xTM7uf3jIJXv/i ZiF0EbVHjUB7WCt4/OA7qB/zoe0hZJiV3w8KHqOfpZYJJrQx7Hde1Qn5DAtw36aYAII+ 4qIQ== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr43054810pbc.42.1392111500726; Tue, 11 Feb 2014 01:38:20 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 11 Feb 2014 01:38:20 -0800 (PST) Date: Tue, 11 Feb 2014 04:38:20 -0500 Message-ID: Subject: CFT: PetiteCloud 0.2.5 From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 09:38:21 -0000 Whats new: * Ability to use physical disks as backing stores * Multiple NIC's * Advanced settings -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 09:51:17 2014 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 ESMTPS id E9A3A1C6 for ; Tue, 11 Feb 2014 09:51:17 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1FAF1D71 for ; Tue, 11 Feb 2014 09:51:17 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so7472821pab.10 for ; Tue, 11 Feb 2014 01:51:17 -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=t0rvaC0be8pSigntVYbNGRA9VuUyg1TAbhBjbTOLNDk=; b=0X+ezjPPJE1tWtpqcH+zpE5+60tIVkslM32Rm1IKv2KsoxAMAy4exT6JeOc14Cd/9G EmXG2pm266YJlh4E7vAIFCTtdi2XiCUDPH2yRSgHylB0TIr10h6rUIPQlJBDXG1AOvTb f6g2WN315odvV4wm3LN8FLAWef+hjxCt4NUKCWKBFvNEWF8wpIZ2dxdiCA8zbVgA2EFC ngL9g+Vtbfab0D2WGm3NoDdYZ1xRR6XOpBhR7kJR5GXZhUD7O/YqyeCli5q9N4GrmDNs JJOZsLqxIU0AN3RTZr+/PPc8GaG1uIiqLeyL2asCBt4K3/oV3X6x7SSJdaXmkgTp6LO7 G6hg== MIME-Version: 1.0 X-Received: by 10.66.141.231 with SMTP id rr7mr30917122pab.41.1392112277464; Tue, 11 Feb 2014 01:51:17 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 11 Feb 2014 01:51:17 -0800 (PST) Date: Tue, 11 Feb 2014 04:51:17 -0500 Message-ID: Subject: reminder to PetiteCloud users From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 09:51:18 -0000 Please ask all issues related to PetiteCloud on our mailing list (on the site) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 16:54:28 2014 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 ESMTPS id 3D5BCDE8 for ; Tue, 11 Feb 2014 16:54:28 +0000 (UTC) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003: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 0000D166B for ; Tue, 11 Feb 2014 16:54:27 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id i4so9502466oah.13 for ; Tue, 11 Feb 2014 08:54:27 -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=/P2wEoT8Idg6MMmMwd6gZCnIbWnYEM2U97sdEiAIawU=; b=lFh3LjrdGE90WEaDsOVQV2Iq1c2kmUrww9IgHxiiRrznYWC7KgvkYeQtNuj7lcEy81 HSxz6cOCAKObZahKevwu7HjigENZUYtOD9CFytEuwFDqEj/feqMyouc6oV7ZN1zaUr7j rvwJosJE51W4LPFEpqiliJhOM6lMDF6NNTN1mXOl8zOhTAfNLhYjlUlesFnEkaW4xWPK 3U2SWsFgV7byxn/sBLRAnOwXwomKNQWpAmjjUoUlfgzt1fYfJtMkHhM5GG1OTuLWchV6 rkLLytppnGi6enX0F2JgEDwOed4fIBcC6AUCOFJTpc/K3wmySX+nc+WEIijjVly4hvuG iMdA== MIME-Version: 1.0 X-Received: by 10.182.131.170 with SMTP id on10mr32901397obb.2.1392137666815; Tue, 11 Feb 2014 08:54:26 -0800 (PST) Received: by 10.76.144.10 with HTTP; Tue, 11 Feb 2014 08:54:26 -0800 (PST) Date: Tue, 11 Feb 2014 17:54:26 +0100 Message-ID: Subject: Routing strangeness on 9.2 jail on 10.0 host with vimage From: Andreas Nilsson To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 16:54:28 -0000 Hello, I have a host running 10.0(-RC5) with vimage and 64 routetables. On that I'm trying to run a 9.2 jail ( with vnet ). jail.conf is as $ cat /etc/jail.conf $ppath="/usr/local/jails/"; exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; vnet; allow.raw_sockets; mount.devfs; host1 { path = "${ppath}/subdir1/host1"; vnet.interface = "epair4b"; } The jail starts up fine, but when trying to check the routing table in the jail I get: $ netstat -rn netstat: no namelist What does it mean? Is there a way around this? On my 10.0 jail it works just fine. Best regards Andreas Nilsson From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 18:25:54 2014 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 ESMTPS id 53643B90 for ; Tue, 11 Feb 2014 18:25:54 +0000 (UTC) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 276A9111E for ; Tue, 11 Feb 2014 18:25:54 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id un15so8039648pbc.24 for ; Tue, 11 Feb 2014 10:25:53 -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=hb09a+3MqXnOfz//1F5rEC/u8Ozgn+LGOYsnJI6/Kg4=; b=QSAdplu1PD1NkiWwLsWOhIwJ8jPZ6F3fvJgTvySfsH0aQxMSpJaV50HrL1NX0rrKkQ TV2Zxlozh09UMdtVgi+HHTEL/n/xd1iwyviRWYQ8I18VbB/M7/tz5pJAwVGb4tUmjWam jszgnDP8p+tuMO9D97qYvEEh/fUPcNsaZLv0qe9JpPhqE/nwTE21ElaCU/r/zfJggaLy 6HxOxjKGw8AM4+/Ric6s86HzpmejjCDsowZjDTpJa36DrGLfVsudeYntstyFysVV6sj1 r9KXlREIy9WGF1gl/KgddhWtZmZQ8hTLd9sIoSWkWgfocSi7KQr4inKGR0Rvghrb4ITx p8vQ== MIME-Version: 1.0 X-Received: by 10.66.179.143 with SMTP id dg15mr34440309pac.52.1392143153709; Tue, 11 Feb 2014 10:25:53 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 11 Feb 2014 10:25:53 -0800 (PST) In-Reply-To: <52F97A84.90308@callfortesting.org> References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> Date: Tue, 11 Feb 2014 13:25:53 -0500 Message-ID: Subject: Re: CFT: bhyve AMD snapshot From: Aryeh Friedman To: Michael Dexter Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 18:25:54 -0000 On Mon, Feb 10, 2014 at 8:19 PM, Michael Dexter wrote: > > I opted to build world with -j4 and kernel on -j2 on a dual-core system > as per Glen Barber's suggestion of how he is building the official > releases. What, if anything, do the parameters to "make world" have to do with ***VIRTUALIZATION***? Please keep your comments on the topic of this list ;-) Namely the ***RESULTS*** of the test you asked people to perform. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 19:49:56 2014 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 ESMTPS id 51F16331; Tue, 11 Feb 2014 19:49:56 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 29BD119B3; Tue, 11 Feb 2014 19:49:56 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 22FCCB988; Tue, 11 Feb 2014 14:49:55 -0500 (EST) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: Detect of BHyve VM was powered off or rebooted? Date: Tue, 11 Feb 2014 14:11:33 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201402111411.33269.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 11 Feb 2014 14:49:55 -0500 (EST) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 19:49:56 -0000 On Sunday, February 09, 2014 7:03:41 pm Neel Natu wrote: > Hi Craig, > > On Sun, Feb 9, 2014 at 1:11 PM, Craig Rodrigues wrote: > > Hi, > > > > I posted some rc.d scripts that I am using to boot a BHyve VM > > and send the output to a serial console using the /dev/nmdm > > driver: > > > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014- January/002040.html > > > > It works quite well. There is some things I would like to improve, > > and would like some advice on the best way to do it. > > > > (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, > > then I do not want to automatically restart the VM in the script. > > User should manually: service bhyvevm start > > > > (2) If the VM was powered down, via shutdown -p, or halt -p, > > then in my script I do not want to restart the VM in the script. > > User should manually: service bhyvevm start > > > > (3) If the VM was rebooted via "reboot" or "shutdown -r", > > then I *do* want the script to restart the VM. > > > > I think if I change my start_vm.sh script to do something like: > > > > > > > > ( > > while [ -e /dev/vmm/${VM} ]; do > > /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc > > -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" > > done > > > > ) & > > > > > > then this might cover cases (1) and (3), but what will cover > > case (2)? > > The exit code of the bhyve process will be 0 if it exited because the > guest rebooted and will be non-zero if the guest did an acpi poweroff. > You can use that to distinguish between cases (2) and (3). > > Having said that there are error conditions for which bhyve exits with > a non-zero exit code. So, we'll need to explicitly define an exit code > to distinguish between an acpi poweroff and these error conditions. OTOH, in all the cases when bhyve exits with a non-zero exit code, you will want to exit the loop which would treat it the same as shutdown -p. I think you can just do this: while [ -e /dev/vmm/${VM} ]; do if ! bhyve ...; then break fi done -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 19:49:57 2014 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 ESMTPS id 3E9C235D for ; Tue, 11 Feb 2014 19:49:57 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 187A419B6 for ; Tue, 11 Feb 2014 19:49:57 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 08145B9B9; Tue, 11 Feb 2014 14:49:56 -0500 (EST) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: bhyve upgrade Date: Tue, 11 Feb 2014 14:15:51 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201402111415.51401.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 11 Feb 2014 14:49:56 -0500 (EST) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 19:49:57 -0000 On Tuesday, February 11, 2014 4:38:10 am Andrea Brancatelli wrote: > Hello all, > > given that I'm not confortable with unofficial upgrades, I was wondering > if, say, a 10-p1 would contain any new bhyve upgrade or should we wait for > an official 10.1 ? There will not be any bhyve features merged to a 10-p1. You'll have to either wait for 10.1 or run stable/10. However, most new bhyve features are in HEAD still. -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 22:29:21 2014 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 ESMTPS id 50BCCC8E; Tue, 11 Feb 2014 22:29:21 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 896E119C1; Tue, 11 Feb 2014 22:29:20 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id hr13so6455732lab.15 for ; Tue, 11 Feb 2014 14:29:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kjnB8mcHjkDxBYrM0Gox27+p4rVBh4Vsd9cAj5w+ncw=; b=0BIsvBSAea6tPRaSk5W/FP3xJvvZ07aGIJg++0p8O1k5GRmqRkCA8kqFfm7QMkC0Mo RO3+heZMJnrUsS5OKTlVTHEXsG45akYyRy5TmaV9WahLIhlcftjG9SN6m0XBhTOLKMng +j6RAYLZC/D2gAttSC4A7r4D/7V+NThrYahKOxFXncL/OW6w4n9k5xDHTLFvpz0bM1HN OtGwxjKtpgszeaV7yObCidOmmjb6FubIHDO7AucLFJYHcvmIpEAYuxRb1lnwC2A76VD0 VXyPv5Xqfz2nDwY9/Ob+4Itpx+1eeVIJB61KTeS/I7sKRYweFogqchK52HsflNsCvO9P kvSw== MIME-Version: 1.0 X-Received: by 10.112.114.228 with SMTP id jj4mr26883596lbb.13.1392157758522; Tue, 11 Feb 2014 14:29:18 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Tue, 11 Feb 2014 14:29:18 -0800 (PST) In-Reply-To: <201402111411.33269.jhb@freebsd.org> References: <201402111411.33269.jhb@freebsd.org> Date: Tue, 11 Feb 2014 14:29:18 -0800 X-Google-Sender-Auth: IClU34vp_VhEINijhW9Jhoiq3RI Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Craig Rodrigues To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 22:29:21 -0000 On Tue, Feb 11, 2014 at 11:11 AM, John Baldwin wrote: > On Sunday, February 09, 2014 7:03:41 pm Neel Natu wrote: > > Hi Craig, > > > > On Sun, Feb 9, 2014 at 1:11 PM, Craig Rodrigues > wrote: > > > Hi, > > > > > > I posted some rc.d scripts that I am using to boot a BHyve VM > > > and send the output to a serial console using the /dev/nmdm > > > driver: > > > > > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014- > January/002040.html > > > > > > It works quite well. There is some things I would like to improve, > > > and would like some advice on the best way to do it. > > > > > > (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, > > > then I do not want to automatically restart the VM in the script. > > > User should manually: service bhyvevm start > > > > > > (2) If the VM was powered down, via shutdown -p, or halt -p, > > > then in my script I do not want to restart the VM in the script. > > > User should manually: service bhyvevm start > > > > > > (3) If the VM was rebooted via "reboot" or "shutdown -r", > > > then I *do* want the script to restart the VM. > > > > > > I think if I change my start_vm.sh script to do something like: > > > > > > > > > > > > ( > > > while [ -e /dev/vmm/${VM} ]; do > > > /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s > 1:0,lpc > > > -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} > ${VM}" > > > done > > > > > > ) & > > > > > > > > > then this might cover cases (1) and (3), but what will cover > > > case (2)? > > > > The exit code of the bhyve process will be 0 if it exited because the > > guest rebooted and will be non-zero if the guest did an acpi poweroff. > > You can use that to distinguish between cases (2) and (3). > > > > Having said that there are error conditions for which bhyve exits with > > a non-zero exit code. So, we'll need to explicitly define an exit code > > to distinguish between an acpi poweroff and these error conditions. > > OTOH, in all the cases when bhyve exits with a non-zero exit code, you > will want to exit the loop which would treat it the same as shutdown -p. I > think you can just do this: > > while [ -e /dev/vmm/${VM} ]; do > if ! bhyve ...; then > break > fi > done > One question, if "bhyve" exits, do I have to call bhyveload again before calling bhyve? The /usr/share/examples/bhyve/vmrun.sh has a loop which does: while [ 1 ] ; do ... bhyvectl --destroy bhyveload bhyve ... done -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 23:18:18 2014 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 ESMTPS id 72350BBA; Tue, 11 Feb 2014 23:18:18 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3189A1D66; Tue, 11 Feb 2014 23:18:18 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lj1so8348793pab.12 for ; Tue, 11 Feb 2014 15:18:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=5O3I49OdIm0d/X26UTs94XHvIXQysRMpKXTApcJ5TIo=; b=v1BIepLABuEDV+S+Vuie2HLQ1d0iRDdQ9cLJCEZrJOI+YZ7NlZoX68LwO8k9VIApn7 miI6VqkzSwDT2ZKdRsZ6UWWKl6E80+gMHdnibpe8IAAq9k+t55/ySNQf+u1PozloNQaN yfNOo5rzLKXL5gQjaJQoLZFyawJ1Sxeofcx5nobOnc4tkRHrp5TvMeXvZvYJrkDNHyN1 e9e5uZkjqTzk4K9+Tg7gsPCoWHSPEmAla3ujfGFpTTU7SNWoav82taiR10lInnxmAT6a 9qjZ8V1AauV9GLzMUuT37ddGzUrODaFYk3rqImywPnjwyJ8HZFVyLWSZNIS+vVYOOi3f MaAg== X-Received: by 10.68.255.101 with SMTP id ap5mr47332053pbd.41.1392160697886; Tue, 11 Feb 2014 15:18:17 -0800 (PST) Received: from [10.123.100.151] (mobile-166-137-214-162.mycingular.net. [166.137.214.162]) by mx.google.com with ESMTPSA id ei4sm56788404pbb.42.2014.02.11.15.18.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Feb 2014 15:18:16 -0800 (PST) References: <201402111411.33269.jhb@freebsd.org> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> X-Mailer: iPhone Mail (11B554a) From: Neel Natu Subject: Re: Detect of BHyve VM was powered off or rebooted? Date: Tue, 11 Feb 2014 15:18:11 -0800 To: Craig Rodrigues Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 11 Feb 2014 23:18:18 -0000 Hi Craig, > On Feb 11, 2014, at 2:29 PM, Craig Rodrigues wrote: >=20 >> On Tue, Feb 11, 2014 at 11:11 AM, John Baldwin wrote: >>=20 >>> On Sunday, February 09, 2014 7:03:41 pm Neel Natu wrote: >>> Hi Craig, >>>=20 >>> On Sun, Feb 9, 2014 at 1:11 PM, Craig Rodrigues >> wrote: >>>> Hi, >>>>=20 >>>> I posted some rc.d scripts that I am using to boot a BHyve VM >>>> and send the output to a serial console using the /dev/nmdm >>>> driver: >>>>=20 >>>> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014- >> January/002040.html >>>>=20 >>>> It works quite well. There is some things I would like to improve, >>>> and would like some advice on the best way to do it. >>>>=20 >>>> (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, >>>> then I do not want to automatically restart the VM in the script. >>>> User should manually: service bhyvevm start >>>>=20 >>>> (2) If the VM was powered down, via shutdown -p, or halt -p, >>>> then in my script I do not want to restart the VM in the script. >>>> User should manually: service bhyvevm start >>>>=20 >>>> (3) If the VM was rebooted via "reboot" or "shutdown -r", >>>> then I *do* want the script to restart the VM. >>>>=20 >>>> I think if I change my start_vm.sh script to do something like: >>>>=20 >>>>=20 >>>>=20 >>>> ( >>>> while [ -e /dev/vmm/${VM} ]; do >>>> /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s >> 1:0,lpc >>>> -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} >> ${VM}" >>>> done >>>>=20 >>>> ) & >>>>=20 >>>>=20 >>>> then this might cover cases (1) and (3), but what will cover >>>> case (2)? >>>=20 >>> The exit code of the bhyve process will be 0 if it exited because the >>> guest rebooted and will be non-zero if the guest did an acpi poweroff. >>> You can use that to distinguish between cases (2) and (3). >>>=20 >>> Having said that there are error conditions for which bhyve exits with >>> a non-zero exit code. So, we'll need to explicitly define an exit code >>> to distinguish between an acpi poweroff and these error conditions. >>=20 >> OTOH, in all the cases when bhyve exits with a non-zero exit code, you >> will want to exit the loop which would treat it the same as shutdown -p. = I >> think you can just do this: >>=20 >> while [ -e /dev/vmm/${VM} ]; do >> if ! bhyve ...; then >> break >> fi >> done >=20 >=20 >=20 > One question, if "bhyve" exits, do I have to call bhyveload again before > calling bhyve? Yes, that is correct. You will also need to destroy the VM after bhyve exits= . Best Neel >=20 > The /usr/share/examples/bhyve/vmrun.sh has a loop which does: >=20 > while [ 1 ] ; do >=20 > ... > bhyvectl --destroy > bhyveload > bhyve >=20 > ... > done >=20 > -- > Craig > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freeb= sd.org" From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 11 23:49:57 2014 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 ESMTPS id 0ACCF339 for ; Tue, 11 Feb 2014 23:49:57 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id B97271120 for ; Tue, 11 Feb 2014 23:49:56 +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 435B112363; Wed, 12 Feb 2014 09:49:55 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRT40422 (AUTH peterg@ptree32.com.au); Wed, 12 Feb 2014 09:49:54 +1000 Message-ID: <52FAB720.7070206@freebsd.org> Date: Tue, 11 Feb 2014 15:49:52 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> 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.17 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, 11 Feb 2014 23:49:57 -0000 Hi Aryeh, > Fatal trap 30: reserved (unknown) fault while in kernel mode I'm not seeing this with a 10.0 guest on my Phenom II X6. However: > root@:/home/aryeh # uname -a > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01 > EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 This isn't the revision of the bhyve_svm branch - did you possibly do a sync before building this ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 00:05:00 2014 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 ESMTPS id 67136628 for ; Wed, 12 Feb 2014 00:05:00 +0000 (UTC) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e: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 36C191296 for ; Wed, 12 Feb 2014 00:05:00 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp16so8427132pbb.34 for ; Tue, 11 Feb 2014 16:05:00 -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 :content-type; bh=DgUv/jIPaZ4og5G6nm8Huu0FwHMiSzkuZPyISluLgK4=; b=lldVAPjUxGinuaHmb06MXD8IHcANvsbQ9XxmAod122AG+8PkS0s6ifsua8Bcxpkshg q5pnBeMMKuvyU0ZE02ZFHgpZtbuvDyJ9h6AOpt9mGJ9kI7bkbwRKo4c24IFfF0/jCWgZ YFLc7A0ePN1cowI8LliSDbnR8xRteINauTfzlaS2bA7jlEb7D4TB1AuvulTekcxsuMx7 k/8ssYjdOZulYo4JVEscSXOhsV9ZTQEOTM/JMV8+MO1vRs/uXQNTiGqVA+qPrFv7R7wM c5UJmbl3ZVlLvWS+6xzmg4so1dc5DjeIBJ3+4DAeas+3toeeVhaYcB1yuNiuSDGUrfot 4j8Q== MIME-Version: 1.0 X-Received: by 10.66.221.199 with SMTP id qg7mr36002175pac.88.1392163499936; Tue, 11 Feb 2014 16:04:59 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 11 Feb 2014 16:04:59 -0800 (PST) In-Reply-To: References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> <52FAB720.7070206@freebsd.org> Date: Tue, 11 Feb 2014 19:04:59 -0500 Message-ID: Subject: Fwd: CFT: bhyve AMD snapshot From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 00:05:00 -0000 ---------- Forwarded message ---------- From: Aryeh Friedman Date: Tue, Feb 11, 2014 at 7:04 PM Subject: Re: CFT: bhyve AMD snapshot To: Peter Grehan root@:/home/aryeh # uname -a >> FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01 >> EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 >> > > This isn't the revision of the bhyve_svm branch - did you possibly do a > sync before building this ? > svn switch -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 00:09:02 2014 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 ESMTPS id CBFB26E0 for ; Wed, 12 Feb 2014 00:09:02 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 856D112D0 for ; Wed, 12 Feb 2014 00:09:02 +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 0CDBD12283; Wed, 12 Feb 2014 10:09:01 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRT42093 (AUTH peterg@ptree32.com.au); Wed, 12 Feb 2014 10:09:00 +1000 Message-ID: <52FABB9A.6000908@freebsd.org> Date: Tue, 11 Feb 2014 16:08:58 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: Fwd: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> <52FAB720.7070206@freebsd.org> 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.17 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, 12 Feb 2014 00:09:02 -0000 Hi Aryeh, > root@:/home/aryeh # uname -a >>> FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 03:19:01 >>> EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 >>> >> >> This isn't the revision of the bhyve_svm branch - did you possibly do a >> sync before building this ? >> > > svn switch Would you be able to retry with a fresh checkout of the branch e.g. svn co svn://svn.freebsd.org/base/projects/bhyve_svm/ . later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 08:53:54 2014 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 ESMTPS id 389BC8B3 for ; Wed, 12 Feb 2014 08:53:54 +0000 (UTC) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e: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 0F9AB17ED for ; Wed, 12 Feb 2014 08:53:54 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp16so8965171pbb.34 for ; Wed, 12 Feb 2014 00:53:53 -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=IZ9aLm7RkUR4hhGHjfEUy2JduxTPCl+XLfvzj8h7Iu4=; b=SncidohNhgc60wgHjHxptfuy5+LzIxomL/7mCcRJTE5A3Qs5Q9JVEdTJ4WC340LqxQ Ge/+H9JOCgd6axy0hZ2nn55w2fRLmfjZ8PLJ5gh0UPY8cWCEh/8F6WeRVGChUxDqVFys fCQrmqiitGFcPRTQx2IKO8IxlHhbEO6KSAEt3xt6kCKNrGP7B8iGhRc6wRoSryxtS1/3 PJuIcSqeBL2eCsm7/9Re+c2nF5ij5X56YySwS9M+B50/Ky6906TG/HOxXXKfom3U+znN KK9iHVgnjbD8uLze5oqxEwDs1UDNuy7gpE8XDALAEtbKdsk0cyJg5xZU3mFKvvdh+gIh 7KEQ== MIME-Version: 1.0 X-Received: by 10.66.179.143 with SMTP id dg15mr38260094pac.52.1392195233543; Wed, 12 Feb 2014 00:53:53 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 12 Feb 2014 00:53:53 -0800 (PST) Date: Wed, 12 Feb 2014 03:53:53 -0500 Message-ID: Subject: PetiteCloud 0.2.5 released From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 08:53:54 -0000 What's new: * Ability to use physical disks as backing stores * Multiple NIC's * Multiple backing stores (1 primary and upto 5 secondary) * Advanced settings -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 09:28:38 2014 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 ESMTPS id 83606F9C for ; Wed, 12 Feb 2014 09:28:38 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 067841A88 for ; Wed, 12 Feb 2014 09:28:37 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id w7so6930667lbi.13 for ; Wed, 12 Feb 2014 01:28:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=4adEKyT8ZUKIOSV4fHAmoKFkzJ5j2uayqlqqmCbqE4o=; b=esedG3avLggsBuTPR9h73mBXTLBy17+WiZVZAF+KaugQCZDSelQwOiD8eAmxZGQsgM Bez/WknAB/jDNg8pz+kP5XN+Amb6lVSHpGbM2g63CDvZDsyNK8pidOeCEh8gPLSvjFcG 3pvbF+TeTb9/6IAehrhtJckMfoKDiwA3d/wW9slkOCtVfYPDWMxWVwANT0fXLrfombCE OX5uHr8PY+U7VngSEaDRRaZ90zu+rDyvYiQ536MELyydUL0E8uPCitk5Fin7YdjkFXIR gup4p3q4VpLnMnFm0GrMysSOupOiuyq4EO/8Oo1xmx/DoEEyUUyb3i6nnc3kUFLfOxco +dPA== MIME-Version: 1.0 X-Received: by 10.112.166.68 with SMTP id ze4mr1021210lbb.58.1392197315674; Wed, 12 Feb 2014 01:28:35 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Wed, 12 Feb 2014 01:28:35 -0800 (PST) In-Reply-To: <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> Date: Wed, 12 Feb 2014 01:28:35 -0800 X-Google-Sender-Auth: n93EvnzhY8Wv21Lj6dKRwcojxbQ Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Craig Rodrigues To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 09:28:38 -0000 On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu wrote: > > > > > > > > > One question, if "bhyve" exits, do I have to call bhyveload again before > > calling bhyve? > > Yes, that is correct. You will also need to destroy the VM after bhyve > exits. > Why can't bhyve clean up after itself as the bhyve process exits and destroy the VM? It seems pointless to me for the user to have to explictly destroy the VM. Once the bhyve process exits, I doesn't seem that I can use the VM again anyways. To run the VM again, I seem to need to call: -> bhyvectl to destroy the VM -> bhyveload to load -> bhyve to run the VM Aryeh has pointed out to me that it is the responsibility of the user to explictly destroy and tap and bridge devices used by the bhyve process after it exits. Is this right? What if I have a single bridge0 device, and 10 tap devices, one per VM? If one VM exits and needs to be restarted, do I need to tear down all the taps and bridge? -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 09:47:13 2014 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 ESMTPS id 927EAC8F; Wed, 12 Feb 2014 09:47:13 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5DC931C36; Wed, 12 Feb 2014 09:47:13 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lj1so8982869pab.12 for ; Wed, 12 Feb 2014 01:47:13 -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=XaZOMBI0LA6heBwXrrGNzv8dXy4zsTCJHkG6OAmSeFc=; b=X/UWs00mnf94rkFwlJz+uBuggdAAUHlobVeXUo4mbEufKLaDqNbeD0pFlxWRfSMqyr fOilhXWiLZX8pIW5WnDnbgIDunULCrLC6Ox8TKywQqO0xfMKpUUNrz4lPS8gX1dMDSFS DjbHloYrKTxaoFKaIGVqnHFc2U2wEOxG7s5e67jsTXf4rvuTty6N/GRzrPnBiA42wsoF QuQfhOdeGVWjKmpaWOp+tJrKJpBkeRrTRvaW7h2hZnnxnfPqGJUYjprCrfAJdNnl7jZ6 rhDJSEMix4CU97HXaYyT6Y0rpIcL6z/a9odU6NUuSlA88gZHnP3Sh8n3Kx+d68N74DGu uYxA== MIME-Version: 1.0 X-Received: by 10.66.141.231 with SMTP id rr7mr37625102pab.41.1392198433053; Wed, 12 Feb 2014 01:47:13 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 12 Feb 2014 01:47:12 -0800 (PST) In-Reply-To: References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> Date: Wed, 12 Feb 2014 04:47:12 -0500 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Aryeh Friedman To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 09:47:13 -0000 On Wed, Feb 12, 2014 at 4:28 AM, Craig Rodrigues wrote: > On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu wrote: > > > > > > > > > > > > > > > One question, if "bhyve" exits, do I have to call bhyveload again > before > > > calling bhyve? > > > > Yes, that is correct. You will also need to destroy the VM after bhyve > > exits. > > > > > Why can't bhyve clean up after itself as the bhyve process exits > and destroy the VM? > > It seems pointless to me for the user to have to explictly > destroy the VM. Once the bhyve process exits, I doesn't seem that I can > use > the VM again anyways. To run the VM again, I seem to need to call: > -> bhyvectl to destroy the VM > -> bhyveload to load > -> bhyve to run the VM > > Aryeh has pointed out to me that it is the responsibility of the > user to explictly destroy and tap and bridge devices used by the > bhyve process after it exits. Is this right? > > What if I have a single bridge0 device, and 10 tap devices, > one per VM? If one VM exits and needs to be restarted, do > I need to tear down all the taps and bridge? > Yes you do. It gets really harry when you have multple vm's and taps per instance that need to start and stop at arbitrary times. We are currently disccusing this issue on the petitecloud mailing list it might be off topic here to get into too much detail. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 14:03:30 2014 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 ESMTPS id 61831C86; Wed, 12 Feb 2014 14:03:30 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2AF9B1612; Wed, 12 Feb 2014 14:03:30 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lj1so9183326pab.26 for ; Wed, 12 Feb 2014 06:03:29 -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=2vqdkAlQCAB1hWeS9o9PP/RKbVq4DUKViZiBqhbkKrc=; b=dtn4AMeaaYA7S0O9ZVsjfeE2moFWfwVex7Ps/l/qmI5vL3Gr6tqdaqpHAFTZraZmYO tJhMwBFJbAJJB0GFeueSj7nis1dyilbWSGeRoouzZ8e0AnLQvZ6HNfXXPNJ7uR0SSt+0 ISlSTkd1Ln9KfrPCFKH5Eb1hDrIcZf6GkTWM9YVwyItfizoGGyVUlnvSqykLnhoUfKd7 5yiI1r7ZidMoedSNaR/lKNt8vxM986YVF3tXMNkwEYbFLIM6hE+HW9b3wM2/BCfw/dte XwE3+7/R3CP2k+NyZrtpa22021VleFOPSgulKBqBEdh4ZWkSkFKr4/LX7VhSu7sCMAsG kluw== MIME-Version: 1.0 X-Received: by 10.66.221.199 with SMTP id qg7mr39881600pac.88.1392213809813; Wed, 12 Feb 2014 06:03:29 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 12 Feb 2014 06:03:29 -0800 (PST) In-Reply-To: <52FABB9A.6000908@freebsd.org> References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> <52FAB720.7070206@freebsd.org> <52FABB9A.6000908@freebsd.org> Date: Wed, 12 Feb 2014 09:03:29 -0500 Message-ID: Subject: Re: Fwd: CFT: bhyve AMD snapshot From: Aryeh Friedman To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 14:03:30 -0000 On Tue, Feb 11, 2014 at 7:08 PM, Peter Grehan wrote: > Hi Aryeh, > > > root@:/home/aryeh # uname -a >> >>> FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261732: Tue Feb 11 >>>> 03:19:01 >>>> EST 2014 aryeh@:/usr/obj/usr/src/sys/GENERIC amd64 >>>> >>>> >>> This isn't the revision of the bhyve_svm branch - did you possibly do a >>> sync before building this ? >>> >>> >> svn switch >> > > Would you be able to retry with a fresh checkout of the branch e.g. > > svn co svn://svn.freebsd.org/base/projects/bhyve_svm/ . > > later, > > > kernel panic during boot -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 15:28:23 2014 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 ESMTPS id B0ABC770; Wed, 12 Feb 2014 15:28:23 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6C3701D82; Wed, 12 Feb 2014 15:28:23 +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 6F73612183; Thu, 13 Feb 2014 01:28:21 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRT85668 (AUTH peterg@ptree32.com.au); Thu, 13 Feb 2014 01:28:20 +1000 Message-ID: <52FB930B.1040607@freebsd.org> Date: Wed, 12 Feb 2014 07:28:11 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: Detect of BHyve VM was powered off or rebooted? References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> 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.17 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, 12 Feb 2014 15:28:23 -0000 Hi Craig, > It seems pointless to me for the user to have to explictly > destroy the VM. We're working on fixing it. What it gave during the development process (and still gives) is the ability to get post-mortem information when the bhyve process exits. > Once the bhyve process exits, I doesn't seem that I can use > the VM again anyways. To run the VM again, I seem to need to call: > -> bhyvectl to destroy the VM > -> bhyveload to load > -> bhyve to run the VM Yes, that's correct. The future version will be: /usr/sbin/bhyve to load/run/reboot the VM in a single process. > Aryeh has pointed out to me that it is the responsibility of the > user to explictly destroy and tap and bridge devices used by the > bhyve process after it exits. Is this right? Only if you won't be using them anymore. > What if I have a single bridge0 device, and 10 tap devices, > one per VM? If one VM exits and needs to be restarted, do > I need to tear down all the taps and bridge? No - leave them there. Think of the tap interfaces as ports on a switch, and the bhyve processes as being plugged/unplugged from the ports. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 15:30:12 2014 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 ESMTPS id DB00F7D4 for ; Wed, 12 Feb 2014 15:30:12 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 929881D92 for ; Wed, 12 Feb 2014 15:30:12 +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 A79C712183; Thu, 13 Feb 2014 01:30:11 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRT85687 (AUTH peterg@ptree32.com.au); Thu, 13 Feb 2014 01:30:10 +1000 Message-ID: <52FB9382.8000401@freebsd.org> Date: Wed, 12 Feb 2014 07:30:10 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: Fwd: CFT: bhyve AMD snapshot References: <52F6953D.2010400@callfortesting.org> <52F7C9FC.5070409@digiware.nl> <52F8735E.8020701@callfortesting.org> <52F8ECC2.2060805@digiware.nl> <52F97A84.90308@callfortesting.org> <52FAB720.7070206@freebsd.org> <52FABB9A.6000908@freebsd.org> 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.17 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, 12 Feb 2014 15:30:12 -0000 Hi Aryeh, > kernel panic during boot Can you post a verbose boot log with the panic (i.e. "boot -v" from the loader prompt) ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 15:38:41 2014 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 ESMTPS id DC0A29C9; Wed, 12 Feb 2014 15:38:41 +0000 (UTC) Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9EAC91EA0; Wed, 12 Feb 2014 15:38:41 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id up15so9445447pbc.0 for ; Wed, 12 Feb 2014 07:38:41 -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=NONPr9FSSZTgTiOMdai6zP7eH6fKz7W3dIBSgecf848=; b=G/znknZYjA6bxeERBKUmDVY3B+gu24HY3OKpDy6cH0ovS5rY0Mh63yQ6wgSHcebjnZ 8fSqPXOFTAsq9Z0rF+l9a4Ju7j3Uu476yJaT0u9GsntojbSAw0kPN9ZKiXyQ54bgUzG3 7jSaPqScyphX8QyD0tGMRj/u/XGImn6ZvzvN/rTL/CunU2Zxr+rOCeLXeqmU7pvk4AvR 36Kkb0tclbihMFtMP/jo5gZD4HYW8FdBn2oyzU34d3Gxylb+6+oqUCXgyJbhXGIN8uDQ XY4VA38vxyEdpy4OVst7OvbNE3iZuZBd4fXG/RwRoNMvgSW8KYHZU9VLscpfT8QohJ4x JqUA== MIME-Version: 1.0 X-Received: by 10.66.221.199 with SMTP id qg7mr40410892pac.88.1392219521314; Wed, 12 Feb 2014 07:38:41 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 12 Feb 2014 07:38:41 -0800 (PST) In-Reply-To: <52FB930B.1040607@freebsd.org> References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> <52FB930B.1040607@freebsd.org> Date: Wed, 12 Feb 2014 10:38:41 -0500 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Aryeh Friedman To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 15:38:41 -0000 On Wed, Feb 12, 2014 at 10:28 AM, Peter Grehan wrote: > No - leave them there. Think of the tap interfaces as ports on a switch, > and the bhyve processes as being plugged/unplugged from the ports. > Every time I have tried this it has lead to bricking the bridge if done in the wrong order and/or there was a packet in transit on the bridge while you have open end points -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 17:14:25 2014 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 ESMTPS id 955BDAC7 for ; Wed, 12 Feb 2014 17:14:25 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77900189A for ; Wed, 12 Feb 2014 17:14:25 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s1CHEMEh010585 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Wed, 12 Feb 2014 12:14:23 -0500 (EST) (envelope-from lists@jnielsen.net) From: John Nielsen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: best branch for bhyve on AMD? Message-Id: Date: Wed, 12 Feb 2014 10:14:28 -0700 To: freebsd-virtualization@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) X-DCC-Etherboy-Metrics: ns1.jnielsen.net 1002; Body=1 Fuz1=1 Fuz2=1 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 17:14:25 -0000 Greetings, I am running FreeBSD 10.0-STABLE r261733 amd64 on a system with an AMD = "Brisbane" CPU: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2835.16-MHz = K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x60fb2 Family =3D 0xf Model =3D = 0x6b Stepping =3D 2 = Features=3D0x178bfbff Features2=3D0x2001 AMD = Features=3D0xea500800 AMD Features2=3D0x11f "kldload vmm" gives these kernel messages: amd_iommu_init: not implemented amdv_init: not implemented amdv_cleanup: not implemented module_register_init: MOD_LOAD (vmm, 0xffffffff80f5abf0, 0) error 6 and "# bhyveload -m 256 -d /dev/zvol/bigz/bhyvetest bhyvetest" gives: vm_create: Device not configured Am I right in thinking that bhyve support for AMD processors is not yet = in -STABLE? If so, is there working code for bhyve under AMD anywhere? Where? -HEAD, = projects/bhyve_svm or somewhere else? Is it considered experimental, = stable, or something in between? Should it work with the above = processor? Looking forward to trying bhyve on this hardware. Thanks! JN From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 17:27:37 2014 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 ESMTPS id D58A3D97 for ; Wed, 12 Feb 2014 17:27:37 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB061197C for ; Wed, 12 Feb 2014 17:27:37 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id z10so9324443pdj.33 for ; Wed, 12 Feb 2014 09:27: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=4qSSVTs5WulYu0K7fblT+VZs7RqJGwo2gc3okWGcGlI=; b=BpUEHcl2lEhVWI+ZKsrasvp0AEG7EKJaW12hxQ/9wGl6BFioYntcmYnmC4JSBYCU94 CoGX00xxVMLcJH8j/JC9/NPkrgW+mvogBti6soC2ZyxnQAvmtp692L2Jo38eXKFEej8k CXOKMiLB2C7TFasIbn8tNUisteBV5/QUFvPILwleCNojcVftmLWMPC6ne6GQ91GBdhCH wo7Zi4kc/WYmyA3qlKF+0FTfLt1JOZxZbVAh/Dtx3jfqjtwXlr+KqsrnlOUXvXmWJqWo iBllgDCr44TGFm7MCs1FKpO9bhasQxcvU3q4X0wipjsyeOrZ9pTkomxJyakKBZqtrJ32 Zz/A== MIME-Version: 1.0 X-Received: by 10.68.138.165 with SMTP id qr5mr53168190pbb.123.1392226057384; Wed, 12 Feb 2014 09:27:37 -0800 (PST) Received: by 10.68.155.36 with HTTP; Wed, 12 Feb 2014 09:27:37 -0800 (PST) In-Reply-To: References: Date: Wed, 12 Feb 2014 12:27:37 -0500 Message-ID: Subject: Re: best branch for bhyve on AMD? From: Thomas Hoffmann To: John Nielsen Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 17:27:37 -0000 On Wed, Feb 12, 2014 at 12:14 PM, John Nielsen wrote: > Greetings, > > I am running FreeBSD 10.0-STABLE r261733 amd64 on a system with an AMD > "Brisbane" CPU: > > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2835.16-MHz K8-class > CPU) > Origin = "AuthenticAMD" Id = 0x60fb2 Family = 0xf Model = 0x6b > Stepping = 2 > > Features=0x178bfbff > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x11f > > "kldload vmm" gives these kernel messages: > amd_iommu_init: not implemented > amdv_init: not implemented > amdv_cleanup: not implemented > module_register_init: MOD_LOAD (vmm, 0xffffffff80f5abf0, 0) error 6 > > and "# bhyveload -m 256 -d /dev/zvol/bigz/bhyvetest bhyvetest" gives: > vm_create: Device not configured > > Am I right in thinking that bhyve support for AMD processors is not yet in > -STABLE? > > If so, is there working code for bhyve under AMD anywhere? Where? -HEAD, > projects/bhyve_svm or somewhere else? Is it considered experimental, > stable, or something in between? Should it work with the above processor? > > Looking forward to trying bhyve on this hardware. > > Thanks! > > JN > This might answer some of your questions: http://bhyve.org/faq/ From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 17:31:55 2014 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 ESMTPS id D50E2F34 for ; Wed, 12 Feb 2014 17:31:55 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 937631A10 for ; Wed, 12 Feb 2014 17:31:55 +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 87FF212269; Thu, 13 Feb 2014 03:31:53 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRT88396 (AUTH peterg@ptree32.com.au); Thu, 13 Feb 2014 03:31:52 +1000 Message-ID: <52FBB006.7060300@freebsd.org> Date: Wed, 12 Feb 2014 09:31:50 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: John Nielsen Subject: Re: best branch for bhyve on AMD? 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.17 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, 12 Feb 2014 17:31:55 -0000 Hi John, > Am I right in thinking that bhyve support for AMD processors is not > yet in -STABLE? Yes, that's correct. > If so, is there working code for bhyve under AMD anywhere? Where? > -HEAD, projects/bhyve_svm or somewhere else? projects/bhyve_svm > Is it considered experimental, stable, or something in between? I'd home somewhere on the stable side of experimental. I've had good success with it on a Phenom II, but looks like at least 1 user has had issues. > Should it work with the above processor? I think your model may be predate the h/w nested paging support that bhyve relies on (EPT, or RVI in early AMD terminology). The list of AMD CPUs with RVI is at: http://support.amd.com/en-us/kb-articles/Pages/GPU120AMDRVICPUsHyperVWin8.aspx ... and the Athlon 64 X2 isn't on that list :( later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 17:59:41 2014 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 ESMTPS id CAE535B7; Wed, 12 Feb 2014 17:59:41 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A96301C16; Wed, 12 Feb 2014 17:59:41 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s1CHxcOH055077 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 12 Feb 2014 12:59:39 -0500 (EST) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: best branch for bhyve on AMD? From: John Nielsen In-Reply-To: <52FBB006.7060300@freebsd.org> Date: Wed, 12 Feb 2014 10:59:45 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <04E4A8F4-F876-4370-9852-7C69900CA3CF@jnielsen.net> References: <52FBB006.7060300@freebsd.org> To: Peter Grehan X-Mailer: Apple Mail (2.1827) X-DCC-Etherboy-Metrics: ns1.jnielsen.net 1002; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 17:59:41 -0000 On Feb 12, 2014, at 10:31 AM, Peter Grehan wrote: > Hi John, >=20 >> Am I right in thinking that bhyve support for AMD processors is not >> yet in -STABLE? >=20 > Yes, that's correct. >=20 >> If so, is there working code for bhyve under AMD anywhere? Where? >> -HEAD, projects/bhyve_svm or somewhere else? >=20 > projects/bhyve_svm >=20 >> Is it considered experimental, stable, or something in between? >=20 > I'd home somewhere on the stable side of experimental. I've had good = success with it on a Phenom II, but looks like at least 1 user has had = issues. >=20 >> Should it work with the above processor? >=20 > I think your model may be predate the h/w nested paging support that = bhyve relies on (EPT, or RVI in early AMD terminology). The list of AMD = CPUs with RVI is at: >=20 > = http://support.amd.com/en-us/kb-articles/Pages/GPU120AMDRVICPUsHyperVWin8.= aspx >=20 > ... and the Athlon 64 X2 isn't on that list :( Thanks for the quick response. Yes, it looks like only K10-ish and newer = have RVI, and my Brisbane is the last of the K8s. Bummer. I'll have to = see if my board will take a newer processor. :) JN From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 22:43:58 2014 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 ESMTPS id 4DE6826C; Wed, 12 Feb 2014 22:43:58 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 282831709; Wed, 12 Feb 2014 22:43:57 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s1CMavgs028304 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 12 Feb 2014 17:36:58 -0500 (EST) (envelope-from lists@jnielsen.net) From: John Nielsen Content-Type: multipart/mixed; boundary="Apple-Mail=_9C1C27D8-519D-4B6F-9C2A-02955E3A8600" Subject: Proposed patch for vmrun.sh Date: Wed, 12 Feb 2014 15:37:04 -0700 Message-Id: <7414975C-B9E6-4B13-8F08-9940FF895546@jnielsen.net> To: Neel Natu Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) X-DCC--Metrics: ns1.jnielsen.net 1282; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 12 Feb 2014 22:43:58 -0000 --Apple-Mail=_9C1C27D8-519D-4B6F-9C2A-02955E3A8600 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii See attached patch for vmrun.sh. It contains two changes: * Use an "err" function that prints to stderr instead of "echo" for = text output * Use "file -s" instead of "file" to allow it to check block devices = (zvol, etc) Feel free to commit it if you find it useful. Thanks! --Apple-Mail=_9C1C27D8-519D-4B6F-9C2A-02955E3A8600 Content-Disposition: attachment; filename=vmrun.sh.patch Content-Type: application/octet-stream; name="vmrun.sh.patch" Content-Transfer-Encoding: 7bit --- share/examples/bhyve/vmrun.sh.orig 2014-02-12 15:20:37.695377968 -0700 +++ share/examples/bhyve/vmrun.sh 2014-02-12 15:25:09.366589771 -0700 @@ -30,6 +30,7 @@ LOADER=/usr/sbin/bhyveload BHYVECTL=/usr/sbin/bhyvectl FBSDRUN=/usr/sbin/bhyve +FILE="/usr/bin/file -s" DEFAULT_MEMSIZE=512M DEFAULT_CPUS=2 @@ -38,21 +39,25 @@ DEFAULT_VIRTIO_DISK="./diskdev" DEFAULT_ISOFILE="./release.iso" +err() { + echo "$*" >&2 +} + usage() { - echo "Usage: vmrun.sh [-hai][-g ][-m ][-d ][-e ][-I ][-t ] " - echo " -h: display this help message" - echo " -a: force memory mapped local apic access" - echo " -c: number of virtual cpus (default is ${DEFAULT_CPUS})" - echo " -d: virtio diskdev file (default is ${DEFAULT_VIRTIO_DISK})" - echo " -e: set FreeBSD loader environment variable" - echo " -g: listen for connection from kgdb at " - echo " -i: force boot of the Installation CDROM image" - echo " -I: Installation CDROM image location (default is ${DEFAULT_ISOFILE})" - echo " -m: memory size (default is ${DEFAULT_MEMSIZE})" - echo " -t: tap device for virtio-net (default is $DEFAULT_TAPDEV)" - echo "" - echo " This script needs to be executed with superuser privileges" - echo "" + err "Usage: vmrun.sh [-hai][-g ][-m ][-d ][-e ][-I ][-t ] " + err " -h: display this help message" + err " -a: force memory mapped local apic access" + err " -c: number of virtual cpus (default is ${DEFAULT_CPUS})" + err " -d: virtio diskdev file (default is ${DEFAULT_VIRTIO_DISK})" + err " -e: set FreeBSD loader environment variable" + err " -g: listen for connection from kgdb at " + err " -i: force boot of the Installation CDROM image" + err " -I: Installation CDROM image location (default is ${DEFAULT_ISOFILE})" + err " -m: memory size (default is ${DEFAULT_MEMSIZE})" + err " -t: tap device for virtio-net (default is $DEFAULT_TAPDEV)" + err "" + err " This script needs to be executed with superuser privileges" + err "" exit 1 } @@ -62,7 +67,7 @@ kldstat -n vmm > /dev/null 2>&1 if [ $? -ne 0 ]; then - echo "vmm.ko is not loaded!" + err "vmm.ko is not loaded!" exit 1 fi @@ -123,30 +128,30 @@ # Create the virtio diskdev file if needed if [ ! -f ${virtio_diskdev} ]; then - echo "virtio disk device file \"${virtio_diskdev}\" does not exist." - echo "Creating it ..." + err "virtio disk device file \"${virtio_diskdev}\" does not exist." + err "Creating it ..." truncate -s 8G ${virtio_diskdev} > /dev/null fi if [ ! -r ${virtio_diskdev} ]; then - echo "virtio disk device file \"${virtio_diskdev}\" is not readable" + err "virtio disk device file \"${virtio_diskdev}\" is not readable" exit 1 fi if [ ! -w ${virtio_diskdev} ]; then - echo "virtio disk device file \"${virtio_diskdev}\" is not writable" + err "virtio disk device file \"${virtio_diskdev}\" is not writable" exit 1 fi -echo "Launching virtual machine \"$vmname\" ..." +err "Launching virtual machine \"$vmname\" ..." while [ 1 ]; do ${BHYVECTL} --vm=${vmname} --destroy > /dev/null 2>&1 - file ${virtio_diskdev} | grep ": x86 boot sector" > /dev/null + ${FILE} ${virtio_diskdev} | grep ": x86 boot sector" > /dev/null rc=$? if [ $rc -ne 0 ]; then - file ${virtio_diskdev} | grep ": Unix Fast File sys" > /dev/null + ${FILE} ${virtio_diskdev} | grep ": Unix Fast File sys" > /dev/null rc=$? fi if [ $rc -ne 0 ]; then @@ -157,8 +162,8 @@ if [ $force_install -eq 1 -o $need_install -eq 1 ]; then if [ ! -r ${isofile} ]; then - echo -n "Installation CDROM image \"${isofile}\" " - echo "is not readable" + err -n "Installation CDROM image \"${isofile}\" " + err "is not readable" exit 1 fi BOOTDISK=${isofile} --Apple-Mail=_9C1C27D8-519D-4B6F-9C2A-02955E3A8600 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii --Apple-Mail=_9C1C27D8-519D-4B6F-9C2A-02955E3A8600-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 13 19:50:04 2014 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 ESMTPS id 94683F7F for ; Thu, 13 Feb 2014 19:50:04 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0ED271AE8 for ; Thu, 13 Feb 2014 19:50:03 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id z11so7510449lbi.40 for ; Thu, 13 Feb 2014 11:50: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=upfK8dj4j5MsbC7II5c1yCEJIiRcWMi+QGMoX/u0yhA=; b=RZxCLwCMCUHXZ3ZoyLdOJq+R15jy+4oqg/pT21Kjj5L8JNcZri+9/8H273egrKMGOm gfxR1VYfRmzsIY4WkDHKVHQF5UNhfSvFH1VTX1y5kMgVCVYxzwW+vWgaIqwiohPYBs2h rIIW9RNuW3+o39fxFJ95Vl3Iix9siwkTDI2RZ/O4CinUrSCCoM6fOa9eYqx47OC6V3lU 1PpwNcGCDoxiy6V6nxj5omzKgIF2OdXiLYpyOSgj0CjnGMNvrIHSictALnj2FGGzQlkW wtCiOFCFEEXmrUFrO1IMFmkIyHbchC/t0nsqwoTzO8b697FmfxT71ujJEcyxpjoHDLaf IIwQ== MIME-Version: 1.0 X-Received: by 10.112.129.168 with SMTP id nx8mr2102881lbb.37.1392321002049; Thu, 13 Feb 2014 11:50:02 -0800 (PST) Received: by 10.114.65.98 with HTTP; Thu, 13 Feb 2014 11:50:01 -0800 (PST) In-Reply-To: References: <201401171615.51057.Mark.Martinec+freebsd@ijs.si> <275866C0-E379-48BE-BAAD-BF87A307A64E@tamu.edu> <20140119214136.GR86491@e-new.0x20.net> Date: Thu, 13 Feb 2014 13:50:01 -0600 Message-ID: Subject: Re: emulators/petitecloud 0.2.1 available From: Jason Garrett To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 13 Feb 2014 19:50:04 -0000 Trying to build 0.2.5 via your instructions on petitecloud.org I get the following error during make install... ===> Creating users and/or groups. ** Cannot find any information about group `petitecloud' in /usr/ports/GIDs. *** Error code 1 Stop. make: stopped in /usr/ports/emulators/petitecloud Any help is appreciated. On Wed, Jan 22, 2014 at 9:30 PM, Aryeh Friedman wrote: > > This is correct behavior since there are no long lived processes all > > running the rc.d does is do some quick system wide inits needed to run > vm's > > correctly (currently it loads vmm, if_tap and aio and also creates the > > bridge that vm's will be using). This is true for all PetiteCloud > > commands, namely they do whatever action they need to perform and then > die > > (no long living processes if you don't count the hyperv's or tomcat). > > > > > Forgot to mention you will also need a cd image to install from that is > kept in where ever your cdPrefix is (/vms/cds by default but settable in > the settings screen or /usr/local/etc/petitecloud/settings.cfg) > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > 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 Feb 13 20:03:52 2014 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 ESMTPS id 49FFE699 for ; Thu, 13 Feb 2014 20:03:52 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E64B1CA0 for ; Thu, 13 Feb 2014 20:03:52 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so11281374pab.38 for ; Thu, 13 Feb 2014 12:03:51 -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=GE8Pe0Dsmlb8HpQM9UycXX/wy0Q1s2utgF18RbssncA=; b=svI6tlNH5ejW9dKeoZkvvghAmk6+Xeltzu3Kdl2Lkk/D2bkgkHfZiOPRxA91tQrx1+ Hl9m2VFNdHGIPmSfhvAQsPnhCVPm1pDX+sOp3W5px9mk+5FsamxR87qD3ugN9nFBM7n3 cnS2BbP0Y0EiBKfHwbyuhA4ZGFqQLcGV8PXdRnFAsPTuPIoPloRnNR8TMtfBkjCCMhkr Xx8YZ/8U1rjjGDfjkW8r3s94OjdHGsTSsLOOev5//owr+eT+XOruupF+LLwP9oCkClgd CXnclyXCm1WJyYSFaj2l8Fx3LloyEKi9zEbC1njh/v/0qN8p/IRc/xJYJDUUwNNa4ylh qsAg== MIME-Version: 1.0 X-Received: by 10.66.179.143 with SMTP id dg15mr4072706pac.52.1392321831134; Thu, 13 Feb 2014 12:03:51 -0800 (PST) Received: by 10.68.155.38 with HTTP; Thu, 13 Feb 2014 12:03:51 -0800 (PST) In-Reply-To: References: <201401171615.51057.Mark.Martinec+freebsd@ijs.si> <275866C0-E379-48BE-BAAD-BF87A307A64E@tamu.edu> <20140119214136.GR86491@e-new.0x20.net> Date: Thu, 13 Feb 2014 15:03:51 -0500 Message-ID: Subject: Re: emulators/petitecloud 0.2.1 available From: Aryeh Friedman To: Jason Garrett , General discussion about PetiteCloud Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 13 Feb 2014 20:03:52 -0000 Either apply the patch (see site) to a unmodified ports tree or move both UIDs and GIDs from the port dir to /usr/ports .... note the released 0.2.5 we had last night had a small but critical bug the current download fixes it (0.2.6) [it was not possible to create instances with less then all 5 drives slots filled in].... please direct ****ALL**** followups to this to petitecloud-general@lists.petitecloud.nyclocal.net (the subscription link is under resources on the site) On Thu, Feb 13, 2014 at 2:50 PM, Jason Garrett wrote: > Trying to build 0.2.5 via your instructions on petitecloud.org I get the > following error during make install... > > ===> Creating users and/or groups. > ** Cannot find any information about group `petitecloud' in > /usr/ports/GIDs. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/emulators/petitecloud > > Any help is appreciated. > > > On Wed, Jan 22, 2014 at 9:30 PM, Aryeh Friedman wrote: > >> > This is correct behavior since there are no long lived processes all >> > running the rc.d does is do some quick system wide inits needed to run >> vm's >> > correctly (currently it loads vmm, if_tap and aio and also creates the >> > bridge that vm's will be using). This is true for all PetiteCloud >> > commands, namely they do whatever action they need to perform and then >> die >> > (no long living processes if you don't count the hyperv's or tomcat). >> > >> > >> Forgot to mention you will also need a cd image to install from that is >> kept in where ever your cdPrefix is (/vms/cds by default but settable in >> the settings screen or /usr/local/etc/petitecloud/settings.cfg) >> >> >> -- >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org >> _______________________________________________ >> 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" >> > > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 14 12:18:09 2014 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 ESMTPS id 66042BA4 for ; Fri, 14 Feb 2014 12:18:09 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EC1B91142 for ; Fri, 14 Feb 2014 12:18:08 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id e4so398808wiv.5 for ; Fri, 14 Feb 2014 04:18:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Y10UhKdZ+g2TRkDRRYI6kukFkzPngfBbrbMPU02U5mE=; b=dDkGOvrwRmRGEM4A2M1iJMqpcsASMNb36dhPMjajDj1yt9THBqt3rOdLyGazSw1q+y nm5g3FiUOo+lPqIEnP7QYPNkflJ+gcemhC9Ed1IxdmGiZDE7aaP9e44uZWfga/6J0+CH rKZ2tbUayYnjUcML7ZHPH+jkMisnOPhq1ND93Ovy0JpxlT4u5TwqUDsknFAGfwo519Jp mpjhL7DjO/qGCcvrLTTSjpLWjN1yJg0HE/f8MgrCEan0l71xgzTSQwpBpK6rrfYF2nLR IMdpFM5mNSsIiBiBi68o1MPatllc1NP1xhgglJ1LjWNV7t2vhdWsfkSmvXZYOY9usj1D aYNQ== X-Received: by 10.180.188.229 with SMTP id gd5mr1965187wic.54.1392380285915; Fri, 14 Feb 2014 04:18:05 -0800 (PST) Received: from localhost (95-91-232-189-dynip.superkabel.de. [95.91.232.189]) by mx.google.com with ESMTPSA id y18sm3972656wie.11.2014.02.14.04.18.04 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Feb 2014 04:18:05 -0800 (PST) Date: Fri, 14 Feb 2014 13:18:02 +0100 From: Stefan Hajnoczi To: Aryeh Friedman Subject: Re: [Qemu-devel] who should I report this to? Message-ID: <20140214121802.GA17391@stefanha-thinkpad.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: qemu-devel@nongnu.org, "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 12:18:09 -0000 On Sat, Feb 01, 2014 at 10:04:23PM -0500, Aryeh Friedman wrote: > Under kvm (ubuntu 12.04.03 LTS) when logged in via VNC and installing > 10-RELEASE the installer just boots you during the disk initialization > phase. Who should this be reported to? Just came across this email. If you haven't gotten any help for this yet, please report it to Ubuntu. Stefan