I do not have this problem here. a reboot can takes a long time after applying updates, just wait a few minutes.
For win2012/win8, disable "fast boot" and try again.
Make sure you run latest packages (post 'pveversion -v' and also your VM config: 'qm config VMID')
Hi Tom. Thanks for the reply.
I think I am running all the latest packages.. Below is my pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
Below is my qm config
bootdisk: ide1
cores: 6
cpu: host
ide0: none,media=cdrom
ide1: local-hd2:103/vm-103-disk-1.raw,size=100G
memory: 8192
name: w2kr2-LYNC
net0: e1000=02:70:56:4D:95:09,bridge=vmbr0
net1: e1000=02:70:56:4D:95:10,bridge=vmbr0
ostype: win7
sockets: 1
Note Prior to changing it to ide1 it was:
bootdisk: sata0
cores: 6
cpu: host
ide0: none,media=cdrom
sata0: local-hd2:103/vm-103-disk-1.raw,size=100G
memory: 8192
name: w2kr2-LYNC
net0: e1000=02:70:56:4D:95:09,bridge=vmbr0
net1: e1000=02:70:56:4D:95:10,bridge=vmbr0
ostype: win7
sockets: 1
As for taking a long time to boot, it has nothing to do with a time issue. When it reboots, it goes into "Windows Recovery" and that's it. There is no way to get back into Windows. It's stuck in it...
I am not sure what you mean by "fast boot"
I am able to re-duplicate this problem over and over again... Just create a new VM, and install Windows 2008 R2 or Win Server 2012 while using sata0 as your boot device. Then do windows updates after install is complete. Windows will reboot, and never come back.. (Will be stuck in Windows Recovery).
Thank you,
Aaron