search for: fsdev

...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 will give you a much more functional system at the cost of a small fraction of a second of additional boot time....

...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 will give you a much more functional system at the cost of a small fraction of a second of additional boot time....

...re's my working Qemu line: > > >> qemu > > >> -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 \ > > >> > > >> -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img \ > > >> -fsdev > > >> local,id=r,path=/srv/overlay/run/irc,security_model=passthrough \ > > >> -device virtio-9p-pci,fsdev=r,mount_tag=root \ > > >> -nographic \ > > >> -m 256M \ > > >> -machine pc-i440fx-2.1,accel=kvm \ > > >> -net...

...Selinux is disabled on the host, and accessmode to the share is set to passthrough in both cases. Here's my working Qemu line: qemu -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img -fsdev local,id=r,path=/srv/overlay/run/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=...

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

...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 1024 \ -kernel $dir/boot/arm-linux-gnueabihf/Image \ -append 'root=/dev/root init=/sbin/ar...

...t; passthrough in both cases. >> >> Here's my working Qemu line: >> qemu >> -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 \ >> >> -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img \ >> -fsdev >> local,id=r,path=/srv/overlay/run/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=...

...rNext/LinuxPort/devfs.README.txt : Value too large for defined data type stat space/sunpci/drives/F.drive/docs/StorNext/StorNextNotes.doc : Value too large for defined data type I also see the same error going from our IRIX 6.5.15 machine, and the error is seen on a directory vs a file: stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver : Value too large for defined data type stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver/CVS : Value too large for defined data type Any ideas as to why this is occurring and what I can do to get around this? I appears that the file ge...

...>> > >> Here's my working Qemu line: > >> qemu > >> -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 \ > >> > >> -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img \ > >> -fsdev > >> local,id=r,path=/srv/overlay/run/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 > &...

...ommand 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 1024 \ -kernel $dir/boot/arm-linux-gnueabihf/Image \ -append 'root=/dev/root init=/sbin/ar...

...too 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: > > localhost ~ # modprobe crc32 > qemu-system-x86_64: virtio: trying to map MMIO memory > &gt...

...nd root=/dev/vda \ -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ -drive file=/var/lib/nova/instances/instance-0000003d/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/lustre/ \ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=testfs,bus=pci.0,addr=0x3 \ -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0000003d/console.log \ -device isa-serial,chardev=charserial0,id=serial0 -charde...

...monitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg/lv_vm_name,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -fsdev local,security_model=mapped,id=fsdev-fs0,path=/srv/share -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=virtfs_share,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:68:90:d8,bus=pci.0,addr=0x4 -chardev pty,id=c...

...too 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: > > localhost ~ # modprobe crc32 > qemu-system-x86_64: virtio: trying to map MMIO memory > &gt...

...nux is disabled on the host, and accessmode to the share is set to passthrough in both cases. Here's my working Qemu line: qemu -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img -fsdev local,id=r,path=/srv/overlay/run/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:r...

...sleep(2); if (syscall(SYS_getrandom, buf, sizeof(buf), 0) == -1) return 5; return 0; } $ qemu-system-x86_64 -nodefaults -machine q35,accel=kvm -nographic -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0 -kernel linux-4.7/arch/x86/boot/bzImage -fsdev local,path="$PWD/root",security_model=none,id=root -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-serial -chardev stdio,id=stdio -device virtconsole,chardev=stdio -monitor none -append "root=/dev/root rw rootfstype=9p rootflags=trans=virtio console=hvc0 init=/str...

...sleep(2); if (syscall(SYS_getrandom, buf, sizeof(buf), 0) == -1) return 5; return 0; } $ qemu-system-x86_64 -nodefaults -machine q35,accel=kvm -nographic -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0 -kernel linux-4.7/arch/x86/boot/bzImage -fsdev local,path="$PWD/root",security_model=none,id=root -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-serial -chardev stdio,id=stdio -device virtconsole,chardev=stdio -monitor none -append "root=/dev/root rw rootfstype=9p rootflags=trans=virtio console=hvc0 init=/str...

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: localhost ~ # modprobe crc32 qemu-system-x86_64: virtio: trying to map MMIO memory The behavior is consistent no matter what c...

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: localhost ~ # modprobe crc32 qemu-system-x86_64: virtio: trying to map MMIO memory The behavior is consistent no matter what c...