Your message dated Fri, 21 Dec 2018 19:16:44 +0300
with message-id <[email protected]>
and subject line Re: Bug#696289: Cannot use virtfs with mount_tag=/dev/root
has caused the Debian Bug report #696289,
regarding Cannot use virtfs with mount_tag=/dev/root
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
696289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696289
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-kvm
Version: 1.1.2+dfsg-3
Severity: normal
kvm doesn't seem to accept mount_tag=/dev/root , and gives a strange
series of error messages when attempting to do so:
kvm: -virtfs local,id=root,path=/,mount_tag=/dev/root,security_model=none:
Parameter 'id' expects an identifier
Identifiers consist of letters, digits, '-', '.', '_', starting with a letter.
duplicate fsdev id: /dev/root
This breaks the ability to use a virtio 9p filesystem as the root
filesystem without using an initramfs, since the kernel always mounts
"/dev/root" as the root filesystem. Judging by the error messages, kvm
seems to get the id and mount_tag options mixed up; looking at the code,
kvm seems to attempt to use mount_tag as the fsdev id, but yet still
requires the id option.
Please consider fixing this, to unbreak virtio 9p root filesystems.
Thanks,
Josh Triplett
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages qemu-kvm depends on:
ii adduser 3.113+nmu3
ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3
ii libaio1 0.3.109-3
ii libasound2 1.0.25-4
ii libbluetooth3 4.99-2
ii libbrlapi0.5 4.4-6
ii libc6 2.13-37
ii libcurl3-gnutls 7.28.0-3
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libgnutls26 2.12.20-2
ii libiscsi1 1.4.0-3
ii libjpeg8 8d-1
ii libncurses5 5.9-10
ii libpng12-0 1.2.49-3
ii libpulse0 2.0-6
ii libsasl2-2 2.1.25.dfsg1-6
ii libsdl1.2debian 1.2.15-5
ii libspice-server1 0.11.0-1
ii libtinfo5 5.9-10
ii libusbredirparser0 0.4.3-2
ii libuuid1 2.20.1-5.3
ii libvdeplug2 2.3.2-4
ii libx11-6 2:1.5.0-1
ii python 2.7.3-3
ii qemu-keymaps 1.1.2+dfsg-3
ii qemu-utils 1.1.2+dfsg-3
ii seabios 1.7.0-1
ii vgabios 0.7a-3
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages qemu-kvm recommends:
pn bridge-utils <none>
ii iproute 20120521-3
Versions of packages qemu-kvm suggests:
ii debootstrap 1.0.44
pn samba <none>
pn vde2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:2.10.0-1
This has been fixed in 2.10, long time ago.
Thanks,
/mjt
--- End Message ---
