On Sat, 12 Jan 2008 14:34:12 -0600
Anthony Liguori <[EMAIL PROTECTED]> wrote:
> What version of gfxboot does openSUSE 10.3 use? gfxboot was broken for
> KVM until very recently. This is probably what you're seeing.
I don't know what version it is but do you talk about the bug due to
the wron
> kvm_run->mmio.is_bigendian = vcpu->arch.some_register &
>From your example code, I can know is_bigendian indicate whether guest
is in bigendian mode when accessing MMIO.
Qemu is responsible for handling MMIO emulation, Qemus always assume it
is running on littleendian mode.
So if guest
>While we tried to make debugging inside the guest work, this
>was never really tested, so it's likely broken. I'll try to
>look at what it will take to make it work; I don't think there's
>much needed.
That sounds encouraging -- I had imagined there might be some
"impossibility factor" in sharin
Anthony Liguori wrote:
> Izik Eidus wrote:
>> Anthony Liguori wrote:
>>> Avi Kivity wrote:
Andi Kleen wrote:
> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
> the kernel outputs anything:
>
>
Yes, I think -kernel is broken.
>
On Sun, 2008-01-13 at 17:24 +0100, Andrea Arcangeli wrote:
> Hello,
>
> This patch is last version of a basic implementation of the mmu
> notifiers.
>
> In short when the linux VM decides to free a page, it will unmap it
> from the linux pagetables. However when a page is mapped not just by
> th
Izik Eidus wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Andi Kleen wrote:
>>>
When I try my 64bit kernel with -kernel ... on kvm-59 I get before
the kernel outputs anything:
>>>
>>> Yes, I think -kernel is broken.
>>>
>>
>> If you are using a guest with m
Hi Andi,
Please give us the _complete_ command line: how do you launch
Qemu/KVM, and which Host and Guest OSes are?
--
-Alexey Eremenko "Technologov"
-
Check out the new SourceForge.net Marketplace.
It's the best place to b
... and eventually it oopsed:
Unable to handle kernel NULL pointer dereference at RIP:
[] :kvm:x86_emulate_memop+0x2c62/0x4527
PGD 11c8ae067 PUD 0
Oops: 0002 [1] SMP
CPU 0
Modules linked in: xfrm_user xfrm4_tunnel af_key xfs kvm_intel kvm usblp deflate
zlib_deflate zlib_inf
FWIW it seems things are broken even without -kernel in -59 too. If I try
to boot an existing image with just -hda ... the VGA screen just stays
black while the process runs at 99% CPU. Again with -49 it works fine.
-Andi
-
Avi Kivity wrote:
> Andi Kleen wrote:
>>> Are you using the modules that come with kvm or from an upstream
>>> kernel? (which?)
>>>
>>
>> kvm from 2.6.24-rc5-gitXXX upstream kernels (see my original mail)
>
> This points the finger at the memory allocation backward compatibility
> logic.
Andi Kleen wrote:
>> Are you using the modules that come with kvm or from an upstream kernel?
>> (which?)
>>
>
> kvm from 2.6.24-rc5-gitXXX upstream kernels (see my original mail)
>
This points the finger at the memory allocation backward compatibility
logic.
Izik, can you take a look
> Are you using the modules that come with kvm or from an upstream kernel?
> (which?)
kvm from 2.6.24-rc5-gitXXX upstream kernels (see my original mail)
-Andi
-
Check out the new SourceForge.net Marketplace.
It's the best
Andi Kleen wrote:
>> If you are using a guest with more than 3.75GB or so. The load_kernel
>> function uses phys_ram_base + addr and that assumption is violated in
>> KVM with guests > ~3.75GB of memory. We either need to allocate memory
>> for the hole and never touch it or change load_kernel
> If you are using a guest with more than 3.75GB or so. The load_kernel
> function uses phys_ram_base + addr and that assumption is violated in
> KVM with guests > ~3.75GB of memory. We either need to allocate memory
> for the hole and never touch it or change load_kernel to use
> cpu_physica
On Sun, Jan 13, 2008 at 01:37:11PM +0200, Uri Lublin wrote:
> Try to build the kernel modules too (remove '--with-patched-kernel' from
> ./configure arguments ):
> ./configure --prefix=/opt/kvm --qemu-cc=/usr/bin/gcc-3.4 ; make -C
> kernel LINUX= sync; make
> You will have to rmmod current kvm mo
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Andi Kleen wrote:
>>
>>> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
>>> the kernel outputs anything:
>>>
>>>
>>
>> Yes, I think -kernel is broken.
>>
>
> If you are using a guest with more than 3.75GB or so. The load
Izik Eidus wrote:
> Avi Kivity wrote:
>
>> Andi Kleen wrote:
>>
>>> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
>>> the kernel outputs anything:
>>>
>>>
>>>
>> Yes, I think -kernel is broken.
>>
>> Izik?
>>
>
> wasnt it was fixed with the qemu_ram_alloc
Avi Kivity wrote:
> Andi Kleen wrote:
>
>> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
>> the kernel outputs anything:
>>
>>
>>
>
> Yes, I think -kernel is broken.
>
If you are using a guest with more than 3.75GB or so. The load_kernel
function uses phys_ram_
Avi Kivity wrote:
> Andi Kleen wrote:
>> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
>> the kernel outputs anything:
>>
>>
>
> Yes, I think -kernel is broken.
>
> Izik?
wasnt it was fixed with the qemu_ram_alloc(0xa) patch ???
(i remembred someone sent patch to fix it
Andi Kleen wrote:
> When I try my 64bit kernel with -kernel ... on kvm-59 I get before
> the kernel outputs anything:
>
>
Yes, I think -kernel is broken.
Izik?
--
error compiling committee.c: too many arguments to function
---
Andi Kleen wrote:
> I needed the following patch to make kvm-59 compile on SUSE 10.2. Yes it's
> a bug in the standard includes.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
Check
When I try my 64bit kernel with -kernel ... on kvm-59 I get before
the kernel outputs anything:
exception 13 (0)
rax rbx rcx rdx
0600
rsi rdi rsp rbp
r8 00
Hello,
This patch is last version of a basic implementation of the mmu
notifiers.
In short when the linux VM decides to free a page, it will unmap it
from the linux pagetables. However when a page is mapped not just by
the regular linux ptes, but also from the shadow pagetables, it's
currently un
I needed the following patch to make kvm-59 compile on SUSE 10.2. Yes it's
a bug in the standard includes.
-Andi
diff -u kvm-59/qemu/usb-linux.c-o kvm-59/qemu/usb-linux.c
--- kvm-59/qemu/usb-linux.c-o 2008-01-01 10:20:24.0 +0100
+++ kvm-59/qemu/usb-linux.c 2008-01-13 17:16:46.0
Marcelo Tosatti <[EMAIL PROTECTED]> writes:
> On Sun, Jan 13, 2008 at 12:19:20PM +0100, Anders wrote:
[...]
>> How do you get that high consumption? What combination of clocks/hz on
>> host/guest are you using?
>
> CONFIG_HZ=250
Okay, with nohz=off (in the guest) I also see some higher load. I
Andrea Arcangeli wrote:
> Hi everyone,
>
> So far KVM swapping has been a limited feature. Depending on the
> workloads huge chunks of the anonymous memory simulating the guest
> physical memory could get pinned and unswappable for extended periods
> of time. Whenever a spte mapps a host physical p
On Sun, Jan 13, 2008 at 12:19:20PM +0100, Anders wrote:
> Marcelo Tosatti <[EMAIL PROTECTED]> writes:
>
> > This reduces idle guest CPU consumption from 14% to 8% on 4-way KVM
> > guest.
>
> How do you get that high consumption? What combination of clocks/hz on
> host/guest are you using?
CONFIG
Avi Kivity wrote:
> Guido Guenther wrote:
>> On Tue, Jan 08, 2008 at 10:50:00AM +0200, Avi Kivity wrote:
>>
>>> Yes, you can press the VM's power button (system_powerdown in the
>>> monitor) and it will invoke the OS shutdown sequence.
>>>
>>> Only worked on Linux in my testing though.
>>>
Hi everyone,
So far KVM swapping has been a limited feature. Depending on the
workloads huge chunks of the anonymous memory simulating the guest
physical memory could get pinned and unswappable for extended periods
of time. Whenever a spte mapps a host physical page, KVM has to pin
the page to pre
Carlo Marcelo Arenas Belon wrote:
> On Sat, Jan 12, 2008 at 06:07:19PM +, Antoine Martin wrote:
If that doesn't work, maybe you can upload an image
for me to debug.
>>> http://194.145.196.85/kvm/vmlinuz-2.6.24-rc7.bz2
>>>
>> Any luck? Any other ideas for me to try?
>
> see if the pr
Robin Holt wrote:
> On Sat, Jan 12, 2008 at 09:51:56PM +0200, Avi Kivity wrote:
>
>> Christoph Lameter wrote:
>>
>>> On Thu, 10 Jan 2008, Avi Kivity wrote:
>>>
>>>
>>>
Actually sharing memory is possible even without this patch; one simply
mmap()s a file into the address
Marcelo Tosatti wrote:
> The boot TSC sync check is failing on recent Linux SMP guests on TSC
> stable hosts.
>
>
What about tsc unstable hosts? If your patch convinces the guest its
tsc is table, while the host tsc is not, then it may cause confusion
later on.
> Following patch attempts to
On Sat, Jan 12, 2008 at 09:51:56PM +0200, Avi Kivity wrote:
> Christoph Lameter wrote:
>> On Thu, 10 Jan 2008, Avi Kivity wrote:
>>
>>
>>> Actually sharing memory is possible even without this patch; one simply
>>> mmap()s a file into the address space of both guests. Or are you
>>> referring
Christian Ehrhardt wrote:
> This includes the comments from Avi to "[PATCH] portability: add top level
> config-$arch files v2". Putting the arch dependencies into if's saves us 4
> config-$arch files which are not essential to fix the current issue.
> Since this is copy&paste from Avis response to
Christoph Hellwig wrote:
> Current kvm userspace git configured with ./configure --prefix=/opt/kvm
> --with-patched-kernel --qemu-cc=/usr/bin/gcc-3.4 gives:
>
> /usr/bin/gcc-3.4 -L /home/hch/work/kvm-userspace/qemu/../libkvm -g -o
> qemu-system-x86_64 vl.o osdep.o monitor.o pci.o loader.o isa_m
Marcelo Tosatti <[EMAIL PROTECTED]> writes:
> This reduces idle guest CPU consumption from 14% to 8% on 4-way KVM
> guest.
How do you get that high consumption? What combination of clocks/hz on
host/guest are you using?
I am cursious, since my idle KVM process is at less than 1%.
Regards,
Ande
Marcelo Tosatti wrote:
> The PIIX4 ACPI controller prior to revision 0x3 contains a bug where
> reading of the timer port is unreliable, so the kernel reads it three
> times for consistency check.
>
> QEMU does not suffer from that problem :)
>
> The datasheet for PIIX4, PIIX4E, and PIIX4M is the s
Hollis Blanchard wrote:
> On Thu, 2008-01-10 at 17:28 +0200, Avi Kivity wrote:
>
>> I'll apply that patch (with a #ifdef CONFIG_PPC so other archs don't
>> use it by mistake).
>>
>
> I don't think that's the right ifdef. For example, I believe IA64 can
> run in BE mode and so will have the
Guido Guenther wrote:
> On Tue, Jan 08, 2008 at 10:50:00AM +0200, Avi Kivity wrote:
>
>> Yes, you can press the VM's power button (system_powerdown in the
>> monitor) and it will invoke the OS shutdown sequence.
>>
>> Only worked on Linux in my testing though.
>>
> It works for me _when_ I
Avi Kivity wrote:
> Christian Ehrhardt wrote:
>> Subject: [PATCH] fill kvm_callback with arch specific
>> dcr_read/dcr_write callbacks v2
>> From: Christian Ehrhardt <[EMAIL PROTECTED]>
>>
>> This Patch adds the callback assignment and handlers for
>> powerpc_dcr_read
>> and ppc_dcr_write which a
Christian Ehrhardt wrote:
> Subject: [PATCH] fill kvm_callback with arch specific dcr_read/dcr_write
> callbacks v2
> From: Christian Ehrhardt <[EMAIL PROTECTED]>
>
> This Patch adds the callback assignment and handlers for powerpc_dcr_read
> and ppc_dcr_write which are called from libkvm.
> This
41 matches
Mail list logo
