search for: rootfstyp

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

...irtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p > rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ > -serial stdio \ > -fsdev local,id=root,path=$dir,security_model=none \ > -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ > -monitor none This is similar to what virtme does, except that virtme wil...

...irtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > > $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ > -m 1024 \ > -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ > -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p > rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ > -serial stdio \ > -fsdev local,id=root,path=$dir,security_model=none \ > -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ > -monitor none This is similar to what virtme does, except that virtme wil...

...bler-import 2010-02-08 10:31:44.000000000 +0100 @@ -46,15 +46,9 @@ cobbler distro add --name="oVirt-Node-$node_arch" --arch=$node_arch \ --initrd=$node_dir/tftpboot/initrd0.img -- kernel=$node_dir/tftpboot/vmlinuz0 \ - --kopts="rootflags=loop root=/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" + --kopts="rootflags=loop root=live:/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" I didn't try this patch but I think this is the way to get this kind of config in /var/lib/tftpboot/pxelin...

...ot with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type ext3 (rw) However, I am unsure if the klibc warning has the potential to cause any problems. Using rootfstype=ext3 gets rid of this error, but it'd still be nice to properly shut this message up on an automatic boot (no rootfstype). - Aaron Griffin

> /diskless/pxelinux.cfg/default > --- > DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo > APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs > nfsroot=10.0.0.11:/diskless/gentoo-x86_64 > init=/linuxrc That pxelinux.cfg/default seems "tolerable" for older versions, but not for Syslinux 5+. Is this an inadequate copy of the actual content? Or is it really a trustworthy copy of your actual default co...

...-i440fx-2.1,accel=kvm \ > > >> -netdev tap,id=net0 -device > > >> virtio-net,netdev=net0,mac=52:54:00:12:36:34 \ > > >> -smp 1,sockets=1,cores=1 \ > > >> -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro > > >> rootfstype=9p console=ttyS0' > > >> > > >> And here my libvirt VM config: > > >> <domain type='kvm'> > > >> <name>irc</name> > > >> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> > > >>...

...--install /boot/extlinux cp /usr/share/syslinux/menu.c32 /boot/extlinux/ and the config file /boot/extlinux/extlinux.conf: TIMEOUT 30 UI menu.c32 MENU TITLE Boot Menu MENU COLOR title 1;37;40 MENU COLOR border 30;40 MENU COLOR unsel 37;40 #title Gentoo bzImage-3.1.0 #kernel /bzImage-3.1.0 quiet rootfstype=ext4 luks enc_root=/dev/sda2 lvm root=/dev/mapper/vg-rootfs #initrd /initramfs.cpio.gz LABEL Gentoo bzImage-3.1.0 KERNEL /bzImage-3.1.0 INITRD /initramfs.cpio.gz APPEND quiet rootfstype=ext4 luks enc_root=/dev/sda2 lvm root=/dev/mapper/vg-rootfs LABEL test MENU LABEL asdasd KERNEL /bzImage...

...phic \ >> -m 256M \ >> -machine pc-i440fx-2.1,accel=kvm \ >> -netdev tap,id=net0 -device >> virtio-net,netdev=net0,mac=52:54:00:12:36:34 \ >> -smp 1,sockets=1,cores=1 \ >> -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro >> rootfstype=9p console=ttyS0' >> >> And here my libvirt VM config: >> <domain type='kvm'> >> <name>irc</name> >> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> >> <memory unit='KiB'>262144</memory> >&...

...model=passthrough -device virtio-9p-pci,fsdev=r,mount_tag=root -nographic -m 256M -machine pc-i440fx-2.1,accel=kvm -netdev tap,id=net0 -device virtio-net,netdev=net0,mac=52:54:00:12:36:34 -smp 1,sockets=1,cores=1 -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM config: <domain type='kvm'> <name>irc</name> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMe...

not just console= This is to allow vendor-specific boot parameters to survive when the image is installed to disk. Signed-off-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-early | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 4b85102..c17ea74 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@

