Bugs item #1814637, was opened at 2007-10-16 20:39 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1814637&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: Windows 2000 setup unstable Initial Comment: The testing reveals that Windows 2000 setup stucks very often after the reboot and before the "Regional Settings" stage. Host: Fedora7, 64-bit, Intel CPU, KVM-46. (A different error happens on AMD machines. But this bug focuses on Intel) Those errors are not always reproduceble, and those fail about half of the time. Tested with: qemu-kvm -hda /disks/win2000.vmdk -cdrom /iso/win2000.iso -m 128 -boot d -Alexey "Technologov". 16.10.2007. ---------------------------------------------------------------------- >Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:29 Message: No reply from bug submitter to query of June 11, so closing as out of date. ---------------------------------------------------------------------- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-11 11:16 Message: Hi, Again looking through old bugs Could you please let us know if this is still a problem with a recent QEMU/KVM. If not, lets close this bug. Thanks, Jes ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-11-01 12:59 Message: Logged In: YES user_id=1839746 Originator: YES Update: this seems to be VMDK-related issue. Windows 2000 setup works fine with qcow2 and raw formats. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-11-01 08:17 Message: Logged In: YES user_id=1839746 Originator: YES Update: There are 3 ways to see if you have buggy version of KVM - 1. Detecting devices setup step in the buggy version takes ~25-30 minutes. 2. You will get "not enough disk space" (-win2k-hack will not help you!) 3. You will get strange error saying: "SAM User database damaged" and setup will close. KVM-36-1 seems to be the commit, that destroyed Windows 2000. (SHA: 263773f7a6606efda85f7b184a067b5f560ed39b) -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-10-17 19:31 Message: Logged In: YES user_id=1839746 Originator: YES While this is strange, but this Win2000 stage often succeeds if I want about 20 minutes. Just usually people don't have that _much_ patience, and they shut down VMs in about 5 minutes of non-progress. -Technologov ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-10-17 10:00 Message: Logged In: YES user_id=1839746 Originator: YES File Added: KVM46-VMX64-Windows2000-loop-screenshot.jpg ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-10-17 09:45 Message: Logged In: YES user_id=1839746 Originator: YES Update: The guest is not fully dead: the mouse responds, but it is looped forever trying to detect some kind of hardware. I made strace logs & screenshot. -Technologov ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1814637&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
