I've got problems installating the VMWARE ESXi Server.
The Installation finishes without any error messages and prompts me to reboot.
After pressing Enter the System reboots. While booting through the yellow loading-screen it switches to black and displays the following Error-Message:
PANIC: Failed to find HD boot partition
All modules have been loaded without any errors.
After typing unsupported into the console the busybox comes up.
I tooked a look into the /dev/disks directory but no disk devices gets listed in difference to the installation process.
Switching to the system-console during installation both sata disks on MPC51 controller are shown.
The controllers are named vmhba0 and vmhba32.
Does anyone know how to solve the problem?!
Hardware is a ESPRIMO P5615 (nForce4) from Fujitsu-Siemens.
The only solution I have found is to run the server from a thumb drive and use the embedded hard drive to store your virtual servers. This solution worked for me.
To achieve this in this way you will need:
A USB thumb drive 1GB or larger
An active Linux machine (or, use a liveCD option on your PowerEdge such as Knoppix or Gentoo LiveCD)
Mount your ESXi ISO:
mount -t iso9660 -o loop VMware-VMvisor-InstallerCD-3.5.0_Update_2-110271.i386.iso /mnt/esx
Write the installer file to the thumb drive:
tar xvzf /mnt/esx/install.tgz usr/lib/vmware/installer/VMware-VMvisor-big-3.5.0_Update_2-110271.i386.dd.bz2 -O | bzip2 -d -c | dd of=/dev/sdb
Assumptions here (adjust to your settings):
/dev/sdb is where your thumb drive resides
VMware-VMvisor-InstallerCD-3.5.0_Update_2-110271.i386.iso is the name of your ISO file
usr/lib/vmware/installer/VMware-VMvisor-big-3.5.0_Update_2-110271.i386.dd.bz2 is the name of the dd file in your iso (run tar ztf /mnt/esx/install.tgz to see what your exact file name is, it should be similar and relatively obvious)
It will take a few minutes to write, and when it's done simply boot off of this thumb drive. The PowerEdge servers have an internal USB (at least mine does) if aesthetics are important to you.
Source: http://cyborgworkshop.org/2008/08/30/install-vmware-esxi-onto-a-usb-thumbdrive/
EDIT 12/19/2009: ESXi 4.0.0 uses image.tgz instead of install.tgz to store it's dd file
Related
My computer kept rebooting lately showing me the blue screen while I was working on RHEL 'n vmware.
The last time the computer had reboot when I turned it on again and tried to work on RHEL here's what I have.
Did anyone of you face the same problem already ?
Thanks
In essence, the error is:
dracut-initqueue[217]: Warning: dracut-initqueue timeout - starting timeout scripts
[...]
dracut-initqueue[217]: Warning: Could not boot.
dracut-initqueue[217]: Warning: /dev/disk/by-uuid/5b757528-cc16-4ff0-819d-805c908d9b35 does not exist
Starting Dracut Emergency Shell...
Warning: /dev/disk/by-uuid/5b757528-cc16-4ff0-819d-805c908d9b35 does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exist the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
EDIT: after #Naushad Ahmad's comment:
# chroot /mnt/sysimage/
chroot: failed to run command '/bin/bash' : No such file ordirectory
# cat /etc/fstab
# cat /boot/grub2/grub.cfg
cat: /boot/grud2/grub.cfg: No such file or directory
# ls /boot
initramfs-3.10.0-693.cl7.x86_64.img
# _
[anaconda] 1:main* 2:shell 3:log 4:storage-log 5:program-log Switch tab: Alt+Tab | Help: F1
But the thing is when I start the rescue mode I ve that error message :
You don't have any Linux partitions.
When building a Docker image, there's some compilations of C++ scripts and I ended up with errors like:
src/amun/CMakeFiles/cpumode.dir/build.make:134: recipe for target 'src/amun/CMakeFiles/cpumode.dir/cpu/decoder/encoder_decoder_state.cpp.o' failed
virtual memory exhausted: Cannot allocate memory
But when building the same .cpp code on the host machine, it works fine.
After some checking, the error message seems to be similar to the one that people get on a Raspberry Pi, https://www.bitpi.co/2015/02/11/how-to-change-raspberry-pis-swapfile-size-on-rasbian/
And after some more googling, this post on the Mac forum says that:
Swapfiles are dynamically created as needed, until either the disk is
full, or the kernel runs out of page table space. I do not think you
can change the page table space limits in the Mac OS X kernel. I have
not seen anything in all the years I've been using OS X.
Is there a way to increase the swap space for Docker build on Mac OS?
If not, how else can be done to overcome the "virtual memory exhausted" error when building a Docker image?
That does not seem trivial to do with XHyve.
As stated in this thread
I think the default size of the VM is 16GB. I kept running out of swap space even after bumping the ram on the VM up to 16GB.
Check if the method used for a VirtualBox VM would apply in XHyve: see "How to increase the swap space available in the boot2docker virtual machine?"
boot2docker ssh
export SWAPFILE=/mnt/sda1/swapfile
sudo dd if=/dev/zero of=$SWAPFILE bs=1024 count=4194304
sudo mkswap $SWAPFILE
sudo chmod 600 $SWAPFILE
sudo swapon $SWAPFILE
exit
Check also this Digital Ocean Setup, again to test in your XHyve context.
mkswap is also seen here or in docker-root-xhyve/contrib/makehdd/makehdd.sh.
Since you have enough available memory in your host, I recommend you to assign more memory to the Docker VM that is behind.
As stated here:
As I can see that you are on OSX, which runs docker over a Linux VM. Configure the max memory clicking the whale icon in the task bar. By default is 2G.
For further information: https://docs.docker.com/docker-for-mac/#memory
I am trying to create a kickstart for Centos 7.3. I have a windows desktop with VMware Workstation Player installed. I started with a dvd that has Centos 7.3 on it. I then created a vm in VMware Workstation Player and installed the os. I restarted the vm and copied over all the files from /dev/sr0 from my dvd to a new place. I copied the anaconda file and renamed it to ks.cfg. I then used the command below to make an iso.
mkisofs -o /home/kickstart.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-road-size 4 -boot-info-able -J -R -v "centos7.3"
Next I took this and burned it to a blank cd using
growisofs --dvd-compat -Z /dev/cdrom=/home/kickstart.iso
When I use this in VirtualBox as the optical drive mounted the installer gets stuck on
Started Show Plymouth Boot Screen
Started Device-Mapper Multipath Device Controller
Starting Open-iSCSI...
Reached target Paths.
Reached target Basic System.
Started Open-iSCSI.
Starting dracut initqueue hook..
then on VMware Workstation Player it goes to
Started Show Plymouth Boot Screen
Started Device-Mapper Multipath Device Controller
Starting Open-iSCSI...
Reached target Paths.
Reached target Basic System.
Started Open-iSCSI.
Starting dracut initqueue hook..
... [sda] Assuming cache: write though
Why is it hanging on these spots? I have tried looked everywhere and can't seem to find any solutions so far.
you've probably found something else for this but in case not, or in case someone else encounters this... I encountered some issues with this as well. I don't know if I have the exact issue, though it was hanging on dracut init, and changing this bit allowed the install to continue.
What it turned out to be was the -V flag on the mkisofs command. Whatever you name it with the -V flag (which it doesn't look like you have), it needs to be the value of LABEL in your /isolinux/isolinux.cfg file. In my fiddling I was using "MyLinuxISO" for this value.
in my /isolinux/isolinux.cfg:
label linux
menu label ^Install CentOS Linux 7 with KS
menu default
kernel vmlinuz
append initrd=initrd.img inst.stage2=hd:LABEL=MyLinuxISO ks=cdrom:/ks.cfg
using mkisofs
mkisofs -o /home/kickstart.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-road-size 4 -boot-info-able -J -R -v -V "MyLinuxISO"
Don't know if this will help you but give it a shot?
Cheers
I've used this in the past but I must have got lucky. Now both Linux OSes I had have been deleted or screwed up but I can't for the life of me remember how I got them installed last time.
I really haven't got a clue, but are these the right steps:
(1) Uninstall all the old stuff
(2) Download Virtualbox 5.1.8 and install it
(3) Set up a new machine (eg. "Ubuntu64") and accept most of the defaults
I now know that that doesn't give me an OS to run! I need a "VDI" file containing a suitable Linux:
(4) Download Linux VDI for Virtualbox, unzip/un7zip etc to .vdi
Now is the tricky bit: how to I link this file to the Virtualbox new VM? In Storage, it seems to be set up to this file:
c:\Users\xxxxxx\VirtualBox VMs\Ubuntu\Ubuntu.vdi
That file exists but is some 2MB. Do I just copy the big .vdi I've just downloaded into that? Because if I do, it gives me an error:
UUID {7bfdc68e-2717-4c80-8613-6a2220358337} of the medium 'C:\Users
\xxxxxx\VirtualBox VMs\Ubuntu\Ubuntu.vdi' does not match the value
{553bdd10-e133-492f-85b9-3ec2c2fa4e67} stored in the media registry
('C:\Users\xxxxxx\.VirtualBox\VirtualBox.xml').
I would have edited that .xml file to match, but the UUID figure in that is different from either of the above! Anyway it seems like there is some official way of telling VB about this vdi; what is it? And if not, what have I done wrong? I downloaded another vdi with the same result.
I have a strange Darcs issue here.
I'm running a VM with a Linux guest OS and a Windows host OS. I've set up /mnt as a "shared folder"; any files placed here are actually stored in a folder on the host OS. Among other things, this causes all files to have their permissions set to 666 root,root. (Naturally, Windows doesn't support Unix-style file modes.)
Here's what happened:
cd /mnt/some-random-folder
darcs init
cd ~/some-random-folder
darcs pull /mnt/some-random-folder
Create a few files
darcs add the files
darcs record
So far, everything works fine. But now...
user1:~/some-random-folder> darcs push
Pushing to "/mnt/some-random-folder"...
Sun Jan 20 12:11:50 GMT 2013 User1
* Update dependencies.
Shall I push this patch? (1/1) [ynW...], or ? for more options: y
darcs: ./_darcs/tentative_pristine-0: rename: permission denied (Permission denied)
Apply failed!
Erm... what the heck just happened??
(And, more to the point, how do I make it stop happening and actually work?)
I tried using cp to synchronise the repos, thinking maybe the problem was that I started with a totally empty repo with no patches. That changes the error message (now it can't open _darcs\index - permission denied), but it still doesn't actually work.
Edit: Darcs 2.8.1 release.
Having played with this further, it appears that accessing files on the host OS from the guest OS does all sorts of strange things. Stuff like, I delete a file, ls tells me the file is gone, but when I try to write to that file, it says it can't because it already exists. Unmount and remount the filesystem and the problem goes away.
In short, I think this is probably nothing to do with Darcs at all, and is just the VMware drives being strange / buggy.
Permissions can be a bit tricky. It's worth checking to see if all file in that /mnt/some-random-folder really are writable by everybody.
I suspect this is not the ideal forum for this sort of question because it will likely involve a lot of back-and-forth chat to figure out what's going on. How about the darcs-users mailing list, or the #darcs IRC channel instead?