[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

 

[fiona]

Hi,
was steht dem im Task Log von VM 100 - Start (Doppelclick im unteren Panel in der GUI)? Was ist die Ausgabe von pveversion -v?

 

[Myol]

Sorry, Doppelpost.
(Dieser hier war irgendwie nicht mehr auffindbar.)
Ist schon gelöst:
https://forum.proxmox.com/threads/vm-startet-nicht-mehr.122169/

Aber danke für die Antwort.