microsoft / microsoft/openvmm

openvmm - disk is not exposed into VM in direct kernel mode (windows aarch64)

Open
#1,399 28 comments 0 reactions 1 assignee View on GitHub

@romank-msft is already working on this.

Since May 30, 2025.

  • #1447 by @romank-msft — merged
storage
Dominant language
Rust
Stars
1.9k
Forks
238
Avg merge
1d 15h
Merged PRs (30d)
100

Description

I am not sure if this is a by design or a defect or a not yet implement, but when I use openvmm with kernel and initrd params, no matter what type of disk I try (-ide, -disk, -nvme) it does not show up in the list of devices.

I use --hv flag and hyperv enabled kernel so vmbus support and other hv_ modules are builtin. Using QEMU I can do exactly that, provide custom kernel with initrd and attach a disk to switch the root to it.

If I use uefi it would look for bootloader from the disk. I thought maybe openvmm needs uefi to provide access to the devices.

Versions - I downloaded the openvmm a few days ago from CI, tried a few different builds. I am on windows on aarch64. I tried kernel from opevmm-deps, tried ubuntu, fedora, etc... Tried compiled version of a kernel (wsl kernel) that works in hyperv.

There are no errors or warnings in dmesg related to disks, would be IDE or scsi or nvme. Tried with --no-enlightenments, no difference. The command line is pretty simple:

openvmm.exe --kernel Image --initrd initrd --no-enlightenments --nic --hv --ide .\arch_openvmm.vhdx

Sorry for bothering with this topic, just experimenting and playing with openvmm.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.