Re: Next features and target for development

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2007-07-10 at 17:23 +0100, Daniel P. Berrange wrote:
> On Tue, Jul 10, 2007 at 05:12:38PM +0100, Richard W.M. Jones wrote:
> >
> > (2) Are the hosts compatible?  (eg. microarchitecture, hypervisor, ... 
> > other sources of incompatibility?)  Should we care at the API level or 
> > just report errors from the hypervisors?
> 
> The app can validate to some degree by looking at the capabilities
> XML to see what's supported on both ends & what the guest is using.
> So I'd let the app do high level validation with that, and just then
> propagate errors from the underlying system - keeping poliucy out of
> the libvirt API.

This question comes up in other contexts than migration, too, for
example, when you want to start an image you just downloaded. I think it
would make sense if there was a common baseline in libvirt that could
tell you if a VM has any chance of running at all - otherwise that logic
will be scattered across lots of apps.

David


--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]