[SOLVED] Win XP Fails to install on 4.4

Jan 2, 2017
12
2
8
32
Just did a clean install of Proxmox 4.4-1/eb2d6f1e and am having issues with Windows XP installing. I created the VM via the web GUI with all the default options, no VirtIO drivers or ballooning memory, etc, and XP installation will get to the "Installing Devices.. 35 Minutes remaining" screen, and then just freeze.

I did some research, and adjusting the display setting from "default" to "Standard VGA" and restarting the install process, the installation will mostly complete. It will freeze at the welcome screen asking you to adjust the display settings, but after a reboot, it will boot successfully.

My issue is that once you get to this point, any display setting above 640x480 with any setting of display hardware will result in the VM freezing.

I've done a memory test with Memtest86, and let it run for about 3 days (system has 24gb) and didn't come up with any memory errors. I've done a reinstall of the OS numerous times, and lastly replaced the graphics card from an Nvidia GeForce 7200 to a GTX650 thinking maybe the video card may be causing an issue. But, issue is still persistent.

The ISO I'm using is a good ISO, been using it forever and have used it many times on Proxmox (just not 4.4). I've also tried recreating the ISO from the original CD, but still end up with this issue.

Has anyone else ran into this issue?

Code:
pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80
 

Richard

Proxmox Staff Member
Staff member
Mar 6, 2015
889
41
48
Austria
Just did a clean install of Proxmox 4.4-1/eb2d6f1e and am having issues with Windows XP installing. I created the VM via the web GUI with all the default options, no VirtIO drivers or ballooning memory, etc, and XP installation will get to the "Installing Devices.. 35 Minutes remaining" screen, and then just freeze.

I did some research, and adjusting the display setting from "default" to "Standard VGA" and restarting the install process, the installation will mostly complete. It will freeze at the welcome screen asking you to adjust the display settings, but after a reboot, it will boot successfully.

My issue is that once you get to this point, any display setting above 640x480 with any setting of display hardware will result in the VM freezing.

I've done a memory test with Memtest86, and let it run for about 3 days (system has 24gb) and didn't come up with any memory errors. I've done a reinstall of the OS numerous times, and lastly replaced the graphics card from an Nvidia GeForce 7200 to a GTX650 thinking maybe the video card may be causing an issue. But, issue is still persistent.

The ISO I'm using is a good ISO, been using it forever and have used it many times on Proxmox (just not 4.4). I've also tried recreating the ISO from the original CD, but still end up with this issue.

Has anyone else ran into this issue?

Code:
pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80


Running the same PVE version I don't have any problems with Windows XP - screen resolution can be adjusted up to 1280x1024.

The configuration file:


Code:
balloon: 512
bootdisk: ide0
cores: 1
ide0: storage:6622/vm-6622-disk-1.qcow2,format=qcow2,size=24G
ide2: none,media=cdrom
memory: 1024
name: WX-6622
net0: virtio=B6:87:8F:16:82:1B,bridge=vmbr0
net1: e1000=C6:1D:84:24:A5:36,bridge=vmbr2
net2: rtl8139=5E:8E:E7:CA:74:49,bridge=vmbr3
net3: vmxnet3=DE:F3:3B:FC:7F:0F,bridge=vmbr3
ostype: wxp
smbios1: uuid=fafb0a32-c958-4567-bfb1-bf7709577fa7
sockets: 1
 
Jan 2, 2017
12
2
8
32
Running the same PVE version I don't have any problems with Windows XP - screen resolution can be adjusted up to 1280x1024.

The configuration file:


Code:
balloon: 512
bootdisk: ide0
cores: 1
ide0: storage:6622/vm-6622-disk-1.qcow2,format=qcow2,size=24G
ide2: none,media=cdrom
memory: 1024
name: WX-6622
net0: virtio=B6:87:8F:16:82:1B,bridge=vmbr0
net1: e1000=C6:1D:84:24:A5:36,bridge=vmbr2
net2: rtl8139=5E:8E:E7:CA:74:49,bridge=vmbr3
net3: vmxnet3=DE:F3:3B:FC:7F:0F,bridge=vmbr3
ostype: wxp
smbios1: uuid=fafb0a32-c958-4567-bfb1-bf7709577fa7
sockets: 1

Richard - Did yo do a fresh install of XP? Or was this VM part of a pve upgrade?

An interesting thing... I disabled "KVM Hardware Virtualization" in the options section of the VM, started the XP machine, and XP successfully installed the GD5446 driver. The VM would previously freeze as soon as the "Found new hardware..." popup would appear. I let the system install the driver, shutdown the VM, re-enabled KVM Hardware, and now I'm able to adjust the resolution higher than 640x480.

Very odd.

Here's the output of my config file for my XP VM.
Code:
bootdisk: ide0
cores: 1
ide0: local-lvm:vm-100-disk-1,size=32G
ide2: local:iso/xp_pro_sp3.iso,media=cdrom
memory: 512
name: XP
net0: rtl8139=8E:CB:53:45:53:F4,bridge=vmbr0
numa: 0
ostype: wxp
smbios1: uuid=a59c1fa6-ebf8-4ac8-a6b3-d69d1448e39e
sockets: 1
 
Jan 2, 2017
12
2
8
32
I've finally found the problem to my Proxmox woes... There appears to be a big issue with using a Xeon X5660 that's an engineering sample. Replacing the engineering sample chip with an actual X5660 that I got for $15 on ebay has remedied all these issues.

Thanks for all the great replies and support that I've gotten!
 

amdxp

New Member
Jul 28, 2017
13
0
1
40
Good to hear, I am failed for install on two machine as they are using es cpu . Then I start to suspect wrong on es cpu
 

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 your own in 60 seconds.

Buy now!