Rusty Russell wrote:
On Friday 21 March 2008 19:15:47 Christian Borntraeger wrote:
Am Freitag, 21. März 2008 schrieb Rusty Russell:
Hmm, panic on device_register fail, but -ENOMEM on add_shared_memory
fail? My theory was that since this is boot time, panic() is the right
thing.
Good spot,
Hello,
I'm using libvirt 0.4.1 and kvm version 63. I try to boot using pxe. I noticed
that qemu uses the ne2k_pci network card as default while kvm has a rtl8139
card. And here I start to get strange results:
With qemu I can use the default network card [1] or the rtl8139 card [2] to
boot
Hi all,
Current 'make clean' deletes config.mak files so
that we have to ./configure again after doing that.
This behavior is different from that of standard
'make clean'.
This patch introduces 'make distclean' to delete
config.mak files instead of 'make clean', following
a standard manner of
Hi all,
Current kvm allows only one VM to use HPET. Is
there a plan to implement a functionality to
allow multiple VMs to use HPET? If so, how
about the status of that?
And I would like to ask right and wrong to
implement the functionality in terms of need
and efficiency (scalability and time
Hey,
I just tried the latest kvm head (kernel+userspace). But my fresh W2k3
Installation failed with a segfault.
Facts:
CPU:
model name : Intel(R) Xeon(R) CPU X3210 @ 2.13GHz
MemTotal: 8196292 kB
Host:
Fedora release 8 (Werewolf) (up to date)
Linux fry.localdomain
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: 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]
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: Martin Schwidefsky [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 process to
reserve space in the page
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
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_run
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
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 to run
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, that
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]
---
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 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 Borntraeger
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
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 PCI
This patch series introduces a backend for kvm to run on IBM System z
machines (aka s390x) that uses the mainframe's sie virtualization
capability. Many thanks for the review feedback we have received so far,
I do greatly appreciate it!
The first submission didn't draw much attention of elder vm
On Fri, Mar 21, 2008 at 03:33:29PM +0100, Carsten Otte wrote:
Am Freitag, den 21.03.2008, 15:06 +0100 schrieb Heiko Carstens:
Just introduce something like MACHINE_FLAG_KVM. The rest can be converted
later. Unless you're bored and feel like fiddling around with assembly code
:)
I've done
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 considered.
What if someone else is poking around with ptrace or
Achieve incredible, unbelievably climaxes for her and you like never before.
http://www.Hanoestly.com/
Get paid starring in our porno film
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R)
Ryota OZAKI wrote:
Hi all,
Current kvm allows only one VM to use HPET. Is
there a plan to implement a functionality to
allow multiple VMs to use HPET? If so, how
about the status of that?
If you use the dyntick clock option (the default, IIRC), and a newer
host kernel, then the kernel
Hi,
I'm trying to get the paravirtualized block device going but get in trouble
with LVM. Both host and guest a very recent snapshot of Fedora 9 rawhide.
The guest is a pristine F9 install with / mounted as /dev/VolGroup00/LogVol00.
When I boot with the command:
/usr/bin/qemu-kvm -m 512 -drive
Dennis Jacobfeuerborn wrote:
Hi,
I'm trying to get the paravirtualized block device going but get in trouble
with LVM. Both host and guest a very recent snapshot of Fedora 9 rawhide.
The guest is a pristine F9 install with / mounted as /dev/VolGroup00/LogVol00.
When I boot with the
Avi Kivity wrote:
And I would like to ask right and wrong to
implement the functionality in terms of need
and efficiency (scalability and time accuracy).
I think that for newer kernels we already have the desired accuracy.
We're not always good at exploiting that accuracy; hence the
27 matches
Mail list logo
