Oops, sorry. Dropping the list was not intentional. I didnt realise I had
sent a "reply" in place of "reply-all" .
Adding back :)
I still would argue that having the VM's name narrows down the problem
space. If a client knows what operations have been fired for a VM over the
last time window, it
On Wed, Mar 22, 2017 at 01:02:19 -0700, Prerna Saxena wrote:
> Current logs:
> error : qemuProcessFindDomainDiskByAlias:411 : internal error: no disk found
> with alias ide0-0-0
>
> There is no way to find which VM was seeing this error.
> Makes debugging very hard, and the message itself is no
Current logs:
error : qemuProcessFindDomainDiskByAlias:411 : internal error: no disk found
with alias ide0-0-0
There is no way to find which VM was seeing this error.
Makes debugging very hard, and the message itself is no good.
Signed-off-by: Prerna Saxena
---