Skip to content
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

colima start CLI ignores --mount-type when qemu is chosen #517

Open
1 of 3 tasks
75th opened this issue Dec 18, 2022 · 2 comments
Open
1 of 3 tasks

colima start CLI ignores --mount-type when qemu is chosen #517

75th opened this issue Dec 18, 2022 · 2 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@75th
Copy link

75th commented Dec 18, 2022

Description

colima start --vm-type qemu uses 9p as the mount type, even if you also specify --mount-type virtiofs. It is only possible to create a new profile with both qemu and virtiofs if you pass the -e flag to colima start and edit the config file directly.

Version

Colima Version: 0.5.0
Lima Version: 0.14.1
Qemu Version: 7.2.0
macOS Ventura 13.1

Operating System

  • macOS Intel
  • macOS M1
  • Linux

Reproduction Steps

  1. Run colima start profile1 --vm-type qemu -e
  2. See that mountType in the options file is 9p
  3. Save and exit
  4. Run colima start profile2 --vm-type qemu --mount-type virtiofs -e
  5. See that mountType in the options file is 9p
  6. Save and exit
  7. Run colima start profile 3 --vm-type qemu -e
  8. Change the mountType from 9p to virtiofs
  9. Save and exit
  10. Run colima status profile1 and see it using 9p.
  11. Run colima status profile2 and see it using 9p.
  12. Run colima status profile3 and see it using virtiofs.

Expected behaviour

  • In steps 2, 8, and 10 above, the mountType perhaps should start off as virtiofs.
  • In steps 5 and 11 above, the mountType definitely should start off as virtiofs.

Additional context

No response

@75th 75th changed the title New profiles use 9p when qemu is chosen, regardless of --mount-type colima start CLI uses 9p when qemu is chosen, regardless of mount type Dec 18, 2022
@75th 75th changed the title colima start CLI uses 9p when qemu is chosen, regardless of mount type colima start CLI ignores --mount-type when qemu is chosen Dec 18, 2022
@rfay
Copy link
Contributor

rfay commented Dec 18, 2022

I started a profile with this (macOS arm64):

colima start vz9p -m 6 --mount-type=9p --vm-type=vz --disk=100 --dns 1.1.1.1

and the config file shows the expected

# Default: vz
vmType: vz

# Volume mount driver for the virtual machine (sshfs, 9p).
#
# 9p is more POSIX compliant and generally handles file permissions better.
# However, it does not properly resolve symlinks (that are created on host).
#
# sshfs is faster than 9p but less reliable when there are lots
# of concurrent reads or writes.
#
# Default: sshfs
mountType: 9p

However, the behavior is as described here, it actually has the virtiofs mount type instead of 9p.

$ ddev ssh
rfay@d9-web:/var/www/html$ df -T .
Filesystem     Type      1K-blocks       Used Available Use% Mounted on
mount0         virtiofs 1948455240 1080547296 867907944  56% /var/www/html

@abiosoft abiosoft added bug Something isn't working documentation Improvements or additions to documentation labels Dec 18, 2022
@abiosoft
Copy link
Owner

Thanks for reporting this, it would be investigated.
Actually, 9p is not usable with vz and virtiofs is not usable with qemu. Only sshfs is usable for both vm types.

There is indeed an oversight in the documentation in the YAML file as well that needs to be updated.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants