I was able to start kvm again, using the same command-line, and the same sequence of events seemed to trigger the hang again. Here's what I did:
1. kvm -hda ReactOS.qcow2 -net nic,model=ne2k_pci -net user 2. wait for the ReactOS desktop to appear 3. open the desktop Command Line icon 4. enter the command "ping 10.0.2.2" 5. use the Start menu to open Programs > ReactOS Explorer 6. Explorer will ask if SDI or MDI style is preferred: select SDI, "open subfolders in separate windows" and click OK 7. Explorer starts to render, but then kvm crashes with the previously-attached trace. I doubt that steps 3-4 are needed, but I've run out of regression- testing time for now. Some setup notes, in case the exact image is needed: it's an odd situation, as I started with a vmware image and converted it to qcow2. I haven't tested whether or not this exact qcow2 image is essential to the problem. $ md5sum ReactOS-0.3.4-REL-vmware.zip 89b01a6d026d2a270855c84c4167b027 ReactOS-0.3.4-REL-vmware.zip $ unzip ReactOS-0.3.4-REL-vmware.zip [ warnings about \ vs / omitted ] $ cd ReactOS-0.3.4-VMware/ $ md5sum ReactOS.v* f2b857b8fdb987252cd3a4398462f71a ReactOS.vmdk b6212264b2f49a7ea0f5e1da2b645c11 ReactOS.vmx $ qemu-img convert ReactOS.vmdk ReactOS.qcow2 (VMDK) image open: flags=0x2 filename=ReactOS.vmdk $ md5sum ReactOS.qcow2 bfd59efdd78086d2138bf4b0d5486128 ReactOS.qcow2 -- frozen kvm while running reactos guest https://bugs.launchpad.net/bugs/219679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
