On Sun, Aug 15, 2010 at 3:23 PM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 08/12/2010 04:07 AM, Mohammed Gamal wrote: >>>> >>>> I was playing around with the non-atomic-injection branch. I decided >>>> to use e_i_g_s=1, and it's worth noting that I never experienced these >>>> faults with the switch enabled. >> >> Hate to spoil it. I did experience the faults again with e_i_g_s=1, >> although much less frequently. >> >> What is rather really strange, is that I could get a Linux guest to >> boot up completely both with e_i_g_s=1 and without it with the real >> mode interrupt patch enabled. It looks to me like the problem mainly >> happens when the BIOS tranfers control to the boot loader. Other >> guests usually fail. >> >> Would you like me to attach a trace? > > > It will be much too big, upload it somewhere or send it to be privately. > > But, use the code with the interrupt injection setup fixed (see my comment > to patch 2). > Please take a look at my latest patch series. We can take the discussion there. > > -- > error compiling committee.c: too many arguments to function > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
