Search results

It boots when I use these parameters: -hda '/dev/sdc' -hdachs 8192,16,32,none It does NOT boot when the config file is read and parameters are generated: -drive file=/dev/sdc,index=0,media=disk -hdachs 8192,16,32,none What is the difference between those two?

It booted under plain qemu using this flag (the last parameter can be none or lba; it doesn't boot using lba): -hdachs 8192,16,32,none Is it possible to add custom parameters in the config file?

My original config file was (I also tried ide0 instead of scsi0, with the same result): ostype: w2k3 memory: 512 name: Windows2_dc1 smp: 1 vlan0: rtl8139=4E:50:EF:96:2C:BE bootdisk: scsi0 scsi0: /dev/sdc boot: cad freeze: 0 cpuunits: 1000 acpi: 1 kvm: 1

This is the log I have: /usr/sbin/qm start 103 qemu: 'file=/dev/sdc,if=scsi,index=0,heads=64,secs=32,cyls=8192,media=disk,boot=on' invalid physical heads number start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/103.mon,server,nowait -vnc...

I can't figure it out. How should it look like in the config file? Something like this: scsi0: /dev/sdc,cyls=8192,heads=64,secs=32 doesn't seem to work.

Why should it help? Anyway, I tried, with a different bootdisk each time, and it fails to boot: bootdisk: ide1 scsi0: /dev/sdc scsi1: /dev/sdc scsi2: /dev/sdc scsi3: /dev/sdc ide0: /dev/sdc ide1: /dev/sdc ide2: /dev/sdc ide3: /dev/sdc

For some reason (DRBD migration and increasing the size of the device in the past) I have these settings hardcoded in the vmware config file for that guest: ddb.virtualHWVersion = "4" ddb.geometry.cylinders = "8192" ddb.geometry.heads = "64" ddb.geometry.sectors = "32"...

Nothing special about this Win2003 installation. It is installed on a iSCSI drive, which is basically /dev/sdX drive to system. What I think DOES matter is listed here - note the differences in fdisk output (I booted SystemRescueCD on both vmware and proxmox guests): proxmox host / guest /...

Also, when trying to use chkdsk from the recovery console, it says the filesystem is broken beyond repair. But it works fine in VMware. I'm puzzled.

OK, I also found this HOWTO: http://www.techspot.com/vb/topic8356.html It says: - boot off an installation CD - choose installation and NOT repair - then, choose repair When I do it, the installer checks the drive shortly and then says (translation from German): Drive C: is damaged and can't...

Unfortunately, it doesn't help. I've followed the instructions on http://support.microsoft.com/kb/330184 Basically, I started "bootcfg /rebuild" and answered the questions. I'm still getting the same error message. Which doesn't wonder - new entries detected by Windows Recovery Console...

It is Windows 2003. Bootloader seems to be fine when I run VMware - it boots correctly then. Let's see if booting from the install ISO helps...

I'm trying to start a KVM guest from which used to be a VMware guest. Document on http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE is pretty straightforward, but some of it doesn't apply in my case: for VMware, I didn't use file images, but raw block device. When I try to start...

Here are some links: http://article.gmane.org/gmane.comp.emulators.kvm.devel/22767/match=scsi (scroll down to see how SCSI write performance compares, not Windows-specific though) Some old one comparing IDE with SCSI - results of SCSI and IDE are similar...

Did anything change here? This post is 6 month old - and I've read on KVM mailing list that using SCSI for Windows should provide much better disk performance. On the other hand, you write that using SCSI for Windows does not provide stability. Is this still valid with the latest release of...