Hi all,
Just finished my prototype of inter-guest virtio, using networking as an
example. Each guest mmaps the other's address space and uses a FIFO for
notifications.
There are two issues with this approach. The first is that neither guest
can change its mappings. See patch 1. The
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and DMA memory
mappings created by map_zeroed_pages.
Signed-off-by: Rusty Russell [EMAIL PROTECTED]
---
Documentation/lguest/lguest.c | 59 --
1
We currently keep Guest memory pointer and size in globals. We move
this into a structure and explicitly hand that to to_guest_phys() and
from_guest_phys() so we can deal with other Guests' memory.
Signed-off-by: Rusty Russell [EMAIL PROTECTED]
---
Documentation/lguest/lguest.c | 89
To deal with other Guest's virtqueue, we need to separate out the
parts of the structure which deal with the actual virtqueue from
configuration information and the device. Then we can change the
virtqueue descriptor handling functions to take that smaller
structure.
Signed-off-by: Rusty Russell
Avi Kivity wrote:
Zhang, Xiantao wrote:
Hi, Avi
Currently, make sync in userspace only syncs x86-specific heads from
kernel source due to hard-coded in Makefile.
Do you have plan to provide cross-arch support for that?
No plans. I'll apply patches though. But don't you need kernel
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
Hi, Avi
Currently, make sync in userspace only syncs x86-specific heads
from kernel source due to hard-coded in Makefile.
Do you have plan to provide
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
I see. ./configure --with-patched-kernel should work for that, but I
have no issue with copying include/asm-ia64 either.
Copy should be ugly, since it needs extral documentation to describle.
If --with-patched-kernel can call a
On Thu, 2008-03-20 at 17:05 +1100, Rusty Russell wrote:
+ snprintf(memfile_path, PATH_MAX, %s/.lguest,
getenv(HOME) ?: );
Hi Rusty,
Is that safe if being run via setuid/gid or shared root? It might be
better to just look it up in /etc/passwd against the real UID,
considering that anyone
david ahern wrote:
Backport of the virtio drivers to RHEL4.
The patch applies against the kvm-guest-drivers-linux-1 release but
also contains diffs for Anthony's spin_lock_irqsave/restore patch. Of
note is that to build for RHEL4 Makefile is renamed to Makefile-2.6 so
that Makefile can
On Wed, Mar 19, 2008 at 07:19:51PM -0500, Ryan Harper wrote:
While exploring the PCI hotplug code recently posted, I encountered a
situation where I don't believe the current behavior is ideal. With
hotplug, we can add additional pci-based nic devices like e1000 and
rtl8139 from the qemu
Bugs item #1920897, was opened at 2008-03-20 14:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1920897group_id=180599
Please note that this message will contain a full copy of
Bugs item #1920900, was opened at 2008-03-20 14:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1920900group_id=180599
Please note that this message will contain a full copy of
Marcelo Tosatti wrote:
Add an ioctl to zap all mappings to a given gfn. This allows userspace
remove the QEMU process mappings and the page without causing
inconsistency.
I'm thinking of comitting rmap_nuke() to kvm.git, and the rest to the
external module, since this is only needed on
Yunfeng Zhao wrote:
Following issues fixed:
1. qcow based smp linux guests likely hang
https://sourceforge.net/tracker/index.php?func=detailaid=1901980group_id=180599atid=893831
2. smp windows installer crashes while rebooting
Avi Kivity wrote:
Rusty Russell wrote:
Hi all,
Just finished my prototype of inter-guest virtio, using networking as an
example. Each guest mmaps the other's address space and uses a FIFO for
notifications.
Isn't that a security hole (hole? chasm)? If the two guests
Rusty Russell wrote:
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and DMA memory
mappings created by map_zeroed_pages.
I created a test program recently that measured the latency of a
reads/writes to an mmap() file in /dev/shm
On Thu, Mar 20, 2008 at 04:16:00PM +0800, Tim Post wrote:
On Thu, 2008-03-20 at 17:05 +1100, Rusty Russell wrote:
+ snprintf(memfile_path, PATH_MAX, %s/.lguest,
getenv(HOME) ?: );
Hi Rusty,
Is that safe if being run via setuid/gid or shared root? It might be
better to just look it up
Rusty Russell wrote:
Hi all,
Just finished my prototype of inter-guest virtio, using networking as an
example. Each guest mmaps the other's address space and uses a FIFO for
notifications.
There are two issues with this approach. The first is that neither guest
can change its
* Avi Kivity [EMAIL PROTECTED] [2008-03-20 07:19]:
Ryan Harper wrote:
While exploring the PCI hotplug code recently posted, I encountered a
situation where I don't believe the current behavior is ideal. With
hotplug, we can add additional pci-based nic devices like e1000 and
rtl8139 from
Anthony Liguori wrote:
Avi Kivity wrote:
Rusty Russell wrote:
Hi all,
Just finished my prototype of inter-guest virtio, using
networking as an example. Each guest mmaps the other's address
space and uses a FIFO for notifications.
Isn't that a security hole (hole? chasm)?
On Thu, Mar 20, 2008 at 09:04:17AM -0500, Anthony Liguori wrote:
Rusty Russell wrote:
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and DMA memory
mappings created by map_zeroed_pages.
I created a test program recently that
Avi Kivity wrote:
Anthony Liguori wrote:
Avi Kivity wrote:
Each guest's host userspace mmaps the other guest's address space.
The userspace then does a copy on both the tx and rx paths.
Well, that's better security-wise (I'd still prefer to avoid it, so we
can run each guest under a
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
Avi Kivity wrote:
Each guest's host userspace mmaps the other guest's address space.
The userspace then does a copy on both the tx and rx paths.
Well, that's better security-wise (I'd still prefer to avoid it, so
we can
Avi Kivity wrote:
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
Avi Kivity wrote:
Each guest's host userspace mmaps the other guest's address space.
The userspace then does a copy on both the tx and rx paths.
Well, that's better security-wise (I'd still prefer to
Anthony Liguori wrote:
Rusty Russell wrote:
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and DMA memory
mappings created by map_zeroed_pages.
I created a test program recently that measured the latency of a
Avi Kivity wrote:
Anthony Liguori wrote:
Rusty Russell wrote:
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and
DMA memory
mappings created by map_zeroed_pages.
I created a test program recently that measured the
Anthony Liguori wrote:
You can have the file descriptor be opened O_RDONLY so trust isn't an
issue.
Reading is just as bad as writing.
This implies trusting the other userspace, which is not a good
thing. Let the kernel copy, we already trust it, and it has more
resources to do the
Avi Kivity wrote:
I disagree. A driver domain is shared between multiple guests, and if
one of the guests manages to break into qemu then it can see other
guest's data.
You still don't strictly need to do things in the kernel if this is your
concern. You can have another process map both
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: 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: 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: 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: 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: 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 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]
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: 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: 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: 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: 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
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]
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
Hollis Blanchard wrote:
On Thu, 2008-03-20 at 17:24 +0100, Carsten Otte wrote:
Index: kvm/include/linux/kvm_host.h
===
--- kvm.orig/include/linux/kvm_host.h
+++ kvm/include/linux/kvm_host.h
@@ -24,7 +24,11 @@
#include
On Thu, 20 Mar 2008 17:25:26 +0100 Carsten Otte wrote:
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
On Thu, 20 Mar 2008 17:25:20 +0100 Carsten Otte wrote:
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
Randy Dunlap wrote:
Index: kvm/arch/s390/kernel/early.c
===
--- kvm.orig/arch/s390/kernel/early.c
+++ kvm/arch/s390/kernel/early.c
@@ -143,6 +143,10 @@ static noinline __init void detect_machi
/* Running on a P/390 ? */
Carsten Otte wrote:
+struct mm_struct *dup_mm(struct task_struct *tsk);
No prototypes in .c files. Put this in an appropriate header.
J
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
Christian Borntraeger wrote:
Rusty,
currently virtio_blk uses one major number per device. While this works
quite well on most systems it is wasteful and will exhaust major numbers
on larger installations.
This patch allocates a major number on init and will use 16 minor numbers
for each
Anthony Liguori wrote:
Christian Borntraeger wrote:
Rusty,
currently virtio_blk uses one major number per device. While this works
quite well on most systems it is wasteful and will exhaust major numbers
on larger installations.
This patch allocates a major number on init and will use 16
On Thu, Mar 20, 2008 at 05:25:26PM +0100, Carsten Otte wrote:
@@ -143,6 +143,10 @@ static noinline __init void detect_machi
/* Running on a P/390 ? */
if (cpuinfo-cpu_id.machine == 0x7490)
machine_flags |= 4;
+
+ /* Running under KVM ? */
+ if
I am trying to understand spikes in system time that I am seeing in a VM. The
guest OS is RHEL4, with 2 vpcus, and 2.5Gb RAM; host is running 2.6.24.2 kernel.
kvm version is kvm-63.
Using the stat scripts Christian Ehrhardt posted a few days ago (thanks,
Christian, very handy tool) I collected
On Thu, 2008-03-20 at 10:28 -0700, Jeremy Fitzhardinge wrote:
Carsten Otte wrote:
+struct mm_struct *dup_mm(struct task_struct *tsk);
No prototypes in .c files. Put this in an appropriate header.
Well, and more fundamentally: do we really want dup_mm() able to be
called from other code?
Dave Hansen wrote:
Well, and more fundamentally: do we really want dup_mm() able to be
called from other code?
Maybe we need a bit more detailed justification why fork() itself isn't
good enough. It looks to me like they basically need an arch-specific
argument to fork, telling the new
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 05:25:26PM +0100, Carsten Otte wrote:
@@ -143,6 +143,10 @@ static noinline __init void detect_machi
/* Running on a P/390 ? */
if (cpuinfo-cpu_id.machine == 0x7490)
machine_flags |= 4;
+
+/* Running under KVM ? */
On Thu, Mar 20, 2008 at 09:37:19PM +0100, Carsten Otte wrote:
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 05:25:26PM +0100, Carsten Otte wrote:
@@ -143,6 +143,10 @@ static noinline __init void detect_machi
/* Running on a P/390 ? */
if (cpuinfo-cpu_id.machine == 0x7490)
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 09:37:19PM +0100, Carsten Otte wrote:
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 05:25:26PM +0100, Carsten Otte wrote:
@@ -143,6 +143,10 @@ static noinline __init void detect_machi
/* Running on a P/390 ? */
if
Using drive_add with bogus devfn values would segfault QEMU when
attempting to add scsi devices. Attached patch checks in hotplug code
for appropriate devices that drive_add() will work with (looking before
leaping) and bails if you don't specify a proper device with your
bus,devfn.
--
Ryan
On Thu, Mar 20, 2008 at 09:59:32PM +0100, Carsten Otte wrote:
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 09:37:19PM +0100, Carsten Otte wrote:
Christoph Hellwig wrote:
On Thu, Mar 20, 2008 at 05:25:26PM +0100, Carsten Otte wrote:
@@ -143,6 +143,10 @@ static noinline __init void
On Friday 21 March 2008 01:04:17 Anthony Liguori wrote:
Rusty Russell wrote:
From: Paul TBBle Hampson [EMAIL PROTECTED]
This creates a file in $HOME/.lguest/ to directly back the RAM and DMA
memory mappings created by map_zeroed_pages.
I created a test program recently that measured the
On Thursday 20 March 2008 17:54:45 Avi Kivity wrote:
Rusty Russell wrote:
Hi all,
Just finished my prototype of inter-guest virtio, using networking as
an example. Each guest mmaps the other's address space and uses a FIFO
for notifications.
Isn't that a security hole (hole?
Rusty Russell wrote:
How odd! Do you have any idea why?
Nope, but part of the reason I did this was I recalled a similar
discussion relating to kqemu and why it used /dev/shm. I thought it was
only an issue with older kernels but apparently not.
/dev/shm is not really for general use.
On Friday 21 March 2008 03:25:28 Carsten Otte wrote:
+static void kvm_set_status(struct virtio_device *vdev, u8 status)
+{
+ BUG_ON(!status);
+ to_kvmdev(vdev)-desc-status = status;
+}
+
+/*
+ * To reset the device, we (ab)use the NOTIFY hypercall, with the descriptor
+ * address
On Thursday 20 March 2008 19:16:00 Tim Post wrote:
On Thu, 2008-03-20 at 17:05 +1100, Rusty Russell wrote:
+ snprintf(memfile_path, PATH_MAX, %s/.lguest,
getenv(HOME) ?: );
Hi Rusty,
Is that safe if being run via setuid/gid or shared root? It might be
better to just look it up in
Avi Kivity wrote:
Yunfeng Zhao wrote:
Following issues fixed:
1. qcow based smp linux guests likely hang
https://sourceforge.net/tracker/index.php?func=detailaid=1901980group_id=180599atid=893831
2. smp windows installer crashes while rebooting
65 matches
Mail list logo
