Returning to this bugreport again, from 23.10.2011. (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646249)
Georg, do you still have problems you described in #646249, when a guest being "clonezilled" stops responding to external events after some time and some massive data copying? I noticed a few things in your report: 1) you specified 4 cores for your guest. Does the problem happen when you use single core too? 2) Does it happen when you use not more virtual cores than you have physical cores on your host? 3) there is no information about your hardware (notable CPU). qemu-kvm bug script collects this information when you run `reportbug qemu-kvm', -- it looks like you removed this info from the bug report for some reason. I want to see content of /proc/cpuinfo on your host. 4) You mentioned that the host kernel is 3.0.0-1 amd64, but system information shows it is 2.6.39-0-generic, i686 (32bit). Which one is correct? 5) if your host kernel is 32bit, why you mentioned that your qemu-kvm is for amd64 architecture? Is it really 64bit or 32bit? 6) in xml vm config I see <memory>2890752</memory>, which is not supported by 32bit qemu-kvm userspace. 7) If qemu-kvm is 64bit, it looks like you have a really bad mix of 32/64bits software on your host, which is definitely not supported. 8) you have a bad mix of packages from ubuntu and from debian. This is definitely not supported configuration. So I want to get something conclusive from this bugreport. First of all, please try to answer the questions above with correct and non-contradicting information. Especiallu, please verify if the problem occurs with only one virtual cpu/core (the first question above), and show information about your cpu (/proc/cpuinfo) And also, please try with current versions of qemu-kvm and host kernel. Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
