search for: initramdisk

....6.12.6-xen0.img For domU, my xm file contains: kernel = "/boot/vmlinuz-2.6.12.6-xenU " My root is an ext3 file system on /dev/hda9 I am not sure about the ramdisk. I created a ramdisk by first doing the depmod and then using the mkinitrd command as given in the README file. I use that initramdisk for dom0. Should I use another ramdisk for domU? >From README, the mkinitrd commands goes like: # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.12.6-xen.img 2.6.12.6-xen Will it make a difference if I change the kernel-version 2.6.12.6-xen to 2.6.12.6-xenU ? The man pa...

Hi, this patch series attempt to uninstall VMware tools on all the Linux guests, and reduce the uninstallation time needed in some cases: - v2v tries to workaround the slowest part of the tarball-installed VMware tools - v2v uninstalls the open source VMware tools (open-vm-tools) Thanks, Pino Toscano (2): v2v: linux: remove open-vm-tools packages v2v: linux: try to trick

...dracut-initqueue timeout .... And it drops to "dracut#" shell, where I can see that there is no /dev/sda listed on /proc/partitions. I think I tried everything! My last try was, during Packer build, to append "add_drivers+=" sd_mod" to /etc/dracut.conf and re-building initramdisk by running "dracut -f". However, it does not boot either (on ESXi)! I can still boot using Rescue mode on VMWare, then, I can see that sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut does not load it! I tried "force_drivers+=" sd_mod", doesn't wor...

When installing the VMware tools from tarball, the installation script rebuilds the initramdisk of all the available kernels to inject the missing kernel drivers; in the end, the information on which kernels were changed is recorded in the internal "database" of the installation answers. When uninstalling the VMware tools, the uninstallation script reads the saved answers, and in t...

...file, I know that .earlybss starts at 0x800 (or 0x1000), and a number of sections directly follow it. I also realize some allocated regions are system specific, depending on what the BIOS returns in its E820 map. I am, not surprisingly, interested in the regions where PXELINUX stores the kernel and initramdisk images after TFTP-ing them over. Thanks. Regards, Andy

Hi, I have been using pxelinux for quite a while. It works extremely well for us. Now, I am looking at something new. We would like to: boot ( some OS - hopefully linux )from the network using pxelinux. make a small partition dos partition on the first disk. connect ( via perl dbi ) to a back end database Download the appropriate files for either a winxp build OR a kernel/ramdisk for a

On Thu, 4 Feb 2016, Martinx - ????? wrote: > My last try was, during Packer build, to append "add_drivers+=" > sd_mod" to /etc/dracut.conf and re-building initramdisk by running > "dracut -f". However, it does not boot either (on ESXi)! > > I can still boot using Rescue mode on VMWare, then, I can see that > sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut > does not load it! I tried "force_drivers+=" sd_mod...

I read the following about memdisk : .... For any other size, the image is assumed to be a hard disk image, and should typically have an MBR and a partition table. The disk C/H/S geometry is determined by examining the partition table, so the entire image should be partitioned for proper operation. .... I'd like to create a bootable cd, wich boots a linux and some other tools. While

...devices as LVM was used in AWS (bare BIOS partitions everywhere else). Upgrading to CentOS 7 using the backup physical partition works without issue. On AWS, because of the LVM in use, and the backup partition being on the LVM, we need to use the CentOS 7.3 versions of the isolinux and EFI kernels, initramdisk images and LiveOS image in order to install from the LVM partition. Starting with 7.4 (1708), there was a change within Anaconda, and in particular the Blivet packages on the LiveOS image, that no longer allows the install source to be on an LVM partition. If you are having partitioning issues, I...

No one knows about this?! It''s normal for domU in Xen-3.3 to have only 16KB of CPU cache size? Thanks! Thiagi 2008/9/18 Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com> > Hi folks! > > After upgrading my Xen-3.2.0 to new Xen-3.3.0/Linux-2.6.18.8-xen-3.3.0 my > domU /proc/cpuinfo shows only: > > administrativo@vsrvXX:~$ cat /proc/cpuinfo >

In the disk partitioner, I can't 1) choose to make the LVM with root and swap be on a RAID 1. Is there some way to do that, rather than two separate partitions RAIDed? 2) They don't align, so I can't clone /dev/sda to /dev/sdb as a failover (for /boot and /boot/efi). I've created those two, manually, and nope, it wiped them out, so I can't clone