From owner-freebsd-virtualization@FreeBSD.ORG Fri Oct 24 22:28:36 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65C68EDA for ; Fri, 24 Oct 2014 22:28:36 +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)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDCF5830 for ; Fri, 24 Oct 2014 22:28:35 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id gf13so4059042lab.1 for ; Fri, 24 Oct 2014 15:28:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ls9hOdWw5J43Xh5eJvtCgUhgJ6fsz2qFLx8YYg+9wPg=; b=gAmSKFfU/2+rqwOU8QZrjEtarXVkyBghP9i/FCAGR4OOLltmeVbqsZ7EdJngc1RhA8 guCqqWOPdlwh1olIfzB4nBT7GnTY7rpMVpIlaLAGwELnYMoWCwL58GEADxI/61CGTEPu CiVo/GQu72rmr94LS65lB8JxZgstcskwSqatFCSeTKcQheeDotAsizN7mjcopPr5yD09 sMbSdQszRtc6QVUCeXhzB3/jOa0z38MzMSx3fw7gf+scO3fP+5Ffw1Tz1hFK+xKXCSy+ ignRbY4MFMbLEFzQ78yQAGFcNNoISs7hOJZD+aia1sbgrxzM4shglubJWicf5XamzzUS eGJQ== MIME-Version: 1.0 X-Received: by 10.112.221.226 with SMTP id qh2mr7325891lbc.5.1414189713650; Fri, 24 Oct 2014 15:28:33 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.84.197 with HTTP; Fri, 24 Oct 2014 15:28:33 -0700 (PDT) In-Reply-To: References: <1414106923-32313-1-git-send-email-cse.cem@gmail.com> <1414106923-32313-2-git-send-email-cse.cem@gmail.com> <20141024045844.GA12422@dev.san.ru> Date: Fri, 24 Oct 2014 15:28:33 -0700 X-Google-Sender-Auth: A1GPm4VJCtbwFmC9IuS6_LO5V_A Message-ID: Subject: Re: [PATCHv2 1/2] bhyve: Support /domain/bootloader configuration for non-FreeBSD guests. From: Craig Rodrigues To: Conrad Rad Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: libvir-list@redhat.com, Roman Bogorodskiy , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 24 Oct 2014 22:28:36 -0000 On Fri, Oct 24, 2014 at 6:11 AM, Conrad Rad wrote: > > Any idea how soon? Months? A year? 5 years? I'm not comfortable > postponing improvements indefinitely for vaporware. In the wonderful > bhyve-UEFI future, we can ignore/warn about . > > Hi, I have to agree with Conrad here. I hope that any perceived future direction of bhyve is not going to be used as an excuse to block some of the libvirt patches that Conrad is submitting. The stuff that Conrad is working on overlaps some of the shortcomings in libvirt/bhyve that I mentioned here: https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-October/002857.html Fixing these issues in libvirt will make libvirt + bhyve more usable today. When the bhyve-UEFI stuff comes out in future, that will be even better, but there are a few people (me and others) who are trying to put together FreeBSD + bhyve systems today that are viable alternatives to Linux + KVM for managing many VM's. bhyve is rapidly improving, but the lack of libvirt support means that a huge ecosystem of software built for libvirt + KVM cannot be used for bhyve. I hope we can start improving libvirt today to eliminate this problem. -- Craig