How to solved or disabled the state of suspended

lynn_yudi

Renowned Member
Nov 27, 2011
86
0
71
hi

the Win7 of the kvm is always a suspended state. how to fix this?

# cat /etc/pve/qemu-server/900.conf
agent: 1
args: -device intel-hda,id=sound0,bus=pci.0,addr=0xf -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0
bootdisk: virtio0
cores: 4
cpuunits: 102400
memory: 4096
name: base-Win7
net0: virtio=62:37:64:63:39:34,bridge=vmbr0,tag=4088
numa: 0
onboot: 1
ostype: win7
smbios1: uuid=bfac6a20-8a2f-4101-bb26-08d64e35fa71
sockets: 1
usb0: spice
vga: qxl2
virtio0: local:900/vm-900-disk-1.qcow2,discard=on,size=16G

# pveversion -v
proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
openvswitch-switch: 2.3.2-2

thanks.
 

Attachments

  • suspended.png
    suspended.png
    26.8 KB · Views: 44
adapt your power settings inside windows to "always on".
 
thanks, will be try it.

# qm monitor 900
Entering Qemu Monitor for VM 900 - type 'help' for help
qm> system_wakeup

this can fixed also, Can be integrated into the 'resume' ?
 
thanks, will be try it.

# qm monitor 900
Entering Qemu Monitor for VM 900 - type 'help' for help
qm> system_wakeup

this can fixed also, Can be integrated into the 'resume' ?

if you access the VM via NoVNC, it will also resume.

so far I see this small problem only with SPICE.
 
it's the windows 7 system, in power settings, no 'always on' options :)

and had tested, if not use the options: 'vga: qxl', it's normal.

I do not remember exactly the name, but you have to set your windows 7 VM that it never suspends - therefore I called it "always on".