I want to use Kvm as hypervisor, but it is difficult. Is says that I don't have space on the node, that is not true.
How could I solve this big problem? http://prntscr.com/2rlcq1
Your question is not clear. First of all you can install Kvm only in a bare-metal physical machine. Though it comes with a linux distribution but it's a hypervisor so it runs directly on the hardware.
Next you have to enable the processor virtualization extension that is Intel-VT/VT-x or AMD-v from bios.
Then only you can install Kvm.
Related
inotify worked in WSL1. Then it was deliberately turned off in WSL2 due to an unsupported feature in a GNU software which is now solved.
How can inotify be enabled or turned on in WSL2?
inotify is supported in WSL2, but only on the Linux-based ext4 filesystem. Where you may be having trouble is that it does not work on Windows drives which are mounted using the 9P protocol (e.g. /mnt/c) or symlinks to any files on those drives.
I'm unaware of this being (per the question) due to "an unsupported feature in a GNU software which is now solved", nor it being "deliberately turned off". It's my understanding that the WSL team just hasn't "plumbed" (their word from the 2019 Build Conference) it in 9P.
It does, as you mention work in WSL1 on Windows drives mounted via drvfs, and using WSL1 is still a viable option for many development tasks. Of course, this is only necessary if you require that your watched files be on a Windows drive. Also note that WSL1 really used the Windows drive for both the Linux filesystem (via an overlay of sorts in your WSL1 directory), so if inotify worked for one, it likely worked for both for the same reason (same implementation of syscall translation).
The simplest solution, though, if it meets your workflow, is to just move your project somewhere on the WSL/Linux/ext4 filesystem, such as under your $HOME folder (again, not using a symlink).
As for how to enable it, I don't think that's going to be possible. While the 9P client is open-source and included in the WSL2 kernel Github project here, the server that runs in Windows and provides access to those drives is, as far as I know, still closed-source.
For more details, see this answer.
Ever since I have upgraded my laptop (Click here for hardware specs.) my screen usually freezes. Mostly in chrome or Firefox browser. I am pretty sure this is a Nvidia driver problem but I can't seem to find the solution. I am running a Nvidia Quadro K2100M.
I am currently running Nvidia 361.42. I have tried using open source Xorg server without any luck.
The only solution I have found so far is forcefully turning off the computer by holding down the power button.
Things that I have tried:
I got keyboard input
I cannot switch to another terminal to restart lightdm
This problem came to me occasionally, making me really annoyed.
As illustrated in many blogs, this may be caused by graphic driver problem. For me, my desktop has a NVIDIA video card, you can run lspci | grep VGA to see what type of your video type, in my case, it returned:
02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
I followed the instruction on jiakai zhang's blog to reinstall proper drivers for the desktop, hope this will help you.
The key steps in [1] are to reinstall the ubuntu desktop and nvidia drivier by:
$ sudo su
$ apt-get update
$ apt-get install --reinstall ubuntu-desktop
$ apt-get install unity
$ apt-get remove --purge nvidia*
$ reboot
$ sudo apt-get install nvidia-current
$ sudo reboot
Updating the grub settings worked for me! Do the following:
1. Open the GRUB configuration
sudo vi /etc/default/grub
2. Change the value of GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
and save the file.
3. Update & Reboot
sudo update-grub
sudo reboot
More info:
This is a bug in the processor, known as the c-state bug. It causes total freezes when the CPU tries to enter an unsupported sleep state. It's a problem for many Bay Trail devices especially with newer (4.*) kernels. There is a simple workaround until it gets properly fixed upstream. You just need to pass a kernel boot parameter and the random freezing stops completely. The parameter may increase battery consumption slightly, but it will give you a usable system. You do this by editing the configuration file for GRUB as described above.
GRUB - boot loader package from the GNU Project, which provides a user the choice to boot one of multiple operating systems
installed on a computer or select a specific kernel configuration available on a particular operating system's partitions;
Intel Bay Trail - new Atom Processors from Intel. Atom is Intel's family of x86 and x86-64 processors that are optimized
for small computing devices, such as smartphones and mobile Internet devices;
C-States - used to optimize optimize or reduce power consumption in idle mode (i. e. when no code is executed) - (C0 to C8)
Reference: here.
I have since fixed this problem by re-installing Ubuntu 16.04 and not switching from the nouveau video driver. I also disable updates and everything been working good for about 2 months now.
Gaming is pretty good but I usually play steam games so doesn't push any kinda hard core graphics
Well, I had the same problem: My PC was freezing randomly. I tried Ubuntu 16, 17 and 18.04 and everything was the same. I tried several drivers and didn't get a solution. I tried several solutions that I found in the forums (including this) and got bad and harmful results.
My solution was: I stopped using the graphical nvidia card, removed it and now I'm using the integrated Intel HD graphics card (Intel® HD Graphics 530 card (Skylake GT2)) and all the problems were solved!
I fixed mine using a few commands from #Qoros solution above. i just ran apt-get update, apt-get install nvidia-current, and sudo reboot. cheers to #Qoros btw!
For me, none of the approaches described in rest of the answers worked.
I was opening multiple terminal tabs running some heavy processes and ubuntu used to freeze when I had 6-7 tabs. I tried monitoring the resources used while I was starting my processes in terminal tabs. You can do it by opening System Monitor app and going to Resources tab.
What I noticed is that when my RAM(8GB) and my swap space(1GB) were completely used up, ubuntu would freeze.
As a solution, I increased my swap space and made it 16GB. After this memory never gets used completely and ubuntu doesn't freeze.
https://askubuntu.com/questions/178712/how-to-increase-swap-space decsibes how to increase swap space.
I am trying to make a use of QEMU in my embedded software development process. I think it will be useful for me to run my code without having to touch the hardware. Especially when the software is sitting in the user-space of Linux. Now, I am trying to get my head wrapped around the big concepts in QEMU.
At what point is QEMU virtualizing the hardware? Can I assume it virtualizes x86 when the host platform is also x86 with virtualization technology built into the processor?
In other words, can I assume QEMU is emulating the hardware when the target platform is not the same as host platform?
It's a general-purpose emulator software (type 2 hypervisor) which can use virtualization when the target and hosts are of the same architecture. In Linux you need to enable the KVM kernel module to be able to use the virtualization technology of the processor.
ESXi installs on a physical machine separately. I mean it's not a software which installs on an OS like a Linux machine. Am I right?
I need something like ESXi server to be installed on a CentOS 5 physical machine.
What's your suggestion?
ESXi is a Hypervisor which installs directly onto hardware. Its almost like a mini OS if you like, so you can't install that on Linux. Software which will provide virtualization on top on the OS will be the likes of KVM, Xen or VirtualBox which would be better suited for you (sounds like it anyway)
Have a look at this link
We have a 64bit virtual machine (CentOS) that we'd like to run on 64bit host-machine (may be running under any OS), but that host-machine doesn't support hardware virtualization, which, you know, should be for running 64bit virtual machines in it.
I tried VirtualBox and VMware Player, but they both have this issue with non-hardware-virtualization processor. I thought maybe another virtualization system may help, like OpenVZ or XEN or KVM? What do you think?
Thanks in advance!
Qemu http://www.qemu.org/ can virtualise architectures without hardware support (even ARM, MIPS, etc). However, it will probably be a lot slower than using qemu-kvm with virtualisation hardware.