> > From: Iustin Pop
> > Date: Mon, 29. Oct 2012 17:26

> > > We're preparing the 2.6.2 release, and I'd like your feedback to ensure
> > > we don't miss any easy fixes that could go in it.

> > I don't know if following is easy to fix. But here is my wish list for
> what I think it could be easy (unordered):

> Thanks for the list!

> > * KVM: default to cache=none,aio=native parameter

> Sorry, more information about this? Was there a thread on it?

> > * Issue 261:  Possibility to set custom kvm parameters on an instance

> Ack, that would be useful, but it would change the config, so it has to
> go onto the next major release (2.7)

> > * gnt-cluster verify: don't blame for non redundant instances in case of
> sharedfile...

> Thanks, good point, I'll try to get this in; patch sent.

> > * gnt-cluster modify --no-lvm-storage: validation bug? Failure:
> prerequisites not met for this operation: error type: wrong_input, error
> details: Parameter 'OP_CLUSTER_SET_PARAMS.vg_name' fails validation

> Oh. I didn't know about this, and I can't find an issue. I filled issue
> 285 for it, thanks!

> > * Issue 262: gnt-instance remove does not remove directory on shared
> file storage path

> Thanks, this should be an easy fix; patch sent.

> > * gnt-instance modify --disk add:...: does not activate disks (in
> preparation for hotplug)

> Hmm… I suppose this is part of/before issue 263, right? I'll have to
> take a look, not sure if it's easy or not.

> > * Issue 225: kvm path is configurable only at build time

> This would require a new hypervisor parameter, so can't go in 2.6.

> > * similar to Issue 259: respect --prealloc-wipe-disks with
> grow-disk/modify --disk add

> This has been implemented in master, but since it's not a trivial fix
> we'll not backport it now. I will update the issue status though, thanks
> for the reminder.

> thanks!
> iustin