Comment 6 for bug 1727138

Hi Peter,
I beg your pardon but I don't know why this was missed since you reported - I'm afraid now most chances to debug are gone but lets continue anyway.

I checked through the trace and it didn't ring a bell for anything that might be known already.
Is (was) this issue reproducible multiple times then?

If so hve you identified some sort of guest/net config that was triggering it so that we might have a chance to reproduce for debugging?