I am running Ubuntu 20.04 X86_64 VM within KVM+QEMU.
And I ran a command within the Ubuntu VM to suspend it from inside "sudo systemctl suspend".
After running it, the SSH and virsh console have no responses. So I think the VM is suspended.
In this case, how can I resume the VM running?
I tried 'sudo virsh inject-nmi ubuntu_vm', but it seemed not work.
'sudo virsh list' shows the VM is in running state.
You can either use,
virsh dompmwakeup ubuntu_vm
or from qemu monitor,
system_wakeup
Related
Problem:
I started my system as usual but my docker-desktop doesn't work, WSL doesn't respond to commands and there is a process called "Vmmem" using 25% of my memory. I have tried a bunch of thing but nothing seems to work.
System Attributes:
Windows 10 Pro (10.0.19045.2486)
docker: 4.15
WSL: 1.0.3.0
More context:
Recently I was having trouble with my docker set up. I have one particular container that was "crashing" the docker. It was not throwing any exception but after some event (that I couldn't find out) all the other container where unreachable any attempt to stop/start another container would result on "Error: 500 failed to respond...". When this happens I usually just restart the system and everything works fine, but today it wasn't the case. I restarted and I noticed that I had the "Vmmem" process already running at 25% (it usually just reaches this point at the end of the day), the docker desktop could not start the docker backend and when I tried running wsl -l -v I got no response. I can use some docker commands like docker -v but the docker compose up doesn't work at all.
What I've tried:
restart the system again (nothing changed, still starting with 25% mem usage)
deactivating Hyper-V (nothing happened)
stop/start docker service using net start/stop <service> (it gives a response but didn't solve the problem)
Uninstall docker-desktop (it crashes before even starting the uninstall process)
Terminate WSL wsl -t Ubuntu (got no response from wsl)
Overwrite installation with Docker 4.16 (it gets stuck on "Preparing for update... / Stopping VM and preparing for update")
Forcefully kill the "Vmmem" (I've got Access denied error)
Edit 1:
I managed to finally install the Docker desktop 4.16 but the problem continues, system starts with 25% Vmmem memory usage and docker desktop is not able to initiate backend.
the process Vmeem It represents the memory and CPU consumed by the combination of all the virtual machines running on your Windows PC, there is a possibility that processes are still running on your PC. I recommend you try to launch these commands from the console:
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
This will stop all containers and delete them.
If this doesn't work, I recommend you enter your bios settings and disable virtualization, that way those processes will stop, then you can enable it again and try. I wish you luck and I hope this resolves.
Steps that I did to be able to stop "Vmmem" process and install docker desktop again:
disable Hyper-V
disable virtualization (BIOS)
restart system
to this point the "Vmmem" problem was gone
uninstall docker desktop
rm all wsl instances
enable Hyper-V
enable hypervisorlaunchtype
restart system
enable virtualization (BIOS)
install wsl Ubuntu instance
install Docker Desktop
Maybe some steps listed here are redundant but that is what I did. hope it helps if other people is passing through the same problem
I have Microsoft Windows 10 Pro version 10.0.19041 N/A Build 19041 and I follow steps here https://learn.microsoft.com/en-us/windows/wsl/install-win10 to install Ubuntu 20.04 LTS on it using WLS2 , I'm doing so to install docker by following steps here https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository
but when I try to run sudo docker run hello-world it gives me this error docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'. I know that a similar question asked here Cannot connect to the Docker daemon at unix:/var/run/docker.sock. Is the docker daemon running? ,and I try to run systemctl daemon-reload and systemctl start docker but al the solutions does not worked for me it gives me another errors like System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down and Also try to fix it but I can't, So I need your help.
Note : I have already install Docker in windows and It works fine.
I have been solving this problem by following these steps
Purge the Grub package Linux command according this issue https://github.com/microsoft/WSL/issues/4903
Stop Docker Desktop from Windows
Run sudo dockerd which is the daemon service for Docker containers
https://i.stack.imgur.com/qgbwE.png
Open new Ubuntu shell session
Run docker run hello-world
and it's work fine with me https://i.stack.imgur.com/6TJ3u.png
I am setting up a Ubuntu 15.04 VM on Win7 using Vagrant 1.7.4 and VBox 5.0.0.
On the first vagrant up I can ssh into the machine using vagrant putty and everything is setup correctly and works. When I run vagrant halt, the VM shuts down gracefully without error messages.
However, when I try to restart the VM using vagrant up; vagrant putty, the machine is in a strange state. For example, the default synced folder /vagrant is empty, even though the second vagrant up call prints this message:
default: /vagrant => C:/Users/ArneUser/numecs/dev_env
Also, this vagrant up call prints the following message in PowerShell:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=
Stdout from the command:
Stderr from the command:
stdin: is not a tty
bash: line 2: /sbin/initctl: No such file or directory
I am running a really basic setup just to test for this error, so I don't think the mistake is in my provisioning script. Some pointers in the right direction would be appreciated.
Open VirtualBox GUI and turn off machine manually, then run again the vagrant up command.
That solved the problem in my case :)
/vagrant is empty
/sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=
From these two lines I suspect that MOUNTPOINT should be /vagrant but its due to /vagrant being empty that SSH is now working.
I've seen similar issues because of Virtualbox 5.
Try to downgrade Virtualbox to 4.3.x and ensure you have the latest Vagrant (1.7.4).
https://github.com/mitchellh/vagrant/issues/5572
Initctl is part of the Upstart init daemon. As far as I'm aware Ubuntu 15.04 is the first version of Ubuntu to abandon Upstart in favor of SystemD, so /sbin/initctl isn't expected to exist in your operating system. I believe this would need to be something that is fixed in the box you're using.
The point of "/sbin/initctl emit ..." is to notify other Upstart units that the vagrant shared folder has been mounted and is available for read/write operations. Since upstart is no longer in use it may be safe to assume that there is no need for this call. It's a rather crude hack, but you could make an empty script at /sbin/initctl. This should allow the vagrant startup process to continue properly and provision your box.
In my case it seems as Marc Young suggested that by opening Virtualbox GUI, the virtual machine itself seems to be hung. I saw these error messages on the virtual box console:
Thus it seems to not to be Vagrant related problem, but the virtual machine (Linux Kernel) itself seems to be hung.
I am trying to re-install boot2docker from
https://github.com/boot2docker/osx-installer/releases/tag/v1.7.0
The installation fails with the following error reported:
The installer has detected that VirtualBox is still running. Please shutdown all running VirtualBox machines and exit VirtualBox then restart the installation.
How can I exit VirtualBox?
Open VirtualBox, it will give you a list of all the VirtualBox VMs you have. You can then easily see which of them are running, and stop them by powering them off.
If boot2docker is still available you should be able to do "boot2docker poweroff" to shutoff the VM behind it.
I've also had some cases where Virtualbox did not show my boot2docker VM as runnning, even though it was. If thats the case, open up your task manager, find the process VBoxHeadless, and kill it.
This is because all the running VMs were not shutdown before uninstalling. Run VBoxManage command to list all running VMs
VBoxManage list runningvms
Then run savestate command to stop the vm
VBoxManage controlvm <name of vm> savestate
Now run the installation again.
My end goal is to run firefox in headless mode with xvfb.
But Xvfb requires Xorg, and I'm running into a problem with Xorg.
When I fire up an instance using this AMI:
ami-4a24d623
RightImage_CentOS_5.4_i386_v5.5.9_EBS
Then do:
yum install Xorg
Then reboot the instance, I get failed status checks, and I can't log into the instance.
Server Logs (Instance Actions->Get Server Log) are blank.
What am I doing wrong? Do I need to configure Xorg somehow?
I disabled SElinux which helped me bring instance up