vm start suspend

[kasenhoo]

hi

I got a problem as following screen shot...

one vm start ...suspend on the first step...

no response ,,even reboot, stop,start etc action...

i have no idea,,,found nothing about this issue,,,no log,no description...

i need help ...thanks..

pve version: 7.0

 

[mira]

Please provide the output of pveversion -v and qm config <VMID> where <VMID> is the ID of your VM.

 

[kasenhoo]

Please provide the output of pveversion -v and qm config <VMID> where <VMID> is the ID of your VM.

Thank you bro.


here is the info:


root@iifox:~# pveversion -v


proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

 

[kasenhoo]

root@iifox:~# qm config 101

boot: c
bootdisk: scsi0
cipassword: **********
ciuser: root
cores: 3
description:
ide2: local-lvm:vm-101-cloudinit,media=cdrom,size=4M
ipconfig0: ip=dhcp
memory: 4096
name: jiangmh001
net0: virtio=72:7D:00:BC:B1:44,bridge=vmbr0
numa: 0
ostype: l26
parent: A20220811
scsi0: local-lvm:vm-101-disk-0,size=200G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=055b8117-4237-43bd-8fdc-08a71935227a
sockets: 2
vga: serial0
vmgenid: 943d2383-108b-49e8-b7de-d3dcb9638911

 

[kasenhoo]

Up

 

[kasenhoo]

Up again

 

[leesteken]

What do you mean with "suspend"? Is the VM not running on the Summary? There are many reasons a VM won't respond to Shutdown etc.
Did you configure the operating system inside the VM to use the serial console?
What is the output when you set Display to Standard VGA or vga: std and use the noVNC console?

 

[mira]

Setting the display to `Serial` only works if your image provides a serial terminal. When that is not the case you have to use the default display.
It seems newer images often enough don't configure a serial terminal.

 

[kasenhoo]

thanks reply.

@leesteken @mira

it is running status in summary...but I can't ssh remotely that error msg is " Network error: Connection timed out"

so I try to connect in PVE Web UI,,,

when I connect it via Console or noVNC ...I found it suspend display just as my first post screenshot above,,,

we also tried to connect via cmd "qm terminal 101"..

there is no any repsone whatever I do,,keyboard keypress, mouse click etc.

this vm is running smoothly for some weeks,,, but connect timeout suddenly one-day,,,

we tried to fix it,,but failed,,,because it suspend and no response outside,,

then we rollback to one snapshot ,,,it works fine,,,,but the vm time is error and we can't update via ntp service,,,

then we reboot ,,,,it suspend again...

any queries,,,pls. reply....thanks very much...

 

[kasenhoo]

I change display to vga:STD。。。

suspend here...

 

[Neobin]

Your PVE version is over one year old [1].
Not going to say that this will definitely fix your problem, but updating (and rebooting afterwards) your PVE to the latest version would be a good starting point for further troubleshooting in my opinion.
Maybe it already fixes your problem or at least you can rule out the old PVE (and all that comes with it) version(s).

[1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0

 

[kasenhoo]

Your PVE version is over one year old [1].
Not going to say that this will definitely fix your problem, but updating (and rebooting afterwards) your PVE to the latest version would be a good starting point for further troubleshooting in my opinion.
Maybe it already fixes your problem or at least you can rule out the old PVE (and all that comes with it) version(s).

[1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0

Thanks bro.

There are lots servers running smoothly on the PVE...

I can't upgrade PVE Version due to only one vm failed...

so,, I hope to save this vm without any actions affecting other vms..

 

[kasenhoo]

Close this thread..

I have no idea about the problem..

maybe try to fix next time.

thanks everyone

 

[YOsip]

I was playing around with the api, and when I put the VM on "pause", and then "reset" via the API the machine enters the "prelaunch" state which looks similar to yours. Another "reset" succeeds but puts the machine it in the same state, it needs to be "resumed" to start working. I think the "pause" state can be caused by a lack of resources (cpu, disk space) from what I saw in some tickets, but I didn't find any documentation on this