On Thu, 2016-09-08 at 14:04 +0000, Guido.Rossmueller@xxxxxxxx wrote: > Hello everybody, > > a colleague of me described last november a problem that we have with libvirt and xen > > https://www.redhat.com/archives/libvir-list/2015-November/msg00130.html > > Jim Fehlig provided for this problem a patch a few days later: > > https://www.redhat.com/archives/libvir-list/2015-November/msg00520.html > > The provided patch work great and we have no problems until we applied them.. > > Now we a in the situation that we want to migrate to libvirt 2.1, and we saw the same > problem that we have last year, again. > After we take a look in the source code, we determine that the patches are didn´t go > in the source code. So we modify the patches in that way, that we could apply them > again, and all looks good. > > My question, is their any special reason why this patches didn´t go in the source code? > > I see same posts on the maillinglist, but absolute statement for or again the patches > from Jim Fehlig. Jim said he would submit a v2 to address some concerns raised during review[1]; later, he reported some issues he'd run into[2] while working on it. So it looks to me like the code was not yet ready for merge, which would explain it being tagged as RFC. And then it probably just slipped through the cracks :) CCing Jim for insights on the current status of the patch. [1] https://www.redhat.com/archives/libvir-list/2015-November/msg00958.html [2] https://www.redhat.com/archives/libvir-list/2015-November/msg00974.html -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list