On Wed, 2007-02-21 at 20:21 +0200, Avi Kivity wrote:
> Avi Kivity wrote:
> > The following patchset moves the kvm userspace interface from having a
> > single fd, to having three types of file descriptors:
>
> Andrew, while the 2.6.21 merge window has closed, please consider
> applying this to 2
Hi all,
I've played with Xen on my Fedora and it's been working fine. Now I'm
testing KVM with 2.6.20 kernel and it's working nicely, too, but I'm
unable to setup a full-blown networking, i.e., a mode where also
icmp/udp work. User-mode networking works well, e.g., yum and firefox
run just fine un
Avi Kivity wrote:
> The following patchset moves the kvm userspace interface from having a
> single fd, to having three types of file descriptors:
Andrew, while the 2.6.21 merge window has closed, please consider
applying this to 2.6.21 anyway. At least one major distribution
(Fedora) is plann
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/kvm.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index 7c9a400..275354f 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -11,7 +11,7 @@
#include
Allocate a distinct inode for every vcpu in a VM. This has the following
benefits:
- the filp cachelines are no longer bounced when f_count is incremented on
every ioctl()
- the API and internal code are distinctly clearer; for example, on the
KVM_GET_REGS ioctl, there is no need to copy
In preparation of some hacking.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 102
1 files changed, 51 insertions(+), 51 deletions(-)
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 981f5d3..6fb36c8
This reflects the changed scope, from device-wide to single vm (previously
every device open created a virtual machine).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 48
1 files changed, 24 insertions(+), 24 deletion
This avoids having filp->f_op and the corresponding inode->i_fop different,
which is a little unorthodox.
The ioctl list is split into two: global kvm ioctls and per-vm ioctls. A new
ioctl, KVM_CREATE_VM, is used to create VMs and return the VM fd.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
-
The kvmfs inodes will represent virtual machines and vcpus, as necessary,
reducing cacheline bouncing due to inodes and filps being shared.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 33 -
1 files changed, 32 insertions(+), 1 delet
The following patchset moves the kvm userspace interface from having a
single fd, to having three types of file descriptors:
- one fd returned by open("/dev/kvm") is used for generic access to the
kvm driver, for example to get the API version and to create virtual
machines
- when you create a
Muli Ben-Yehuda wrote:
> On Tue, Feb 20, 2007 at 09:46:17AM +0200, Avi Kivity wrote:
>
>> Muli Ben-Yehuda wrote:
>>
>>> Thanks for the analysis, this problem is understood. Avi commited a
>>> fix for -14 a few days back, but the fix re-breaks
>>> --kerneldir. Reenabling --kerneldir is simpl
Anthony Liguori wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Aurelien Jarno wrote:
>>>
> What is your disk image file format, or are you using a partition?
>
>
I am using a raw image file on an ext3 partition.
>>>
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Aurelien Jarno wrote:
>>
>>>
>>>
What is your disk image file format, or are you using a partition?
>>> I am using a raw image file on an ext3 partition.
>>>
>>>
>>>
Do the results change (o
Avi Kivity wrote:
> Aurelien Jarno wrote:
>>
>>> What is your disk image file format, or are you using a partition?
>>>
>> I am using a raw image file on an ext3 partition.
>>
>>
>>> Do the results change (on kvm-14) if you pin the guest to a core with
>>> 'taskset 1 qemu ...'
>>>
Aurelien Jarno wrote:
>
>> What is your disk image file format, or are you using a partition?
>>
>
> I am using a raw image file on an ext3 partition.
>
>
>> Do the results change (on kvm-14) if you pin the guest to a core with
>> 'taskset 1 qemu ...'
>>
>
> Bingo. It now works eve
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> Aurelien Jarno wrote:
>>>
The bad news is that kvm-14 seems to be a lot slower than kvm-12 +
modules from kernel 2.6.20. This is the case with a GNU/kFreeBSD guest.
kvm-12 was about 1.5 time faster th
Bugs item #1664779, was opened at 2007-02-21 01:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1664779&group_id=180599
Please note that this message will contain a full copy
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
>>> The bad news is that kvm-14 seems to be a lot slower than kvm-12 +
>>> modules from kernel 2.6.20. This is the case with a GNU/kFreeBSD guest.
>>> kvm-12 was about 1.5 time faster than qemu + kqemu. kvm-20 is slo
18 matches
Mail list logo
