I have a boot2docker version of minishift installed on my laptop. Since I am using Windows 10 Home edition, I am forced to use Virtual box to run the minishift OS. However, every time I have to load the OS, minishift takes ages to boot up.
It takes almost 15 minutes to fully start the system. Plus I have to rsync my changes again as they are lost every time I stop the machine. Is there any solution to this?
Related
When I connect x2go with XFCE Ubuntu 20.04 (KVM VM) after ~10 minutes of idle time, x2go will lose its mouse focus and keyboard focus and there is no way to grab control of the session. Even restarting x2go will not bring the focus back.
The XFCE VM is still running because I can see the top output in the console.
I tried several key combinations to bring the focus back but it does not. I tried LXDE and it does not have this issue. I tried XFCE desktop 20.04 on its running in a KVM VM. I also tried installing Ubuntu server 20.04 and load Xubuntu-desktop (KVM VM) - the same issue. After ~10 minutes the x2go session-focus is lost.
What brings the session focus back is if I reboot the VM and then connect to the VM again using x2go. as I mentioned just restarting x2go will not bring the session focus back.
I tried uninstalling the screensaver and the power management features in XFCE but that did not fix this issue.
Update: this x2go bug report log suggests its screensaver related. Using the applications/settings/screensaver allowed me to turn off anything related to the screensaver, solving the problem for me. Issue appears to be solved here similarly: askubuntu forum
I've been having the same issue w/ XFCE and LXDE both after an idle period (10-15 minutes), and only on Ubuntu 20.04, not on 18.04 or earlier. In either desktop env, the session was not recoverable and required termination of the session either from the client side or via a separate terminal ssh session to kill <PID> the x2gocleansessio process on the server side (after seeing it was running using top). For a short period, I regained control in the new session until the cycle recurred.
Seems like a major problem for x2go in Ubuntu 20.04.
Just to save everyone the time of digging through the AskUbuntu forum... run this + restart and you should be good to go on Ubuntu 20.04 -
sudo apt-get remove xfce4-screensaver
If your are login via x2go and don't want to uninstall xfce4-screensaver, it's hard to solve the problem because there are intern script of xfce who launch xfce4-screensaver whatever you told him to do. I found my own workaround WITHOUT root privilege:
First activate screensaver on start-up :settings-manager -> Session and Startup->check screensaver(that sound weird but by this way you are sure to launch your xfce4-screensaver localy otherwise it's the root user who launch it which this own startup file which you can't edit without root)
Second : in ~/.config/autostart/xfce4-screensaver.desktop (if it doesn't exist uncheck then check screensaver in first step). Add to the end of this file:
Exec=sh -c "kill $(pgrep -u <YOUR-USERNAME> screen)"
This will launch it but auto-kill it after OnLogin
Edit: it's better than uninstall it because in my case that was the administrator that install for every user xfce4-screensaver so I can't uninstall it because the computer need a screensaver on the real sessions (I mean not in ssh on the physique machine). Maybe switch to Xscreensaver or other screensaver will solve this problem
I'm trying to run minishift in a Centos 7 VM running in Oracle VirtualBox on a Windows 7 PC. When I issue the "minishift start" command , the session hangs at "Starting VM minshift". I've tried starting minishift with the debug flag "--show-libmachine-logs -v 5" , but with no results.
The environment is a Windows 7 PC with an I3-4160 processor and 16G memory, with 11G and two threads allocated to the VM. Minishift is using the KVM drivers.
Does anyone have any ideas or suggestions, or are there any other debug flags I can specify?
Thanks,
Graeme
I would suggest to re-install it. I currently have the same CPU and it might be a possibility that your CPU is not in the recommended system specifications. But that might be a possibility.
Running Windows 10 on my laptop (with a compatible GPU) and just started using tensorflow-gpu 2 days ago. Every time I close the lid to put the laptop to sleep, it restarts when I wake it up. This never happened when I was just running normal tensorflow. I thought I'd see here if this is normal or known before running it up the flagpole on their git repo.
I need to run an intensive CPU task that maxes all cores of my CPU to 100%.
After a few days of running this task, I find that the machine becomes unresponsive and I am no longer able to SSH into it. I then have to restart the machine and begin the task again. This task could take several weeks or even months to compute.
I'd like to find a way to run this task to completion.
I've tried running the task on Debian 8 and Ubuntu Server LTS. Both of these operating system exhibited the same problem. I thought about running the task inside a Virtual Machine and using Cron to snapshot it every hour, but this seems quite extreme and would suffer an overhead.
Why is it that my machine is unstable?
Could it be due to power fluctuations?
Should I try under-clocking the CPU?
Thanks
I would like to use boot2docker for Windows inside a VirtualBox (Windows XP 64-bits, VT-x enabled).
I tried to start the last version of boot2docker (v1.6.2) but the boot2docker start command does not end, both using the Boot2docker shortcut or running directly boot2docker start in Windows terminal.
The "boot2docker init" actually works, but the "boot2docker up" outputs (I waited for one hour, still up):
Waiting for VM and Docker daemon to start..............................................ooooooo
There is no failure, no message, nothing major in Logs from boot2docker-vm and its state is "running".
I tried "boot2docker ssh" in another Terminal but it fails with error "error in run: exit status 255" ("boot2docker ip" fails with "Failed to get VM Host only IP address. Was the VM initialized using boot2docker?").
I guess this issue can be related to the usage of Windows inside a VB by contrast with "native" Windows.
Did someone already successfully use older versions of boot2docker inside a VirtualBox? Or maybe it is not possible...
This happened to me once, and I did a
boot2docker delete
boot2docker init
boot2docker up
and it worked.
It is rather impossible to run boot2docker inside the VirtualBox as boot2docker is based also on VirtualBox and unfortunately such nesting is not supported - here is feature request concerning this (its worth to show your interest there! :).
People are reporting success running nested VirtualBox configuration but they are using 32 bit OS for inner instance and docker supports currently only 64 bit OS.
There are however some unofficial tries to run docker on 32 bit OS but then there is a need of dedicated 32 bit docker images.
It would be interesting if such combination of above have worked for somebody.