-
Notifications
You must be signed in to change notification settings - Fork 63
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
Memory issue on chrome os crostini? #72
Comments
How about commenting out this line? |
Hi what line do I comment out? |
madvise(system_ram_host_, machine_->ram_size_, MADV_MERGEABLE) == 0 |
#MV_ASSERT(madvise(system_ram_host_, machine_->ram_size_, MADV_MERGEABLE) == 0); Like that? If so, it still displays the same error for some reason |
Anything else I can do to get past the error? |
Yes, comment thie line out, and recompile the mvisor. PS: We haven't tested mvisor on chrome os yet. We recommend to use ubuntu or rocky linux |
Ok, I didn't recompile yet. Also, to mention I'm running chrome os crostini which is running debian bookworm. |
Did this: /*MV_ASSERT(madvise(system_ram_host_, machine_->ram_size_, MADV_MERGEABLE) == 0); */ recompiled and running now |
Trying this on chrome os crostini debian bookworm
Error when entering "sudo ./build/mvisor -c config/sample.yaml -vnc 5900"
[0.003] core/memory_manager.cc:95 InitializeSystemRam() panic-error: Assertion failed, madvise(system_ram_host_, machine_->ram_size_, MADV_MERGEABLE) == 0 errno=22, Invalid argument
terminate called after throwing an instance of 'std::runtime_error'
what(): Panic
Config file:
sample.txt
The text was updated successfully, but these errors were encountered: