Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ability to perform instance reboot using limactl cli #1994

Closed
hasan4791 opened this issue Nov 9, 2023 · 6 comments · Fixed by #3323
Closed

Ability to perform instance reboot using limactl cli #1994

hasan4791 opened this issue Nov 9, 2023 · 6 comments · Fixed by #3323
Labels
area/cli limactl CLI user experience enhancement New feature or request good first issue Good for newcomers

Comments

@hasan4791
Copy link
Contributor

Description

If we have sockets shared across host & guest, issuing reboot from the instance is breaking the connection. I had to run 2 commands inorder to reboot the instance from limactl. So it would be great if we provide reboot feature from limactl itself.

@afbjorklund
Copy link
Member

You can do stop and start

@hasan4791
Copy link
Contributor Author

yes, but if cli supports reboot which does stop&start, it would be great.

@AkihiroSuda AkihiroSuda added enhancement New feature or request good first issue Good for newcomers area/cli limactl CLI user experience labels Nov 9, 2023
@hasan4791
Copy link
Contributor Author

@AkihiroSuda I'm working on this one and have an issue. I'm calling stopAction initially which is stopping the instance fine and calling startAction which starts the instance, but the limactl commands never throws any output of hostagent and the process stays awake untill ctrl+c. I believe it has something to do with the context, but what it is, I dont know.

INFO[0000] Using the existing instance "default"        
DEBU[0000] Make sure "user-v2" network is stopped       
DEBU[0000] Make sure usernet network is stopped         
DEBU[0000] Make sure "shared" network is stopped        
DEBU[0000] Make sure "bridged" network is stopped       
DEBU[0000] Make sure "host" network is stopped          
INFO[0000] Starting the instance "default" with VM driver "qemu" 
DEBU[0000] Executed [codesign --verify /opt/homebrew/bin/qemu-system-aarch64]: out=""  error="<nil>"
DEBU[0000] Executed [codesign --display --entitlements - --xml /opt/homebrew/bin/qemu-system-aarch64]: out="Executable=/opt/homebrew/Cellar/qemu/8.1.2/bin/qemu-system-aarch64\n<?xml version=\"1.0\" encoding=\"UTF-8\"?><!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"https://www.apple.com/DTDs/PropertyList-1.0.dtd\"><plist version=\"1.0\"><dict><key>com.apple.security.hypervisor</key><true/></dict></plist>\n"  error="<nil>"
INFO[0000] QEMU binary "/opt/homebrew/bin/qemu-system-aarch64" seems properly signed with the "com.apple.security.hypervisor" entitlement                 
FATA[0600] did not receive an event with the "running" status 
(issue-1994) lima> 

@hasan4791
Copy link
Contributor Author

Does the current context is released by stopAction when its done?

@kairveeehh
Copy link
Contributor

Is this issue open to work , as there has been no update on it since a year and more

@hasan4791
Copy link
Contributor Author

Is this issue open to work , as there has been no update on it since a year and more

Feel free to go ahead ✌️

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area/cli limactl CLI user experience enhancement New feature or request good first issue Good for newcomers
Projects
None yet
4 participants