Quoting s10 ([email protected]): > This bug still present in libvirt 1.2.2. And patch has not been > discussed upstream.
Why has the patch not been discussed upstream? In general while we are happy to take important patches which are not yet in a release, we want them to be at least mentioned on the list, and preferably committed to git. Three advantages there are that they have a Signed-off-by, have a description, and have a chance for upstream to point out potential problems. None of those have happened here. If we put this into our package, were you expecting us to then push it upstream? We again could not do so without a signed-off-by and a good description, and since we didn't know that was your goal, it wouldn't have happened and so we would be dropping the patch right now (before release). Please discuss this patch upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
