Proxmox Server restart when installing windows server 2016

Khaled Suliman

New Member
Oct 18, 2018
1
0
1
35
Hello,
I'm installing windows server on the proxmox server, after finishing the installation and during boot, the system freezes and the server restart by its own, sometimes during the installation
I'm just having this problem with Windows Server, Linux works like a charm

System details:
CPU: Intel Scalable Gold 6154
RAM: 128GB
2 m.2 nvme drives as raid1 (for VM's)
2 SSD drives as raid1 (for Proxmox)
proxmox: 5.2-1

VE Configuration:
os: windows server
CPU Type: skylake
hard drive: (tried all of them, SATA, SCSI, VIRTO block)

in some configuratio,n the system works, but after a while when the windows is in load the server restart by itself
also, I'm not getting anything in the "Syslog".
Code:
Dec  1 06:01:12 pve1 kernel: [  319.596968] device tap100i0 entered promiscuous mode
Dec  1 06:01:12 pve1 kernel: [  319.605994] vmbr1: port 2(tap100i0) entered blocking state
Dec  1 06:01:12 pve1 kernel: [  319.605995] vmbr1: port 2(tap100i0) entered disabled state
Dec  1 06:01:12 pve1 kernel: [  319.606605] device enp61s0f0 entered promiscuous mode
Dec  1 06:01:13 pve1 kernel: [  320.863717] vmbr1: port 2(tap100i0) entered blocking state
Dec  1 06:01:13 pve1 kernel: [  320.863719] vmbr1: port 2(tap100i0) entered forwarding state
Dec  1 06:01:14 pve1 pvedaemon[20961]: <root@pam> end task UPID:pve1:0000876A:00007C9A:5C01F978:qmstart:100:root@pam: OK
Dec  1 06:01:22 pve1 pvedaemon[20962]: <root@pam> starting task UPID:pve1:0000892F:000080AE:5C01F982:vncproxy:100:root@pam:
Dec  1 06:01:22 pve1 pvedaemon[35119]: starting vnc proxy UPID:pve1:0000892F:000080AE:5C01F982:vncproxy:100:root@pam:
Dec  1 06:02:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Dec  1 06:02:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Dec  1 06:03:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Dec  1 06:03:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Dec  1 06:04:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Dec  1 06:04:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Dec  1 06:05:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Dec  1 06:05:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Dec  1 06:22:24 pve1 systemd-modules-load[3525]: Inserted module 'iscsi_tcp'
Dec  1 06:22:24 pve1 systemd-modules-load[3525]: Inserted module 'ib_iser'
Dec  1 06:22:24 pve1 systemd-modules-load[3525]: Inserted module 'vhost_net'
Dec  1 06:22:24 pve1 kernel: [    0.000000] Linux version 4.15.17-1-pve (root@nora) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PVE 4.15.17-9 (Wed, 9 May 2018 13:31:43 +0200) ()
Dec  1 06:22:24 pve1 keyboard-setup.sh[3509]: cannot open file /tmp/tmpkbd.ITBR10
Dec  1 06:22:24 pve1 kernel: [    0.000000] Command line: BOOT_IMAGE=/ROOT/pve-1@/boot/vmlinuz-4.15.17-1-pve root=ZFS=rpool/ROOT/pve-1 ro root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet
Dec  1 06:22:24 pve1 kernel: [    0.000000] KERNEL supported cpus:
Dec  1 06:22:24 pve1 kernel: [    0.000000]   Intel GenuineIntel
Dec  1 06:22:24 pve1 kernel: [    0.000000]   AMD AuthenticAMD
Dec  1 06:22:24 pve1 kernel: [    0.000000]   Centaur CentaurHauls
Dec  1 06:22:24 pve1 systemd-udevd[3647]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32.
Dec  1 06:22:24 pve1 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec  1 06:22:24 pve1 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec  1 06:22:24 pve1 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dec  1 06:22:24 pve1 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'



Code:
proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-1
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-3
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!