Bugs item #2062623, was opened at 2008-08-20 17:59 Message generated for change (Comment added) made by onedot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2062623&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: intel Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Marvin Vek (onedot) Assigned to: Nobody/Anonymous (nobody) Summary: virtio blockdev & -smp 2 unstable Initial Comment: After days and days of constant testing, it turns out the virtio block device in combination with -smp 2 is very very unstable: it seems it loses the disk. At a freeze, things like # dmesg still work, but accessing the disk is the end. Running the tests without if=virtio does not freeze at all. Doing the test with the if=virtio but -smp 1, is as stable as without if=virtio. A freeze did not give any messages at all. If you can tell me what i should enable in the kernel to make something possible pop up at a freeze, or what file to check, let me know. ### TEST SETUP # Start: kvm -drive file=~/guest.iso,index=0,media=disk,if=virtio,boot=on -m 2048 -smp 2 .. # Having the guest recompile the whole system, till it freezes: # emerge -e system && emerge -e world. ### HOST # Distro: Gentoo Linux # CPU: Intel Core 2 Duo (Mobile) "Penryn" T9300, cpuinfo added as attachment # Kernel: 2.6.25-gentoo-r7 # Kernel config: Added as attachment # Bitness: x86_64 multilib # KVM: 72-r1 (with ncurses and sdl support), kvm.ko and kvm-intel.ko built into the kernel. ### GUEST # Distro: Gentoo Linux # Kernel: 2.6.25-gentoo-r7 # Kernel config: added asattachment # Bitness: x86_64 no-multilib, pure 64bit ---------------------------------------------------------------------- >Comment By: Marvin Vek (onedot) Date: 2008-08-25 17:37 Message: Logged In: YES user_id=2187666 Originator: YES Having the new KVM-73 installed, deselected the kernel modules (kvm.ko, kvm-intel.ko and kvm-amd.ko), and using KVM-73's modules instead on the same kernel as above, resulted in a perfectly stable environment with the same tests and virtio block device. My guess is that the in-kernel modules are outdated, or something got fixed from 72 to 73, so i marked this bug as Out Of Date and Closed. Thanks a lot! ---------------------------------------------------------------------- Comment By: Marvin Vek (onedot) Date: 2008-08-20 18:02 Message: Logged In: YES user_id=2187666 Originator: YES File Added: .config ---------------------------------------------------------------------- Comment By: Marvin Vek (onedot) Date: 2008-08-20 18:00 Message: Logged In: YES user_id=2187666 Originator: YES File Added: cpuinfo ---------------------------------------------------------------------- Comment By: Marvin Vek (onedot) Date: 2008-08-20 17:59 Message: Logged In: YES user_id=2187666 Originator: YES File Added: .config ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2062623&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
