The Image is a QCow2 file, yes login possible, but not everytime.
> I dont think that this is a proxmox issue
I am still of the opinion that Qemu from version 7 to version 10 not only
makeup changes were made, like bigger Cursor, faster blinking, or other font
style, I think you mean what I think now
greetings
-----Ursprüngliche Nachricht-----
Von: to...@tuxteam.de <to...@tuxteam.de>
Gesendet: Sonntag, 15. Juni 2025 11:28
An: Maurizio Caloro <mauri...@caloro.ch>
Cc: debian-user@lists.debian.org
Betreff: Re: qcow2 maintanance
On Sun, Jun 15, 2025 at 10:59:38AM +0200, Maurizio Caloro wrote:
> > How does that "unclean start" looks like?
>
> hmm let me explain, the Router (cli-based) don't start-up correctly, staring
> but, the interfaces will stay still down (not possible to bring up), the used
> Protocol not propagate (you dont see any answer), the cli prompt freez and
> come with a little luck back 10-15min later, the "system" are 100% unusable.
> The CPU+Memory usage are almost in sleepingstate with some normal rashes.
That "Router" is a VM, right? Can you log into it? Is it that what you mean by
"cli based"?
What happens if you try to get a terminal to your VM (e.g. "qm terminal
<number>").
(or "pct", I don't know yet whether yours is a VM or a container).
In other words -- it would be nice to see the boot messages of such a failing
instance. Perhaps someone more knowledgeable here knows how to do that in
Proxmox.
Cheers
--
tomás
