You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like support for mapped volumes was dropped in libkrun by this commit in February 2024: libkrun/libkrun@186083d
That commit mentions using "multiple virtio-fs devices" instead. It appears krunvm still calls the deprecated function unconditionally, so it always fails even if the user does not configure any mapped volumes:
In krunvm:
#[cfg(target_os = "macos")]fnmap_volumes(ctx:u32,vmcfg:&VmConfig,rootfs:&str){letmut volumes = Vec::new();for(host_path, guest_path)in vmcfg.mapped_volumes.iter(){// ...}// ...let ret = unsafe{ bindings::krun_set_mapped_volumes(ctx, vols.as_ptr())};if ret < 0{println!("Error setting VM mapped volumes");
std::process::exit(-1);}}
Activity
walteh commentedon May 25, 2025
I have the same problem on my M1 Max, same macOS version - krunvm --version
0.2.3stephen-fox commentedon Jun 8, 2025
It looks like support for mapped volumes was dropped in
libkrunby this commit in February 2024: libkrun/libkrun@186083dThat commit mentions using "multiple virtio-fs devices" instead. It appears krunvm still calls the deprecated function unconditionally, so it always fails even if the user does not configure any mapped volumes:
In krunvm:
... and in libkrun