You should be seeing a bit more output : coldadmin@bacon:~$ sudo systemctl status qemu.slice ● qemu.slice Loaded: loaded Active: active since Sat 2020-02-08 11:26:41 EST; 3 weeks 4 days ago Tasks: 52 Memory: 30.0G CGroup: /qemu.slice ├─102.scope │ └─2660 /usr/bin/kvm -id 102 -name foreman -chardev socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile ├─126.scope │ └─2911 /usr/bin/kvm -id 126 -name pbx -chardev socket,id=qmp,path=/var/run/qemu-server/126.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var ├─134.scope │ └─14073 /usr/bin/kvm -id 134 -name kolla-compute001 -chardev socket,id=qmp,path=/var/run/qemu-server/134.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control ├─139.scope │ └─14030 /usr/bin/kvm -id 139 -name kolla-compute002 -chardev socket,id=qmp,path=/var/run/qemu-server/139.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control └─155.scope └─2967 /usr/bin/kvm -id 155 -name rancher01 -chardev socket,id=qmp,path=/var/run/qemu-server/155.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfil
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. On Wed, Mar 4, 2020 at 10:44 AM Gilberto Nunes <gilberto.nune...@gmail.com> wrote: > systemctl status qemu.slice > > --- > Gilberto Nunes Ferreira > > > Em qua., 4 de mar. de 2020 às 11:23, Luis G. Coralle via pve-user < > pve-user@pve.proxmox.com> escreveu: > > > > > > > > > ---------- Forwarded message ---------- > > From: "Luis G. Coralle" <luiscora...@fi.uncoma.edu.ar> > > To: PVE User List <pve-user@pve.proxmox.com> > > Cc: > > Bcc: > > Date: Wed, 4 Mar 2020 11:21:57 -0300 > > Subject: Error starting VM > > Hello! > > I'm trying to start windows 10 VM and I get: > > TASK ERROR: timeout waiting on systemd > > The VM was running fine. Last day it crash. I rebooted it and now it > > won't start... > > > > PVE version is 5.4-13 > > Did someone have the same thing? > > Thanks > > > > -- > > Luis G. Coralle > > Secretaría de TIC > > Facultad de Informática > > Universidad Nacional del Comahue > > (+54) 299-4490300 Int 647 > > > > > > > > ---------- Forwarded message ---------- > > From: "Luis G. Coralle via pve-user" <pve-user@pve.proxmox.com> > > To: PVE User List <pve-user@pve.proxmox.com> > > Cc: "Luis G. Coralle" <luiscora...@fi.uncoma.edu.ar> > > Bcc: > > Date: Wed, 4 Mar 2020 11:21:57 -0300 > > Subject: [PVE-User] Error starting VM > > _______________________________________________ > > pve-user mailing list > > pve-user@pve.proxmox.com > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > _______________________________________________ > pve-user mailing list > pve-user@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user