Updated my KVM server last week and now the KVM hosts will not start.
I get this error:
Failed to start domain OX
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
The libvrtd service is running.
root@ucs-fs:~# ps -Af | grep [l]ibvirt
root 2323 1 0 11:17 ? 00:00:01 /usr/sbin/libvirtd -l
//Thanks Bengt
Make sure the kvm_intel or kvm_amd Linux kernel module is loaded on your host system:
grep kvm /proc/modules
If not, load them via modprobe. If the still do not load, check the output of dmesg for error messages.
After loading the module a device node /dev/kvm should exists, should be owned by user root and read- and writable by group kvm:
# ls -l /dev/kvm
crw-rw---- 1 root kvm 10, 232 Sep 27 12:24 /dev/kvm
The user used by libvirtd should be a member of the group kvm:
# id libvirt-qemu
uid=64055(libvirt-qemu) gid=113(kvm) Gruppen=113(kvm),24(cdrom),64055(libvirt-qemu)
Sometimes it helps to restart libvirtd:
sudo systemctl restart libvirtd.service
Otherwise check /var/log/libvirt/libvirtd.log for extra error messages.
Apparently is KVM not loaded as “grep kvm /proc/modules” returns empty.
[ 8808.134046] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 8808.135089] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[ 8822.040752] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 8822.041765] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[12226.943923] kvm: Unknown symbol cpu_mitigations_off (err 0)
[12226.944967] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[13087.538043] kvm: Unknown symbol cpu_mitigations_off (err 0)
[13087.539138] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[13095.847527] kvm: Unknown symbol cpu_mitigations_off (err 0)
[13095.848572] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
root@ucs-fs:/etc# cat /var/log/libvirt/libvirtd.log
2019-05-31 08:57:50.020+0000: 13880: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-05-31 08:57:50.020+0000: 13880: info : hostname: ucs-fs
2019-05-31 08:57:50.020+0000: 13880: error : virNetTLSContextCheckCertDNWhitelist:395 : Client’s Distinguished Name is not on the list of allowed clients (tls_allowed_dn_list). Use ‘certtool -i --infile clientcert.pem’ to view the Distinguished Name field in the client certificate, or run this daemon with --verbose option.
2019-05-31 08:57:50.020+0000: 13880: error : virNetTLSContextCheckCertificate:1133 : authentication failed: Failed to verify peer’s certificate
2019-06-02 04:26:19.187+0000: 16070: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-06-02 04:26:19.187+0000: 16070: info : hostname: ucs-fs
2019-06-02 04:26:19.187+0000: 16070: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-03 19:05:34.172+0000: 2073: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-06-03 19:05:34.172+0000: 2073: info : hostname: ucs-fs
2019-06-03 19:05:34.172+0000: 2073: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-03 19:24:38.067+0000: 2134: error : virCommandWait:2572 : internal error: Child process (/bin/mount ucs-fs.sunhut.local:vmimages /var/lib/libvirt/images/Nfspool) unexpected exit status 32: mount.nfs: access denied by server while mounting ucs-fs.sunhut.local:vmimages
2019-06-03 19:32:51.708+0000: 2131: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-ox1-0.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-03 19:34:27.557+0000: 2133: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-ox1-0.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-03 19:34:50.069+0000: 2134: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-pdc02.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-03 19:56:38.409+0000: 2133: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-ox1-0.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-03 19:59:46.080+0000: 2132: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-ox1-0.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-04 13:30:15.308+0000: 2157: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-06-04 13:30:15.308+0000: 2157: info : hostname: ucs-fs
2019-06-04 13:30:15.308+0000: 2157: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-ox1-0.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-04 14:16:02.739+0000: 2157: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-06-04 14:16:53.524+0000: 2161: error : virStorageFileGetMetadataRecurse:3232 : Cannot access storage file ‘/var/lib/libvirt/images/nfspool/ucs-pdc02.qcow2’ (as uid:64055, gid:64055): Filen eller katalogen finns inte
2019-06-04 14:21:33.921+0000: 2104: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout
2019-06-04 16:08:32.033+0000: 2159: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-06-04 16:48:41.357+0000: 2104: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-04 18:17:43.001+0000: 2104: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-04 18:20:10.660+0000: 2104: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-04 18:48:25.967+0000: 2104: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-04 18:52:09.925+0000: 2157: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-06-04 18:52:09.925+0000: 2157: info : hostname: ucs-fs
2019-06-04 18:52:09.925+0000: 2157: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-06-04 18:52:25.315+0000: 2156: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-06-09 19:13:44.809+0000: 2095: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-06-09 19:14:50.170+0000: 2095: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth5a44e09/operstate’: Filen eller katalogen finns inte
2019-06-09 19:14:50.170+0000: 2095: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth5a44e09/operstate: Filen eller katalogen finns inte
2019-06-09 19:14:50.429+0000: 2095: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth121c442/operstate’: Filen eller katalogen finns inte
2019-06-09 19:14:50.429+0000: 2095: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth121c442/operstate: Filen eller katalogen finns inte
2019-06-09 19:19:56.259+0000: 2189: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-06-09 19:19:56.259+0000: 2189: info : hostname: ucs-fs
2019-06-09 19:19:56.259+0000: 2189: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-06-09 19:20:11.485+0000: 2187: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-07-13 07:38:18.257+0000: 2201: info : libvirt version: 3.0.0, package: 4+deb9u3A~4.3.0.201905250642 (Univention builddaemon buildd@univention.de Sat, 25 May 2019 06:42:12 +0200)
2019-07-13 07:38:18.257+0000: 2201: info : hostname: ucs-fs
2019-07-13 07:38:18.257+0000: 2201: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-07-13 07:38:22.271+0000: 2199: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-07-19 15:30:49.221+0000: 25102: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-07-19 15:30:49.221+0000: 25102: info : hostname: ucs-fs
2019-07-19 15:30:49.221+0000: 25102: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-07-19 15:30:52.271+0000: 25102: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth32e2dc2/operstate’: Filen eller katalogen finns inte
2019-07-19 15:30:52.271+0000: 25102: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth32e2dc2/operstate: Filen eller katalogen finns inte
2019-07-19 15:30:52.275+0000: 25102: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth9462666/operstate’: Filen eller katalogen finns inte
2019-07-19 15:30:52.275+0000: 25102: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth9462666/operstate: Filen eller katalogen finns inte
2019-07-19 15:37:20.064+0000: 2134: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-07-19 15:37:20.064+0000: 2134: info : hostname: ucs-fs
2019-07-19 15:37:20.064+0000: 2134: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-07-19 15:37:24.222+0000: 2134: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-08-07 09:22:37.035+0000: 2100: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-08-07 09:29:29.053+0000: 2446: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-08-07 09:29:29.053+0000: 2446: info : hostname: ucs-fs
2019-08-07 09:29:29.053+0000: 2446: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-08-07 09:29:32.485+0000: 2448: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-08-18 17:14:40.745+0000: 2368: error : virNetSocketReadWire:1801 : End of file while reading data: In/ut-fel
2019-08-25 09:18:50.218+0000: 2368: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-08-25 09:27:09.471+0000: 2368: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-08-25 09:27:12.845+0000: 2368: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth4711704/operstate’: Filen eller katalogen finns inte
2019-08-25 09:27:12.845+0000: 2368: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth4711704/operstate: Filen eller katalogen finns inte
2019-08-25 09:27:12.847+0000: 2368: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth0645730/operstate’: Filen eller katalogen finns inte
2019-08-25 09:27:12.847+0000: 2368: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth0645730/operstate: Filen eller katalogen finns inte
2019-08-25 09:30:06.511+0000: 2309: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-08-25 09:30:06.511+0000: 2309: info : hostname: ucs-fs
2019-08-25 09:30:06.511+0000: 2309: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth42b1445/operstate’: Filen eller katalogen finns inte
2019-08-25 09:30:06.512+0000: 2309: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth42b1445/operstate: Filen eller katalogen finns inte
2019-08-25 09:30:06.653+0000: 2309: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth1f7ff1c/operstate’: Filen eller katalogen finns inte
2019-08-25 09:30:06.653+0000: 2309: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth1f7ff1c/operstate: Filen eller katalogen finns inte
2019-08-25 09:30:17.699+0000: 2309: error : virNetTLSSessionHandshake:1362 : authentication failed: TLS handshake failed Error in the push function.
2019-08-25 09:34:29.143+0000: 2446: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-08-25 09:34:29.143+0000: 2446: info : hostname: ucs-fs
2019-08-25 09:34:29.143+0000: 2446: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-08-25 09:34:32.328+0000: 2446: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-03 11:29:26.973+0000: 2344: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-09-03 11:54:24.885+0000: 2411: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-09-03 11:54:24.885+0000: 2411: info : hostname: ucs-fs
2019-09-03 11:54:24.885+0000: 2411: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-03 11:54:45.616+0000: 2413: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-12 14:36:51.475+0000: 2352: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-09-12 14:36:54.706+0000: 2352: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth547326a/operstate’: Filen eller katalogen finns inte
2019-09-12 14:36:54.706+0000: 2352: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth547326a/operstate: Filen eller katalogen finns inte
2019-09-12 14:36:54.706+0000: 2352: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth69ab9f8/operstate’: Filen eller katalogen finns inte
2019-09-12 14:36:54.706+0000: 2352: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth69ab9f8/operstate: Filen eller katalogen finns inte
2019-09-12 14:40:10.998+0000: 2441: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-09-12 14:40:10.998+0000: 2441: info : hostname: ucs-fs
2019-09-12 14:40:10.998+0000: 2441: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-12 14:40:16.762+0000: 2441: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-24 17:44:36.584+0000: 2375: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth9ac02e6/operstate’: Filen eller katalogen finns inte
2019-09-24 17:44:36.584+0000: 2375: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth9ac02e6/operstate: Filen eller katalogen finns inte
2019-09-24 17:44:39.423+0000: 2375: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth4aa2f1a/operstate’: Filen eller katalogen finns inte
2019-09-24 17:44:39.423+0000: 2375: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth4aa2f1a/operstate: Filen eller katalogen finns inte
2019-09-24 17:45:59.185+0000: 2375: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-09-24 18:34:50.726+0000: 2443: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-09-24 18:36:31.617+0000: 2443: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-02 14:18:46.891+0000: 2789: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-10-02 14:18:46.891+0000: 2789: info : hostname: ucs-fs
2019-10-02 14:18:46.891+0000: 2789: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-02 14:18:47.425+0000: 2789: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-25 23:38:41.958+0000: 2761: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-10-25 23:38:41.958+0000: 2761: info : hostname: ucs-fs
2019-10-25 23:38:41.958+0000: 2761: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-25 23:38:42.476+0000: 2761: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-26 18:25:58.684+0000: 2362: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-10-26 18:30:44.724+0000: 2918: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-10-26 18:30:44.724+0000: 2918: info : hostname: ucs-fs
2019-10-26 18:30:44.724+0000: 2918: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-10-26 18:30:59.055+0000: 2918: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-11-17 17:55:15.256+0000: 2474: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2019-11-28 19:59:53.779+0000: 2394: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-11-28 20:04:39.343+0000: 2394: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-11-28 20:11:26.002+0000: 2579: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-11-28 20:11:26.002+0000: 2579: info : hostname: ucs-fs
2019-11-28 20:11:26.002+0000: 2579: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:11:26.003+0000: 2579: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘PDC-02’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:11:26.050+0000: 2579: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:11:26.050+0000: 2579: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘OX’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:11:26.124+0000: 2441: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:11:26.166+0000: 2437: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:12:25.735+0000: 2437: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:12:37.070+0000: 2441: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:13:54.842+0000: 2438: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:15:14.541+0000: 2394: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-11-28 20:15:16.329+0000: 2394: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth2bc47cf/operstate’: Filen eller katalogen finns inte
2019-11-28 20:15:16.329+0000: 2394: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth2bc47cf/operstate: Filen eller katalogen finns inte
2019-11-28 20:15:16.424+0000: 2394: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth192e425/operstate’: Filen eller katalogen finns inte
2019-11-28 20:15:16.424+0000: 2394: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth192e425/operstate: Filen eller katalogen finns inte
2019-11-28 20:18:11.853+0000: 2623: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-11-28 20:18:11.853+0000: 2623: info : hostname: ucs-fs
2019-11-28 20:18:11.853+0000: 2623: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:18:11.854+0000: 2623: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘OX’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:18:11.901+0000: 2623: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:18:11.901+0000: 2623: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘PDC-02’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:26:33.989+0000: 2399: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-28 20:27:11.104+0000: 2399: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:44:40.639+0000: 2399: error : qemuConnectGetDomainCapabilities:19023 : invalid argument: KVM is not supported by ‘/usr/bin/kvm’ on this host
2019-11-29 08:44:44.866+0000: 2400: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:44:57.118+0000: 2398: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:45:05.068+0000: 2396: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:45:31.645+0000: 2397: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:45:55.814+0000: 2400: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:46:16.950+0000: 2400: error : qemuConnectGetDomainCapabilities:19023 : invalid argument: KVM is not supported by ‘/usr/bin/kvm’ on this host
2019-11-29 08:46:22.278+0000: 2396: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:47:00.181+0000: 2397: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-11-29 08:47:09.300+0000: 2399: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:16:11.487+0000: 2341: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-12-03 10:16:13.328+0000: 2341: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/vethfd28b2d/operstate’: Filen eller katalogen finns inte
2019-12-03 10:16:13.328+0000: 2341: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/vethfd28b2d/operstate: Filen eller katalogen finns inte
2019-12-03 10:18:57.737+0000: 2710: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-12-03 10:18:57.737+0000: 2710: info : hostname: ucs-fs
2019-12-03 10:18:57.737+0000: 2710: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:18:57.738+0000: 2710: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘OX’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:18:57.742+0000: 2710: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:18:57.742+0000: 2710: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘PDC-02’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:20:43.679+0000: 2371: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:22:10.913+0000: 2372: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:22:22.466+0000: 2323: error : virNetSocketReadWire:1801 : End of file while reading data: In/ut-fel
2019-12-03 10:34:21.428+0000: 2368: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:54:51.565+0000: 2323: error : virNetSocketReadWire:1793 : Cannot recv data: In/ut-fel
2019-12-03 10:54:52.958+0000: 2323: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/vethfb7b77e/operstate’: Filen eller katalogen finns inte
2019-12-03 10:54:52.958+0000: 2323: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/vethfb7b77e/operstate: Filen eller katalogen finns inte
2019-12-03 10:54:53.507+0000: 2323: error : virFileReadAll:1388 : Failed to open file ‘/sys/class/net/veth7904828/operstate’: Filen eller katalogen finns inte
2019-12-03 10:54:53.507+0000: 2323: error : virNetDevGetLinkInfo:1880 : unable to read: /sys/class/net/veth7904828/operstate: Filen eller katalogen finns inte
2019-12-03 10:57:35.519+0000: 2570: info : libvirt version: 3.0.0, package: 4+deb9u4A~4.4.0.201906241311 (Univention builddaemon buildd@univention.de Mon, 24 Jun 2019 13:11:37 +0200)
2019-12-03 10:57:35.519+0000: 2570: info : hostname: ucs-fs
2019-12-03 10:57:35.519+0000: 2570: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:57:35.520+0000: 2570: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘PDC-02’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:57:35.524+0000: 2570: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:57:35.524+0000: 2570: error : qemuAutostartDomain:297 : internal error: Failed to autostart VM ‘OX’: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
2019-12-03 10:57:44.061+0000: 2385: error : qemuProcessStartValidate:4644 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
I need urgent assistance .
Further testing indicates that I have a broken package
root@ucs-fs:~# apt install kvm
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
kvm : Depends: qemu-kvm but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Univention-install kvm returns the same message.
Apparently is the package qemu-common missing för some reason
How about ap --reinstall install xxxxxxx?
Thanks for the suggestion.
I have already tried that and I’m just now running round in circles, Searching internet returns the same suggestions I have already tried.
root@ucs-fs:~# apt --reinstall install kvm
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
kvm : Depends: qemu-kvm but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
so, that is quite clear and easy one 
$ apt-get -f install
$ apt update
$ apt-get autoremove
should fix the “broken” packages and try the reinstallation
Thanks, I tried that to without success.
However I removed all kvm, virsh and qemu* related packages explicitly, cleaned up and reinstalled.
The re-installation went without issues.
Problem is still not solved same issue
Error migrating domain “29192f54-830d-45d7-b775-507229d9e33a”: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
Virtualization is enabled in BIOS
root@ucs-fs:~# lscpu | grep --color vmx
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb invpcid_single ssbd ibrs ibpb stibp kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
kvm is missing in /dev
dmesg returns
root@ucs-fs:~# dmesg | grep kvm
[ 4.176552] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 4.176827] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[ 4.198147] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 4.198446] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[ 4.218797] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 4.219494] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[ 4.286525] kvm: Unknown symbol cpu_mitigations_off (err 0)
[ 4.286766] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
[61855.792461] kvm: Unknown symbol cpu_mitigations_off (err 0)
[61855.793504] kvm: Unknown symbol itlb_multihit_kvm_mitigation (err 0)
great
With the rest, I pass. I just can assume, that your domain controller and/or other servers run as VM? can you restore the VMs or build new ones?
Domain integration I have done yet, so you might if VMs all functional, open another topic to domain integration and someone else might jump into help on this
Reinstallation was without errors but the original issues persists.
I have searched internet for resolutions but I cannot find anything substantial.
I am downsizing my server estate, going from three servers to one. my VM’s are safe, migrated to another server. I assume that I have to build another backup DC, promote that one to master, then take down my old master rebuild that one and subsequently promote this on to master again.
What I want for Christmas is native ZFS support for my Univention servers. Not only is it faster but so much easier to administer,
You seem to have an issue with the Linux kernel: For some reason the kvm module fails to load, which later on leads to qemu falling back to software emulation only, which explains the error about the missing feature __kvm_hv_spinlocks.
Check grep kvm /proc/modules to list 2 modules: kvm and either kvm_intel or kvm_amd.
Please also check (and provide) the version of the Linux kernel you are running: uname -rv.
Make sure the Linux kernel packages are installed correctly: dpkg -l linux-image-$(uname -r)\*
Re-run depmod -a to generate the dependency information between the kernel modules and reboot your system. It might have happened that there was an incompatible change between in the Kernel-ABI and your currently running kernel fails to load the modules from disk, which belong to the previous or next version.
root@ucs-fs:~# grep kvm /proc/modules
root@ucs-fs:~# uname -rv
4.9.0-11-amd64 #1 SMP Debian 4.9.189-3 (2019-09-02)
root@ucs-fs:~# dpkg -l linux-image-$(uname -r)*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±==============-============-============-=================================
ii linux-image-4. 4.9.189-3+de amd64 Linux 4.9 for 64-bit PCs
ii linux-image-4. 5.0.0-9A~4.4 amd64 UCS - Linux kernel (standard)
root@ucs-fs:~# depmod -a
root@ucs-fs:~#
Rebooted the server but it didn’t help
To get the full package version please change my last command to
dpkg-query -W linux-image-$(uname -r)
If my reading of your output is correct you are running a mismatching kernel 4.9.189-3, which no longer maps to the modules 4.9.189-3+deb9u2 - notice the suffix +deb9u2.
Please verify that the Linux kernel is correctly installed:
sha256sum /boot/vmlinuz-4.9.0-11-amd64
# 1f29896febde9599d8135cf8426aa3266f40c984c42c0cb2d5da74a785e8bd73 /boot/vmlinuz-4.9.0-11-amd64
If not, please re-install the Linux kernel package:
apt-get --reinstall install linux-image-4.9.0-11-amd64
Please verify that this kernel is mentioned in /boot/grub/grub.cfg:
grep -n --color vmlinuz /boot/grub/grub.cfg
# 148: linux /vmlinuz-4.9.0-11-amd64 root=/dev/mapper/vg_ucs-root ...
If not re-create the file by running
update-grub
When in the GRUB boot screen, verify that this kernel is loaded and not some old backup file!
Please verify that the kernel is actually installed in the right filesystem:
df -T /boot
# Dateisystem Typ 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
# /dev/sda2 ext2 483946 45940 413021 11% /boot
If not, please check which partition should be mounted and why it does not work:
grep --color -n /boot /etc/fstab
# 9:# /boot was on /dev/sdb2 during installation
# 10:UUID=...-... /boot ext2 defaults 0 2
lsblk
# NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
# ...
# ├─sda2 8:2 0 488M 0 part /boot
If you’re using a (U)EFI platform, this are different.
This is the output.
root@ucs-fs:~# dpkg-query -W linux-image-$(uname -r)
linux-image-4.9.0-11-amd64 4.9.189-3+deb9u2
root@ucs-fs:~# sha256sum /boot/vmlinuz-4.9.0-11-amd64
1f29896febde9599d8135cf8426aa3266f40c984c42c0cb2d5da74a785e8bd73 /boot/vmlinuz-4.9.0-11-amd64
root@ucs-fs:~# apt-get --reinstall install linux-image-4.9.0-11-amd64
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 21 not upgraded.
Need to get 39.2 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://updates.software-univention.de/4.4/maintained 4.4-3/amd64/ linux-image-4.9.0-11-amd64 4.9.189-3+deb9u2 [39.2 MB]
Fetched 39.2 MB in 9s (4,234 kB/s)
(Reading database … 122455 files and directories currently installed.)
Preparing to unpack …/linux-image-4.9.0-11-amd64_4.9.189-3+deb9u2_amd64.deb …
Unpacking linux-image-4.9.0-11-amd64 (4.9.189-3+deb9u2) over (4.9.189-3+deb9u2) …
Setting up linux-image-4.9.0-11-amd64 (4.9.189-3+deb9u2) …
/etc/kernel-img.conf:12: W: ignoring unknown parameter do_bootfloppy
/etc/kernel-img.conf:13: W: ignoring unknown parameter silent_loader
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-11-amd64
/etc/kernel/postinst.d/ucs-reboot-required:
Create update/reboot/required
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file …
/usr/sbin/grub-probe: warning: Couldn’t find physical volume (null)'. Some modules may be missing from core image.. Found background: /boot/grub/uniboot.png /usr/sbin/grub-probe: warning: Couldn't find physical volume(null)’. Some modules may be missing from core image…
/usr/sbin/grub-probe: warning: Couldn’t find physical volume (null)'. Some modules may be missing from core image.. Found background image: /boot/grub/uniboot.png Found linux image: /boot/vmlinuz-4.9.0-11-amd64 Found initrd image: /boot/initrd.img-4.9.0-11-amd64 /usr/sbin/grub-probe: warning: Couldn't find physical volume(null)’. Some modules may be missing from core image…
Found linux image: /boot/vmlinuz-4.9.0-9-amd64
Found initrd image: /boot/initrd.img-4.9.0-9-amd64
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
/usr/sbin/grub-probe: warning: Couldn’t find physical volume `(null)’. Some modules may be missing from core image…
Found memtest86+ image: /boot/memtest86+.bin
done
root@ucs-fs:~# grep -n --color vmlinuz /boot/grub/grub.cfg
151: linux /boot/vmlinuz-4.9.0-11-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash
172: linux /boot/vmlinuz-4.9.0-11-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash
192: linux /boot/vmlinuz-4.9.0-11-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash init=/lib/sy svinit/init
212: linux /boot/vmlinuz-4.9.0-11-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro single
232: linux /boot/vmlinuz-4.9.0-9-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash
252: linux /boot/vmlinuz-4.9.0-9-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash init=/lib/sys vinit/init
272: linux /boot/vmlinuz-4.9.0-9-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro single
292: linux /boot/vmlinuz-4.9.0-8-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash
312: linux /boot/vmlinuz-4.9.0-8-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro quiet loglevel=0 rootdelay=5 splash init=/lib/sys vinit/init
332: linux /boot/vmlinuz-4.9.0-8-amd64 root=UUID=a7512d76-e6f6-41fc-80a0-b11e29c02141 ro single
root@ucs-fs:~# update-grub
Generating grub configuration file …
/usr/sbin/grub-probe: warning: Couldn’t find physical volume (null)'. Some modules may be missing from core image.. Found background: /boot/grub/uniboot.png /usr/sbin/grub-probe: warning: Couldn't find physical volume(null)’. Some modules may be missing from core image…
/usr/sbin/grub-probe: warning: Couldn’t find physical volume (null)'. Some modules may be missing from core image.. Found background image: /boot/grub/uniboot.png Found linux image: /boot/vmlinuz-4.9.0-11-amd64 Found initrd image: /boot/initrd.img-4.9.0-11-amd64 /usr/sbin/grub-probe: warning: Couldn't find physical volume(null)’. Some modules may be missing from core image…
Found linux image: /boot/vmlinuz-4.9.0-9-amd64
Found initrd image: /boot/initrd.img-4.9.0-9-amd64
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
/usr/sbin/grub-probe: warning: Couldn’t find physical volume `(null)’. Some modules may be missing from core image…
Found memtest86+ image: /boot/memtest86+.bin
done
root@ucs-fs:~# df -T /boot
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/disk/by-uuid/a7512d76-e6f6-41fc-80a0-b11e29c02141 ext4 224931220 20239836 193010668 10% /
root@ucs-fs:~# grep --color -n /boot /etc/fstab
root@ucs-fs:~# lsblk
root@ucs-fs:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 2G 0 part
└─sda2 8:2 0 929.5G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 2G 0 part
└─sdb2 8:18 0 929.5G 0 part
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 2G 0 part
└─sdc2 8:34 0 929.5G 0 part
sdd 8:48 0 238.5G 0 disk
├─sdd1 8:49 0 222.6G 0 part
├─sdd2 8:50 0 1K 0 part
└─sdd5 8:53 0 15.9G 0 part
sde 8:64 0 238.5G 0 disk
├─sde1 8:65 0 222.6G 0 part
│ └─md0 9:0 0 222.5G 0 raid1 /
├─sde2 8:66 0 1K 0 part
└─sde5 8:69 0 15.9G 0 part
└─md1 9:1 0 15.9G 0 raid1 [SWAP]
sr0 11:0 1 1024M 0 rom
This is weird.
sda, sdb and sdc is my ZFS environment
sdd and sde is supposed to be a software RAID 1 (i.e. mirror) holding my UCS OS. what has happened here? Is my software RAID broken. How do I recreate this.
You can check the status of your RAID with
cat /proc/mdstat
The UCS upgrade removed these devices /dev/sdd1 and dev/sdd5 from the mdadm array.
How do I reinstate these devices in the array.
root@ucs-fs:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sde5[1]
16630784 blocks super 1.2 [2/1] [_U]
md0 : active raid1 sde1[1]
233286656 blocks super 1.2 [2/1] [_U]
bitmap: 2/2 pages [8KB], 65536KB chunk
unused devices:
sdd1 and sdd5 is missing from the array.
root@ucs-fs:~# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Fri Nov 30 16:35:31 2018
Raid Level : raid1
Array Size : 233286656 (222.48 GiB 238.89 GB)
Used Dev Size : 233286656 (222.48 GiB 238.89 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Thu Feb 6 19:55:43 2020
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Name : debian:0
UUID : ead6b725:9ea5b4ba:f8572b8f:620c0c1c
Events : 8945529
Number Major Minor RaidDevice State
- 0 0 0 removed
1 8 65 1 active sync /dev/sde1
root@ucs-fs:~# mdadm --detail /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Fri Nov 30 16:35:56 2018
Raid Level : raid1
Array Size : 16630784 (15.86 GiB 17.03 GB)
Used Dev Size : 16630784 (15.86 GiB 17.03 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent
Update Time : Thu Feb 6 19:40:02 2020
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Name : debian:1
UUID : 6cbe502b:90301da0:e8eea3a7:18550c63
Events : 83684
Number Major Minor RaidDevice State
- 0 0 0 removed
1 8 69 1 active sync /dev/sde5Thanks, this was driving me crazy.
So my problems related to a broken software RAID.
Using mdadm to add the devices that for some reason were removed from the array solved my problems.
KVM is again working as expected.
Now I have read that upgrading the kernel may break the software raid by removing devices from the array.