-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to reuse ram.qcow2 in parallel fuzzing mode. #15
Comments
Hi! I have not seen this but I also barely use the VM-style launching. |
Hello! I have the same problem and this error appears on both qemu-5.0 and qemu-4.2. |
It seems this is a feature and there are half-documented options to get around it. I'm not sure from the description if you just need to supply -U/--force-share to qemu-img when creating the backing image, or supply shared-rw (renamed to force-share=on?) on qemu cmdline, or both. Also it looks like force-share=on may only work for -blockdev, which is the modern version of -drive.. |
I also use the method that @nola-milkin mentioned, it's useful. |
The separate vm_ram option was removed some time ago when testing on Windows. Do we know if the above approach also allows using multiple cores for Windows VM fuzzing? Cc @vient |
Do you mean if we can make several RAM copies and use them for Windows fuzzing instead of removing |
Thanks. I just also confirmed that the Linux VM use case works with just the overlay_N file. Will update the guide accordingly. |
The snapshot file "ram.qcow2" is used concurrently by the instances in parallel fuzzing mode. But maybe modern QEMU introduced a new feature "file lock"?
The error log looks like:
Does this error take place in your environment?
The text was updated successfully, but these errors were encountered: