We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure why I need QEMU page set when I'm building a vbox image
➜ ws-uk export PATH=~/bin:$PATH ➜ ws-uk capstan build -v -p vbox Building ws-uk... Downloading cloudius/osv-base/index.yaml... 154 B / 154 B [================================================================================================================================================================================] 100.00 % Downloading cloudius/osv-base/osv-base.vbox.gz... 20.15 MB / 20.15 MB [==========================================================================================================================================================================] 100.00 % No QEMU installation found. Use the CAPSTAN_QEMU_PATH environment variable to specify its path. ➜ ws-uk export CAPSTAN_QEMU_PATH=/usr/local/Cellar/qemu/2.4.0.1/bin/qemu-system-x86_64 ➜ ws-uk capstan build -v -p vbox Building ws-uk... OSv v0.23 eth0: 192.168.122.15 Waiting for connection from host... (process:1832): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported Uploading files... hello.so --> /tools/hello.so Adding /tools/hello.so...
The text was updated successfully, but these errors were encountered:
Same on this end. After installing QEMU and setting the environment variable it builds fine for VirtualBox though.
Sorry, something went wrong.
the same issue still exists
No branches or pull requests
Not sure why I need QEMU page set when I'm building a vbox image
The text was updated successfully, but these errors were encountered: