Il 10/05/2013 00:20, Chegu Vinod ha scritto: >> >> Wow, I didn't know that either. Perhaps this must be causing the >> entire QEMU process and its threads to seize up. >> >> It may be necessary to run the pinning command *outside* of QEMU's I/O >> lock in a separate thread if it's really that much overhead. > > Not really sure if the BQL is causing the freeze...but in general > pinning of all memory when the guest is run is perhaps not the best > choice for large enterprise class guests...i.e. its better to do it as > part of the start of the guest.
If pinning is done in the setup phase, it should run outside the BQL. Paolo
