[SOLVED] VM startet nicht mehr

[Myol]

Hallo zusammen,

ich brauche dringend Hilfe.
Ich habe Raspberrymatic als VM unter Proxmox laufen.
Bisher ohne Probleme.

Jetzt hatte ich den gesamten Rechner vorhin kurz runtergefahren und nach dem Neustart bootet die VM nicht mehr.

Das steht im Log:

Feb 04 17:33:12 pve pvedaemon[3729]: start VM 100: UPID:pve:00000E91:000070F9:63DE88C8:qmstart:100:root@pam:
Feb 04 17:33:12 pve pvedaemon[1061]: <root@pam> starting task UPID:pve:00000E91:000070F9:63DE88C8:qmstart:100:root@pam:
Feb 04 17:33:12 pve systemd[1]: Started 100.scope.
Feb 04 17:33:12 pve systemd-udevd[3747]: Using default interface naming scheme 'v247'.
Feb 04 17:33:12 pve systemd-udevd[3747]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 04 17:33:12 pve kernel: device tap100i0 entered promiscuous mode
Feb 04 17:33:12 pve systemd-udevd[3750]: Using default interface naming scheme 'v247'.
Feb 04 17:33:12 pve systemd-udevd[3750]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 04 17:33:12 pve systemd-udevd[3750]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 04 17:33:12 pve systemd-udevd[3747]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered blocking state
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered disabled state
Feb 04 17:33:13 pve kernel: device fwpr100p0 entered promiscuous mode
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered blocking state
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered forwarding state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Feb 04 17:33:13 pve kernel: device fwln100i0 entered promiscuous mode
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered disabled state
Feb 04 17:33:13 pve kernel: device fwln100i0 left promiscuous mode
Feb 04 17:33:13 pve kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Feb 04 17:33:13 pve kernel: device fwpr100p0 left promiscuous mode
Feb 04 17:33:13 pve kernel: vmbr0: port 3(fwpr100p0) entered disabled state
Feb 04 17:33:13 pve pvedaemon[3729]: start failed: QEMU exited with code 1
Feb 04 17:33:13 pve pvedaemon[1061]: <root@pam> end task UPID:pve:00000E91:000070F9:63DE88C8:qmstart:100:root@pam: start failed: QEMU exited with code 1
Feb 04 17:33:13 pve systemd[1]: 100.scope: Succeeded.

Kann damit jemand was anfangen und mir sagen, was da los ist?
Ich kenne mich so tief leider nicht aus.

Danke und Gruß
Oliver

 

[Myol]

In der Task-History der VM steht bei jedem Startversuch folgendes:

Use of uninitialized value $PVE::JSONSchema::PVE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 161.
Use of uninitialized value $PVE::JSONSchema::PVE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 196.
Use of uninitialized value $PVE::JSONSchema::PVE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 196.
Use of uninitialized value $PVE::JSONSchema::PVE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 222.
Use of uninitialized value $PVE::JSONSchema::PVE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 222.
kvm: Address space limit 0xffffffffff < 0x440ffffffff phys-bits too low (40)
TASK ERROR: start failed: QEMU exited with code 1

Kann damit jemand was anfangen?

 

[Myol]

So, weitere Forensuche hat mich zur Lösung geführt.

Ich hatte zuletzt vor 2 oder 3 Wochen mein Proxmox (pve) mit apt-get update und apt-get upgrade auf Stand gebracht.
Seitdem die Raspimatic aber nicht mehr neu gestartet, so dass der Fehler erst jetzt aufgeteten ist.

Im Proxmox muss man aber statt "apt-get upgrade" ein "apt-get dist-upgrade" machen.
Habe das jetzt getan und schon läufts wieder.