On Wed, Sep 10, 2014 at 05:17:35PM +0200, Sven Kieske wrote:
On 10/09/14 17:05, Nathanaƫl Blanchet wrote:
> Hello everyone,
>
> I experiment the same error with all of my host with vdsm 4.14.11.2 since I upgraded
to engine 3.4.x.
> I can't boot any new VMs, and the issue is about the duplicate ID drive.
> If I run once instead of "run", the vm boots fine.
> I've tested the suggested workaround and it works but it is not comfortable...
> What about this nasty bug? will it be resolved with 3.4.4?
> Thanks.
I'm not aware of this bug reported at
bugzilla.redhat.com
I may have missed it because there are plenty of bugs, but if you
don't report the bug there it's not very likely to get fixed.
I'm not 100% that it's the same issue, but I have cloned
Bug 1140323 - fails to run VM - duplicate ID
to 3.4.4. Let's see if what virt developers say.