Linus, please pull from the repo and branch
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
The patches fix a memory leak, ioperm() failures on unrelated processes
on the host, a locking issue, and a host crash when host userspace changes
the memory map.
Diffstat, shortlog
Hello Everyone,
I was trying to install Ubuntu on a VM and tried to boot the
installation directly from the ISO image, doing that KVM crashes
giving this output:
--
exception 0 (0)
rax 0053 rbx 0080 rcx 0031 rdx
000
>Is this caused by KVM not supporting real mode on Intel hosts, or is it caused
>by some other reason?
Yes, it is correct. Ubuntu 7.04/7.10 won't work anytime soon.
There are few workarounds:
1. use text-mode bootloader
2. use special patches for KVM (not included in mainline, but in Alexander
Solution #2 patches:
>Any pointers to where I can get these patches.
http://packages.opensuse-community.org/
http://download.opensuse.org/repositories/home:/algraf/openSUSE_10.3/src/
Get the src.RPM, and extract patches from it.
Not sure about solution #3 patches.
---
On Tue, Mar 25, 2008 at 11:58 AM, Alexey Eremenko
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> >Is this caused by KVM not supporting real mode on Intel hosts, or is it
> caused by some other reason?
>
> Yes, it is correct. Ubuntu 7.04/7.10 won't work anytime soon.
>
> There are few workarounds:
> 1. use
On Tue, 2008-03-25 at 12:35 +0200, Mohammed Gamal wrote:
> On Tue, Mar 25, 2008 at 11:58 AM, Alexey Eremenko
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > >Is this caused by KVM not supporting real mode on Intel hosts, or is it
> > caused by some other reason?
> >
> > Yes, it is correct. Ubunt
this is the shrinker patch with all comments applied beside adding aging
mechanism
it look like the aging mechanism is not really needed and therefor for now it
isn't
implemented.
>From 8503a57ae88ba819e4eac6371172772c98b485f0 Mon Sep 17 00:00:00 2001
From: Izik Eidus <[EMAIL PROTECTED]>
Date: T
Вeдeниe кассoвых oпeраций. Правила, нарушeния, кoнтрoль.
Сeминар прoйдёт 15 апрeля 2008, г. Мoсква
В прoграммe:
1. oбщиe правила вeдeния кассoвых oпeраций в РФ. Нoрмативная база.
2. oрганизация наличных расчeтoв на прeдприятии
3. oфoрмлeниe кассoвых дoкумeнтoв
4. Дeнeжная наличнoсть в кассe пр
Izik Eidus wrote:
> this is the shrinker patch with all comments applied beside adding aging
> mechanism
> it look like the aging mechanism is not really needed and therefor for now it
> isn't
> implemented.
>
> From 8503a57ae88ba819e4eac6371172772c98b485f0 Mon Sep 17 00:00:00 2001
> From: Izik E
Anthony Liguori wrote:
> Part of the feedback we received from Fabrice about the KVM patches for QEMU
> is that we should create a separate device for the in-kernel APIC to avoid
> having lots of if (kvm_enabled()) within the APIC code that were difficult to
> understand why there were needed.
>
>
On Tue, Mar 25, 2008 at 1:23 PM, Dor Laor <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2008-03-25 at 12:35 +0200, Mohammed Gamal wrote:
> > On Tue, Mar 25, 2008 at 11:58 AM, Alexey Eremenko
> > <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >
> > >
> > > >Is this caused by KVM not supporting real m
Jerone Young wrote:
> Fix big bug found by Anthony, as well formating comments that he commented on.
> Bombs away!
>
> This set of patches enables the following:
> -Device tree Support
> - Add libfdt to kvm-userspace
> - Add bamboo device tree to qemu source
> Thanks Dor. I was also facing another issue. I installed MINIX and
> GNU/HURD on other VMs, and when I try to boot from their harddisk
> images I get a similar message (but with a different exception number)
That's probably another problem.
I didn't see it in the
http://kvm.qumranet.com/kvmwiki
Avi Kivity wrote:
> Izik Eidus wrote:
>> this is the shrinker patch with all comments applied beside adding
>> aging mechanism
>> it look like the aging mechanism is not really needed and therefor for
>> now it isn't
>> implemented.
>>
>> From 8503a57ae88ba819e4eac6371172772c98b485f0 Mon Sep 17 00:
Avi was concerned that this would cause problems with migration. I
haven't specifically tested it yet, but it seems there will be no
problems introduced by this change: the IO thread will stop all vcpu's
in the same way the vcpu0 thread did before.
QEMU/KVM: separate thread for IO handling
Move
Hello,
is it possible to connect to the virtual monitor/keyboard/mouse of
an already running kvm instance using a socket when started without an
x-window system and _not_ using vnc? I have something in the back of my
head using libvirt but I am unable to find it.
Thomas
--
Marcelo Tosatti wrote:
> Avi was concerned that this would cause problems with migration. I
> haven't specifically tested it yet, but it seems there will be no
> problems introduced by this change: the IO thread will stop all vcpu's
> in the same way the vcpu0 thread did before.
>
I believe thi
Am Mittwoch, 12. März 2008 schrieben Sie:
>
> The patch titled
> kvm: provide kvm.h for all architecture: fixes headers_install
> has been added to the -mm tree. Its filename is
> kvm-provide-kvmh-for-all-architecture-fixes-headers_install.patch
>
Hello Andrew,
is there a chance to s
Am Freitag, den 21.03.2008, 11:29 -0700 schrieb Dave Hansen:
> What you've done with dup_mm() is probably the brute-force way that I
> would have done it had I just been trying to make a proof of concept or
> something. I'm worried that there are a bunch of corner cases that
> haven't been conside
Am Montag, 24. März 2008 schrieb Avi Kivity:
> Christian Borntraeger wrote:
> > Am Freitag, 21. März 2008 schrieb Anthony Liguori:
> >
> >> This patch breaks QEMU build when doing a 'make sync'. When you do a
> >> top-level ./configure, libkvm is built with kerneldir pointing to
> >> kvm-user
Christian Borntraeger wrote:
> Am Montag, 24. März 2008 schrieb Avi Kivity:
>
>> Christian Borntraeger wrote:
>>
>>> Am Freitag, 21. März 2008 schrieb Anthony Liguori:
>>>
>>>
This patch breaks QEMU build when doing a 'make sync'. When you do a
top-level ./configure, l
It does work with gcc 4.2.3 . Though no idea if gcc-4.3 & 4.4 would
workout. Though they should. I'll need to to compile them and give them
a try.
On Mon, 2008-03-24 at 20:42 +0100, Segher Boessenkool wrote:
> > This patch adds -Werror to CFLAGS for compilation of libkvm. This
> > should stop com
We'd like to invite all of you to attend the second annual KVM Forum.
Following the success of the last year's event, we'd like to keep the
format similar. The purpose of the forum is to bring together
developers, testers and other technical individuals from within the
community to discuss the stat
Hollis Blanchard wrote:
> On Fri, 2008-03-21 at 13:02 +0200, Avi Kivity wrote:
>
>> Other than that, and the few minor comments that popped up, this
>> (very
>> nice) patchset will be very easy to merge. IIRC you mentioned it is
>> possible for me to get an s390 account; this will be very use
Jerone Young wrote:
> It does work with gcc 4.2.3 . Though no idea if gcc-4.3 & 4.4 would
> workout. Though they should. I'll need to to compile them and give them
> a try.
>
While I'm a fan of -Werror, I have to agree with Anthony it can cause no
end of pain to users if they have a slightly d
From: Martin Schwidefsky <[EMAIL PROTECTED]>
From: Carsten Otte <[EMAIL PROTECTED]>
The SIE instruction on s390 uses the 2nd half of the page table page to
virtualize the storage keys of a guest. This patch offers the s390_enable_sie
function, which reorganizes the page tables of a single-threaded
Many thanks for the review feedback we have received so far,
and many thanks to Andrew for reviewing our common code memory
management changes. I do greatly appreciate that :-).
All important parts have been reviewed, all review feedback has been
integrated in the code. Therefore we would like to
From: Heiko Carstens <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch changes the s390 memory management defintions to use the pgste field
for dirty and reference bit tracking of host and guest code. Usually on s390,
dirty and referenced are tracked in storage keys,
From: Christian Borntraeger <[EMAIL PROTECTED]>
The address 0x11b8 is used by z/VM for pfault and diag 250 I/O to
provide a 64 bit extint parameter. virtio uses the same address, so
its time to update the lowcore structure.
Acked-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Christian
From: Christian Borntraeger <[EMAIL PROTECTED]>
drivers/s390/sysinfo.c uses the store system information intruction to query
the system about information of the machine, the LPAR and additional
hypervisors. KVM has to implement the host part for this instruction.
To avoid code duplication, this
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
From: Heiko Carstens <[EMAIL PROTECTED]>
This patch contains the port of Qumranet's kvm kernel module to IBM zSeries
(aka s390x, mainframe) architecture. It uses the mainframe's virtualization
instruction SIE t
From: Carsten Otte <[EMAIL PROTECTED]>
This patch contains the s390 interrupt subsystem (similar to in kernel apic)
including timer interrupts (similar to in-kernel-pit) and enabled wait
(similar to in kernel hlt).
In order to achieve that, this patch also introduces intercept handling
for instru
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch introduces in-kernel handling of some intercepts for privileged
instructions:
handle_set_prefix()sets the prefix register of the local cpu
handle_store_prefix() stores the content of the
From: Carsten Otte <[EMAIL PROTECTED]>
This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's
user interface that are unique to s390 architecture.
Signed-off-by: Carsten Otte <[EMAIL PROTECTED]>
---
Documentation/s390/kvm.txt | 125 +++
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch introduces in-kernel handling of _some_ sigp interprocessor
signals (similar to ipi).
kvm_s390_handle_sigp() decodes the sigp instruction and calls individual
handlers depending on the operation reque
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This path introduces handling of sie intercepts in three flavors: Intercepts
are either handled completely in-kernel by kvm_handle_sie_intercept(),
or passed to userspace with corresponding data in struct kvm_ru
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch introduces interpretation of some diagnose instruction intercepts.
Diagnose is our classic architected way of doing a hypercall. This patch
features the following diagnose codes:
- vm storage size, th
From: Carsten Otte <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch adds the virtualization submenu and the kvm option to the kernel
config. It also defines HAVE_KVM for 64bit kernels.
Acked-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Christian Borntrae
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch implements kvm guest kernel support for paravirtualized devices
and contains two parts:
o a basic virtio stub using virtio_ring and external interrupts and hypercalls
o full hypercall implementation in kvm_para.h
Currently we dont have PC
From: Christian Borntraeger <[EMAIL PROTECTED]>
From: Carsten Otte <[EMAIL PROTECTED]>
This patch adds functionality to detect if the kernel runs under the KVM
hypervisor. A macro MACHINE_IS_KVM is exported for device drivers. This
allows drivers to skip device detection if the systems runs non-vi
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch adds an entry for kvm on s390 to the MAINTAINERS file :-). We intend
to push all patches regarding this via Avi's kvm.git.
Signed-off-by: Christian Borntraeger <[EMAIL PROTECTED]>
Signed-off-by: Carsten Otte <[EMAIL PROTECTED]>
---
MAINT
Thomas Glanzmann wrote:
> Hello,
> is it possible to connect to the virtual monitor/keyboard/mouse of
> an already running kvm instance using a socket when started without an
> x-window system and _not_ using vnc? I have something in the back of my
> head using libvirt but I am unable to find it.
On Tue, 2008-03-25 at 18:56 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > On Fri, 2008-03-21 at 13:02 +0200, Avi Kivity wrote:
> >
> >> Other than that, and the few minor comments that popped up, this
> >> (very
> >> nice) patchset will be very easy to merge. IIRC you mentioned it is
So it's actually really easy using cross compiler to build everything. I
use my laptop and then copy over to our nfs root that our boards use.
Here are some instructions I wrote up for someone earlier. Excuse the
parts but it is enough to get you going:
On Tue, 2008-03-25 at 18:56 +0200,
* Sorry was going for paste, and somehow hit send.
So it's actually really easy using cross compiler to build everything. I
use my laptop and then copy over to our nfs root that our boards use.
Here are some instructions I wrote up for someone earlier. Excuse the
parts but it is enough to get y
Yeah. This could "potentially" cause hell for users (non developers)
down the road. I'm just going to keep this patch in my queue for myself,
so no one will complain about warnings from my patches anymore.
I think having a --developer flag to configure could work, but we would
then need separate
On Tue, 25 Mar 2008 16:31:46 +0100
Christian Borntraeger <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 12. M__rz 2008 schrieben Sie:
> >
> > The patch titled
> > kvm: provide kvm.h for all architecture: fixes headers_install
> > has been added to the -mm tree. Its filename is
> > kvm-provi
I was getting some kvm userspace crashes trying to run a Windows guest.
So, I decided to try a recent kernel (2.6.25-rc6-00333-ga4083c9) with
the kvm kernel code that shipped with that kernel.
I've had some lockups doing similar things over the last month or two,
but figured it was something real
Hello,
Here there is a series of 20 patches that lays the foundations for
using dma_ops in i386 in the very same way x86_64, as well as many other
architectures already do.
The functions themselves for i386 are placed in a pci-base_32.c, but just
a few among them are actually implemented. Most we
take it off the x86_64 specific header
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h| 54 ++
include/asm-x86/dma-mapping_64.h | 49 --
2 files changed, 54 insertions(+), 49 deletions(-
the old i386 implementation is moved to pci-base_32.c
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c| 19 +++
include/asm-x86/dma-mapping.h|8 +++-
include/asm-x86/dma-mapping_32.h | 20
include/asm-x86/d
i386 base does not need it, so it gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 10 ++
include/asm-x86/dma-mapping_32.h |7 ---
include/asm-x86/dma-mapping_64.h |8 ---
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 12
include/asm-x86/dma-mapping_32.h |6 --
include/asm-x86/dma-mapping_64.h | 11 ---
4 files changed, 1
That's already the name of the game for x86_64. For i386,
we add a pci-base_32.c, that will hold the default operations.
The function call itself goes through dma-mapping.h , the common
header
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/Makefile |1 +
arch/x86
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 11 +++
include/asm-x86/dma-mapping_32.h |7 ---
include/asm-x86/dma-mapping_64.h | 11 ---
4 files changed, 1
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h|9 +
include/asm-x86/dma-mapping_32.h |8
include/asm-x86/dma-mapping_64.h |8
4 files changed, 10 in
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 14 ++
include/asm-x86/dma-mapping_32.h |8
include/asm-x86/dma-mapping_64.h | 12
4 files chang
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 11 +++
include/asm-x86/dma-mapping_32.h |7 ---
include/asm-x86/dma-mapping_64.h | 12
4 files changed,
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h|9 +
include/asm-x86/dma-mapping_32.h |6 --
include/asm-x86/dma-mapping_64.h | 11 ---
4 files changed, 10 i
they are the same between architectures (except for the fact
that x86_64 has duplicate code)
move them to dma-mapping.h
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h| 10 ++
include/asm-x86/dma-mapping_32.h |9 -
include/asm-x86/dma-
Do it instead of using the conservative approach we're currently
doing. This is the way x86_64 does, and this patch makes this piece
of code the same between them, ready to be integrated
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping_32.h |2 +-
1 files chang
i386 gets an empty function
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|1 +
include/asm-x86/dma-mapping.h| 11 +++
include/asm-x86/dma-mapping_32.h |7 ---
include/asm-x86/dma-mapping_64.h | 12
4 files changed,
all the code that is left is ready to be merged as-is
in dma-mapping.h
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h| 19 +--
include/asm-x86/dma-mapping_32.h | 23 ---
include/asm-x86/dma-mapping_64.h | 17 ---
they are the same in both architectures.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h|6 ++
include/asm-x86/dma-mapping_32.h |7 ---
include/asm-x86/dma-mapping_64.h |7 ---
3 files changed, 6 insertions(+), 14 deletions(-)
diff -
They are similar enough to do this move.
the macro version is ugly, and we use inline functions instead
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h| 14 ++
include/asm-x86/dma-mapping_32.h | 15 ---
include/asm-x86/dma-mapping
This is the way x86_64 does, so this make them equal. They have
to be extern now in the header, and the extern definition is moved to
the common dma-mapping.h header
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-dma_32.c | 33 +
inc
We provide a map_error function in pci-base_32.c to make
sure i386 keeps with the same behaviour it used to.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-base_32.c|7 +++
include/asm-x86/dma-mapping.h|8
include/asm-x86/dma-mapping_32.h |
It's initially 0, since we don't expect any DMA there.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel/pci-dma_32.c |4
include/asm-x86/dma-mapping.h|2 ++
include/asm-x86/dma-mapping_64.h |1 -
3 files changed, 6 insertions(+), 1 deletions(-)
diff -
define it conditionally to i386
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
include/asm-x86/dma-mapping.h| 14 ++
include/asm-x86/dma-mapping_32.h | 12
2 files changed, 14 insertions(+), 12 deletions(-)
diff --git a/include/asm-x86/dma-mapping.h b/inclu
virtio is currently pretty sloppy about accessing guest memory directly. This
is problematic both because phys_ram_base + PA is not only valid but also
because it requires the host and guest both be of the same endianness.
This patch converts virtio to use the QEMU st/ld functions to manipulate t
Avi Kivity wrote:
>
> Please separate the code movement and changes into separate patches.
I'm not sure there's a great way to do this that preserves bisectability
and results in meaningful history. I could leave the #ifdef's in
i8254-kvm.c and then have a second patch that removes them. That
I'm trying to get a Fedora 9 Beta guest to use the virtio block device.
I've included virtio_blk and virtio_pci in the initrd on the guest and when
booting virtio_blk detects vda1 and vda2 correctly but when the system
tries to find the volume groups it doesn't find any. Is there something
spec
On Tue, Mar 25, 2008 at 04:58:06PM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >Avi was concerned that this would cause problems with migration. I
> >haven't specifically tested it yet, but it seems there will be no
> >problems introduced by this change: the IO thread will stop all vcpu's
>
From: Randy Dunlap <[EMAIL PROTECTED]>
Prevent failed randconfig builds with KVM_CLOCK being enabled
on Voyager or VISWS.
build-rand9.out: Using /local/linsrc/next-20080325 as source for kernel
build-rand9.out: from
/local/linsrc/next-20080325/include/linux/irqflags.h:46,
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
: :
: Эффeктивнoe yпpавлeниe финансами:
: :
:~:~:~:~:
I've been sifting through docs and code to try to figure out if I can
actually expose this Sangoma card to a virtual container running Asterisk.
I've found reference to pci_add, but have yet to figure out what it takes to
build my kvm with pci_add function.
Is it possible to do what I am attempti
Hi All,
This is today's KVM test result against kvm.git
680615e31ee986b6a5d64783c536ed9fae67c010 and kvm-userspace.git
52be1a18bb7429506acc95c7fdcf4f87ded7a92c.
Issue list
1. Booting four guests likely fails
https://sourceforge.net/tracker/?fun
77 matches
Mail list logo
