The Buildbot has detected a new failure of next-i386 on kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/next-i386/builds/144
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly scheduler named 'nightly_nex
The Buildbot has detected a new failure of next-x86_64 on kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/next-x86_64/builds/144
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly scheduler named 'nightly
The Buildbot has detected a new failure of i386 on kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/i386/builds/155
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly scheduler named 'nightly_master' trigg
The Buildbot has detected a new failure of x86_64 on kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/x86_64/builds/166
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly scheduler named 'nightly_master' t
The Buildbot has detected a new failure of disable_kvm_i386_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_out_of_tree/builds/757
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_k
The Buildbot has detected a new failure of disable_kvm_i386_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_i386_debian_5_0/builds/809
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm
The Buildbot has detected a new failure of disable_kvm_x86_64_debian_5_0 on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_debian_5_0/builds/808
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu
The Buildbot has detected a new failure of disable_kvm_x86_64_out_of_tree on
qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_out_of_tree/builds/757
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qe
Sorry, I found cn...@gmx.de gave a patch in this maillist for this issue.
Best Regards,
Yongjie Ren(Jay)
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On Behalf Of
Ren, Yongjie
Sent: Friday, April 22, 2011 9:21 AM
To: kvm@vger.kernel.org
Hi,
I use kvm.git 51138ead... ( the latest commit in upstream ). I got the
following error, could you have a look? Is the code’s issue or my configuration
issue ? Thanks a lot.
arch/x86/kvm/emulate.c:4095:25: error: macro "wbinvd" passed 1 arguments, but
takes just 0
arch/x8
On Fri, Apr 08, 2011 at 11:07:23PM +0200, Jan Kiszka wrote:
> On 2011-04-08 20:53, David Ahern wrote:
> > 2.6.38.2 kernel with trace-cmd git pulled this morning:
> >
> > trace-cmd record -e kvm
> >
> > trace-cmd report 2>&1 | less
> >
> > trace-cmd: No such file or directory
>
> Does this error
Hi,
I noticed recently NMI on guest kernel is not working well. host/guest
kernel is 2.6.39-rc4, and using vmx.
And test code is something like the following:
local_irq_disable();
for (i = 0; i < 10; i++) {
int cpu = get_cpu();
printk("%s: nmi %u,
Commit 0b56652e33c72092956c651ab6ceb9f0ad081153 fails to build:
CC [M] arch/x86/kvm/emulate.o
arch/x86/kvm/emulate.c: In function 'x86_emulate_insn':
arch/x86/kvm/emulate.c:4095:25: error: macro "wbinvd" passed 1 arguments, but
takes just 0
arch/x86/kvm/emulate.c:4095:3: warning: statement wit
I am running 2.6.37-5.dmz.1-liquorix-amd64 with ubuntu 10.10, and when
i am compiling the kvm mod for 2.6.37 kernel it throws the following
errors :
nano@server:~/Work/kvm-kmod-2.6.37$ make
make -C /lib/modules/2.6.37-5.dmz.1-liquorix-amd64/build M=`pwd` \
LINUXINCLUDE="-I`pwd`/include -Ii
On Thu, 2011-04-21 at 18:23 +0200, Jan Kiszka wrote:
> Hi,
>
> latest qemu-kvm bails out on cleanup as it tries to call
> cpu_register_physical_memory with a zero-sized region of an assigned
> device. That made me dig into the setup/cleanup of memory mapped io
> regions, trying to consolidate and
=
KVM Forum 2011: Call For Participation
August 15-16, 2011 - Hyatt Regency Vancouver - Vancouver, Canada
=
KVM is an industry leading open source hypervisor that provide
Hi,
latest qemu-kvm bails out on cleanup as it tries to call
cpu_register_physical_memory with a zero-sized region of an assigned
device. That made me dig into the setup/cleanup of memory mapped io
regions, trying to consolidate and fix the code.
What are the differences between normal and slow m
On Thu, 2011-04-21 at 16:42 +0100, David Woodhouse wrote:
> On Thu, 2011-04-21 at 15:28 +0100, Alex Williamson wrote:
> > I've been wondering the exact same thing. My last patch took weeks of
> > prodding, finally went into the maintainer's tree without
> > acknowledgment, and there's hardly been
From: Randy Dunlap
arch/x86/kvm/emulate.c:2598: warning: integer constant is too large for 'long'
type
Signed-off-by: Randy Dunlap
---
arch/x86/kvm/emulate.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20110421.orig/arch/x86/kvm/emulate.c
+++ linux-nex
On 2011-04-21 16:10, Yaniv Kaul wrote:
> Fedora 15beta/x64, latest git:
> [ykaul@ykaul qemu]$ make
> CCx86_64-softmmu/kvm.o
> /home/ykaul/qemu/target-i386/kvm.c: In function ‘kvm_get_xsave’:
> /home/ykaul/qemu/target-i386/kvm.c:953:29: error: variable ‘fop’ set but
> not used [-Werror=unused-
On Thu, 2011-04-21 at 15:28 +0100, Alex Williamson wrote:
> I've been wondering the exact same thing. My last patch took weeks of
> prodding, finally went into the maintainer's tree without
> acknowledgment, and there's hardly been any activity there to suggest
> a pull request for 2.6.39 is going
From: Takuya Yoshikawa
This patch optimizes the guest page table walk by using get_user()
instead of copy_from_user().
With this patch applied, paging64_walk_addr_generic() has become
about 0.5us to 1.0us faster on my Phenom II machine with NPT on.
Signed-off-by: Takuya Yoshikawa
---
arch/x86
Changelog v1->v2: dropped slot_hint and wrapper.
As Avi said, get_user() alone achieved most of the improvement.
Before
2.994 us | paging64_walk_addr_generic();
1.480 us | paging64_walk_addr_generic();
0.996 us | paging64_walk_addr_generic();
1.108 us | paging64_walk_addr_gene
On 04/21/2011 05:23 PM, Nguyen Thai Ngoc Duy wrote:
On Thu, Apr 21, 2011 at 9:11 PM, Avi Kivity wrote:
> On 04/21/2011 04:49 PM, Nguyen Thai Ngoc Duy wrote:
>>
>> Hi,
>>
>> I have a specialized e1000 device driver that expects to receive a
>> single frame per interrupt, no more. It's by desi
On Tuesday 19 April 2011, Ashish Saxena wrote:
> @Arnd, I would like to initiate the dig into into macvtap driver. Could you
> please provide me some pointers/docs to start with.
I dont' have any general recommendations.
I'd suggest you start reading the macvlan.c and macvtap.c source code and
co
On Thu, 2011-04-21 at 14:32 +0200, Jan Kiszka wrote:
> On 2011-01-04 11:42, Jan Kiszka wrote:
> > Am 10.12.2010 19:44, Chris Wright wrote:
> >> * Jan Kiszka (jan.kis...@siemens.com) wrote:
> >> --- a/drivers/pci/intel-iommu.c
> >> +++ b/drivers/pci/intel-iommu.c
> >> @@ -3627,9 +3627,9
On Wed, Apr 20, 2011 at 3:36 PM, Shirley Ma wrote:
> This patchset add supports for TX zero-copy between guest and host
> kernel through vhost. It significantly reduces CPU utilization on the
> local host on which the guest is located (It reduced 30-50% CPU usage
> for vhost thread for single stre
On Thu, Apr 21, 2011 at 9:11 PM, Avi Kivity wrote:
> On 04/21/2011 04:49 PM, Nguyen Thai Ngoc Duy wrote:
>>
>> Hi,
>>
>> I have a specialized e1000 device driver that expects to receive a
>> single frame per interrupt, no more. It's by design and very hard to
>> change (and it does not serve IP tr
On 04/21/2011 04:12 PM, Pekka Enberg wrote:
On Thu, Apr 21, 2011 at 4:00 PM, Sasha Levin wrote:
> This can also be extended to use hugetlbfs.
Recent Linux kernels support transparent hugepages so you can do
MADV_HUGEPAGE on mmap'd memory.
Note, it has to be aligned correctly (to a 2M boundar
On 04/21/2011 04:49 PM, Nguyen Thai Ngoc Duy wrote:
Hi,
I have a specialized e1000 device driver that expects to receive a
single frame per interrupt, no more. It's by design and very hard to
change (and it does not serve IP traffic). -net socket or tap can
sometimes deliver more than one frame
On Thu, 2011-04-21 at 16:12 +0300, Pekka Enberg wrote:
> Well, I don't still quite see the point of this feature. Is there some
> real world use for running guests with huge memory space that's
> swap-backed?
Not a single guest, but multiple guests which take more RAM than the
host can provide usi
* Jan Kiszka (jan.kis...@siemens.com) wrote:
> On 2011-01-04 11:42, Jan Kiszka wrote:
> > Am 10.12.2010 19:44, Chris Wright wrote:
> >> * Jan Kiszka (jan.kis...@siemens.com) wrote:
> >> --- a/drivers/pci/intel-iommu.c
> >> +++ b/drivers/pci/intel-iommu.c
> >> @@ -3627,9 +3627,9 @@ stati
Hi,
I have a specialized e1000 device driver that expects to receive a
single frame per interrupt, no more. It's by design and very hard to
change (and it does not serve IP traffic). -net socket or tap can
sometimes deliver more than one frame in a row and blow up the driver
in turn. I'd like to e
On Thu, Apr 21, 2011 at 4:00 PM, Sasha Levin wrote:
> It's an alternative to creating more swap.
> When using large RAM sizes for guests on hosts with limited physical
> RAM/swap this option gives the user a way to use files instead of swap.
Well, I don't still quite see the point of this feature
On 04/21/2011 03:31 PM, Stefan Hajnoczi wrote:
On Thu, Apr 21, 2011 at 9:07 AM, Avi Kivity wrote:
> Note I think in both cases we can make significant improvements:
> - for VFs, steer device interrupts to the cpus which run the vcpus that will
> receive the interrupts eventually (ISTR some wo
On Thu, 2011-04-21 at 15:48 +0300, Pekka Enberg wrote:
> On Thu, Apr 21, 2011 at 3:45 PM, Sasha Levin wrote:
> > Add --use-backing to allow for the usage of a temporary backing file for
> > guest RAM.
> > A temporary file is created and aollocated under /tmp and is used to back
> > the RAM memor
On Thu, Apr 21, 2011 at 3:45 PM, Sasha Levin wrote:
> Add --use-backing to allow for the usage of a temporary backing file for
> guest RAM.
> A temporary file is created and aollocated under /tmp and is used to back the
> RAM memory which is mmaped for the guest.
> There should be enough storage
Add --use-backing to allow for the usage of a temporary backing file for guest
RAM.
A temporary file is created and aollocated under /tmp and is used to back the
RAM memory which is mmaped for the guest.
There should be enough storage space under /tmp to use this option (at least
the size of the
On Thu, Apr 21, 2011 at 3:34 PM, Sasha Levin wrote:
> Using mmap to allocate the RAM enables us to allocate large blocks of memory
> for the guest, allowing to boot guests with a large RAM.
> Since if we try KVM_SET_USER_MEMORY_REGION with a large memory block KVM used
> to Oops (now it just fai
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #41 from prochazka 2011-04-21
12:39:11 ---
Hi,
I never test #38 from avi kivity suggest,
and now i suppres all bridge ( brctl) and netfilter configuration from my
server,
i'm using openvswitch without this problem.
Regards,
Using mmap to allocate the RAM enables us to allocate large blocks of memory
for the guest, allowing to boot guests with a large RAM.
Since if we try KVM_SET_USER_MEMORY_REGION with a large memory block KVM used
to Oops (now it just fails), we had to move the actual ioctl to after we
KVM_CREATE_
On 2011-01-04 11:42, Jan Kiszka wrote:
> Am 10.12.2010 19:44, Chris Wright wrote:
>> * Jan Kiszka (jan.kis...@siemens.com) wrote:
>> --- a/drivers/pci/intel-iommu.c
>> +++ b/drivers/pci/intel-iommu.c
>> @@ -3627,9 +3627,9 @@ static int intel_iommu_attach_device(struct
>> iommu_domai
On Thu, Apr 21, 2011 at 9:07 AM, Avi Kivity wrote:
> Note I think in both cases we can make significant improvements:
> - for VFs, steer device interrupts to the cpus which run the vcpus that will
> receive the interrupts eventually (ISTR some work about this, but not sure)
> - for virtio, use a D
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #40 from Avi Kivity 2011-04-21 12:13:33 ---
(In reply to comment #39)
> Is this issue resolved?
> I'm seeing almost the same issue with 2.6.38 + qemu-kvm-0.14.0 (on NEC
> Express5800/110Ge server), except that my backtrace is call
https://bugzilla.kernel.org/show_bug.cgi?id=27052
Taisuke Yamada changed:
What|Removed |Added
CC||tai.ker...@cc.rakugaki.org
--- Comme
https://bugzilla.kernel.org/show_bug.cgi?id=33762
Anton Kochkov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Hi, Avi
I'm sorry to reply you a little late.
I spent some time on finding information to fix the EFLAGS[30] issue, and I
have got it now.
Here is some comment from Centaur.:
EFLAGS:30 was used on C7 but not by Nano. EFLAGS:30 is undefined for Intel. C7
used it as a way of improving performa
By reserving 0 as an invalid x86_intercept_stage, we no longer
need to store a valid flag in x86_intercept_map.
Signed-off-by: Avi Kivity
---
arch/x86/include/asm/kvm_emulate.h |1 +
arch/x86/kvm/svm.c | 12
2 files changed, 5 insertions(+), 8 deletions(-)
dif
Signed-off-by: Avi Kivity
---
arch/x86/kvm/emulate.c | 56 +++
1 files changed, 13 insertions(+), 43 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index e8f146d..522b4a5 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/k
While it isn't defined, no need to force a #UD. If it becomes defined
in the future this can cause wierd problems for the guest.
Signed-off-by: Avi Kivity
---
arch/x86/kvm/emulate.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/
Signed-off-by: Avi Kivity
---
arch/x86/kvm/emulate.c | 146 ---
1 files changed, 99 insertions(+), 47 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index f683ce1..bf4284d 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/k
A little step towards removing the big switch ().
Avi Kivity (3):
KVM: x86 emulator: move 0F 01 sub-opcodes into their own functions
KVM: x86 emulator: Don't force #UD for 0F 01 /5
KVM: x86 emulator: Use opcode::execute for 0F 01 opcode
arch/x86/kvm/emulate.c | 169 +++
On 04/20/2011 11:31 PM, Alex Williamson wrote:
Store the device saved state so that we can reload the device back
to the original state when it's unassigned. This has the benefit
that the state survives across pci_reset_function() calls via
the PCI sysfs reset interface while the VM is using the
On 04/20/2011 11:31 PM, Alex Williamson wrote:
v2 -> v3:
Saved structure has variable contents.
Avi, see if this adds any credibility to the pci-core allocated
opaque buffer. It was wrong in the previous versions to distill
the variable device capability save list into a fixed struct.
This
On Thu, Apr 21, 2011 at 12:57 AM, Paolo Bonzini wrote:
> On 04/21/2011 05:40 AM, Cheng Renquan wrote:
>>
>> I'm trying to use qemu-kvm to run Fedora15-beta with gnome3,
>> but it told me graphics hardware failed to run gnome3 specific
>> features and it fallback to gnome2;
>
> Sorry, none of the c
On 04/21/2011 09:53 AM, Liu Yuan wrote:
From: Liu Yuan
Function ioapic_debug() in the ioapic_deliver() misnames
one filed by reference. This patch correct it.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsu
On 04/21/2011 04:02 AM, Takuya Yoshikawa wrote:
On Wed, 20 Apr 2011 15:33:16 +0200
"Roedel, Joerg" wrote:
> @@ -245,13 +257,17 @@ walk:
>goto error;
>
>if (write_fault&& !is_dirty_gpte(pte)) {
> - bool ret;
> + int ret;
>
>trace_kvm_mmu_set_dirty_
On 04/21/2011 05:35 AM, Alex Williamson wrote:
Device assignment via a VF provides the lowest latency and most
bandwidth for *getting data off the host system*, though virtio/vhost is
getting better. If all you care about is VM-VM on the same host or
VM-host, then virtio is only limited by memor
On 04/21/2011 05:40 AM, Cheng Renquan wrote:
I'm trying to use qemu-kvm to run Fedora15-beta with gnome3,
but it told me graphics hardware failed to run gnome3 specific
features and it fallback to gnome2;
Sorry, none of the cards provided by KVM (including the SPICE-specific
QXL card) currentl
This case is used to test the drift between host and guest.
Use taskset to make tsc program execute in a single cpu.
If the drift ratio bigger than 10%, then fail this case.
Signed-off-by: Amos Kong
---
client/tests/kvm/deps/get_tsc.c| 27 ++
client/tests/kvm/tests/tsc_drift.py
60 matches
Mail list logo
