Sponsored Content
Operating Systems Linux Red Hat help about qemu-kvm boot with initrd Post 302691875 by yanglei_fage on Sunday 26th of August 2012 09:07:42 AM
Old 08-26-2012
Quote:
Originally Posted by neutronscott
I believe with initramfs you don't specify root.

Just find that it seems the initramfs in redhat not contains rootfs, only contains the kernel modules. how about in your side, I don't know how to check if it contains the rootfs

I see with initramfs, the kernel module loaded, and the if I sepcify with disk file for the root, it boot well
 

9 More Discussions You Might Find Interesting

1. Linux

initrd

ok, I'm trying to roll an initrd from scratch for learning purposes. I'm using cramfs for the filesystem so that I can modularize ext2 and ext3. The initrd has the modules required for ext3, a static insmod, a statis 'ash', static pivot_root, and a linuxrc that mounts the needed root partition... (0 Replies)
Discussion started by: thmnetwork
0 Replies

2. UNIX for Dummies Questions & Answers

kernel and initrd on machine with little amount of RAM

(rus cp1251) Вобщем смысл поста такой: я пытаюсь сделать Linux на дискетке и всё это опробовать на 386... =D поскольку памяти там мало, а ядро и initrd вроде как зажаты, я хотел бы узнать а) я сделал ядро (bzImage) оно 600 Кб. оно в памяти займёт 600 Кб или оно ещё разожмётся? б) аналогично с initrd. и ещё: он вроде 4МБ а можно в параметрах ядра сделать поменьше, можно-ли в 1-2МБ памяти уместить initrd и ядро? (eng) i am try to make linux on diskette and run it on i386... =D there are... (0 Replies)
Discussion started by: MR.Z
0 Replies

3. UNIX for Dummies Questions & Answers

Anyone ever used qemu and networked it ?

hi i got a virtual linux machine running on qemu my problem is connecting it to the internet im a bit confused weather i have to make a virtual network card in qemu and than tun tap it? can anyone thats done it before help me out? (1 Reply)
Discussion started by: russian460
1 Replies

4. Red Hat

Fedora installation getting stuck in initrd.img

I have a 80GB hard disk with WinXP already installed.I had tried installing Fedora 10 earlier without creating new partitions(real foolish and ignorant of me :o:o ) and tried creating partitions using Fedora10 bootable.It didnt work.Then I created a free partition and again tried installing... (4 Replies)
Discussion started by: ganesh.k28
4 Replies

5. Linux

What's role of swap in initrd?

Hello, I want to know why initrd need swap for work. In the shell of mkinitrd, it look for the swap partation for "swsuspdev", then write a sentence "resume /dev/sdXX" in the file init from initrd.gz, and the /dev/sdXX is the swap partation. Why initrd need swap when it boot a system? what is... (4 Replies)
Discussion started by: ZR_Lang
4 Replies

6. UNIX for Advanced & Expert Users

Could I get the initrd.img file without recompile the kernel?

Hi, all: The vmlinuz-3.0.4.old is a kernel previous to the current running kernel vmlinuz-3.0.4 which is compiled the most currently. Could I get the initrd.img-3.0.4.old without recompile under the condition that the config-3.0.4.old, System.map-3.0.4.old and vmlinuz-3.0.4.old exist? if it... (1 Reply)
Discussion started by: liklstar
1 Replies

7. UNIX for Advanced & Expert Users

Help with adding a new driver in initrd at install time

I have a really old distro (FC7) that I am trying to make compatible with some new hardware (ie. new RAID drivers)... I put the RAID driver into the ISO so that the installer can detect the RAID set... but post-install (aka: first boot) it appears that the Anaconda-generated initrd does not have... (0 Replies)
Discussion started by: jjinno
0 Replies

8. Virtualization and Cloud Computing

QEMU performance?

Heyas So, i like doing custom a LiveImage of my OS. Using Redhats kickstart/livecd-creator method. Anyway, so i would like to test the liveimages... AND also, i WOULD like to install FreeBSD, Solaris, or whatever, onto a Virtual Machine. I used to use Oracles Virtualbox, but eversince... (3 Replies)
Discussion started by: sea
3 Replies

9. Red Hat

KVM/Qemu allocated memory not showing in guest

So we have a RHEL 7.6 workstation with 128 gigs of ram. The OS sees all the ram and 80 cors (40 HT) We have 1 guest with 8 CPUs and 32gigs of ram running RHEL 7.6 workstation as well. We are trying to create another guest with 64 CPUs and 80 gigs of ram. We setup the system using... (0 Replies)
Discussion started by: joeg1484
0 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 02:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy