-
Notifications
You must be signed in to change notification settings - Fork 653
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
Enable support for image launching on macOS and Windows #1260
Comments
Hi @moondev yeah, we currently have to pass kernel + initrd directly to hyperkit (no bootloader), so we can't really support images that we can't be sure will work with the kernels we use… We're working on it, though! |
@Saviq Thanks for the details! Very interesting as well as clever way to leverage hyperkit for cloud-init. Looking forward to a future update to support this. I suppose using an alternative hypervisor could be an option but then you would need to install it first which is no fun. Congrats on the |
Would qemu work as an alternative with its hardware acceleration? |
Hi @alexellis we'll be evaluating |
How are you planning on dealing with networking? I had issues getting any examples for qemu on MacOS to work for port mapping. |
Ideally I would love to be able to build a custom pre-built Ubuntu image and download them from the launch command. We have a hefty cloud-config setup right now that would reduce our setup by just downloading an image instead. (I know this is on the roadmap, just excited to see the progress being made) |
Originally posted by @m-bers in #1857 (comment) @m-bers, all, it would be near impossible for us to ensure the user experience with custom images. There are certain requirements of the image to be compatible with Multipass. Those of you requesting it would probably be fine with it, but others may be surprised and frustrated that "random" images downloaded from the Internet don't work. Apart from |
Wouldn't it be easy to add a parameter flag to enable "experiment" mode and allow it in Windows/MacOS, and we users would be responsible if the image would work or not? I don't understand at all the reason to forbid Windows and MacOS users to have this feature even if they explicitly would accept it as experimental and unsupported. To give an example: This blocks me right now to do a large demo of something that works really nice on my personal laptop with Ubuntu as main host, but can't run it on my work laptop with Windows, and my company forbids to use another device for the demo purely of some company policies. |
Hi, do you have any update on this problem? |
I succeeded substituting Ubuntu 20 disk image with CentOS 7 cloud image on macOS:
The contents of the instance vault directory should look like:
The instance uses Ubuntu 20 kernel and initrd which should be suitable for almost any recent Linux cloud image Additionally, you may need to copy out /lib/modules from Ubuntu image (e.g. boot Ubuntu instance, copy /lib/modules out, then boot your image, copy /lib/modules back) so that kernel modules in the image match the kernel used by multipass. Make sure you umount /lib/modules (or /usr/lib/modules) before copying it back because it is mounted (I guess by initird) as tmpfs (copymods):
|
Hey @mkhon, That's quite enterprising to say the least:wink: |
Now that Mac OS version of Multipass is switching to Qemu, would the team consider enabling instance creation from custom URLs/ISOs? |
+1 |
Do we have a plan to support CentOS? |
Hello! Where do I need to place the downloaded Debian Cloud image to run it on MacOS with M1 processor? |
@Saviq I don't think this argument holds up while multipass supports launching images from files on linux. If I download some random image from the internet and try to start it on linux, canonical has exactly as much control over the user experience in that situation as it does on macos or windows. The users of multipass on mac/win are likely mostly developers. The users that even want to try building a qcow2 image out of an iso for some non ubuntu cloud image probably know what they are doing enough to be aware of the pitfalls and debug them. And it's pretty likely those users are trying to use a file based image in multipass to make their lives easier via the really nice ux multipass provides. In other words, by not supporting file based images on mac/win you are ensuring users will have a much worse experience working with their custom images. Please address this issue. |
Since I have been following this thread for over 2 years, I found an alternative solution to run other distro's in the same fashion as Multipass does, with Lima. After installing Lima, you can create a Debian VM as such: Start your VM with And then shell into your vm with @canonical, if I violate the terms of service, please just remove my comment. |
Thank you!
|
currently i was exploring the flow of creating a packer image from our production docker image and then launch it with multipass on Mac. and also stucked with the same limitation. Not sure if any other way to do this exists. While workaround exists, it looks like a very strange limitation, especially if workaround really works (in progress of checking this) |
Bump up the issue. |
Is it possible to directly launch a qcow2/img cloud-init enabled image on macOS? This works great on Linux. Is this due to differences between qemu and hyperkit image format?
Test image used: https://download.fedoraproject.org/pub/fedora/linux/releases/31/Cloud/x86_64/images/Fedora-Cloud-Base-31-1.9.x86_64.qcow2
works on linux
fails on macos
The text was updated successfully, but these errors were encountered: