From owner-freebsd-virtualization@freebsd.org Sun May 29 21:00:09 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C77A2B54B6E for ; Sun, 29 May 2016 21:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A647D1E20 for ; Sun, 29 May 2016 21:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4TL011q082026 for ; Sun, 29 May 2016 21:00:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201605292100.u4TL011q082026@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 29 May 2016 21:00:09 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 21:00:09 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 202322 | [bhyve,patch] add option to have bhyve write its 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon May 30 07:25:34 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47B1EB5486D for ; Mon, 30 May 2016 07:25:34 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail1.yamagi.org (yugo.yamagi.org [212.48.122.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F8A91FFD; Mon, 30 May 2016 07:25:33 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from [192.168.100.101] (helo=aka) by mail1.yamagi.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1b7HZG-0001tS-Nc; Mon, 30 May 2016 09:25:25 +0200 Date: Mon, 30 May 2016 09:24:49 +0200 From: Yamagi Burmeister To: grehan@freebsd.org Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve graphics support Message-Id: <20160530092449.399f5c4f315d12e1144b49b8@yamagi.org> In-Reply-To: <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org> References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> <20160527104405.GA15808@e-new.0x20.net> <20160527115540.GB15808@e-new.0x20.net> <20160527141557.e2ee91ee437a3893f818c468@yamagi.org> <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 07:25:34 -0000 Hello, > > As far as I know UEFI supports ahci-* boot devices only. For the basic > > UEFI support without GOP the AHCI devices needed to be mapped on slot 3 > > and 4. I don't know if that's still the case. >=20 > Depends on the o/s being booted - if it needs legacy interrupt=20 > support, the only available slots with routing set up are 3/4/5/6. >=20 > UEFI operates in polled-mode so it has no constraints on it's own. Ah okay. That's good to know. At least for the Windows 2016 case. > > I've got working VNC access to a FreeBSD 10.3 VM. My Windows 7 install > > disc starts up, but the mouse is not working. Keystrokes through VNC > > give "atkbd data buffer full" errors. I'll open a new thread for that > > if I can't figure it out. >=20 > XHCI isn't in Windows7 so you can just remove that config line,=20 > pushing mouse input through the PS2 mouse. That was a little bit strange, it seemed like the emulated ps/2 devices just wouldn't work on a Win 7 VM. The "atkbd data buffer full" may be an indication for not delivered interrupts or something like that. After I've rebooted the host things suddenly started to work. Maybe some kind of system inconsistency. It was some 11-CURRENT with about 4 weeks uptime. It may be a good idea to add a note to the Windows installation guide at https://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt that Window 7 requieres AHCI disks with a blocksize if 512 bytes. Otherwise the installation will fail with "Windows Setup could not configure Windows on this computer?s hardware" and Windows Update will bail out with error 0xc8000247. Regards, Yamagi --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB From owner-freebsd-virtualization@freebsd.org Tue May 31 21:03:14 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B3FDB58C21 for ; Tue, 31 May 2016 21:03:14 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34DEB1DB7 for ; Tue, 31 May 2016 21:03:14 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: by mail-oi0-x22d.google.com with SMTP id j1so313209477oih.3 for ; Tue, 31 May 2016 14:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=altometrics.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=UzxvjkLxz6oTqc180l1RhL3kex59uMyWR1zD1lVPZ+w=; b=ei7PGSGzbkgVg3Jeqo57BfbxVOohb2PJErWWwkn2rd7lMbrG0tyXPcJIbUpul/GrKG ZXSerIiVdsgu4kEeYcIz1umnMhRyF7uWtqS3wjctU86QmP8gGfhz8H6tkLRKo0DMU+FM YYjnR9CZwEXSj5tU+P8mzY4rkVX09RVyc8L3c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UzxvjkLxz6oTqc180l1RhL3kex59uMyWR1zD1lVPZ+w=; b=dDIKXI2R6WY1gWLsc01IuHlOp+uO7amUA8sR4jgcXo9m7c11fXnNFzqlVcnDxUeb+F Dmg8tjm7q/72XgjD+jH2NBe76hgYJ7xmF+kRtk6MgL5/qtONITn3EaQSIAWGEwUYdZl/ Fxjm0feceaofAzfbz5Hu21KYqzkmQ7x34b/A8ZsHoZILgsdzw2w+vyOamnuQ3IlO0vqA T8OzYvLU9w4JhVExxaPz2fy3zhDYDhfx+cv74HI9AYNHtHGjGcV6CZF16y7WnKLe5Wu2 0pXPfEZhx7OmOkLrII4C/jpEIRdvtLMT2vZckTN7ck0xULp3x9GH+DURHoWz1Hxlnj8p ZDHA== X-Gm-Message-State: ALyK8tKpCJjsdQnFYahdMaRNs7+90Kf2ZgjDnXmpzB+tUXQ4EpbODRKe8PEpwFfD2Ifh6B23swqDTaru2P6Fhw== X-Received: by 10.202.75.132 with SMTP id y126mr18659591oia.107.1464728593467; Tue, 31 May 2016 14:03:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.245.75 with HTTP; Tue, 31 May 2016 14:02:34 -0700 (PDT) X-Originating-IP: [174.109.43.132] From: Jeff Terrell Date: Tue, 31 May 2016 17:02:34 -0400 Message-ID: Subject: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 21:03:14 -0000 To work around the current inability to mount volumes in FreeBSD docker, I'd like to use a FreeBSD docker image on a non-FreeBSD host. Then I can both run FreeBSD in a docker container and mount a volume in the container, both of which are necessary for my purposes. (For background, I'm trying to do this to extend jsass, the Java SASS compiler [1], to work on FreeBSD. I started a thread documenting this attempt on Github [2].) [1] https://github.com/bit3/jsass [2] https://github.com/bit3/jsass/issues/40 Unfortunately, every FreeBSD image I can find requires a FreeBSD host to run. This requirement is rarely documented, but it is absolute, at least at the moment. For each image matching "freebsd" on Docker Hub, I pulled the image, ran `docker run IMAGE_NAME ls`, and the command produced the output I expected when I ran it on my FreeBSD machine, but not when I ran it on my iMac. (I added comments on Docker Hub to this effect, to hopefully save others some time and spare them some confusion.) I'm acquainted with docker, but I don't know enough to understand why an image would run in a container on one OS but not in a container on another OS. I thought the whole point of docker was that, assuming the image worked at all, it worked regardless of which host you used. So that's an incidental question I have: what's going on here? Is it something particular to FreeBSD's implementation of docker? But my main question is, what can I do to run a FreeBSD image on a non-FreeBSD host? I'm willing to [figure out how to] build my own image if necessary. I just don't want to go to the trouble if it's a non-starter for some reason I don't understand. Solving this problem could, of course, open some avenues for others to discover and use FreeBSD relatively painlessly, so I'm thinking it would be helpful in general to the FreeBSD community. Can somebody point me in the right direction here? Thanks, -- Jeff Terrell, Ph.D. | Chief Technology Officer ALTOMETRICS, Inc. (919) 357-3116 | www.altometrics.com From owner-freebsd-virtualization@freebsd.org Tue May 31 22:07:00 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41215B563BD for ; Tue, 31 May 2016 22:07:00 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 264ED1FA4 for ; Tue, 31 May 2016 22:06:59 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.1.10] (unknown [192.168.1.10]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C4F69D3DB for ; Tue, 31 May 2016 22:06:58 +0000 (UTC) Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org References: From: Allan Jude Message-ID: <42cc8e38-733d-4750-3490-562b241b1b62@freebsd.org> Date: Tue, 31 May 2016 18:06:54 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 22:07:00 -0000 On 2016-05-31 17:02, Jeff Terrell wrote: > To work around the current inability to mount volumes in FreeBSD docker, > I'd like to use a FreeBSD docker image on a non-FreeBSD host. Then I can > both run FreeBSD in a docker container and mount a volume in the container, > both of which are necessary for my purposes. > > (For background, I'm trying to do this to extend jsass, the Java SASS > compiler [1], to work on FreeBSD. I started a thread documenting this > attempt on Github [2].) > > [1] https://github.com/bit3/jsass > [2] https://github.com/bit3/jsass/issues/40 > > Unfortunately, every FreeBSD image I can find requires a FreeBSD host to > run. This requirement is rarely documented, but it is absolute, at least at > the moment. For each image matching "freebsd" on Docker Hub, I pulled the > image, ran `docker run IMAGE_NAME ls`, and the command produced the output > I expected when I ran it on my FreeBSD machine, but not when I ran it on my > iMac. (I added comments on Docker Hub to this effect, to hopefully save > others some time and spare them some confusion.) > > I'm acquainted with docker, but I don't know enough to understand why an > image would run in a container on one OS but not in a container on another > OS. I thought the whole point of docker was that, assuming the image worked > at all, it worked regardless of which host you used. So that's an > incidental question I have: what's going on here? Is it something > particular to FreeBSD's implementation of docker? > > But my main question is, what can I do to run a FreeBSD image on a > non-FreeBSD host? I'm willing to [figure out how to] build my own image if > necessary. I just don't want to go to the trouble if it's a non-starter for > some reason I don't understand. > > Solving this problem could, of course, open some avenues for others to > discover and use FreeBSD relatively painlessly, so I'm thinking it would be > helpful in general to the FreeBSD community. > > Can somebody point me in the right direction here? > > Thanks, > Yes, FreeBSD docker images will require a FreeBSD host. You can't run Mac OS X applications on a Linux box either. It is a different operating system. You may be spoiled by the ability of a FreeBSD host to run some Linux images, via the linux_compat layer. The only way to run a FreeBSD docker image on another OS would be via a VM. I am not that familiar with docker, what do you mean by 'mount of a volume in the docker' -- Allan Jude From owner-freebsd-virtualization@freebsd.org Wed Jun 1 14:53:54 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8658BB60661 for ; Wed, 1 Jun 2016 14:53:54 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 61804133E for ; Wed, 1 Jun 2016 14:53:54 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: by mail-oi0-x22c.google.com with SMTP id w184so31080226oiw.2 for ; Wed, 01 Jun 2016 07:53:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=altometrics.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=36yJWnjLix2I97ia4bF5vnQsVurvxQlbXcGuxXP2vTs=; b=UEU4Pjjo4w0FLqyqDwHTO+eWFHacfv7HFCiIIq7zJupcbU6W5SJiM4BV2/4wPj2T65 ZA2Lfk+iBpetui5e+Ae6Fr68WBkrrahWzjfArE8pikF+PzjOVmkMLnO3fDoDNZWY629d ZOjqJW9juH4FuE01kH/H0SXHnsXNl9yHRTykY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=36yJWnjLix2I97ia4bF5vnQsVurvxQlbXcGuxXP2vTs=; b=gv/JSLeMtvJk+o/oMGuTRhnhkfaa1pu7Wbl5GZWzxuHyQm8w30YzegIWFett5gjmQ1 UMO1ls0zLUtBnahTaN6f7VTLCoLISQJTxbtMPrRNoP7E9MB+ki+XJbnsQfecAIZHy8qm 1C4/M2+iQdvminInVTflmgcw7SnmwVZW5yN2Xc4xhrW6k6KnOLJ0olDJIUkC3nhWhoqA +bJo5vxJIVHHLOX7+lr69/u0MD9Hq51gi7qKmwwFm/3LH7QyPFnvD/U+ysbJ5N1LEN5H Wxfll6JPKJsPOELs2GkJdZA+u18N+bPGwZbjww0QE2Nt9QvxPzH+CBwHAOBzW2mCi5HK uqmQ== X-Gm-Message-State: ALyK8tLc3iCbQ8WIu+NP6oiqUnlOnQsMHFrzhdnpkaOYOS3J6QDOusJjN6RTesnuJV3snjlqHhYJyGLdWS65BQ== X-Received: by 10.157.44.240 with SMTP id e45mr1906892otd.177.1464792833574; Wed, 01 Jun 2016 07:53:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.245.75 with HTTP; Wed, 1 Jun 2016 07:53:14 -0700 (PDT) X-Originating-IP: [174.109.43.132] From: Jeff Terrell Date: Wed, 1 Jun 2016 10:53:14 -0400 Message-ID: Subject: [administrative] 503 error when attempting to subscribe To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:53:54 -0000 I ran into a slight obstacle when I tried to subscribe to this list yesterday. I figured I would document it here, in case anybody cares about it. (And fine with me if nobody does.) I requested subscription through the mailman web interface. I got an email to confirm that I wanted to subscribe. In the email was a link [1] that I could allegedly click to confirm subscription. [1] https://lists.freebsd.org/mailman/confirm/freebsd-virtualization/97272bfc4ed40f86c05133d54728cd7fcdb2db19 When I clicked that link, I got a page that said: > Error 503 Backend fetch failed > > Backend status: Backend fetch failed > > Transaction ID: 143895569 I was able to subscribe by replying to the email, however. -- Jeff Terrell, Ph.D. | Chief Technology Officer ALTOMETRICS, Inc. (919) 357-3116 | www.altometrics.com From owner-freebsd-virtualization@freebsd.org Wed Jun 1 15:54:44 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF1AAB61EE8 for ; Wed, 1 Jun 2016 15:54:44 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies, LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DF131BCC for ; Wed, 1 Jun 2016 15:54:44 +0000 (UTC) (envelope-from lidl@pix.net) Received: from torb.pix.net (torb.pix.net [192.168.16.32]) (authenticated bits=0) by hydra.pix.net (8.15.2/8.15.2) with ESMTPA id u51Fsg49011012; Wed, 1 Jun 2016 11:54:42 -0400 (EDT) (envelope-from lidl@pix.net) To: freebsd-virtualization@freebsd.org References: Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts From: Kurt Lidl Message-ID: Date: Wed, 1 Jun 2016 11:54:42 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 15:54:44 -0000 > I'm acquainted with docker, but I don't know enough to understand > why an image would run in a container on one OS but not in a > container on another OS. I thought the whole point of docker was > that, assuming the image worked at all, it worked regardless of which > host you used. So that's an incidental question I have: what's going > on here? Is it something particular to FreeBSD's implementation of > docker? Docker provides a "container" for running a particular application. It's similar to a FreeBSD jail, in that the running process(es) in the container cannot interact with the rest of the system, except at the system call level, and where the host running docker has mapped any files into the docker filesystem namespace. What isn't really explained in so many words -- the container uses the system calls from the hosting computer to evaluate anything that it needs the "kernel" to do. So your "FreeBSD docker" image, when run on a Linux machine, is attempting to make FreeBSD system calls into the Linux kernel. > But my main question is, what can I do to run a FreeBSD image on a > non-FreeBSD host? I'm willing to [figure out how to] build my own > image if necessary. I just don't want to go to the trouble if it's > a non-starter for some reason I don't understand. You'd have to use some other solution to provide a "FreeBSD system call interface" to your FreeBSD docker image. The recent import of Linux 64bit emulation in FreeBSD allows for running stock "docker" images on FreeBSD, because there's now a shim that translates Linux system calls to FreeBSD ones. On the Mac, they have shims that provide filesystem access to the Mac's filesystems, and a virtualized machine using the xhyve stuff, providing the Linux system call interface. Make no mistake about, docker is Linux inside. If you want to run FreeBSD inside a virtual machine, try the xhyve stuff on the Mac, or under KVM on Linux. -Kurt From owner-freebsd-virtualization@freebsd.org Wed Jun 1 16:05:26 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F2DFB61223 for ; Wed, 1 Jun 2016 16:05:26 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCA8A133E for ; Wed, 1 Jun 2016 16:05:25 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: by mail-oi0-x235.google.com with SMTP id j1so34619175oih.3 for ; Wed, 01 Jun 2016 09:05:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=altometrics.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=NBFJX8MSvnxeZr64o819mma2xTLUlgr+g+ia7QU003k=; b=Cnig+NF9i3GsaJA/RaF26bI0kqqQ0Wq58+9x/BGYOPsyZBEtVXSXATJ/YR/yNEe8Yj GVGTxYWXtuLK2yxt1SGI9SEzfDb9B5Q+GN2w0splCzJXrgtRsrBkTCsYW4BABqmjFvfm sn+qA9+jn56hqlMiOxkBXa0RRIxiUv4VXCkgI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NBFJX8MSvnxeZr64o819mma2xTLUlgr+g+ia7QU003k=; b=SLn9tJ5BFiVaun8qXppiTy+oQzUPsdF+1wm2g0YdAp+YZjanRbvKhCYRenjn08B84T y8W/Y3lXIVzAp5SQGutqR/oa4wNAO7F3AVItVxTpYgX5nkKbODLollqAiJdDezeHxRnJ 3SQjXNo9+z70r8OAejnplQ6W7NpyGX5vsm4n0BZIhQ7FIPxK78glsPuW74a1WYxNsUoA T8I/LTOud36tpxhzDNCKRuQ0VZt58X0Bywgztmqm48Y6P6HS8RLThUlg3ZOlkzvPZdmJ 3FSI+QOXOh6QCfJOozxxKDAqP0nTBf82evXDPgqWDHw4jx0qP3NBp1C/JymtGW2FFzqb nWJA== X-Gm-Message-State: ALyK8tKo+aJuNB6fYhypHFTwJkURv7PBt2NTdSEWHvaPgfy84CWYzKtAS5cSi6SJK0mNZgp5oJvmyCwxI5HdDg== X-Received: by 10.202.84.199 with SMTP id i190mr14480714oib.78.1464797125039; Wed, 01 Jun 2016 09:05:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.245.75 with HTTP; Wed, 1 Jun 2016 09:04:44 -0700 (PDT) X-Originating-IP: [174.109.105.28] In-Reply-To: References: From: Jeff Terrell Date: Wed, 1 Jun 2016 12:04:44 -0400 Message-ID: Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 16:05:26 -0000 On Tue, May 31, 2016 at 6:08 PM, Kurt Lidl wrote: > What isn't really explained in so many words -- the container uses the > system calls from the hosting computer to evaluate anything that it > needs the "kernel" to do. So your "FreeBSD docker" image, when run on > a Linux machine, is attempting to make FreeBSD system calls into the > Linux kernel. > > You'd have to use some other solution to provide a "FreeBSD system call interface" to your FreeBSD docker image. > > The recent import of Linux 64bit emulation in FreeBSD allows for running > stock "docker" images on FreeBSD, because there's now a shim that > translates Linux system calls to FreeBSD ones. > > On the Mac, they have shims that provide filesystem access to the Mac's filesystems, and a virtualized machine using the xhyve stuff, providing > the Linux system call interface. > > Make no mistake about, docker is Linux inside. > > If you want to run FreeBSD inside a virtual machine, try the xhyve stuff > on the Mac, or under KVM on Linux. > > -Kurt Ah, now I get it. I didn't realize that system calls were the interface between the docker images in a container and the host. But that definitely explains why the FreeBSD images won't work apart from a FreeBSD host. So it looks like, if I'm committed to docker, I could run FreeBSD inside a KVM inside a container on Linux. Then others who might be interested in FreeBSD could play around with it on their Linux hosts via docker. And I suppose, since I need to mount a volume, I'd need to mount it both into the docker container and, from there, through KVM to FreeBSD. Not fun, but plausible at least. Thanks very much for the explanation, Kurt! -- Jeff Terrell, Ph.D. | Chief Technology Officer ALTOMETRICS, Inc. (919) 357-3116 | www.altometrics.com From owner-freebsd-virtualization@freebsd.org Wed Jun 1 16:31:22 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67DFDB61B32 for ; Wed, 1 Jun 2016 16:31:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CFFE1D07 for ; Wed, 1 Jun 2016 16:31:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (localhost [127.0.0.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPS id 3FD7D125EE5 for ; Wed, 1 Jun 2016 09:31:21 -0700 (PDT) Received: from [192.168.41.105] (unknown [72.34.113.100]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.nomadlogic.org (Postfix) with ESMTPSA id 38A3D125EBA for ; Wed, 1 Jun 2016 09:31:21 -0700 (PDT) Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org References: From: Pete Wright Message-ID: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> Date: Wed, 1 Jun 2016 09:31:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 16:31:22 -0000 On 06/01/2016 09:04 AM, Jeff Terrell wrote: > > So it looks like, if I'm committed to docker, I could run FreeBSD > inside a KVM inside a container on Linux. Then others who might be > interested in FreeBSD could play around with it on their Linux hosts > via docker. why?!? why put yourself and your co-workers through that much hell to test out freebsd. having worked on docker (and before that other linux jail-like systems) i never understood the thought process that forces everyone to try to fit all use-cases under one umbrella like this. if you have some workflow that is totally docker depedent then just run freebsd+docker and be done with it. you'll have some linux docker nodes, and some freebsd docker nodes and your on your way. or as mentioned earlier - there are all sorts of para-virtualization technologies that allow one to run freebsd ontop of a linux (or mac) hypervisor. the benefit with either of these approaches is that you remove about 50 hoops and support headaches and probably learn a bit more about how to manage heterogeneous environments along the way. -pete -- Pete Wright pete@nomadlogic.org From owner-freebsd-virtualization@freebsd.org Thu Jun 2 20:51:01 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5626FB65982 for ; Thu, 2 Jun 2016 20:51:01 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26A471D6D for ; Thu, 2 Jun 2016 20:51:01 +0000 (UTC) (envelope-from jeff@altometrics.com) Received: by mail-oi0-x229.google.com with SMTP id j1so96672593oih.3 for ; Thu, 02 Jun 2016 13:51:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=altometrics.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=E501FlfyFfl9ImXDT9dzq1XxU8hySzwhceOhMW/5fUQ=; b=LNqvrFG/8HpckSBCtmMXkM7QQcZlZmEKVW6fbBpaMM2ypzxan6OKSdgVWI9azqO+7h Lb/hnLX3DCNg6Ayp0lfea/gTtsS4MB9oCc88UqvfpOQqL6Lcc1p8PjSYx8mhsVS/jlU6 +hhQIVCKcGcv9HhHMglfThQ8glMpLCdijrocg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=E501FlfyFfl9ImXDT9dzq1XxU8hySzwhceOhMW/5fUQ=; b=b++keuWLJBHKjwKVEButBKBo3QDo1XMuiEqI9KsKyMWdznj3hbI6noYHuFTMg2G+k0 jloEmHIFwAsyo3etJpQJXBnOz5FZdtblH2ms22v6QtGjrwazt6vW2ATsaiR8MqskYjFj xxUp9ObCbEFLuPpHdLuk6nOaxFPNt9wqZzMZSn/ivdRUapWezy56wHv5hVroCHm8ekj2 Mgyans7uH7rE/GjlUk/HmUYktvEX52xZj5xBe6MvALhozdW8IQTc2ZcxCpk+ER1la0tu pDTC5r+TUoq45wUM1hewfNF1nICdrDhoMOE1OgKiqyorqLXnEPER9CpXQdt4MjX0wK2M 6EmQ== X-Gm-Message-State: ALyK8tKncMfzQ8vMTt2Y3C0EdTEiNKuADp6zrW0S0l+c7OmQsM7iaxe8fwTnF91V2h4goKKDvzel9DCcwruoDA== X-Received: by 10.157.26.22 with SMTP id a22mr81852ote.5.1464900660012; Thu, 02 Jun 2016 13:51:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.245.75 with HTTP; Thu, 2 Jun 2016 13:50:19 -0700 (PDT) X-Originating-IP: [174.109.43.132] In-Reply-To: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> References: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> From: Jeff Terrell Date: Thu, 2 Jun 2016 16:50:19 -0400 Message-ID: Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 20:51:01 -0000 On Wed, Jun 1, 2016 at 12:31 PM, Pete Wright wrote: >> So it looks like, if I'm committed to docker, I could run FreeBSD >> inside a KVM inside a container on Linux. Then others who might be >> interested in FreeBSD could play around with it on their Linux hosts >> via docker. > > why?!? Thanks for the challenge. (Seriously.) I don't want to add pain to myself and others needlessly. :-) > why put yourself and your co-workers through that much hell to test out > freebsd. having worked on docker (and before that other linux jail-like > systems) i never understood the thought process that forces everyone to t= ry > to fit all use-cases under one umbrella like this. > > if you have some workflow that is totally docker depedent then just run > freebsd+docker and be done with it. you'll have some linux docker nodes, > and some freebsd docker nodes and your on your way. > > or as mentioned earlier - there are all sorts of para-virtualization > technologies that allow one to run freebsd ontop of a linux (or mac) > hypervisor. the benefit with either of these approaches is that you remo= ve > about 50 hoops and support headaches and probably learn a bit more about = how > to manage heterogeneous environments along the way. I think these are great points. And if it were up to me, I can imagine this would be a better approach in many respects. But alas, this is for a project that I don't control. They've chosen docker, and I'm trying to fit a FreeBSD option in among the mix as painlessly as possible (for them). The fuller details are here, if you're interested. [1] [1] https://github.com/bit3/jsass/issues/40 (Indeed, I don't think this problem really requires virtualization at all. It's just that nobody has solved my problem in a portable language yet. The Java software [2], which I'm using indirectly from the Clojure software [3], doesn't solve the problem directly but instead uses JNA [4] to effectively shell out to a library, libsass.so [5].) [2] https://github.com/bit3/jsass/ [3] https://github.com/deraen/sass4clj [4] https://en.wikipedia.org/wiki/Java_Native_Access [5] http://sass-lang.com/libsass That said, if one did create such a monstrosity as a docker image containing a KVM hypervisor containing a FreeBSD VM=E2=80=94and figured out how to pass commands and mount volumes from docker -> FreeBSD via KVM=E2=80=94that could be a nice "evangelism" move to give the masses who u= se docker a cheap and easy way to try out FreeBSD. Plus, such an image could be used to provide FreeBSD support for other software as well. Maybe I'll add that to my "one of these days" list... --=20 Jeff Terrell, Ph.D. | Chief Technology Officer ALTOMETRICS, Inc. (919) 357-3116 | www.altometrics.com From owner-freebsd-virtualization@freebsd.org Thu Jun 2 21:05:32 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F29B1B65D84 for ; Thu, 2 Jun 2016 21:05:32 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5CDFC1729 for ; Thu, 2 Jun 2016 21:05:32 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Thu, 02 Jun 2016 23:04:18 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B16B3251-C280-4512-A7C1-46C6D3C06B7B.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Thu, 02 Jun 2016 23:04:12 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Running FreeBSD docker images on non-FreeBSD hosts From: Rainer Duffner In-Reply-To: Date: Thu, 2 Jun 2016 23:04:10 +0200 Cc: freebsd-virtualization@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5E648734-37C3-48EF-B78F-A58E6E7B0C78@ultra-secure.de> References: <94b39ea0-5b80-6d7b-044c-2810d3026761@nomadlogic.org> To: Jeff Terrell X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=13 total_conn=3 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 237, bad: 1, connections: 404, history: 236, asn_score: 178, asn_connections: 199, asn_good: 179, asn_bad: 1, pass:asn, relaying X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 21:05:33 -0000 > Am 02.06.2016 um 22:50 schrieb Jeff Terrell : >=20 >=20 > That said, if one did create such a monstrosity as a docker image > containing a KVM hypervisor containing a FreeBSD VM A guy at work ran a chef-server on Ubuntu in a headless VirtualBox in a = Solaris 10 Zone. He really liked Solaris. From owner-freebsd-virtualization@freebsd.org Sat Jun 4 14:35:24 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F39B7B6A4F7 for ; Sat, 4 Jun 2016 14:35:24 +0000 (UTC) (envelope-from rowley.evan@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA9CF1CD5 for ; Sat, 4 Jun 2016 14:35:24 +0000 (UTC) (envelope-from rowley.evan@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id g64so53057635pfb.2 for ; Sat, 04 Jun 2016 07:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=yGRrbuWKpnjggR+BN0gHareKAmvcGCnSOFhMlcXqCIU=; b=KJCLCk61uG/Fx5a7JajCnDahfGYd09Kdpzmi62KpGHLmpkfQR1q8HmMistNDdsxURM QpRsxK+9qTiVfpt9gQEUdJq6dmhnw6rn8gK9k4GYdOoqVFdZ7k9OONkLMeDXLd+//w+P OiubyOxlmlSoGXUA/DHLP7uA85ITOEASjH6dbWpA+Q5kjt1JzdKaBrJkA60Yoharlbhv 6uDYFWrVcqebnbNF8WmMqNs6fv5zQTIFqxPm0mhEgchWhJHMG1t7qCxSohEEF2zD4V1C 2oX/Oujya0bvTcLNh4kkAiVsMiD/7fnCIE9ljH9DioexvPiAa5p+iZbSUsx30Dq1wEWF QkDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yGRrbuWKpnjggR+BN0gHareKAmvcGCnSOFhMlcXqCIU=; b=gutXxIcoChdIjjd1EBQGWgzhet9mnTxJiBaTMe1hUxwsoUvWK8hDj3WxZqt5wrdspH K1CyNyhXSFhjGU9PdZc37biCz3g8FQOfPwUg1z6GYREUcMvJLZ/HTM9wl5Zs/V7YsuAV 5abpcPf8BJ0MXlKqruXNhwi/vsUquO08fC0MxNDnYDYalVhSX+VSbwn2Zm7wKM2U3XKB xfxMAORmLnsaWGH8U2iP3HvUY3xNsEZMq4LLGHJgEe2h1CcNAPu8HPjxKgNVGcWg2vNp BnhSKQw7Q1K/U9+iCFP+IzTyMNFzFCsGTPnL+Qys8IvLF8ZS7j/ujg5BNqseFn/eW0K3 lcIA== X-Gm-Message-State: ALyK8tJ4WHOctxgOKquqRfc6VKdOQHBBl1HieWCfOed6ZKT+n8XtcfgFMs+A/FDYLjVgmJ4DoXrVSonqunSfPg== X-Received: by 10.98.52.65 with SMTP id b62mr4102779pfa.40.1465050924076; Sat, 04 Jun 2016 07:35:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.75.225 with HTTP; Sat, 4 Jun 2016 07:35:23 -0700 (PDT) From: Evan Rowley Date: Sat, 4 Jun 2016 10:35:23 -0400 Message-ID: Subject: a bhyve and Windows Server 2012R2 story To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 14:35:25 -0000 I've booted my first Windows Server 2012R2 VM in bhyve. It took about 1 day's setup but I finally have it working. My notes below detail a couple pitfalls and things which I did differently than described in online references I used. The further I progressed in this, the more I realized that the directions I started from are based on directions from other places on the net. Started here: https://jameslodge.com/freebsd-bhyve-hypervisor-running-windows-server-2012-r2-standard/ Discovered this: https://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt And this: https://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt Finally, saw this: https://wiki.freebsd.org/bhyve/Windows Anyways, my machine is TRUEOS 11.0-CURRENTMAY2016 [root@true11] ~# uname -a FreeBSD true11 11.0-CURRENTMAY2016 FreeBSD 11.0-CURRENTMAY2016 #19 5bab0d2(master): Fri May 6 17:56:25 UTC 2016 root@devastator:/usr/obj/usr/src/sys/GENERIC amd64 CPU is AMD 6366 HE Motherboard is SuperMicro H8DGU-F In the guide, the p7zip-9.38.1_2 package is used. Here is the latest version that I installed: [root@true11] /mnt/vm0/ds0/iso# pkg info | grep 7z p7zip-15.14 File archiver with high compression ratio Unfortunately, it seems this version of 7z was not able to extract the UDF ISO correctly. Also, the version on this TrueOS11 machine required a different syntax to specify the output folder, compared to the syntax shown in the link above. Many error messages have been omitted, but here is basically what happened: [root@true11] /mnt/vm0/ds0/iso# //usr/local/bin/7z x msdn/en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso -o{win2012iso} .... ERROR: Data Error : support/logging/setupcletw.dll ERROR: Data Error : support/logging/setupetw.dll ERROR: Data Error : support/logging/setupugcetw.dll ERROR: Data Error : support/logging/sysprepetw.dll ERROR: Data Error : support/logging/windeployetw.dll ERROR: Data Error : support/logging/winsetupetw.dll ERROR: Data Error : support/samples/headlessunattend.xml Sub items Errors: 2075 Archives with Errors: 1 Open Errors: 1 Sub items Errors: 2075 ^ this is the output For each of the files that "ERROR: Data Error" was shown, their z7 extracted contents were 0 bytes in size. Here is an example of the last file's word count: [root@true11] /mnt/vm0/ds0/iso# wc win2012iso/support/samples/headlessunattend.xml 0 0 0 win2012iso/support/samples/headlessunattend.xml I decided to try extraction on Windows using graphical 7zip. The version my computer had installed was 15.06. It worked. Here is the word count for the same file, computed in Cygwin: ejr@win7box1 ~ $ wc /cygdrive/c/Users/ejr/Downloads/Win2012R2/support/samples/headlessunattend.xml 108 301 6475 /cygdrive/c/Users/ejr/Downloads/Win2012R2/support/samples/headlessunattend.xml I also added NetKVM drivers from this version virtio-win-0.1.102.iso, not virtio-win-0.1.96.iso as was specified in the guide. After editing the set files on my Windows machine according to the guide, I transferred the files back to my TrueOS 11 machine using smbclient. The mkisofs command to create the new ISO worked flawlessly. I decided to use the 2016 version of the UEFI loader: https://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20160526.fd Here is the command I used to boot the VM: bhyve \ -c 1 \ -s 0,hostbridge \ -s 3,ahci-hd,/dev/zvol/vm0/ds0/test/w2012R2-0/disk0 \ -s 4,ahci-cd,/mnt/vm0/ds0/iso/Win2012R2.iso \ -s 10,virtio-net,tap0 \ -s 31,lpc -l com1,/dev/nmdm0A \ -l bootrom,/mnt/vm0/ds0/test/w2012R2-0/BHYVE_UEFI_20160526.fd \ -m 2G -H \ -w w2012R2-0 My VM had a problem. It did boot and the SAC channels did start - but somewhere after WIMApplyImage message was displayed in the SACSetupAct - the VM would hang and top would show the bhyve process at 99% WCPU. I destroyed the VM after it hanged like this for 1 hour. It took some guessing, but eventually I recalled reading somewhere - possibly on a KVM/QEMU/Xen wiki page - that IOMMU is needed for more than 1 core. I suspected that this machine's IOMMU was disabled because I've set the SuperMicro BIOS to Optimized Defaults a couple times before and noticed that IOMMU would get turned off. I couldn't recall if I had re-enabled it. Rather than reboot the machine and set IOMMU to Enabled, I decided to re-launch the bhyve VM with only 1 core. This way I was able to compete the installation. Later, enabling IOMMU and relaunching the VM with 2 cores worked. I had difficulty at first with the network configuration. TrueOS has ipfw enabled and I suspect it was originally blocking my RDP traffic. Also, I did not have any successful network connections before I set and loaded what's described in 21.7.7 Persistent Configuration: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html At first, I attempted to RDP to an IP I had assigned from the SAC channel using the i <#> command. This never worked and I am not sure why. Eventually, I created a CMD channel, then used ipconfig to determine that Windows had leased a different IP via DHCP. Using RDP to reach the DHCP IP worked! Oddly, I did not see the static IP I had set in SAC updated with the DHCP one - but I checked later, and it was updated. I'm new to SAC and maybe this is just one of it's quirks. Not a FreeBSD problem in any case, but perhaps a stumbling block others on freebsd-virtualization may encounter. -- - EJR From owner-freebsd-virtualization@freebsd.org Sat Jun 4 15:39:44 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9910BB6A149 for ; Sat, 4 Jun 2016 15:39:44 +0000 (UTC) (envelope-from James@Lodge.me.uk) Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0134.outbound.protection.outlook.com [157.55.234.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAF921C8A for ; Sat, 4 Jun 2016 15:39:42 +0000 (UTC) (envelope-from James@Lodge.me.uk) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gavinlodge.onmicrosoft.com; s=selector1-Lodge-me-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=TgTSBU9bgErp30MfrtvNw6gpazJkWk+FngrxdMuVjUk=; b=Uz/tA7wmQxo9i7+CNrp+usaYsgVU+f6NGANuIGcxbZ/VF3VlneDsDhgKlcgep9emZINE5V2UBadH3ZeiT/dCzHEGJz0AbsJwgHeL+wKtPGx9TFOTxoCLkaX9Ta3M12LHNTR5OZSZowdAdPft22EsoHrE2zn2ldnAkrdvOBLM56I= Received: from DB5PR06MB1718.eurprd06.prod.outlook.com (10.165.213.16) by DB5PR06MB1719.eurprd06.prod.outlook.com (10.165.213.17) with Microsoft SMTP Server (TLS) id 15.1.517.2; Sat, 4 Jun 2016 14:53:59 +0000 Received: from DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) by DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) with mapi id 15.01.0511.010; Sat, 4 Jun 2016 14:53:59 +0000 From: James Lodge To: Evan Rowley , "freebsd-virtualization@freebsd.org" Subject: Re: a bhyve and Windows Server 2012R2 story Thread-Topic: a bhyve and Windows Server 2012R2 story Thread-Index: AQHRvm5cYjPFrwmhNkWb09Te2Bb6VZ/ZY4fF Date: Sat, 4 Jun 2016 14:53:59 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=Lodge.me.uk; x-originating-ip: [25.165.200.132] x-ms-office365-filtering-correlation-id: 9a83fe90-ce9a-40eb-01ba-08d38c880fc2 x-microsoft-exchange-diagnostics: 1; DB5PR06MB1719; 6:PLruay9woD+WS7fJqeeufXVa30hAzFoKmxnVlXQovC/HU9TKP+hNGAw8OjRTrZNZWQarf6juvH4+xlM5xujLPP2+TGEaPcyXHfnGVBLHaevtZYfcJgagk61uB7Xj66hCha6WJF8Wu/m3nxLNGmOW0ujwQkbKNzr+3Q1L0kFQcNviWt4OmAIKoPyagl9M3aPFsSUm1oKDODYw7QSVrDKglQH7ur1jUtn4LKYrOa3HDuAzYH5OnAgVO8MB+D1GPe5OoPcZgL28DSLhcmnCqXNQZBATFjNtIe4KWkEWJdUxkidL5uPSvGeg13JjTDfUQzgQ; 5:ZQ/m6O7Cg3+IoM8ZEgMzumhqa3DZjkmqj9p0y2Hs8m3pDGLeLRwFzW5XjoqW81I2d53htrWbv4ZOQAMdMfognTTXWsR/KJPJ9teKySfUrcQudJR88rCZKj5YOI7YijTYWHOD1kbT94FZkjT0drJO+A==; 24:5xBrNybtAKrIid2Immr9ug648yvLhEnyVmRz4z+fylEIiLvKo+oTF12/fpp3QMei120XUON8RvZxS1zG/FIW9E3A7f3x+Rf3p4opz02qQYE=; 7:YVy17LhlV0qQlFj20bSQZLh9S5Ep5u9U7N8sZ1/EQzMdHXTlFYGiTHBAc3tNyv2sUJw6VT6O/5537B5KOVkljinBhr0F+oykhfg09bYT5npCqRsMyeTNkEUqQDKASVMyFgr+vvUPtw4wEDwnI1cAg9zwGSPOB8GYhwJVtdT0OGLw8FlmaNiugYpUufZ+hjT+KBA6Pc1L3YovBXThfsHyZ1fMpxn8cHbR5s7Z34biTZY= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB1719; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(209352067349851)(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040130)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041072)(6043046); SRVR:DB5PR06MB1719; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB1719; x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(51914003)(5004730100002)(5008740100001)(74316001)(10400500002)(87936001)(575784001)(86362001)(102836003)(5003600100002)(3846002)(6116002)(8676002)(81166006)(2906002)(5002640100001)(11100500001)(106116001)(586003)(8936002)(3660700001)(3280700002)(9686002)(76576001)(66066001)(19580395003)(19580405001)(54356999)(50986999)(92566002)(76176999)(107886002)(2950100001)(2900100001)(80792005)(5001770100001)(2501003)(19627405001)(77096005)(189998001)(15975445007)(33656002)(122556002)(19617315012)(16236675004)(74482002)(19625215002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR06MB1719; H:DB5PR06MB1718.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; CAT:NONE; LANG:en; CAT:NONE; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: Lodge.me.uk X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2016 14:53:59.4883 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ded56ae9-7c77-4cf6-bbfd-39e6a505742d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR06MB1719 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 15:39:44 -0000 I've booted my first Windows Server 2012R2 VM in bhyve. It took about 1 day's setup but I finally have it working. My notes below detail a couple pitfalls and things which I did differently than described in online references I used. The further I progressed in this, the more I realized that the directions I started from are based on directions from other places on the net. Started here: https://jameslodge.com/freebsd-bhyve-hypervisor-running-windo= ws-server-2012-r2-standard/ Discovered this: https://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt And this: https://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.= txt Finally, saw this: https://wiki.freebsd.org/bhyve/Windows Anyways, my machine is TRUEOS 11.0-CURRENTMAY2016 [root@true11] ~# uname -a FreeBSD true11 11.0-CURRENTMAY2016 FreeBSD 11.0-CURRENTMAY2016 #19 5bab0d2(master): Fri May 6 17:56:25 UTC 2016 root@devastator:/usr/obj/usr/src/sys/GENERIC amd64 CPU is AMD 6366 HE Motherboard is SuperMicro H8DGU-F In the guide, the p7zip-9.38.1_2 package is used. Here is the latest version that I installed: [root@true11] /mnt/vm0/ds0/iso# pkg info | grep 7z p7zip-15.14 File archiver with high compression ratio Unfortunately, it seems this version of 7z was not able to extract the UDF ISO correctly. Also, the version on this TrueOS11 machine required a different syntax to specify the output folder, compared to the syntax shown in the link above. Many error messages have been omitted, but here is basically what happened: [root@true11] /mnt/vm0/ds0/iso# //usr/local/bin/7z x msdn/en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso -o{win2012iso} .... ERROR: Data Error : support/logging/setupcletw.dll ERROR: Data Error : support/logging/setupetw.dll ERROR: Data Error : support/logging/setupugcetw.dll ERROR: Data Error : support/logging/sysprepetw.dll ERROR: Data Error : support/logging/windeployetw.dll ERROR: Data Error : support/logging/winsetupetw.dll ERROR: Data Error : support/samples/headlessunattend.xml Sub items Errors: 2075 Archives with Errors: 1 Open Errors: 1 Sub items Errors: 2075 ^ this is the output For each of the files that "ERROR: Data Error" was shown, their z7 extracted contents were 0 bytes in size. Here is an example of the last file's word count: [root@true11] /mnt/vm0/ds0/iso# wc win2012iso/support/samples/headlessunattend.xml 0 0 0 win2012iso/support/samples/headlessunattend.xml I decided to try extraction on Windows using graphical 7zip. The version my computer had installed was 15.06. It worked. Here is the word count for the same file, computed in Cygwin: ejr@win7box1 ~ $ wc /cygdrive/c/Users/ejr/Downloads/Win2012R2/support/samples/headlessunat= tend.xml 108 301 6475 /cygdrive/c/Users/ejr/Downloads/Win2012R2/support/samples/he= adlessunattend.xml I also added NetKVM drivers from this version virtio-win-0.1.102.iso, not virtio-win-0.1.96.iso as was specified in the guide. After editing the set files on my Windows machine according to the guide, I transferred the files back to my TrueOS 11 machine using smbclient. The mkisofs command to create the new ISO worked flawlessly. I decided to use the 2016 version of the UEFI loader: https://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20160526.fd Here is the command I used to boot the VM: bhyve \ -c 1 \ -s 0,hostbridge \ -s 3,ahci-hd,/dev/zvol/vm0/ds0/test/w2012R2-0/disk0 \ -s 4,ahci-cd,/mnt/vm0/ds0/iso/Win2012R2.iso \ -s 10,virtio-net,tap0 \ -s 31,lpc -l com1,/dev/nmdm0A \ -l bootrom,/mnt/vm0/ds0/test/w2012R2-0/BHYVE_UEFI_20160526.fd \ -m 2G -H \ -w w2012R2-0 My VM had a problem. It did boot and the SAC channels did start - but somewhere after WIMApplyImage message was displayed in the SACSetupAct - the VM would hang and top would show the bhyve process at 99% WCPU. I destroyed the VM after it hanged like this for 1 hour. It took some guessing, but eventually I recalled reading somewhere - possibly on a KVM/QEMU/Xen wiki page - that IOMMU is needed for more than 1 core. I suspected that this machine's IOMMU was disabled because I've set the SuperMicro BIOS to Optimized Defaults a couple times before and noticed that IOMMU would get turned off. I couldn't recall if I had re-enabled it. Rather than reboot the machine and set IOMMU to Enabled, I decided to re-launch the bhyve VM with only 1 core. This way I was able to compete the installation. Later, enabling IOMMU and relaunching the VM with 2 cores worked. I had difficulty at first with the network configuration. TrueOS has ipfw enabled and I suspect it was originally blocking my RDP traffic. Also, I did not have any successful network connections before I set and loaded what's described in 21.7.7 Persistent Configuration: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html At first, I attempted to RDP to an IP I had assigned from the SAC channel using the i <#> command. This never worked and I am not sure why. Eventually, I created a CMD channel, then used ipconfig to determine that Windows had leased a different IP via DHCP. Using RDP to reach the DHCP IP worked! Oddly, I did not see the static IP I had set in SAC updated with the DHCP one - but I checked later, and it was updated. I'm new to SAC and maybe this is just one of it's quirks. Not a FreeBSD problem in any case, but perhaps a stumbling block others on freebsd-virtualization may encounter. -- - EJR _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" Hi Evan, Thanks for the information, I will look to update my post with your finding= s to hopefully make it easier for others to running Windows under Bhyve. James From owner-freebsd-virtualization@freebsd.org Sat Jun 4 16:41:14 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36C9DB6A9E0 for ; Sat, 4 Jun 2016 16:41:14 +0000 (UTC) (envelope-from James@Lodge.me.uk) Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0129.outbound.protection.outlook.com [157.55.234.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8854816EA; Sat, 4 Jun 2016 16:41:12 +0000 (UTC) (envelope-from James@Lodge.me.uk) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gavinlodge.onmicrosoft.com; s=selector1-Lodge-me-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=B6KSjq0q2frVivzXdkfjfmz1RlM77tCMfYymwmzjllY=; b=bYtQOzlLjV90YkNsifhnxAAQanx2ub5Wet+6ODoUu3qIIH2gRVTQGfHR9YfzpkciAXU/LvW/dXR/VB6sCzhsawXBbMqJ841brtY3jeH1qsTA5eIZ0QpfiXvDGAYyrdelni88Rmi4rBqjw8ztCvus3py26WsZbyTyL/HamkeMaZw= Received: from DB5PR06MB1718.eurprd06.prod.outlook.com (10.165.213.16) by DB5PR06MB1718.eurprd06.prod.outlook.com (10.165.213.16) with Microsoft SMTP Server (TLS) id 15.1.511.6; Sat, 4 Jun 2016 16:41:04 +0000 Received: from DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) by DB5PR06MB1718.eurprd06.prod.outlook.com ([10.165.213.16]) with mapi id 15.01.0511.010; Sat, 4 Jun 2016 16:41:04 +0000 From: James Lodge To: "grehan@freebsd.org" CC: "freebsd-virtualization@freebsd.org" Subject: Re: bhyve graphics support Thread-Topic: bhyve graphics support Thread-Index: AQHRt/KG0yvznyLwNEaEVF7x4/Wwz5/MmX0AgAAHlwCAAAxnAIAABauAgAAxEoCABDSVgIAIczGO Date: Sat, 4 Jun 2016 16:41:04 +0000 Message-ID: References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> <20160527104405.GA15808@e-new.0x20.net> <20160527115540.GB15808@e-new.0x20.net> <20160527141557.e2ee91ee437a3893f818c468@yamagi.org> <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org>, <20160530092449.399f5c4f315d12e1144b49b8@yamagi.org> In-Reply-To: <20160530092449.399f5c4f315d12e1144b49b8@yamagi.org> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=Lodge.me.uk; x-originating-ip: [25.165.200.132] x-ms-office365-filtering-correlation-id: b6ddb38a-75c6-4887-e44d-08d38c970552 x-microsoft-exchange-diagnostics: 1; DB5PR06MB1718; 5:Nvqprdf4DiPmGXRtKZGSquRmtLuR2Xy7YnC3l5CajOQyyDf9DcSzY5Ss4Nh/xuVQMTmOoBudv+GpLoEZvvixxJCMPKC0trM7nzyF4PzF0iy7SHXmFHDAg48XhwPGEsQfmF7+53VezFg+4ea2b3verA==; 24:39lfRHDfeALnm4bdVMnRzHG1d9hCMCTkBdyj8DkR9dSuUTF+R5Bl7oGPJJB5bfh5Vc9117Jz1rJb6u11TNFPb1Lh3xImoLuF5WPtGU3Ez2o=; 7:rC+SLUSShCV+M1bSj40pGVN/lix/0Ly4hCrLYPooWaWwkD6RIKpmOMUirJyN2GYMpE6+VH9qSNwsbckJhANz7FP0wW4b9ityRPyBNBnBpMknPGr2hKxql7TX3EoZJpbXuO2b8S8yU0E7hPknBE696KrsY9Jwz3M5+dsvFQTMnNXFoliWVLoKU6LIzvGkqXJX3s//giWHyijzkVHk1ce7KVlM0lgCnhHCyQf5In/fGY4= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR06MB1718; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040130)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041072)(6043046); SRVR:DB5PR06MB1718; BCL:0; PCL:0; RULEID:; SRVR:DB5PR06MB1718; x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(122556002)(77096005)(110136002)(2950100001)(2900100001)(106116001)(5640700001)(16236675004)(1680700002)(19627405001)(345774005)(2351001)(2501003)(76576001)(10400500002)(16601075003)(450100001)(33656002)(8676002)(92566002)(93886004)(3660700001)(8936002)(74316001)(15975445007)(3280700002)(66066001)(74482002)(76176999)(11100500001)(19617315012)(54356999)(2906002)(5004730100002)(3480700004)(19580405001)(9686002)(19580395003)(80792005)(189998001)(50986999)(1730700003)(5002640100001)(86362001)(81166006)(6116002)(19625215002)(4326007)(5003600100002)(586003)(5008740100001)(3846002)(102836003)(87936001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR06MB1718; H:DB5PR06MB1718.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: Lodge.me.uk X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2016 16:41:04.5489 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ded56ae9-7c77-4cf6-bbfd-39e6a505742d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR06MB1718 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 16:41:14 -0000 >Hello, > > As far as I know UEFI supports ahci-* boot devices only. For the basic > > UEFI support without GOP the AHCI devices needed to be mapped on slot 3 > > and 4. I don't know if that's still the case. > > Depends on the o/s being booted - if it needs legacy interrupt > support, the only available slots with routing set up are 3/4/5/6. > > UEFI operates in polled-mode so it has no constraints on it's own. Ah okay. That's good to know. At least for the Windows 2016 case. > > I've got working VNC access to a FreeBSD 10.3 VM. My Windows 7 install > > disc starts up, but the mouse is not working. Keystrokes through VNC > > give "atkbd data buffer full" errors. I'll open a new thread for that > > if I can't figure it out. > > XHCI isn't in Windows7 so you can just remove that config line, > pushing mouse input through the PS2 mouse. That was a little bit strange, it seemed like the emulated ps/2 devices just wouldn't work on a Win 7 VM. The "atkbd data buffer full" may be an indication for not delivered interrupts or something like that. After I've rebooted the host things suddenly started to work. Maybe some kind of system inconsistency. It was some 11-CURRENT with about 4 weeks uptime. It may be a good idea to add a note to the Windows installation guide at https://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt that Window 7 requieres AHCI disks with a blocksize if 512 bytes. Otherwise the installation will fail with "Windows Setup could not configure Windows on this computer?s hardware" and Windows Update will bail out with error 0xc8000247. Regards, Yamagi -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" Hi Peter, I've been looking forward to this feature and having a graphical console in= Windows for something, thank you for your effort. I'm currently using Bhyv= e on Freenas 9.10 ( FreeBSD 10.3). I've built from source in FreeBSD 11 r30= 1289 and copied the Bhyve binary over. There were a few other hoops to jump= through, but I can now launch Bhyve with the GOP UEFI binary. If I execute Bhyve without the fbuf device, Bhyve runs and Windows boots n= ormally. If I include the fbuf, Bhyve returns without error, but does not = run. If I include the XHCI tablet backend, again Bhyve executes and Windows= boots as normal. Am I missing something that is required by fbuf outside of the Bhyve binary= ? Regards James Lodge