Originally created by @VictorLee0321 on GitHub (Jun 23, 2021).
OS base info
I have other disk capability
After run docker run -it ... and stuck in this windows
What's the problem, and how can I solve it ? THX.
Originally created by @VictorLee0321 on GitHub (Jun 23, 2021).
## OS base info

### I have other disk capability

## After run `docker run -it ...` and stuck in this windows

What's the problem, and how can I solve it ? THX.
@DiscordDigital commented on GitHub (Jul 2, 2021):
I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
Not sure what causes it.
@DiscordDigital commented on GitHub (Jul 2, 2021):
I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
Not sure what causes it.

@DiscordDigital commented on GitHub (Jul 2, 2021):
I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
Not sure what causes it.
Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
@DiscordDigital commented on GitHub (Jul 2, 2021):
> I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
> Not sure what causes it.
Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
Not sure what causes it.
Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
This is a required command, and actually I had been missing it for a while, I will rearrange the documentation in a bit.
@sickcodes commented on GitHub (Jul 5, 2021):
> > I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.
> > Not sure what causes it.
>
> Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
This is a required command, and actually I had been missing it for a while, I will rearrange the documentation in a bit.
Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
where to run this?
@qr4d commented on GitHub (Jan 8, 2023):
> Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
where to run this?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @VictorLee0321 on GitHub (Jun 23, 2021).
OS base info
I have other disk capability
After run
docker run -it ...and stuck in this windowsWhat's the problem, and how can I solve it ? THX.
@DiscordDigital commented on GitHub (Jul 2, 2021):
I just ran into a similar looking issue, however this occurred after I restarted my host and the container was working before the restart.

Not sure what causes it.
@DiscordDigital commented on GitHub (Jul 2, 2021):
Update: I just checked the README and ran "echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs" which fixed the issue for me, however I don't know if the original issue is related to this "solution".
@sickcodes commented on GitHub (Jul 5, 2021):
This is a required command, and actually I had been missing it for a while, I will rearrange the documentation in a bit.
@VictorLee0321 commented on GitHub (Jul 12, 2021):
yes, fixed it by setting this.
@qr4d commented on GitHub (Jan 8, 2023):
where to run this?