cannot install Windows Server OS - missing drivers / disks?!

[mikeyboy01443]

Hi all,

I have just set up PROXMOX 3.4 to test, in the lab. It is running nested inside ESXi 5.5 but I don't think my issue is related to this.

I have created a VM, powered it on, and it boots up fine, I get into the first few stages of the windows install, but it soon comes up with a screen saying that a required CD/DVD device driver is missing, etc.
The CD/DVD drives are IDE (1 and 2)
I have seen many posts relating to this sort of thing and people advising to install the VIRTIO drivers, but I don't think this is the issue. It doesn't even get to the bit where I select which version of Windows to install, it comes up before that. I have tried using the latest VIRTIO ISO drivers, and an older version (0.1.30).
The hardware of the VM I have tried (to no joy yet) include:
dynamic RAM / Fixed RAM
IDE / SCSI / VIRTIO drives
qcow2 / RAW disks

I have also got a KVM server on RHEL running on the same ESX host, with no probs, so seems something in this server which wont let it SEE the disk?

also running diskpart in the windows setup, it can see the disk (a 20gb disk) so I know its visible to the VM itself....

please help!

 

[tom]

check the windows ISO, looks damaged (check md5sum)

 

[mikeyboy01443]

just an update - managed to get it working. Strange what caused it:
I had mounted the ISO on the (virtual) Proxmox host, in VMware, same as if the host had the DVD inserted. I told the VM to install from the host DVD device, and it could clearly read it as it booted into the windows setup environment.
But in the end I needed to upload the (same) ISO onto the Proxmox ISO store, and mounted that in the VM then. This worked! Hopefully might help someone else if they come across the same issue.
Got some VMs up and running also, but I could not get the networking to work, as expected.

I thought I could just create a bridge device for each VLAN (not tested open-vswitch yet), but when I did this, VLAN tagging did not work. I needed to manually create a vlan interface for each VLAN, and then create bridge devices on top of these. The VLAN interfaces show up in the web interface as "unknown". I will probably bung another NIC in and test with open-vswitch soon
I also needed to set the aging on each bridge to 0 as without doing this, I get very poor network performance (had to do the same in my other KVM test host)