https://bugzilla.novell.com/show_bug.cgi?id=704537 https://bugzilla.novell.com/show_bug.cgi?id=704537#c10 G Venk <gvenkat@attglobal.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gvenkat@attglobal.net | --- Comment #10 from G Venk <gvenkat@attglobal.net> 2012-05-10 00:06:40 UTC --- The steps reported in the first post IS the consistent way to reproduce it except for the additional information that Avast be running in the guest. This is why the crash would happen only in Windows guests. My VM would consistently crash every alternate boot after a period of time varying from 1 min to 10 min or so from start. As I understand it, Avast just tickles the bug in the virtio block driver not that it is doing anything wrong. The virtio block driver needs to handle it when guest applications make large requests. Not sure what the protocol is but I suspect it is to return some correct error code so the guest application can then ask for a smaller block. Avast just happens to THE application in this case that was making the large request. And the block driver crashed on such requests bringing down the whole VM. I can also confirm that after I installed the "fixed" driver in the link above in the Guest, the VM is no longer crashing. The diff in the source code for the driver from the previous version should indicate what the fix was in the block driver. Suspect it is a fairly simple fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.