Peter Grehan <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #3 from Peter Grehan <> ---
Thanks for the report.

The panic was "spin lock held too long" which usually indicates that one of the
vCPUs wasn't able to run for some amount of time.

Other than the 'portsnap extract' in the guest, was there much happening on the
host system at the same time ? i.e. lots of other processes running, high
memory utilization etc ?

(A simple interim workaround is to use a single-vCPU guest).

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to