![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Look until you’re part of the turbo team… WALK SLOWLY
Look until you’re part of the turbo team… WALK SLOWLY
Not sure what’s funnier. your first comment or the comment explaining it to someone who obviously not part of a turbo team
You could also try debugging with gdb. https://qemu-project.gitlab.io/qemu/system/gdb.html
This may me way more technical than you wish to dive into, but it also might shed some light on where things are stuck.
Could you try addkng “-serial stdio” and see if any info comes out on the console?
Is it literally named new volume? If so perhaps the space is throwing things off. Try quoting the whole path perhaps?
Dear Stamets,
Get better.
Sincerely, Some guy who laughs at all the content you post.
What are the permissions on the directory the file resides in?
Do you take Pepsi points?
All the comments here are great. One other suggestion I didn’t see: use chrt to start the build process with the sched_batch policy. It’s lower than sched_other, which most processes will be in, so the compilation processes should be bumped off the CPU for virtually everyone else