> Currently the timeout for reading startup output is 3 seconds. If the > host is under any sort of load, we can easily trigger this. Lets bump > it to 30 seconds. > > Since the polling loop checks to see if the process has died, we shouldn't > erroneously hit this timeout if qemu bombs (only if it is stuck in some > infinite loop). > > Signed-off-by: Cole Robinson <crobinso@xxxxxxxxxx> > --- > src/qemu/qemu_driver.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) It wouldn't be hard to make it fail even with 30 seconds timeout but then it doesn't really make sense to try to start a new guest on a host which is under such a big load. I think we should be fine with 30 seconds unless we want to optimize for stuck qemu. ACK -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list