I am still holding to few patches for big real mode. After rebase I will
push those patches.
Thanks & Regards,
Nitin
Linux Open Source Technology Center, Intel Corporation
The Mind is like a parachute; it works much bett
Practicing Physicians in the US
788,260 in total <> 17,168 emails
Many popular specialties like Emergency Medicine, Plastic Surgery, OBGYN,
Oncology, Pediatrics and more
Sort by over a dozen different fields
reduced price is now: $397
!!! ITEMS BELOW ARE INCLUDED IN THE DEAL AT NO
On Wed, Feb 06, 2008 at 11:02:35AM +, Paul Knowles wrote:
> mmu_reset_needed |= vcpu->arch.cr0 != sregs->cr0;
> - vcpu->arch.cr0 = sregs->cr0;
> kvm_x86_ops->set_cr0(vcpu, sregs->cr0);
Why should this fix anything? The vcpu->arch.cr0 is also set in
kvm_x86_ops->set_cr0() aka vm
Dietmar Maurer wrote:
> Hi Anthony,
>
> The problem is that memory always grows, even after rebooting the VM.
>
When you start a VM, none of the memory for that VM has been reserved by
Linux regardless of what you specify in the '-m' parameter. Instead, as
the guest starts to access memory,
On Wed, 2008-02-06 at 11:32 -0600, Anthony Liguori wrote:
> Guillaume Thouvenin wrote:
> > Hello,
> >
> > I read on the kvmwiki/TODO that there is a work in progress for
> > extending x86 emulator to support more instructions in real mode and for
> > changing the execution loop to call the emula
Guillaume Thouvenin wrote:
> Hello,
>
> I read on the kvmwiki/TODO that there is a work in progress for
> extending x86 emulator to support more instructions in real mode and for
> changing the execution loop to call the emulator for real mode.
>
Yes, Nitin has done some work in this area.
Yeah, rate-limiting makes sense. Maybe we could take it one step further
and only print the warning the first time a particular unemulated DCR is
accessed.
I also agree about the captalization. :)
--
Hollis Blanchard
IBM Linux Technology Center
On Wed, 2008-02-06 at 12:25 +0100, Christian Ehrha
On Wed, 2008-02-06 at 13:07 +0100, Guillaume Thouvenin wrote:
> On Wed, 06 Feb 2008 10:52:54 +0200
> Izik Eidus <[EMAIL PROTECTED]> wrote:
> >
> > i am not expert for the emulator area, but as far as i remember:
> >
> > virtual 8086 have some checks related to segments (the big mode
> > problem)
On Wed, 06 Feb 2008 10:52:54 +0200
Izik Eidus <[EMAIL PROTECTED]> wrote:
>
> i am not expert for the emulator area, but as far as i remember:
>
> virtual 8086 have some checks related to segments (the big mode
> problem), it mean that for some addresses it wont be able to execute
> anything, you
hi Jerone,
I think this is good for debugging to find unsupported hardware, but it should
not be enabled by default (you could get a printf storm if a guest workload
does stupid things). Maybe qemu has some debug/verbose options you can use.
And additionally it would be useful for the dcr_write p
Whilst working on getting a VM to initialize in to IA32e mode I found
this issue. set_cr0 relies on comparing the old cr0 to the new one to
work correctly.
Whilst this fix gets me a little closer I still fail to run due to an
invalid VMX state. Has anybody else ever tried to set up a VM to j
On Wed, 2008-02-06 at 08:33 +0100, Guillaume Thouvenin wrote:
> Hello,
>
> I read on the kvmwiki/TODO that there is a work in progress for
> extending x86 emulator to support more instructions in real mode and for
> changing the execution loop to call the emulator for real mode.
>
> As I'm
12 matches
Mail list logo
