Mohammed Gamal wrote:
+vmx_inject_irq(vcpu, vec);
kvm_queue_exception()
OK.
Not so fast, the GP# pops up again with kvm_queue_exception(). Why
should we use kvm_queue_exception() here?
kvm_queue_exception() will also block interrupt injection. Without
this
Jan Kiszka wrote:
But it seems the best thing to do is not to trap #DB in
update_exception_bitmap()?
Was my first idea as well. I do not understand what is going on there,
but when I simply exclude #DB from the exception bitmap in real mode,
the problem pops up again: #GP on th
On Sun, Jul 13, 2008 at 12:09 PM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
> Avi Kivity wrote:
>> Jan Kiszka wrote:
>>> It looks like that we should forward all #DB exceptions to the guest in
>>> real mode unless we are sure they were caused by a host-injection. Here
>>> is more or less a hack to achi
Avi Kivity wrote:
> Jan Kiszka wrote:
>> It looks like that we should forward all #DB exceptions to the guest in
>> real mode unless we are sure they were caused by a host-injection. Here
>> is more or less a hack to achieve this (breaking guest debugging for
>> now):
>>
>> diff --git a/arch/x86/kv
Jan Kiszka wrote:
It looks like that we should forward all #DB exceptions to the guest in
real mode unless we are sure they were caused by a host-injection. Here
is more or less a hack to achieve this (breaking guest debugging for
now):
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index
Mohammed Gamal wrote:
> On Fri, Jul 11, 2008 at 1:53 PM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
>> Mohammed Gamal wrote:
>>> On Fri, Jul 11, 2008 at 12:22 AM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
Mohammed Gamal wrote:
> On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]>
On Fri, Jul 11, 2008 at 1:53 PM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
> Mohammed Gamal wrote:
>> On Fri, Jul 11, 2008 at 12:22 AM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
>>> Mohammed Gamal wrote:
On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]>
wrote:
> Mohammed
Mohammed Gamal wrote:
> On Fri, Jul 11, 2008 at 12:22 AM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
>> Mohammed Gamal wrote:
>>> On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
Mohammed Gamal wrote:
> On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECT
On Fri, Jul 11, 2008 at 12:22 AM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
> Mohammed Gamal wrote:
>> On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>>> Mohammed Gamal wrote:
On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECTED]>
wrote:
>
Mohammed Gamal wrote:
> On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>> Mohammed Gamal wrote:
>>> On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECTED]>
>>> wrote:
>>>
Mohammed Gamal wrote:
> After updating my kvm-userspace tree to the lat
> After booting FreeDOS, there are a number of boot options with
> different memory extenders, after selecting any option the system
> freezes
Sorry, I meant the VM, not the whole system.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED
On Thu, Jul 10, 2008 at 11:02 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Mohammed Gamal wrote:
>>
>> On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> Mohammed Gamal wrote:
>>>
After updating my kvm-userspace tree to the latest git tree. I am
Mohammed Gamal wrote:
On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
Mohammed Gamal wrote:
After updating my kvm-userspace tree to the latest git tree. I am no
more able to run FreeDOS. The VM freezes after choosing any of the
boot options. I am running both
On Thu, Jul 10, 2008 at 7:31 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Mohammed Gamal wrote:
>>
>> After updating my kvm-userspace tree to the latest git tree. I am no
>> more able to run FreeDOS. The VM freezes after choosing any of the
>> boot options. I am running both latest kvm.git and
Mohammed Gamal wrote:
After updating my kvm-userspace tree to the latest git tree. I am no
more able to run FreeDOS. The VM freezes after choosing any of the
boot options. I am running both latest kvm.git and kvm-userspace.git
Can you bisect to the commit that broke it?
Regards,
Anthony Li
After updating my kvm-userspace tree to the latest git tree. I am no
more able to run FreeDOS. The VM freezes after choosing any of the
boot options. I am running both latest kvm.git and kvm-userspace.git
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to
On Thu, Jul 10, 2008 at 6:47 PM, Mohammed Gamal <[EMAIL PROTECTED]> wrote:
> After updating my kvm-userspace tree to the latest git tree. I am no
> more able to run FreeDOS. The VM freezes after choosing any of the
> boot options. I am running both latest kvm.git and kvm-userspace.git
>
Forgot to
17 matches
Mail list logo
