I have Promox 4.4-13/7ea56165 installed for couple weeks now on a
Supermicro AMD 6000 series
H8QGi-F
- It has all 4 cores, 256GB ECC RAM
- It has a 10GBE ISCSI to a SAN which holds VM OS Disks
I put a bunch of Ubuntu VMs on it and they have run flawless for 2 weeks straight.
I just put a Win2008R2 on it, and its been just turning OFF randomly every couple hours.
- I followed all the Promox guide to installing Win2008
- I started with Virtio disk and Network, I just changed them to IDE / Intel (but IDE gets 70% speed penalty)
- I turned off power saving, turned off Note on Reboot, installed Qemu agent
- I turned off Ballooning and gave it 16gigs ram
- It has 8 cores / 1 CPU
- Has the latest Windows Updates
When it happens I see no notices in the Proxmox control panel logs of any kind its just OFF. I can start it again no problem. Windows event viewer shows nothing about the crash I can see.
What am I missing? How or where would Proxmox show why its OFF?
After swapping to IDE/Intel I am now running a LOAD TEST for 15 mins at max CPU etc and it's still UP for now...
root@cloud1:~# pveversion -v
proxmox-ve: 4.4-84 (running kernel: 4.4.44-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-96
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80
if I look in dmseg I see some errors not sure what they relate to:
156.085514] kvm [2550]: vcpu0 unhandled rdmsr: 0xc001100d
[ 156.277022] kvm [2550]: vcpu1 unhandled rdmsr: 0xc001100d
[ 157.867827] kvm [2624]: vcpu0 unhandled rdmsr: 0xc001100d
[ 158.060401] kvm [2624]: vcpu1 unhandled rdmsr: 0xc001100d
[ 158.242241] device tap104i0 entered promiscuous mode
[ 158.262295] vmbr0: port 5(tap104i0) entered forwarding state
[ 158.262316] vmbr0: port 5(tap104i0) entered forwarding state
[ 160.778841] kvm [2682]: vcpu0 unhandled rdmsr: 0xc001100d
[ 162.682941] kvm: zapping shadow pages for mmio generation wraparound
[ 162.694188] kvm: zapping shadow pages for mmio generation wraparound
[ 169.777927] device tap108i0 entered promiscuous mode
[ 169.799082] vmbr0: port 6(tap108i0) entered forwarding state
[ 169.799103] vmbr0: port 6(tap108i0) entered forwarding state
[ 170.752349] device tap108i1 entered promiscuous mode
[ 170.773501] vmbr2: port 3(tap108i1) entered forwarding state
[ 170.773525] vmbr2: port 3(tap108i1) entered forwarding state
[ 172.013861] kvm: zapping shadow pages for mmio generation wraparound
[ 172.018002] kvm: zapping shadow pages for mmio generation wraparound
[ 189.321530] kvm [2824]: vcpu25 unhandled rdmsr: 0x3a
[ 189.321607] kvm [2824]: vcpu25 unhandled rdmsr: 0xd90
[ 189.321678] kvm [2824]: vcpu25 unhandled rdmsr: 0xc0000103
root@cloud1:~# qm config 104
agent: 1
balloon: 0
boot: c
bootdisk: ide0
cores: 8
hotplug: disk,network
ide0: QsKVM1:vm-104-disk-1,size=100G
ide1: QsKVM1:vm-104-disk-2,size=100G
memory: 16000
name: CanarcWin2008
net0: e1000=E6:EA:EB:20:A3:A4,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
scsihw: virtio-scsi-pci
smbios1: uuid=94dabc99-239f-4d6d-b702-bcc84b325301
sockets: 1
tablet: 0
Supermicro AMD 6000 series
H8QGi-F
- It has all 4 cores, 256GB ECC RAM
- It has a 10GBE ISCSI to a SAN which holds VM OS Disks
I put a bunch of Ubuntu VMs on it and they have run flawless for 2 weeks straight.
I just put a Win2008R2 on it, and its been just turning OFF randomly every couple hours.
- I followed all the Promox guide to installing Win2008
- I started with Virtio disk and Network, I just changed them to IDE / Intel (but IDE gets 70% speed penalty)
- I turned off power saving, turned off Note on Reboot, installed Qemu agent
- I turned off Ballooning and gave it 16gigs ram
- It has 8 cores / 1 CPU
- Has the latest Windows Updates
When it happens I see no notices in the Proxmox control panel logs of any kind its just OFF. I can start it again no problem. Windows event viewer shows nothing about the crash I can see.
What am I missing? How or where would Proxmox show why its OFF?
After swapping to IDE/Intel I am now running a LOAD TEST for 15 mins at max CPU etc and it's still UP for now...
root@cloud1:~# pveversion -v
proxmox-ve: 4.4-84 (running kernel: 4.4.44-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-96
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80
if I look in dmseg I see some errors not sure what they relate to:
156.085514] kvm [2550]: vcpu0 unhandled rdmsr: 0xc001100d
[ 156.277022] kvm [2550]: vcpu1 unhandled rdmsr: 0xc001100d
[ 157.867827] kvm [2624]: vcpu0 unhandled rdmsr: 0xc001100d
[ 158.060401] kvm [2624]: vcpu1 unhandled rdmsr: 0xc001100d
[ 158.242241] device tap104i0 entered promiscuous mode
[ 158.262295] vmbr0: port 5(tap104i0) entered forwarding state
[ 158.262316] vmbr0: port 5(tap104i0) entered forwarding state
[ 160.778841] kvm [2682]: vcpu0 unhandled rdmsr: 0xc001100d
[ 162.682941] kvm: zapping shadow pages for mmio generation wraparound
[ 162.694188] kvm: zapping shadow pages for mmio generation wraparound
[ 169.777927] device tap108i0 entered promiscuous mode
[ 169.799082] vmbr0: port 6(tap108i0) entered forwarding state
[ 169.799103] vmbr0: port 6(tap108i0) entered forwarding state
[ 170.752349] device tap108i1 entered promiscuous mode
[ 170.773501] vmbr2: port 3(tap108i1) entered forwarding state
[ 170.773525] vmbr2: port 3(tap108i1) entered forwarding state
[ 172.013861] kvm: zapping shadow pages for mmio generation wraparound
[ 172.018002] kvm: zapping shadow pages for mmio generation wraparound
[ 189.321530] kvm [2824]: vcpu25 unhandled rdmsr: 0x3a
[ 189.321607] kvm [2824]: vcpu25 unhandled rdmsr: 0xd90
[ 189.321678] kvm [2824]: vcpu25 unhandled rdmsr: 0xc0000103
root@cloud1:~# qm config 104
agent: 1
balloon: 0
boot: c
bootdisk: ide0
cores: 8
hotplug: disk,network
ide0: QsKVM1:vm-104-disk-1,size=100G
ide1: QsKVM1:vm-104-disk-2,size=100G
memory: 16000
name: CanarcWin2008
net0: e1000=E6:EA:EB:20:A3:A4,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
scsihw: virtio-scsi-pci
smbios1: uuid=94dabc99-239f-4d6d-b702-bcc84b325301
sockets: 1
tablet: 0