-
Notifications
You must be signed in to change notification settings - Fork 19
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
virtio disk not supported #23
Comments
Hi, |
Thanks for reporting! This is most likely an oversight, I don't think we intentionally exclude KVM. I can give it a try by adding 253 to the list. I am not familiar with KVM though. @dcasota IIUC, this is about finding the hard disk to install to, not the CD device to install from. |
Hi @hadmut , thanks for raising this. |
@oliverkurth we should be less restrictive in block device discovery mask. |
Let's remove a mask ("-I 7,8,179,202,254,259") and allow user to pick any disk. |
@dcasota: Good hint. Providing the disk as sata makes the installation run. Unfortunately, just calling qemu/kvm and omitting the if= parameter doesn't make the disk a sata disk. It takes the parameter -M q35 to emulate a particular hardware model, which makes my machine complain about a missing CPU feature, but runs. Nevertheless, virtio should be supported. |
I have it fixed locally. I will push the fix soon, and give some instructions how to use it. |
I have created a PR with a fix, and instructions on building your own ISO: #24 |
Describe the bug
Hi,
I am not really sure whether this is a bug or an intentional company decision.
Today I read a recommendation to use Photon OS, wanted to try it, and found, that it is not possible to install it in a virtual machine: It just does not find the disk device /dev/vda to install on.
The reason is, that
/usr/lib/python3.11/site-packages/photon_installer/device.py
calls lsblk to look for disks with option '-I', '7,8,179,202,254,259', which keeps /dev/vda (major 253) out of the list.
I wonder if this is intentionally restricted to vmware environments, has technical reasons, or is just an unintentional omission.
regards
Reproduction steps
...
Expected behavior
Installation
Additional context
No response
The text was updated successfully, but these errors were encountered: