search for: mount_tag

...inux-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. And virtme sometimes supports modules :) > > $dir/bin/x86_64-linux-gnu/qemu-system-arm \...

...inux-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. And virtme sometimes supports modules :) > > $dir/bin/x86_64-linux-gnu/qemu-system-arm \...

...> printed when virtio doesn't find any match in device name so it would > look like the mount name doesn't match maybe? > > Could we get your exact qemu command line to confirm? (the name that > needs to match is /dev/root here, used for booting as root= and for qemu > as mount_tag) I re-transposed Richard'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/...

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

...l6.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 \ > &gt...

...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 combination of things that I > try. So far, I have trie...

...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/arm-linux-gnueabihf/init rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro console=tty...

...ere'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=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM config:ircffbd3...

...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 combination of things that I > try. So far, I have trie...

...ay/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=trans=virtio,vers...

Good afternoon. I am having trouble trying to set up shared folders in the guest VM using VirtualBox hypervisor. No matter what configuration is defined in my XML, it never works, I mean, no shared folder is added/specifyed, then, inside the guest, when I try to mount the folder, I always get a protocol error. If I use VirtualBoxManage, I can add/specify shared folders easily and mount it with

This is an extended version of: https://www.redhat.com/archives/libguestfs/2019-September/msg00178.html It adds a couple of simple code changes, so it makes it possible to drop more modules. In addition, more unused modules were dropped. Pino Toscano (5): tests: switch away from xgetcwd daemon: move read_whole_file to common utils daemon: switch from read_file to read_whole_file daemon:

...do 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 combination of things that I try. So far, I have tried Linux 3.10.7-gentoo (Gentoo patchset)...

...do 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 combination of things that I try. So far, I have tried Linux 3.10.7-gentoo (Gentoo patchset)...

v1 -> v2: - Use intprops macro suggested by danpb. Rich.

This is an extended version of: https://www.redhat.com/archives/libguestfs/2019-September/msg00288.html Apparently I forgot it on my tree, so I'm posting that series again, adding an extra cleanup more due to the v2v/common splits. Pino Toscano (6): tests: switch away from xgetcwd daemon: move read_whole_file to common utils daemon: switch from read_file to read_whole_file daemon:

...e guest which has active filesystem shares (type='mount'). I get this error: Call to virDomainSaveFlags failed: internal error: unable to execute QEMU command 'migrate': Migration is disabled when VirtFS export path '${TARGET_PATH}' is mounted in the guest using mount_tag '$TAG' (Libvirt::Error) I have a use case where I very much would like this combination. It wouldn't be a problem if the filesystem shares would have to be temporarily unmounted while taking the snapshot, and mounted again after restoring it. However, while trying that, `mount` han...

...9;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=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM co...

...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=virt...