Re: [libvirt] [PATCH 2/2] qemu: Update next usable PCI slot on domain reconnect

> > There's no requirement to plug devices in ascending slot order - we can > > have gaps at will with any ordering. > > At this point, I'm starting to think that we can just drop this 2/2 > patch and not worry about nextslot being stable across libvirtd restarts. Which means we don't even need most of 1/2 since the reason for changing the hash payload to be a structure instead of a string was this second patch. So what do you think, should I push it as is or make a smaller patch which would just fix OOM checking when PCI addresses are converted to strings?