I am using VPS in the GMO cloud.
dnf update
If you try to restart after running and connect with SSH, you can use the
ssh: connect to host [IP address] port [Port number]: Resource temporary unavailable
will be
Do I have to do something after the update?
<About the Environment>
·GMO Cloud VPS
·CentOS 8
Please let me know if you need any information.
The following is the matter I received from Metropolis.
This is ssh-vvv host.
(Reinstalling and not "dnf update")
OpenSSH_8.0p1, OpenSSL 1.1.1c FIPS 28 May 2019
debug1: Reading configuration data/etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line51—Including file/etc/ssh/ssh_config.d/05-redhat.conf depth0
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug2—Checking match for 'final all' host [host] originally [host]
debug3: /etc/ssh/ssh_config.d/05-redhat.confline3: not matched 'final'
debug2: match not found
debug3: /etc/ssh/ssh_config.d/05-redhat.confline5:Including file/etc/crypto-policies/back-ends/openssh.config depth1 (parse only)
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug3: gss kex names ok: [gss-gex-sha1-, gss-group14-sha1-]
debug3: kex names ok: [curve25519-sha256, [email protected], ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha-diff-diffie12-diff-diffie-diffie16
debug1: configuration requests final Match pass
debug2: resolve_canonicalize: hostname [host] is address
debug1: re-parsing configuration
debug1: Reading configuration data/etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line51—Including file/etc/ssh/ssh_config.d/05-redhat.conf depth0
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug2—Checking match for 'final all' host [host] originally [host]
debug3: /etc/ssh/ssh_config.d/05-redhat.confline3: matched 'final'
debug2: match found
debug3: /etc/ssh/ssh_config.d/05-redhat.confline5:Including file/etc/crypto-policies/back-ends/openssh.config depth1
debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config
debug3: gss kex names ok: [gss-gex-sha1-, gss-group14-sha1-]
debug3: kex names ok: [curve25519-sha256, [email protected], ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha-diff-diffie12-diff-diffie-diffie16
debug2: ssh_connect_direct
debug1: Connecting to [host] [[host]] port 22.
debug1: connect to address [ host ] port 22: Connection refused
ssh: connect to host [ host ] port 22: Connection refused
In January 2021, the same (*) issue occurred in my environment as the one in the environment (GMO Cloud VPS), but as of July 18, 2021, this issue no longer occurred in my environment.
※ CentOS 8 stops starting after dnf update
The version of Windows, VirtualBox, and kernel on the host has changed, and it remains unclear why the problem stopped, but I suspect the kernel version 4.18.0-240.el8.x86_64 was the direct cause.
[Environment used for confirmation]
(1) Host Win10 Pro 1909
↓
(2) Host Win10 Pro 20H2
(1) VirtualBox version 6.1.16 r140961 (Qt5.6.2)
↓
(2) VirtualBox version 6.1.22 r144080 (Qt5.6.2)
(1) Kernel 4.18.0-240.el8.x86_64
↓
(2) US>Kernel
4.18.0-257.el8.x86_64 dBefore dnf update
4.18.0-315.el8.x86_64 dAfter dnf update
(1) The version when the problem occurs
(2)The version I checked this time
Media CentOS-Stream-8-x86_64-20201211-dvd1.iso
when CentOS was installedIt may be different from what happened in my environment, but booting to the 4.18.0-193 kernel may solve the problem.
※ I don't know what to do with VPS in the GMO cloud
My environment (VirtualBox) no longer has CENTOS 8 starting with dnf update.
再現 It is reproducible.
When you start the VM, the screen remains completely dark and does not proceed.
VBox.log shows the following error:
01:01:40.197365 MsrExit/0:0010:fffffffbc264d98/LM:WRMSR00000033,20000000:00000000->VERR_CPUM_RAISE_GP_0!
I looked into what it meant, but I didn't really understand.
There was an old article that might be related to Hyper-V, so I tried to enable or disable Hyper-V, but the symptom did not change.
[Additional note] I checked with systeminfo.exe and found that Hyper-V was disabled on the control panel, but it was not completely disabled.It may be resolved if Hyper-V can be completely disabled.
The reason is that the kernel version has changed from 4.18.0-193.el8.x86_64 to 4.18.0-240.el8.x86_64.
After dnf update, the default kernel では will not boot the VM.②Select to start the VM.
C CentOS Linux (4.18.0-240.1.el8_3.x86_64)8
②CentOS Linux (4.18.0-193.28.1.el8_2.x86_64) 8 (Core)
は was created with dnf update.
[Environment used for confirmation]
CentOS-8.3.2011-x86_64-dvd1.iso and CentOS-Stream-8-x86_64-20201211-dvd1.iso have the same symptoms.
CentOS-8.2.2004-x86_64-dvd1.iso appears to be currently unavailable.個人I was able to test the reproduction because I had a personal backup left.
© 2024 OneMinuteCode. All rights reserved.