On Wednesday 27 January 2010, Anthony Liguori wrote:
Introducing something that is known to be problematic from a security
perspective without any clear idea of what the use-case for it is is a
bad idea IMHO.
vepa on existing kernels is one use-case.
Considering
On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
x86 pentium
x86 pentium2
x86 pentium3
x86 athlon
x86
Marcelo Tosatti wrote:
The last two hunks will cause the same !CONFIG_KVM breakages qemu-kvm's
mpstate used to as well. You may either fix it up temporarily or wait
for my refactoring that is now scheduled with highest priority (should
be ready today or tomorrow).
It needs to go in
The final version of VCPU events in 2.6.33 will allow to skip
nmi_pending and sipi_vector on KVM_SET_VCPU_EVENTS. For now let's write
them unconditionally, which is unproblematic for upstream due to missing
SMP support. Future version which enable SMP will write them only on
reset.
Signed-off-by:
2010/1/28 Brian Jackson i...@theiggy.com:
What version of qemu-kvm?
qemu-kvm 0.12.2-1
There was a similar thread a while back, maybe you could try some of the
suggestions and/or info gathering tips from it.
tried every suggestion form that thread... contacted the original
poster and narrowed
On 28.01.2010, at 09:19, Arnd Bergmann wrote:
On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
x86 pentium
x86 pentium2
x86
Marcelo Tosatti wrote:
On Wed, Jan 27, 2010 at 03:54:08PM +0100, Jan Kiszka wrote:
This patch originates in the mp_state writeback issue: During runtime
and even on reset, we must not write the previously saved VCPU state
back into the kernel in an uncontrolled fashion. E.g mp_state should
Hi there,
I would need a system running in a VM with high availability. My current
version of KVM in Debian Lenny does not support to take snapshots of the
VM while it is running. So I was wondering if I can migrate the VM and
then make the snapshot on the source host. Once the snapshot is
Am 28.01.2010 06:22, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
CC: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
On Tue, Jan 26, 2010 at 03:11:34PM -0200, Lucas Meneghel Rodrigues wrote:
On Tue, 2010-01-26 at 11:25 +0800, Yolkfull Chow wrote:
This is designed to test all subcommands of 'qemu-img' however
so far 'commit' is not implemented.
Hi Yolkful, this is very good! Seeing this test made me think
Bugs item #2941537, was opened at 2010-01-28 11:57
Message generated for change (Tracker Item Submitted) made by nebukadneza
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2941537group_id=180599
Please note that this message will contain a full copy of
Upgraded to 2.6.33-rc5, same qemu-kvm version, same hardware.
The Vnc screen is still black and the virtual machine, but now I don't
have anymore messages in the logs but directly at standard output:
KVM internal error. Suberror: 2
extra data[0]: 8010
extra data[1]: 8b0d
rax
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Pablo Mellado
Sent: Donnerstag, 28. Jänner 2010 09:55
To: kvm@vger.kernel.org
Subject: High availability VM
Hi there,
I would need a system running in a VM with high availability.
Sridhar Samudrala wrote:
On Wed, 2010-01-27 at 22:39 +0100, Arnd Bergmann wrote:
we already have -net socket,fd and any user that passes an fd into
that already knows what he wants to do with it. Making it work with
raw sockets is just a natural extension to this
Didn't realize that -net
The new function pointer names match better with the
top-level functions of the iommu-api which are using them.
Main intention of this change is to make the -{un}map
pointer names free for two new mapping functions.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/kernel/amd_iommu.c
This patch changes the old map_size parameter of alloc_pte
to a page_size parameter which can be used more easily to
alloc a pte for intermediate page sizes.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/include/asm/amd_iommu_types.h | 28 +
This patch implements the new callbacks for the IOMMU-API
with functions that can handle different page sizes in the
IOMMU page table.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/kernel/amd_iommu.c | 29 +
1 files changed, 29 insertions(+), 0
These functions are not longer used and can be removed
savely. There functionality is now provided by the
iommu_{un}map functions which are also capable of multiple
page sizes.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/kernel/amd_iommu.c | 48
Hi,
here is a patch set which implements support for variable page sizes in the
IOMMU-API and changes the KVM device passthrough code to map the guest physical
memory with the best page sizes.
With this code a guest with 1GB of memory mapped with a 1GB page will not use
4kb PTEs in the IO page
This patch changes the implementation of of
kvm_iommu_map_pages to map the pages with the host page size
into the io virtual address space.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
virt/kvm/iommu.c | 106 ++---
1 files changed, 84
These two functions provide support for mapping and
unmapping physical addresses to io virtual addresses. The
difference to the iommu_(un)map_range() is that the new
functions take a gfp_order parameter instead of a size. This
allows the IOMMU backend implementations to detect easier if
a given
This patch extends the amd_iommu_iova_to_phys() function to
handle different page sizes correctly. It doesn't use
fetch_pte() anymore because we don't know (or care about)
the page_size used for mapping the given iova.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
This patch adds new callbacks for mapping and unmapping
pages to the iommu_ops structure. These callbacks are aware
of page sizes which makes them different to the
-{un}map_range callbacks.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/base/iommu.c |6 ++
This patch extends the functionality of iommu_unmap_page
and fetch_pte to support arbitrary page sizes.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/include/asm/amd_iommu_types.h |6 ++
arch/x86/kernel/amd_iommu.c| 90 +--
2 files
This patch changes the iommu-api functions for mapping and
unmapping page ranges to use the new page-size based
interface. This allows to remove the range based functions
later.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
drivers/pci/intel-iommu.c | 22 --
1 files
2010/1/28 Matteo Ghezzi tenyos...@gmail.com:
SNIP
I've tried starting the old vmachines on the new hardware but if I
enable kvm acceleration in qemu I got a black screen via vnc, and the
Enable kvm in qemu? KVM should always be enabled in Arch, when you run
qemu-kvm. You're not running
On Thu, 2010-01-28 at 17:37 +0800, Yolkfull Chow wrote:
On Tue, Jan 26, 2010 at 03:11:34PM -0200, Lucas Meneghel Rodrigues wrote:
That said, I was wondering if we could consolidate all qemu-img tests to
a single execution, instead of splitting it to several variants. We
could keep a failure
Bugs item #2941282, was opened at 2010-01-27 17:19
Message generated for change (Comment added) made by sjolshagen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2941282group_id=180599
Please note that this message will contain a full copy of the comment
Hi,
Sorry for a bit noisy cleanups. But during this
work, we noticed some buggy return value checks
and determined to send this work as a patch series.
Thanks,
Takuya Yoshikawa
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
read_std is one of the x86_emulate_ops. This patch fix the
return value check to use the proper macro.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/emulate.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/emulate.c
On Tue, Jan 26, 2010 at 10:26:22PM -0200, Marcelo Tosatti wrote:
@@ -374,6 +375,7 @@ static int cpu_post_load(void *opaque, int version_id)
kvm_load_tsc(env);
kvm_load_mpstate(env);
+kvm_put_vcpu_events(env);
}
It is confusing to call functions load/save for
This patch differentiate the X86EMUL_* values returned from
X86EMUL_* type functions.
Note: During this work, we noticed some buggy return value
checks in x86_emulate_insn(). See FIXME in this patch.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/emulate.c |
These two functions should return X86EMUL_* values.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/x86.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index ac8672f..78b8ddb 100644
---
pio_copy_data() and load|save_guest_segment_descriptor()
return X86EMUL_* values. Mixing up these values with 0, 1, ...
may produce unpridictable bugs.
Signed-off-by: Takuya Yoshikawa yoshikawa.tak...@oss.ntt.co.jp
---
arch/x86/kvm/x86.c | 27 +++
1 files changed, 15
Gleb Natapov wrote:
On Tue, Jan 26, 2010 at 10:26:22PM -0200, Marcelo Tosatti wrote:
@@ -374,6 +375,7 @@ static int cpu_post_load(void *opaque, int version_id)
kvm_load_tsc(env);
kvm_load_mpstate(env);
+kvm_put_vcpu_events(env);
}
It is confusing to call
On 01/28/2010 02:43 AM, Alexander Graf wrote:
On 28.01.2010, at 09:19, Arnd Bergmann wrote:
On Monday 25 January 2010, Dor Laor wrote:
x86 qemu64
x86 phenom
x86 core2duo
x86kvm64
x86 qemu32
x86 coreduo
x86 486
On 01/28/2010 07:56 AM, Michael S. Tsirkin wrote:
Now, the most important use case I see for the raw socket interface
in qemu is to get vhost-net and the qemu user implementation to
support the same feature set. If you ask for a network setup involving
a raw socket and vhost-net and the kernel
On 01/28/2010 08:13 AM, Anthony Liguori wrote:
On 01/28/2010 07:56 AM, Michael S. Tsirkin wrote:
Now, the most important use case I see for the raw socket interface
in qemu is to get vhost-net and the qemu user implementation to
support the same feature set. If you ask for a network setup
On Thu, Jan 28, 2010 at 08:13:53AM -0600, Anthony Liguori wrote:
On 01/28/2010 07:56 AM, Michael S. Tsirkin wrote:
Now, the most important use case I see for the raw socket interface
in qemu is to get vhost-net and the qemu user implementation to
support the same feature set. If you ask for a
On 01/28/2010 08:52 AM, Michael S. Tsirkin wrote:
On Thu, Jan 28, 2010 at 08:13:53AM -0600, Anthony Liguori wrote:
On 01/28/2010 07:56 AM, Michael S. Tsirkin wrote:
Now, the most important use case I see for the raw socket interface
in qemu is to get vhost-net and the qemu user
Bugs item #2941282, was opened at 2010-01-27 17:19
Message generated for change (Comment added) made by sjolshagen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2941282group_id=180599
Please note that this message will contain a full copy of the comment
On Thu, Jan 28, 2010 at 09:05:45AM -0600, Anthony Liguori wrote:
On 01/28/2010 08:52 AM, Michael S. Tsirkin wrote:
On Thu, Jan 28, 2010 at 08:13:53AM -0600, Anthony Liguori wrote:
On 01/28/2010 07:56 AM, Michael S. Tsirkin wrote:
Now, the most important use case I see for the raw
On Thursday 28 January 2010, Arnd Bergmann wrote:
On Wednesday 27 January 2010, Sridhar Samudrala wrote:
On Wed, 2010-01-27 at 22:39 +0100, Arnd Bergmann wrote:
On Wednesday 27 January 2010, Anthony Liguori wrote:
I think -net socket,fd should just be (trivially) extended to work
Bugs item #2930756, was opened at 2010-01-12 11:20
Message generated for change (Comment added) made by jamincollins
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2930756group_id=180599
Please note that this message will contain a full copy of the
On 01/28/2010 10:37 AM, Michael S. Tsirkin wrote:
So actually, this is an interesting argument in favor of
turning disablenetwork from per-process as it is now
to per-file.
Yup. I think we really need a file-based restriction mechanism and so
far, neither disablenetwork or network
On Thu, Jan 28, 2010 at 11:58:48AM -0600, Anthony Liguori wrote:
On 01/28/2010 10:37 AM, Michael S. Tsirkin wrote:
So actually, this is an interesting argument in favor of
turning disablenetwork from per-process as it is now
to per-file.
Yup. I think we really need a file-based
A vcpu can be stopped after handling IO in userspace,
but before returning to kernel to finish processing.
Add ioctls to get/set the PIO state.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/include/asm/kvm.h b/arch/x86/include/asm/kvm.h
index f46b79f..c1b2b8c 100644
Save/restore in-kernel KVM PIO state. This is necessary to allow
migration with in-progress PIO operation.
FIXME: adjust CPUState and VMState version.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu-kvm/target-i386/cpu.h
qemu patches against uq/master.
MMIO suffers from the same problem.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
1) Make git build of only the userspace bits
2) If kernel module build fails (kvm-kmod bug), issue a warning
and proceed with test.
3) Cleanup usage of private methods using name mangling (_ instead
of __ prepended to the name of the methods).
This is in preparation to new distros and a future
On 01/28/2010 12:04 PM, Michael S. Tsirkin wrote:
On Thu, Jan 28, 2010 at 11:58:48AM -0600, Anthony Liguori wrote:
On 01/28/2010 10:37 AM, Michael S. Tsirkin wrote:
So actually, this is an interesting argument in favor of
turning disablenetwork from per-process as it is now
to
On 01/28/2010 01:03 PM, Marcelo Tosatti wrote:
KVM uses a page mapped by userspace as a buffer for PIO.
Save/restore it.
Signed-off-by: Marcelo Tosattimtosa...@redhat.com
Index: qemu-kvm/target-i386/cpu.h
===
---
On Thursday 28 January 2010, Anthony Liguori wrote:
normal user uses libvirt to launch custom qemu instance. libvirt passes
an fd of a raw socket to qemu and puts the qemu process in a restricted
network namespace. user has another program running listening on a unix
domain socket and
On Thu, 2010-01-28 at 12:37 +0100, Joerg Roedel wrote:
This patch changes the iommu-api functions for mapping and
unmapping page ranges to use the new page-size based
interface. This allows to remove the range based functions
later.
+ size = 0x1000UL gfp_order;
Um, that's not a
On Thu, Jan 28, 2010 at 09:30:51AM +0100, Jan Kiszka wrote:
The final version of VCPU events in 2.6.33 will allow to skip
nmi_pending and sipi_vector on KVM_SET_VCPU_EVENTS. For now let's write
them unconditionally, which is unproblematic for upstream due to missing
SMP support. Future version
Hello,
I'm trying to start using kvm to do some research here at MIT. I would
like to try out some interesting page mapping ideas we have that would
be easier to try out in a hypervisor than inside the linux kernel.
However, I would like to start hacking a simple version of kvm that
On Thu, Jan 28, 2010 at 12:37:57PM +0100, Joerg Roedel wrote:
This patch changes the implementation of of
kvm_iommu_map_pages to map the pages with the host page size
into the io virtual address space.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
virt/kvm/iommu.c | 106
On Thursday 28 January 2010 17:17:22 Kevin Wolf wrote:
Am 28.01.2010 06:22, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
CC: Naphtali Sprei
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
Cc: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
qemu-img.c | 15 ++-
1 files
Jan Kiszka wrote:
Nicholas Amon wrote:
So now I can step instruction but my breakpoints do not work. I have
verified that disabling kvm restores the breakpoint functionality. Any
suggestions?
What kind of breakpoints, hardware-assisted or normal BPs? Are you
trying to break into
When using python 2.4, use the recommended hashlib.
When using python 2.4, fall back to the md5 and sha
modules.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/kvm_utils.py | 18 ++
client/tests/kvm/ppm_utils.py | 12 +---
Define reasonable defaults for the kvm test, to make it
easier to start using KVM autotest and encourage people
to play with it. The defaults are:
* qemu and qemu-kvm are expected to be found under
/usr/bin.
* The auxiliary directories are expected to be
found under
system_reset, system_powerdown and shutdown *must*
be the last ones defined, since the effect of such
tests can leave the VM on a bad state.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/tests_base.cfg.sample | 35 +--
1 files changed,
Some of the auxiliary kvm test programs need to
use logging configuration, we ended up duplicating
code across the test. Move the duplicated instances
to a single one living in kvm_utils.py.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/cd_hash.py|7 +--
When using python 2.5, use the recommended hashlib.
When using python 2.4, fall back to the md5 and sha
modules.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/kvm_utils.py | 18 ++
client/tests/kvm/ppm_utils.py | 12 +---
In order to make it easier to get started with KVM
testing, add a script that helps with setting up
directories, paths and iso files for the default
test configuration (Fedora 12 guest install, boot
test, shutdown). Once the first idea of how things
work is formed, one may start to tinker with
These 2 patches enable optional parameter(default 0) - PCI segment(or
domain) besides BDF, when assigning PCI device to guest.
Signed-off-by: Zhai Edwin edwin.z...@intel.com
--
best rgds,
edwin
Index: linux-2.6/virt/kvm/assigned-dev.c
This is designed to test all subcommands of 'qemu-img' however
so far 'commit' is not implemented.
* For 'check' subcommand test, it will 'dd' to create a file with specified
size and see whether it's supported to be checked. Then convert it to be
supported formats ('qcow2' and 'raw' so far) to
On Fri, Jan 29, 2010 at 03:00:09PM +0800, Yolkfull Chow wrote:
This is designed to test all subcommands of 'qemu-img' however
so far 'commit' is not implemented.
* For 'check' subcommand test, it will 'dd' to create a file with specified
size and see whether it's supported to be checked.
Am 29.01.2010 03:15, schrieb Sheng Yang:
Commit 03cbdac7 Disable fall-back to read-only when cannot open drive's
file for read-write result in read-only image can't be used as backed
image in qemu-img.
Cc: Naphtali Sprei nsp...@redhat.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
flexpriority_enabled implies cpu_has_vmx_virtualize_apic_accesses() returning
true, so we don't need this check here.
Signed-off-by: Gui Jianfeng guijianf...@cn.fujitsu.com
---
arch/x86/kvm/vmx.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c
On Friday 29 January 2010 15:36:59 Gui Jianfeng wrote:
flexpriority_enabled implies cpu_has_vmx_virtualize_apic_accesses()
returning true, so we don't need this check here.
Looks fine to me.
--
regards
Yang, Sheng
Signed-off-by: Gui Jianfeng guijianf...@cn.fujitsu.com
---
72 matches
Mail list logo
