Hey Guys,
a VM was turned off by the Host, after starting the VM, the Host just restarted by himself..
The syslog looks like this:
Jun 16 13:02:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:03:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:03:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:03:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:04:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:04:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:04:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:04:51 server_name pvedaemon[4712]: <root@pam> successful auth for user 'root@pam'
Jun 16 13:05:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:05:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:05:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:05:09 server_name pvedaemon[5271]: start VM 900: UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam:
Jun 16 13:05:09 server_name pvedaemon[4418]: <root@pam> starting task UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam:
Jun 16 13:05:09 server_name systemd[1]: Started 900.scope.
Jun 16 13:05:09 server_name systemd-udevd[5281]: Using default interface naming scheme 'v240'.
Jun 16 13:05:09 server_name systemd-udevd[5281]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 16 13:05:09 server_name systemd-udevd[5281]: Could not generate persistent MAC address for tap900i0: No such file or directory
Jun 16 13:05:10 server_name kernel: [9579793.076063] device tap900i0 entered promiscuous mode
Jun 16 13:05:10 server_name kernel: [9579793.081287] vmbr950: port 1(tap900i0) entered blocking state
Jun 16 13:05:10 server_name kernel: [9579793.081534] vmbr950: port 1(tap900i0) entered disabled state
Jun 16 13:05:10 server_name kernel: [9579793.081826] vmbr950: port 1(tap900i0) entered blocking state
Jun 16 13:05:10 server_name kernel: [9579793.082064] vmbr950: port 1(tap900i0) entered forwarding state
Jun 16 13:05:10 server_name pvedaemon[4418]: <root@pam> end task UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam: OK
Jun 16 13:05:13 server_name pvedaemon[4418]: VM 900 qmp command failed - VM 900 qmp command 'guest-ping' failed - got timeout
Jun 16 13:09:12 server_name kernel: [ 0.000000] Linux version 5.3.18-2-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.3.18-2 (Sat, 15 Feb 2020 15:11:52 +0100) ()
Jun 16 13:09:12 server_name kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-2-pve root=UUID=3b44b2e9-90e4-441b-832b-fb915601832a ro modprobe.blacklist=btrfs
Between 13:05:13 and 13:09:12 the Server didn't response to anything, it seemed offline.
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-2-pve: 5.3.13-2
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve4
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
pve-zsync: 2.0-2
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
Thanks for your help!
a VM was turned off by the Host, after starting the VM, the Host just restarted by himself..
The syslog looks like this:
Jun 16 13:02:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:03:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:03:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:03:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:04:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:04:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:04:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:04:51 server_name pvedaemon[4712]: <root@pam> successful auth for user 'root@pam'
Jun 16 13:05:00 server_name systemd[1]: Starting Proxmox VE replication runner...
Jun 16 13:05:01 server_name systemd[1]: pvesr.service: Succeeded.
Jun 16 13:05:01 server_name systemd[1]: Started Proxmox VE replication runner.
Jun 16 13:05:09 server_name pvedaemon[5271]: start VM 900: UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam:
Jun 16 13:05:09 server_name pvedaemon[4418]: <root@pam> starting task UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam:
Jun 16 13:05:09 server_name systemd[1]: Started 900.scope.
Jun 16 13:05:09 server_name systemd-udevd[5281]: Using default interface naming scheme 'v240'.
Jun 16 13:05:09 server_name systemd-udevd[5281]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 16 13:05:09 server_name systemd-udevd[5281]: Could not generate persistent MAC address for tap900i0: No such file or directory
Jun 16 13:05:10 server_name kernel: [9579793.076063] device tap900i0 entered promiscuous mode
Jun 16 13:05:10 server_name kernel: [9579793.081287] vmbr950: port 1(tap900i0) entered blocking state
Jun 16 13:05:10 server_name kernel: [9579793.081534] vmbr950: port 1(tap900i0) entered disabled state
Jun 16 13:05:10 server_name kernel: [9579793.081826] vmbr950: port 1(tap900i0) entered blocking state
Jun 16 13:05:10 server_name kernel: [9579793.082064] vmbr950: port 1(tap900i0) entered forwarding state
Jun 16 13:05:10 server_name pvedaemon[4418]: <root@pam> end task UPID:server_name:00001497:3919B159:5EE8A765:qmstart:900:root@pam: OK
Jun 16 13:05:13 server_name pvedaemon[4418]: VM 900 qmp command failed - VM 900 qmp command 'guest-ping' failed - got timeout
Jun 16 13:09:12 server_name kernel: [ 0.000000] Linux version 5.3.18-2-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.3.18-2 (Sat, 15 Feb 2020 15:11:52 +0100) ()
Jun 16 13:09:12 server_name kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-2-pve root=UUID=3b44b2e9-90e4-441b-832b-fb915601832a ro modprobe.blacklist=btrfs
Between 13:05:13 and 13:09:12 the Server didn't response to anything, it seemed offline.
pve-version -v proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-2-pve: 5.3.13-2
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve4
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
pve-zsync: 2.0-2
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
Thanks for your help!
