Re: [PATCH 2/2] conf: Introduce the virDomainNetModel enumeration

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

 



On Thu, Jul 27, 2017 at 15:08:11 +0200, Andrea Bolognani wrote:
> On Thu, 2017-07-27 at 14:36 +0200, Peter Krempa wrote:
> > > Would you still be against it if the enumeration was extended
> > > to include every NIC model ever supported by QEMU and Xen? As
> > > mentioned, other drivers already perform their own validation
> > > and only accept a very limited number of models, so there's
> > > no risk of regression there.
> > 
> > I don't think that will help. It will prevent missing any working
> > configuration, but it will still make any invalid configuration vanish.
> 
> Do we really need to care that much about guests that never
> had a chance to even start? I honestly don't see the point.

But they were present in the list of VMs and could be edited. If they
fail to parse and thus vanish, users have to go into the file with a big
"DO NOT EDIT THIS FILE" sign and edit it.

Even if you don't see the point we still try to not make existing
configs vanish. Validation callback is your friend in this case.

Attachment: signature.asc
Description: Digital signature

--
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]
  Powered by Linux