Hi Mark,another report, so when not using virtio for drive I'm able to compile few haskell packages which is about a week or so of run. I've seen just one issue when the compilation stopped for about 22 hours and then continued well.
Anyway, as you are dealing with SPARC/Qemu, I'd like to note that I'm a little bit surprised how slow this is in comparison with ARMv8 emulation. Please don't get me wrong! It's a tremendous value to have SPARC/64 emulated at all. It's just a little bit surprise for me since I always first nbench2 emulator and then work with it when the results are kind of acceptable. Basically I get +- similar nbench2 results from running SPARC64 and AArch64 emulation with Linux and nbench2 on top of that, cut:
SPARC64: MEMORY INDEX : 3.176 INTEGER INDEX : 3.640 FLOATING-POINT INDEX: 0.528 Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38 ARMv8: MEMORY INDEX : 2.378 INTEGER INDEX : 3.249 FLOATING-POINT INDEX: 0.708 Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38and yet, it looks like SPARC is more than 7 times slower on compilation of the nbench. I guess it's also slower generally. For your information it takes around 1 minute to compile nbench2 on ARMv8 and more then 7 minutes to compile on SPARC64.
Do you have any idea why this may be so different? Both running the same qemu version and on the same host OS and the same host machine (Solaris 11/xeon e5-2620).
Thanks! Karel On 01/27/15 11:44 PM, Mark Cave-Ayland wrote:
On 27/01/15 06:22, Karel Gardas wrote:Hi Mark, I've kept running qemu-sparc64 with debian 7.7 and was compiling new GHC compiler there. It now failed on not enough space on a drive so at least I'm reporting that even after 300 hours of hard work, the thing is still running. Now I'll have a look if I'm somehow able to grow the qemu drive and then grow debian fs as I would like to avoid reinstall... If any lockups happen here, I'll let you know. Thanks, KarelHi Karel, Thanks for the update - good to hear a report that it's working well for you. Fingers crossed it makes it all the way to the end... If your image is a qcow2 then it should be simple to use qemu-img to expand the image, then boot into a suitable rescue CD in order to resize the filesystem. ATB, Mark.