On Fri, Oct 24, 2014 at 03:28:33PM -0700, Craig Rodrigues wrote:
> On Fri, Oct 24, 2014 at 6:11 AM, Conrad Rad <cse....@gmail.com> 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 <bootloader>.
> >
> >
> 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, 

Libvirt has a goal that we never break application compatibility,
which includes the way the XML is configured for guests. So when
reviewing patches like this series it is important to try to have
an awareness of what further patches may be coming down the pipe
in the future, so we can avoid painting ourselves into a corner.
So this question of Roman's isn't really about blocking patches
for future vapourware, but rather about making sure that decisions
we make today don't cause us undue problems with UEFI does arrive
at some point later.

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to