.../irc,security_model=passthrough -device virtio-9p-pci,fsdev=r,mount_tag=root -nographic -m 256M -machine pc-i440fx-2.1,accel=kvm -netdev tap,id=net0 -device virtio-net,netdev=net0,mac=52:54:00:12:36:34 -smp 1,sockets=1,cores=1 -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM config:ircffbd32eb-a693-eadd-8923-18de801374722621442621441hvm/srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64/srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.imgroot=virtfs:root rootflags=trans=virtio,version...

On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 11:50 AM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 8:45 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >>> On Wed, Aug 27, 2014 at 08:11:15AM -0700, Andy Lutomirski wrote: >>>> On Aug 26, 2014 11:46 PM, "Stefan Hajnoczi" <stefanha

On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 11:50 AM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 8:45 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >>> On Wed, Aug 27, 2014 at 08:11:15AM -0700, Andy Lutomirski wrote: >>>> On Aug 26, 2014 11:46 PM, "Stefan Hajnoczi" <stefanha

...hard's command line to my environment and it worked. Thanks for pointing me in that direction. For the record, I used: $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ -m 1024 \ -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ -serial stdio \ -fsdev local,id=root,path=$dir,security_model=none \ -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ -monitor none $dir/bin/x86_64-linux-gnu/qemu-system-arm \ -M virt \ -cpu cortex-a15 \ -m 102...

....0.0.11 GATEWAY IP: 10.0.0.1 PXE-E32: TFTP open timeout PXE-E32: TFTP open timeout PXE-E32: TFTP open timeout PXE-M0F: Exiting Broadcom PXE ROM. strike F1 to retry boot, F2 for setup utility --- /diskless/pxelinux.cfg/default --- DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs nfsroot=10.0.0.11:/diskless/gentoo-x86_64 init=/linuxrc /etc/conf.d/in.tftpd (using tftp-hpa) --- INTFTPD_PATH="/diskless" INTFTPD_OPTS="-R 4096:32767 -v -s ${INTFTPD_PATH}" /etc/dhcp/dhcpd.conf --- ddns-update-style none; authoritative; log-facility local7...

...3. This worked perfectly fine for all non-root fs, but I am having trouble converting the root fs, too. Here's what I did: 1. rebuilt my kernel (2.4.20, x86) with ext3 support linked in statically - no module. 2. Added a journal file to my root fs using 'tune2fs -j'. 3. Added 'rootfstype=ext3' to the kernel arguments in lilo.conf and of course ran lilo. During startup, my kernel emits the following lines: Kernel command line: auto BOOT_IMAGE=normal ro root=301 rootfstype=ext3 1 <lines deleted> kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesyste...

...t; >> -machine pc-i440fx-2.1,accel=kvm \ > >> -netdev tap,id=net0 -device > >> virtio-net,netdev=net0,mac=52:54:00:12:36:34 \ > >> -smp 1,sockets=1,cores=1 \ > >> -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro > >> rootfstype=9p console=ttyS0' > >> > >> And here my libvirt VM config: > >> <domain type='kvm'> > >> <name>irc</name> > >> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> > >> <memory unit='KiB'&...

...propriate virtio dievice?) Virtme looks interesting. If it's any use, here is my modest QEMU command line collection. $dir/bin/x86_64-linux-gnu/qemu-system-x86_64 \ -m 1024 \ -kernel $dir/boot/x86_64-linux-gnu/bzImage-x86_64 \ -append 'root=/dev/root init=/sbin/x86_64-linux-gnu/init rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' \ -serial stdio \ -fsdev local,id=root,path=$dir,security_model=none \ -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root \ -monitor none $dir/bin/x86_64-linux-gnu/qemu-system-arm \ -M virt \ -cpu cortex-a15 \ -m 102...

Hi Richard, On 11/25/2013 10:49 AM, Richard Yao wrote: > I booted a Gentoo Linux installation in QEMU with a 9P rootfs as follows: > > sudo qemu-kvm -cpu host -m 1024 -kernel > /mnt/test/usr/src/linux-3.13-rc1/arch/x86/boot/bzImage -append > 'root=/dev/root rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro > console=ttyS0' -serial stdio -fsdev > local,id=root,path=/mnt/test,security_model=none -device > virtio-9p-pci,fsdev=root,mount_tag=/dev/root > > The system boots fine, but attempting to load any module will fail: > > local...