Difference between revisions of "Multipass: Modify number of CPU on an existing instance"
Jump to navigation
Jump to search
↑ https://github.com/canonical/multipass/issues/1158
Line 1: | Line 1: | ||
>= [[multipass v1.10]] (Jul 2022) | >= [[multipass v1.10]] (Jul 2022) | ||
− | multipass set local.YOUR-VM1-NAME.memory=8GB | + | [[multipass set]] local.YOUR-VM1-NAME.memory=8GB |
(no output) | (no output) | ||
multipass set local.YOUR-VM1-NAME.cpus=2 | multipass set local.YOUR-VM1-NAME.cpus=2 |
Latest revision as of 10:26, 21 March 2024
>= multipass v1.10 (Jul 2022)
multipass set local.YOUR-VM1-NAME.memory=8GB (no output) multipass set local.YOUR-VM1-NAME.cpus=2
multipass stop your-instance
sudo launchctl unload /Library/LaunchDaemons/com.canonical.multipassd.plist sudo vi /var/root/Library/Application\ Support/multipassd/multipassd-vm-instances.json
sudo vi "/var/root/Library/Application Support/multipassd/qemu/multipassd-vm-instances.json"
Modify: num_cores
sudo launchctl load /Library/LaunchDaemons/com.canonical.multipassd.plist multipass start your-instance
Related terms[edit]
virsh setvcpus
multipass start
- mem_size = 4294967296 and 4096
See also[edit]
- Multipass,
MULTIPASS_STORAGE
,/Library/Logs/Multipass/multipassd.log
,/var/run/multipass_socket
, Multipass releases, multipassd
Advertising: