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

After halt, it will been blocked and have no response #1839

Closed
yankunsam opened this issue May 16, 2017 · 5 comments
Closed

After halt, it will been blocked and have no response #1839

yankunsam opened this issue May 16, 2017 · 5 comments

Comments

@yankunsam
Copy link

Description
/ # ls
Makefile dev init proc sbin tmp
bin etc lib root srv usr
containers home media run sys var
/ # halt
Terminated
/ # [ 106.830184] reboot: System halted

Steps to reproduce the issue:

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

@thebsdbox
Copy link
Contributor

I'd recommend poweroff as some of the hypervisor backends will keep the VM in a powered on state even though the CPU has been halted.

@rn
Copy link
Member

rn commented May 16, 2017

I don't think this is not something we can fix with LinuxKit. It depends how your Hypervisor reacts to the various VM exit reason. For example in hyperkit we do the following: https://github.com/moby/hyperkit/blob/master/src/hyperkit.c#L531

Which backend are you using? Qemu/KVM? hyperkit? which version?

@avsm
Copy link
Contributor

avsm commented May 17, 2017

This is probably happening because you are using the qemu backend. It exists successfully with hyperkit

@yankunsam
Copy link
Author

I use kvm.

@yankunsam
Copy link
Author

Thanks. "poweroff " is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants