I question whether it's correct to dismiss this as invalid on the basis
that this is a minimal image. In general, my expectation is that the
minimal image is a suitable base for deploying any of the software in
Ubuntu, it's just a smaller starting point.
And the purpose of having a separate KVM kernel flavor is to provide the
best kernel for booting in VMs, excluding hardware-specific drivers that
are necessarily irrelevant when running on a reasonably-configured VM.
It does not obviously follow from either of these points that the nfsd
driver should be excluded from the KVM kernel. It's as reasonable to
run an nfs server in a VM as it is anywhere else. And installing the
nfs-server package in a minimal VM shouldn't fail with obscure errors.
** Changed in: linux-meta-kvm (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1968612
Title:
Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
Status in cloud-images:
Invalid
Status in linux-meta-kvm package in Ubuntu:
New
Bug description:
I just installed the Ubuntu 20.04 LTS minimal cloud image (from here:
https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a
Proxmox VM. Then I installed the NFS Server with
apt install nfs-server
But it fails to start with these errors in journalctl:
Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS
configuration...
-- Subject: A start job for unit nfs-config.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit nfs-config.service has begun execution.
--
-- The job identifier is 563.
Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown
filesystem type 'nfsd'.
Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process
exited, code=exited, status=32/n/a
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An n/a= process belonging to unit proc-fs-nfsd.mount has exited.
--
-- The process' exit code is 'exited' and its exit status is 32.
Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with
result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit proc-fs-nfsd.mount has entered the 'failed' state with result
'exit-code'.
Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration
filesystem.
-- Subject: A start job for unit proc-fs-nfsd.mount has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit proc-fs-nfsd.mount has finished with a failure.
--
-- The job identifier is 556 and the job result is failed.
Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount
Daemon.
"mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it
seems, that the nfsd kernel module is missing:
# modprobe nfsd
modprobe: FATAL: Module nfsd not found in directory
/lib/modules/5.4.0-1061-kvm
I can't figure out how to install this for the running kernel.
Any idea?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
