Avi Kivity wrote: > So vfork() is required, or in light of its man page and glowing > recommendations from the security people,
vfork() on Linux is fine to use, as long as you respect it's unwritten requirements :-) In a multithreaded program: you can start by spawning a thread for the sole purpose of spawning a process. Call vfork() from the new thread. Then a slow exec() call won't delay the rest of the program, because it's only blocking the thread you created. > we can mark guest memory as > shared on fork and use plain fork(), like we do for pre mmu notifier > kernels. Aiee - what's the plan? Can a running KVM be forked, as in into two separate processes to run the forked guests in parallel, or not? Thanks, -- Jamie
