>> > Now that more platforms are joining the KVM wagon, we should define
a
>> > common bus. PCI was a overkill anyway - its irq are shared and we
don't
>> > have to use its io/mmio areas.
>> > Do you guys have something to start with?
>> We do have something basic, our vdev bus. The bad thing is, i
On Thu, Jun 07, 2007 at 08:09:48AM +0300, Avi Kivity wrote:
> Some extra logic is needed on i386 with >= 4GB. Current code will
> wraparound since gfn_t is 32-bits long, but casting it to 64-bits is not
> the answer since the processor will truncate it back to 32 bits (the
> return value is eventu
Kamble, Nitin A wrote:
> Hi Peter,
> I see SuSE has taken a fail back path to the code so the
> releases after 10.3 detects the presence of VMM and avoid the big real
> mode path.
> I think people from SuSE should be able to confirm it better for you.
Big real mode is evil in the extreme n
Hi Peter,
I see SuSE has taken a fail back path to the code so the
releases after 10.3 detects the presence of VMM and avoid the big real
mode path.
I think people from SuSE should be able to confirm it better for you.
Thanks & Regards,
Nitin
Linux Open Source Technology Center
Intel C
Kamble, Nitin A wrote:
> On Thu, 2007-06-07 at 20:52 -0700, H. Peter Anvin wrote:
>> Kamble, Nitin A wrote:
>> > Hi Avi,
>> >I am in the middle of implementing the big real support in the KVM
>> > now. I am trying to boot SuseLinux 10.1 on KVM, which uses extensive big
>> > real mode code in th
On Thu, 2007-06-07 at 20:52 -0700, H. Peter Anvin wrote:
> Kamble, Nitin A wrote:
> > Hi Avi,
> >I am in the middle of implementing the big real support in the
> KVM
> > now. I am trying to boot SuseLinux 10.1 on KVM, which uses extensive
> big
> > real mode code in the boot loader.
>
> Ye go
I remember this bug before and I thought I figured it out by using the
bootloader on the image instead of using the -kernel and -initrd
commandline options to qemu.
However, the guest just stopping has come back. For some reason using
the latest kvm with 2.6.21 both in fedora 7 (kvm-25) and debian
1: I/F between user/kernel
a: Similar with the question in kernel side, current I/F only
support an IRQ set notification, we need clear notification too.
Especially when guest use IMR to mask the interrupt.
b: following code read irq from PIC which means IRR ->ISR, but
kernel may
