You can install the correct kernel header files like so:
$ sudo yum install "kernel-devel-uname-r == $(uname -r)"
This command will always install the right version.
$ sudo yum install "kernel-devel-uname-r == $(uname -r)"
Loaded plugins: auto-update-debuginfo, changelog, langpacks, refresh-packagekit
No package kernel-devel-uname-r == 3.12.6-200....
You're not going to be able to use GParted because the filesystem is on LVM and GParted does not support that.
First, TAKE A BACKUP OF THE VM. Then perform the following as "root" from a command line.
It looks like you've already rebooted but just in case, ensure the kernel recognizes the larger disk
echo 1 > /sys/class/scsi_disk/0:0:0:0/device/rescan
From Ubuntu (in VM) Install gparted by executing sudo apt-get install gparted in Terminal.
Open gparted either from terminal or from dash. Then extend you disk, maybe you may have to move your extended partition at the end of disk.
You do not need a live CD for this to work. I'm basically summarizing the other answers given here:
From Ubuntu (in VM) install gparted by executing sudo apt-get install gparted in terminal
Open sudo gparted from terminal
Rightclick on the swap partition, click "swapoff"
Delete swap partition
Extend your data partition, but leave enough space to create a ...
If you only changed the partition size, you're not ready to resize the logical volume yet. Once the partition is the new size, you need to do a pvresize on the PV so the volume group sees the new space. After that you can use lvextend to expand the logical volume into the volume group's new space. You can pass -r to the lvextend command so that it ...
From the btrfs gotchas page:
Files with a lot of random writes can become heavily fragmented (10000+ extents) causing trashing on HDDs and excessive multi-second spikes of CPU load on systems with an SSD or large amount a RAM.
On servers and workstations this affects databases and virtual machine images.
The nodatacow mount option may be ...
It worked for me too on a HP Spectre 4k laptop (windows 10):
Right click on the vmware player icon on the desktop shortcut and click properties.
Move to compatibility tab.
Check the option "override high DPI scaling behavior. And select the System Enhanced for Scaling performed by:.
Apply and restart VM.
It should work. Got a result after 5 hours spent on ...
This worked better for me as it gives me specific information about the manufacturer and the product name.
dmidecode -t system|grep 'Manufacturer\|Product'
Output on Dell server:
Manufacturer: Dell Inc.
Product Name: PowerEdge C5220
Output on Virtualbox VM:
Manufacturer: innotek GmbH
Product Name: VirtualBox
Output on KVM/QEMU:
When you install CentOS with the GUI installer, is very easy to miss the configuration part where you make able the network interface to be bringed up when the system boots.
You have to edit /etc/sysconfig/network-scripts/ifcfg-YOUR_NIC_NAME, and specifically this:
next time you will boot the server, the NIC should be up.
Download gparted LIVECD iso from here
From your VM Choose the iso file and boot as live CD
Add the iso into your cd-rom drive from the GuestVM settings
Set to boot from the CDROM in BIOS (F2 when you start your VM)
Once tha gparted Live Cd runs you can use gparted now
Choose the partition to resize and choose the new size and then apply
When end ...
There's nothing to fix. This is normal operation. When the logfile is rotated by logrotate, it tells rsyslog to close and re-open its logfile file handles by sending it a HUP signal.
If rsyslog doesn't do that, then it will continue to write its log output to the OLD logfiles, not to the new ones because the file handles will still connect to the old ...
I would upgrade the kernel release version itself instead of trying to install the Linux kernel headers for the old version (4.3.0) of the kernel. Perform the following step after updating the Kali /etc/apt/sources.list file with the latest version of the Kali rolling repository:
sudo apt-get update # this pulls the latest packages list from the kali ...
Background on KVM
I think this is partly due to expectations with KVM. KVM is first and foremost a server product and not a desktop product for virtualization. It can be used in either application but it's definitely suited more for being used on a server.
I use it on 3+ hosts at work each hosting 5-10 VMs apiece and it has run flawlessly and is easy to ...
I have similar problem on Ubuntu. The workaround I use is:
echo never > /sys/kernel/mm/transparent_hugepage/defrag
echo 0 > /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
The source of the workaround is in a Fedora bug report “khugepaged eating 100%CPU”. The bug was never fixed.
This is less drastic then disabling entire transparent_hugepage ...
open-vm-tools is developed by VMware, see their GitHub page for details. That page provides the following answer to your question:
It is recommended that open-vm-tools be used for the Linux distributions where open-vm-tools is available. VMware will not provide OSPs for operating systems where open-vm-tools is available.
So you should install open-vm-...
Your problem could be "distribution synchronization". Running this command solved my problem.
Synchronizes the installed package set with the latest packages
available, this is done by either obsoleting, upgrading or downgrading
as appropriate. (http://man7.org/linux/man-pages/man8/yum.8.html)
That's typically not a problem. The WiFi on the host is not actually directly accessible to the VMware guests, or any VM guests using other technologies such as KVM, VirtualBox, etc.
The hardware that's present in the physical host is interacted through virtual hardware that's presented to the guest VMs through the software BIOS that the various ...
VMware's ESXi is apparently based on the linux kernel. There is a lawsuit about this because the linux kernel is under GPL v2.
Here is a comparison between a system using a complete linux kernel and a system with VMware ESXi.
(Figure under CC BY-SA 4.0 by Software Freedom Conservancy)
Read the following FAQ for full details:
Frequently Asked Questions ...
It's likely related to the mass storage being VMware in both cases. Basically, it's saying that it tried to execute a SCSI command called WRITE SAME which is used to write the the same block of data over x number of consecutive disk blocks. It's usually used to zero particular regions on a disk.
If the actual zero'ing operation doesn't fail then the ...
Sorry, I think I've found the answer myself: http://wiki.squid-cache.org/KnowledgeBase/IllegalInstructionError.
Illegal Instruction errors on Squid 3.4
Synopsis Squid 3.4 and later, running on certain paravirtualized
systems and even some claiming full virtualization (at least KVM, Xen,
and Xen derivatives are confirmed so far) ...
For installing the open source VMware Tools for CentOS, you need first to install the EPEL repository with:
yum --enablerepo=extras install epel-release
Then to install the actual open source VMware Tools, it is indeed:
yum install open-vm-tools
This time, it won't give you any error.
Additionally, if installing VMWare Tools (open or not), take care to ...
After blacklisting piix4_smbus, run update-initramfs -u.
I don't remember off the top of my head which storage controller drivers are used in a VMware virtual machine, but ata_piix is a very likely candidate.
If the initramfs generator only does simple string matching on module names, it might be picking up i2c-piix4 in addition to the ata_piix storage ...