Trouble with qcow2 disk corruption for windows 2000 server guests.

  • Thread starter Thread starter TonyLudwick
  • Start date Start date
T

TonyLudwick

Guest
Good Afternoon All,
I am new to Proxmox and fairly new to virtualization. I am very impressed with Proxmox and it's ease of use. I have a bunch of Windows 2000 physical servers that I need to convert to virtual servers running on a Proxmox 1.9 host. I have successfully converted one server using the method in the Proxmox migration HowTo http://pve.proxmox.com/wiki/Migrati...erver_to_Proxmox_VE_.28KVM.29_using_SelfImage.
My second server I am having troble with disk corruption. The physical machine is a Windows 2000 box with two drives. Drive 0 (IDE 0:0) is Basic 103 gb with the first partition being a 31mb fat utility partition, the second being a 7.91 gb ntfs partition that is the C: Boot Drive, the third being a 93.76 gb ntfs partition that is the D: drive, and 1.30 gb is unallocated. Drive 1 (IDE 0:1) is Dynamic 411 gb with the first partition being a 116.47 gb ntfs partition that is the E: Drive, the second being a 195.31 gb ntfs partition that is the F: Drive, and the third being a 99.22 gb ntfs partition that is the G: drive. I have not had any trouble with drive 0. The trouble is with Drive 1, it converts, the VM starts, but then out of the blue, one or more partitions on the drive become corrupted and/or loose their drive letters. I have also tried recreating the drive from scratch, defining it as a Basic drive in windows and manually creating the partitions, and then copying the data accross the network from live physical to live virtual, and I have the same problem. I have also tried restoring the data to the drive with backup-exec, and have the same problem. The VM is defined with 1 CPU, 512 mb memory, and Virtio network card. I would greatly appreciate if anyone could point me in the right direction in getting this problem solved.

In addition to the problem above, because I am a beginner, I have a few other related questions:

All of the servers that I wish to virtualize are Windows 2000 with a couple Windows NT4 servers. My main concerns and priorities are Reliability/Stability and Performance, in that order. What are the best VM settings to use for my situaion? For instance, which disk format is best, qcow2, Raw, or vdmk? Which network card would be best? Which Video Graphics adapter? How many CPU units, and what effect does this have, is it essentialy the priority that the host gives the VM? Lastly, do I need to be running any OS update procedure on the Proxmox Host, or does it auto update itself.


Thank you in advance for your patience and help.

Regards,
Tony
 
Hi Tony,
can you try with raw-format? You can convert the file with qemu-img.

For the Windows-server I can recommend following:
vmdisk-format: raw (or on lvm, which is also raw)
disks: virtio (or IDE for VMs without heavy disk-io).
network: e1000 with the driver from intel (I have made allways bad experiences with virtio-net on windows - even with registry-tuning).
vga: standard

Auto-update on windows?? Realy? OK, I'm not an windows-guy ;)

Udo
 
Udo,
Thanks for the reply. Regarding "Update" or "Auto-Update", my question was referring to the Proxmox host OS. In other words, do I need to go to the Proxmox console and issue commands "apt-get update" and "apt-get upgrade" periodically or does Proxmox have a routine that monitors for updated Debian and Proxmox packages.

Regards,
Tony
 
Udo,
Thanks for the reply. Regarding "Update" or "Auto-Update", my question was referring to the Proxmox host OS. In other words, do I need to go to the Proxmox console and issue commands "apt-get update" and "apt-get upgrade" periodically or does Proxmox have a routine that monitors for updated Debian and Proxmox packages.

Regards,
Tony
Hi Tony,
you must do update&upgrade by hand. Especial the upgrade-feature should not run automaticly, because often you get an new kernel and need an reboot, or an new qemu-version and need an restart of all VMs. This should any admin do in the right time...

Udo
 
I tried creating Disk1 as raw on the vm, but after the P2V conversion using selfimage, the disk still ends up as unreadable or corrupt to the vindows2000 vm. Is there anything special I need to do since disk1 on the physical machine is a dynamic disk? Do any of you have any ideas as to why I would be having this problem?

Regards,
Tony