Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : KVM VPS doesn't boot - Input/output error



Threaded Mode | Print  

 KVM VPS doesn't boot - Input/output error (1 Replies, Read 364 times)
Havri
Group: Member
Post Group: Newbie
Posts: 3
Status:
Hello,

I am encountering an error with KVM VPS' from the virtualizor interface. I have two servers (one is Master - localhost and the other is the Slave - public IP).

I have the following in the log for the VM after I create a new KVM VM (/var/log/libvirt/qemu/v1004.log):


Code
2018-09-03 07:51:24.361+0000: starting up libvirt version: 3.9.0, package: 14.el7_5.5 (CentOS BuildSystem <http://bugs.centos.org>, 2018-05-22-02:42:56, c1bm.rdu2.centos.org), qemu version: 1.5.3 (qemu-kvm-1.5.3-156.el7_5.2), hostname: virtnode01.octosquid.com
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name v1004 -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off -cpu host -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 74a86d08-20bd-459c-9169-ead322f99e4f -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-37-v1004/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg_home/vsv1004-dzseiogfivowqx2j-re0qfc6twdbqvl2l,format=raw,if=none,id=drive-ide0-0-0,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/dev/vg_home/vsv1004-dxyqrrswug2ssdvi-re0qfc6twdbqvl2l,format=raw,if=none,id=drive-ide0-0-1,cache=none -device ide-hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/dev/vg_home/vsv1004-ddhxjy3ecuhoe6pj-re0qfc6twdbqvl2l,format=raw,if=none,id=drive-ide0-1-0,cache=none -device ide-hd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=29,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:05:04:25,bus=pci.0,addr=0x3 -netdev tap,fd=31,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=00:16:3e:67:22:83,bus=pci.0,addr=0x4 -device usb-tablet,id=input0,bus=usb.0,port=1 -device AC97,id=sound0,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
2018-09-03 07:51:24.361+0000: Domain id=37 is tainted: host-cpu
libvirt:  error : libvirtd quit during handshake: Input/output error
2018-09-03 07:51:24.372+0000: shutting down, reason=failed



Moreover, I have some errors with the libvirtd service. I tried restarting the libvirtd service, but it started showing errors (journalctl -u libvirtd.service):

Code
Sep 03 10:42:36 virtnode01.octosquid.com systemd[1]: Stopping Virtualization daemon...
Sep 03 10:42:36 virtnode01.octosquid.com systemd[1]: Starting Virtualization daemon...
Sep 03 10:42:36 virtnode01.octosquid.com systemd[1]: Started Virtualization daemon.
Sep 03 10:42:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:42:36.487+0000: 25497: info : libvirt version: 3.9.0, package: 14.el7_5.5 (CentOS BuildSystem <http://bugs.centos.org>, 2018-05-22-02:42:56
Sep 03 10:42:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:42:36.487+0000: 25497: info : hostname: virtnode01.octosquid.com
Sep 03 10:42:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:42:36.487+0000: 25497: error : qemuMonitorOpenUnix:385 : failed to connect to monitor socket: No such process
Sep 03 10:42:56 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:42:56.716+0000: 25496: error : virDBusCall:1570 : error from service: GetMachineByPID: Failed to activate service 'org.freedesktop.machine1
Sep 03 10:42:56 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:42:56.730+0000: 25409: warning : qemuDomainObjTaint:5378 : Domain id=23 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:43:21 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:43:21.737+0000: 25498: error : virDBusCall:1570 : error from service: GetMachineByPID: Failed to activate service 'org.freedesktop.machine1
Sep 03 10:43:46 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:43:46.754+0000: 25500: error : virDBusCall:1570 : error from service: GetMachineByPID: Failed to activate service 'org.freedesktop.machine1
Sep 03 10:43:46 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:43:46.754+0000: 25409: error : virSystemdCreateMachine:361 : Failed to activate service 'org.freedesktop.machine1': timed out
Sep 03 10:43:46 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:43:46.958+0000: 25409: error : qemuAutostartDomain:285 : internal error: Failed to autostart VM 'v1004': Failed to activate service 'org.fr
Sep 03 10:43:46 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:43:46.970+0000: 25409: warning : qemuDomainObjTaint:5378 : Domain id=24 name='v1010' uuid=724f6647-b1b0-4fdb-bbeb-8b0ea4e4cc59 is tainted:
Sep 03 10:44:11 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:44:11.765+0000: 25499: error : virDBusCall:1570 : error from service: GetMachineByPID: Failed to activate service 'org.freedesktop.machine1
Sep 03 10:44:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:44:36.773+0000: 25409: error : virSystemdCreateMachine:361 : Failed to activate service 'org.freedesktop.machine1': timed out
Sep 03 10:44:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:44:36.974+0000: 25409: error : qemuAutostartDomain:285 : internal error: Failed to autostart VM 'v1010': Failed to activate service 'org.fr
Sep 03 10:44:36 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:44:36.985+0000: 25409: warning : qemuDomainObjTaint:5378 : Domain id=25 name='v1011' uuid=96a01fad-4c04-4f5d-8f54-912bfa7f0e31 is tainted:
Sep 03 10:45:01 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:01.998+0000: 25409: error : virSystemdCreateMachine:361 : Failed to activate service 'org.freedesktop.machine1': timed out
Sep 03 10:45:02 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:02.199+0000: 25409: error : qemuAutostartDomain:285 : internal error: Failed to autostart VM 'v1011': Failed to activate service 'org.fr
Sep 03 10:45:02 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:02.241+0000: 25378: warning : qemuDomainObjTaint:5378 : Domain id=26 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:45:27 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:27.259+0000: 25378: error : virSystemdCreateMachine:361 : Failed to activate service 'org.freedesktop.machine1': timed out
Sep 03 10:45:29 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:29.505+0000: 25378: warning : qemuDomainObjTaint:5378 : Domain id=27 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:45:54 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:45:54.541+0000: 25378: error : virSystemdCreateMachine:361 : Failed to activate service 'org.freedesktop.machine1': timed out
Sep 03 10:46:38 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:38.793+0000: 25379: warning : qemuDomainObjTaint:5378 : Domain id=28 name='v1011' uuid=96a01fad-4c04-4f5d-8f54-912bfa7f0e31 is tainted:
Sep 03 10:46:38 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:38.801+0000: 25379: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:46:41 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:41.044+0000: 25379: warning : qemuDomainObjTaint:5378 : Domain id=29 name='v1011' uuid=96a01fad-4c04-4f5d-8f54-912bfa7f0e31 is tainted:
Sep 03 10:46:41 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:41.053+0000: 25379: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:46:58 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:58.488+0000: 25376: warning : qemuDomainObjTaint:5378 : Domain id=30 name='v1010' uuid=724f6647-b1b0-4fdb-bbeb-8b0ea4e4cc59 is tainted:
Sep 03 10:46:58 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:46:58.498+0000: 25376: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:47:00 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:00.743+0000: 25378: warning : qemuDomainObjTaint:5378 : Domain id=31 name='v1010' uuid=724f6647-b1b0-4fdb-bbeb-8b0ea4e4cc59 is tainted:
Sep 03 10:47:00 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:00.753+0000: 25378: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:47:51 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:51.687+0000: 25378: warning : qemuDomainObjTaint:5378 : Domain id=32 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:47:51 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:51.698+0000: 25378: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:47:53 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:53.943+0000: 25378: warning : qemuDomainObjTaint:5378 : Domain id=33 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:47:53 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:47:53.954+0000: 25378: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:48:06 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:48:06.211+0000: 25370: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error
Sep 03 10:48:09 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:48:09.338+0000: 25370: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error
Sep 03 10:49:00 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:49:00.691+0000: 25380: warning : qemuDomainObjTaint:5378 : Domain id=34 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:49:00 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:49:00.701+0000: 25380: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:49:02 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:49:02.941+0000: 25379: warning : qemuDomainObjTaint:5378 : Domain id=35 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:49:02 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:49:02.953+0000: 25379: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:51:22 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:51:22.109+0000: 25380: warning : qemuDomainObjTaint:5378 : Domain id=36 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:51:22 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:51:22.119+0000: 25380: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:51:24 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:51:24.361+0000: 25380: warning : qemuDomainObjTaint:5378 : Domain id=37 name='v1004' uuid=74a86d08-20bd-459c-9169-ead322f99e4f is tainted:
Sep 03 10:51:24 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:51:24.372+0000: 25380: error : virSystemdCreateMachine:361 : Connection is closed
Sep 03 10:56:08 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:56:08.350+0000: 25370: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error
Sep 03 10:56:11 virtnode01.octosquid.com libvirtd[25370]: 2018-09-03 07:56:11.486+0000: 25370: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error


The curious thing is that on the Slave node everything works well and the problem only resides on the master server.

Can anyone point me in the right direction to get this solved?

Thank you.
IP: --   

KVM VPS doesn't boot - Input/output error
Havri
Group: Member
Post Group: Newbie
Posts: 3
Status:
Hello,

It seems like there was something stale with the systemd-machined service. According to the documentation, this service is " a tiny daemon that tracks locally running Virtual Machines and Containers in various ways.".

Of course, this was my case.

https://www.freedesktop.org/wiki/Software/systemd/machined/


Code
[root@server1 log]# systemctl status systemd-machined
● systemd-machined.service - Virtual Machine and Container Registration Service
  Loaded: loaded (/usr/lib/systemd/system/systemd-machined.service; static; vendor preset: disabled)
  Active: active (running) since Mon 2018-09-03 13:26:13 EEST; 3min 13s ago
    Docs: man:systemd-machined.service(8)
          http://www.freedesktop.org/wiki/Software/systemd/machined
Main PID: 26149 (systemd-machine)
  Status: "Processing requests..."
    Tasks: 1
  CGroup: /system.slice/systemd-machined.service
          └─26149 /usr/lib/systemd/systemd-machined

Sep 03 13:26:13 server1.mytld.com systemd[1]: Starting Virtual Machine and Container Registration Service...
Sep 03 13:26:13 server1.mytld.com systemd[1]: Started Virtual Machine and Container Registration Service.
Sep 03 13:26:13 server1.mytld.com systemd-machined[26149]: New machine qemu-7-v1002.
Sep 03 13:26:13 server1.mytld.com systemd-machined[26149]: New machine qemu-2-v1001.
Sep 03 13:26:13 server1.mytld.com systemd-machined[26149]: New machine qemu-19-v1005.
Sep 03 13:26:13 server1.mytld.com systemd-machined[26149]: New machine qemu-17-v1003.
Sep 03 13:26:22 server1.mytld.com systemd-machined[26149]: New machine qemu-27-v1011.
Sep 03 13:29:56 server1.mytld.com systemd-machined[26149]: New machine qemu-28-v1010.


After restarting the service, I could start the fresh VMs from the Virtualizor interface.

For anyone having the same error even after running "yum update" and restarting the libvirtd.service, dbus.service, tuned.service and systemd-logind services, try to restart systemd-machined and check if the session for each new VM is created in /run/systemd/system/ .

Good luck.
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is October 20, 2018, 6:13 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.203