-
Notifications
You must be signed in to change notification settings - Fork 618
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
Unexpected WARN: Ignoring: vmType vz: [OS] #1768
Comments
Update: Ignoring the WARN log, the instance starts successfully with the macOS Virtual Machine Service: $ limactl start template://experimental/vz
? Creating an instance "vz" Proceed with the current configuration
WARN[0000] `vmType: vz` is experimental
WARN[0000] Ignoring: vmType vz: [OS]
INFO[0000] Attempting to download the image arch=aarch64 digest= location="https://cloud-images.ubuntu.com/releases/22.04/release/ubuntu-22.04-server-cloudimg-arm64.img"
INFO[0000] Using cache "/Users/foo/Library/Caches/lima/download/by-url-sha256/17dad398d7fab7f11627da46d973b43a812847ace3b3216a590667981417c25d/data"
INFO[0000] Converting "/Users/foo/.lima/vz/basedisk" (qcow2) to a raw disk "/Users/foo/.lima/vz/diffdisk"
2.20 GiB / 2.20 GiB [-------------------------------------] 100.00% 176.07 MiB/s
INFO[0013] Expanding to 100GiB
INFO[0013] Attempting to download the nerdctl archive arch=aarch64 digest="sha256:32a2537e0a80e1493b5934ca56c3e237466606a1b720aef23b9c0a7fc3303bdb" location="https://github.com/containerd/nerdctl/releases/download/v1.5.0/nerdctl-full-1.5.0-linux-arm64.tar.gz"
INFO[0013] Using cache "/Users/foo/Library/Caches/lima/download/by-url-sha256/2e9505df478bbb8427823380c3ab4ef36836e7c2c9317f6c885d39be36546b19/data"
INFO[0014] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/foo/.lima/vz/serial*.log")
INFO[0014] [hostagent] new connection from to
INFO[0014] [hostagent] Setting up Rosetta share
INFO[0014] SSH Local Port: 59791
INFO[0014] [hostagent] [VZ] - vm state change: running
INFO[0014] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
...
INFO[0066] [hostagent] The final requirement 1 of 1 is satisfied
INFO[0066] READY. Run `limactl shell vz` to open the shell. I can find a new |
The warning message is confusing, but it is just ignoring |
Got it. I used to interpret that log message to mean that it ignoring the setting to vmType and falling back to the qemu. 🤦 |
Side effect from PR: Same problem as before, no tests for vz in Linux - so when you add a field, it is missing. |
This commit fix lima-vm#1768 by: 1. add `"OS"` to the know list since lima-vm#1735 introduced this field. 2. make the log message more clear: `Ignoring: vmType vz: [...]` -> `Ignoring following configuration due to the use of vmType vz: [...]`
I glanced over the code and made a quick PR (#1769) to fix this. I am not sure if these changes are correct. Please check it. |
This commit fix lima-vm#1768 by: 1. add `"OS"` to the know list since lima-vm#1735 introduced this field. 2. make the log message more clear: `Ignoring: vmType vz: [...]` -> `Ignoring following configuration due to the use of vmType vz: [...]` Signed-off-by: Yuehchan Chueng <[email protected]>
This commit fix lima-vm#1768 by: 1. add `"OS"` to the know list since lima-vm#1735 introduced this field. 2. make the log message more clear: `Ignoring: vmType vz: [...]` -> `Ignoring following configuration due to the use of vmType vz: [...]` Signed-off-by: CDFMLR <[email protected]>
This commit fix lima-vm#1768 by: 1. add `"OS"` to the know list since lima-vm#1735 introduced this field. 2. make the log message clear: `Ignoring: vmType vz: [...]` -> `vmType vz: ignoring ...` Signed-off-by: CDFMLR <[email protected]>
This commit fix lima-vm#1768 by: 1. add `"OS"` to the know list since lima-vm#1735 introduced this field. 2. make the log message clear: `Ignoring: vmType vz: [...]` -> `vmType vz: ignoring ...` Signed-off-by: CDFMLR <[email protected]>
Description
I always get unexpected
WARN[0000] Ignoring: vmType vz: [OS]
when trying to start virtual machines withvmType: vz
.Same the
--vm-type
option:P.s. There is a vz instance, created months ago by colima, works fine on the machine.
$ limactl list NAME STATUS SSH VMTYPE ARCH CPUS MEMORY DISK DIR colima Running 127.0.0.1:53004 vz aarch64 2 4GiB 40GiB ~/.lima/colima
Version:
The text was updated successfully, but these errors were encountered: