I have been using ubuntu 14.x from windows using virtual box.but suddenly ubuntu instance stopped working and when i start the virtual machine using vagrant up command it is saying
Couldn't remount RDWR because of unprocessed orphan inode list.
Does anyone knows how to boot virtual machine and solve mounting issue.?
Related
vagrant 1.9
virtualbox 5.1.12
base box: https://github.com/CommanderK5/packer-centos-template/releases/download/0.7.2/vagrant-centos-7.2.box
Current Laptop: Windows7 on Dell Latitude E7270 with 250gb ssd on bitlocker.
So with that out of the way, I was previously using vagrant with the same version of vagrant, virtualbox and base box on a different computer with a mechanical hdd without bitlocker. Everything is ok until I upgraded my laptop.
In vagrant if we do vagrant init in a folder and launch vagrant it will mount the folder with the VagrantFile to the /vagrant on the guest machine. On the current laptop it takes a loong time for vagrant to mount this shared folder.
Do you think its bitlocket that might be causing this issue?
Thanks
I am trying to boot a cloned image on KVM ,which is in the raw format, the image is a clone of aws ubuntu 14.04 LTS hvm instance. It gives me an error saying no bootable device found. The same image boots up when I specify the kernel path explicitly while creating the VM.
I am using virt-manager to create the VM and the qemu version is 2.0.0
I have tried changing the disk bus but nothing helped.
Can anyone help ?
It was because of the partitions on the Ubuntu 14.04 LTS. Cloned the entire disk. Boots up fine now.
I'm trying to run a CentOS distribution on VMWare. Because the Linux is running calculations, i need this machine to never stop.
I've tried to run it in VMWare player, after 20 minutes of "innactivity", the session logout. I've tried to run it in VMWare Workstation, it does the same.
How do i manage the Linux or VMWare to prevent this logout ?
Thank you.
I had the same problem a while ago, if I can remember correctly, you need to do the following:
Shutdown the Virtual Machine.
Locate the Virtual Machine .vmx File.
Open The .vmx file in any text Editor.
Add This line: suspend.disabled = "TRUE"
Start the Virtual Machine again.
Hope this helps.
Problem description:
When I boot my VirtualBox Guest OS, the mounting of the shared file-system - which is referenced in /etc/fstab - fails.
However, after login - mount -a succeeds.
Details:
The boot process gets stuck here ...
... and pressing s continues the boot process, which finishes.
In the shell, I verify that my shared directory is not mounted:
But now, from the shell, the mount of the shared file-system succeeds:
What should I do to make my mount succeed during start-up?
Environment:
VirtualBox: 4.3.12.r93733
Host OS: Windows 7
Guest OS: Linux ubuntu 3.13.0-32-generic #57~precise1-Ubuntu x86_64 GNU/Linux
/etc/fstab
Relevant lines in /var/log/boot.log
You don't have to mount it, VitrualBox will make it for you. For me,these steps worked on my System (VirtualBox 5.0.10 on Windows 7 and Kubuntu 14.04 guest system):
In VirtualBox, configure your shared folder for your machine under 'Shared Folder'. Pick up the directory on your host system (e.g. D:\shared) and set a name for your guest system (e.g. shared).
Boot the guest system. Now you should have a mounted folder under \media\sf_shared.
Thats all. VirtualBox manages this for you.
You need to install VirtualBox Guest Additions properly and use VirtualBox Manager to specify share folders. The issue happens because the mount point is in place with root permissions. The default mount location is in /media/sf_.
You can change mount point with VBoxControl command. To change the mount point from /media/sf_... to /home/user/sf_... use the command:
sudo VBoxControl guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir /home/user/
To check if that's working:
sudo VBoxControl guestproperty get /VirtualBox/GuestAdd/SharedFolders/MountDir
After attempting to import data from one Oracle database to another on my D drive my computer started to hang and I had to manually reboot my machine. In doing so my virtualbox CentOS vm was hard rebooted as well. Now when I attempt to start my CentOS VM I get this error:
I went to this forum to see if they had a solution, but the solution for checking the 'Use host I/O cache' didn't work for me:
virtualbox forum
I also tried removing the vm instance and recreating a new instance with the same storage, but that didn't work either and I got the same error.
Any suggestions?
The problem ended up being that because the D: drive was dirty, I had to move over the CentOS virtual drive to the C: drive.