Let the size of your shaft grow to its full potential with this.
http://www.susates.com/
Increase to a monster size shaft-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
htt
From 134d79f944f8742000fe65dd3fcfa850b9c876d1 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Fri, 14 Mar 2008 17:15:07 +0800
Subject: [PATCH] kvm: libkvm: Fix compile warning for kvm_disable_pit_creation
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
libkvm/libkvm.h | 1
Hi
I'm trying various thing with qemu to resolve my other issue and I've
tried to use oprofile.
But as soon as I run these:
opcontrol --vmlinux=mine/vmlinux
opcontrol --start
I get kernel oops (see bellow)
Is the fault in qemu (i.e. NMI is not emulated) or do I have to use
some other tools ?
O
Hello all,
I'm testing the last kvm version, 62. I was doing an iperf benchmark to
test the network performance in a Feisty virtual machine and I got
values surround 100Mbits when my card is actually 1Gbit. The testing
environment is conformed by 2 machines, both with Gbit interfaces. The
vm
What emulated nic are you using? I think only the e1000 emulated nic
supports 1 GB.
Miguel Araujo wrote:
> Hello all,
>
> I'm testing the last kvm version, 62. I was doing an iperf benchmark to
> test the network performance in a Feisty virtual machine and I got
> values surround 100Mbits when
Alexey Eremenko wrote:
> KVM fully uses all 4 CPUs.
>
> 1. You need to make sure KVM is activated (not Qemu).
> 2. You need to have the guest workload to be multi-threaded.
>
>
Hi Alexey,
Thanks, I worked it out - I had an issue on the kernel and on my custom
resource scheduling, now it is wor
On Wed, Mar 12, 2008 at 2:46 AM, Dor Laor <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-03-11 at 15:30 -0700, Dhirendra Pal Singh wrote:
> > I tried e1000 and it says "qemu: Unsupported NIC: e1000" :( Did I
> > miss something.. ?
> >
> > I downloaded the latest code base for qemu, and I see the
Dhirendra Pal Singh wrote:
> I got the latest snapshot of qemu and sure enough there was e1000
> driver support in it.. Though I didn't see much difference between
> RealTek Driver Vs e1000...
> Following was the test result...
>
> Copying 1GB file
> real3m48.284s
> user0m0.072s
> sys
This set address issues disscussed by Hollis on the first go around.
As well as some minor fixes.
This set of patches enables the following:
-Device tree Support
- Add libfdt to kvm-userspace
- Add bamboo device tree to qemu source
- Detectio
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205507804 18000
# Branch merge
# Node ID d96091321011ee86681f00bbaf72337ebc937791
# Parent b573d2790e7813337bf26c76a5c773a59592da5d
Add libfdt support to qemu
This patch adds needed configuration options to compile in libfdt sup
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205514172 18000
# Branch merge
# Node ID 9dd933f712ce2983997be94bae401572d5bba8f2
# Parent 60d8930ecedd292053f9c5340c95704b20e10c65
Add dynamic device tree manipulation & change uboot loader for PPC bamboo board
model
This patc
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205507804 18000
# Branch merge
# Node ID 8b68dc88abc897e7502e2c73ca1e40eb2084104f
# Parent d96091321011ee86681f00bbaf72337ebc937791
Create new load_uboot() & gunzip support to uboot loader in Qemu
This patch adds the ability for
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205514173 18000
# Branch merge
# Node ID 63237bde74818a5dc3cdb1baee781dab101290ce
# Parent 9dd933f712ce2983997be94bae401572d5bba8f2
Modify PPC bamboo & ppc440 board models
This patch renames pp440_init to ppc440ep_init, as ppc44
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205514170 18000
# Branch merge
# Node ID 60d8930ecedd292053f9c5340c95704b20e10c65
# Parent 8b68dc88abc897e7502e2c73ca1e40eb2084104f
Add PPC 440EP bamboo board device tree source & binary into qemu
This patch places the bamboo de
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1205514174 18000
# Branch merge
# Node ID 3060b75a9597d4ab67c23871df41fc5e5476df2b
# Parent 63237bde74818a5dc3cdb1baee781dab101290ce
Add ability to specify ram on command line for bamboo board model
This patch adds the ability to
From: Randy Dunlap <[EMAIL PROTECTED]>
Make KVM_CLOCK depend on HAVE_KVM. Otherwise a Voyager build can
fail with:
CC arch/x86/kernel/asm-offsets.s
In file included from include2/asm/irqflags.h:59,
from /local/linsrc/next-20080314/include/linux/irqflag
From: Randy Dunlap <[EMAIL PROTECTED]>
kvmclock needs to #include apic.h to prevent a build error:
next-20080314/arch/x86/kernel/kvmclock.c:142: error: implicit declaration of
function 'setup_secondary_APIC_clock'
elan1.out:make[2]: *** [arch/x86/kernel/kvmclock.o] Error 1
Sign
There is no zImage, so those comments do not make sense. "Filled in by
loader" would be more accurate.
You left MAL0 and EMAC0 commented out; please remove them.
You left PCI0 uncommented; please comment it out until qemu actually
emulates the PCI controller.
--
Hollis Blanchard
IBM Linux Techn
On Fri, 2008-03-14 at 14:06 -0500, Hollis Blanchard wrote:
> There is no zImage, so those comments do not make sense. "Filled in by
> loader" would be more accurate.
Currently the values there are hard coded. But I do still need to know
what values are filled in by zImage, that we are currently not
On Fri, 2008-03-14 at 14:16 -0500, Hollis Blanchard wrote:
> On Fri, 2008-03-14 at 12:09 -0500, Jerone Young wrote:
> > # HG changeset patch
> > # User Jerone Young <[EMAIL PROTECTED]>
> > # Date 1205514174 18000
> > # Branch merge
> > # Node ID 3060b75a9597d4ab67c23871df41fc5e5476df2b
> > # Parent
On Fri, 2008-03-14 at 12:09 -0500, Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <[EMAIL PROTECTED]>
> # Date 1205514174 18000
> # Branch merge
> # Node ID 3060b75a9597d4ab67c23871df41fc5e5476df2b
> # Parent 63237bde74818a5dc3cdb1baee781dab101290ce
> Add ability to specify ram o
On Fri, 2008-03-14 at 12:09 -0500, Jerone Young wrote:
> This set address issues disscussed by Hollis on the first go around.
> As well as some minor fixes.
Btw, please also update the description for patches 3 and 5 to rename
"load_uboot_l".
--
Hollis Blanchard
IBM Linux Technology Center
---
Hello
Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
(with many debug options) I've noticed that over the time my memory
seems to disappear somewhere.
Here is my memory trace after boot and some time of work - thus memory
should be populated.
MemTotal: 2007460 kB
MemF
On Fri, 14 Mar 2008 18:48:15 -0700 (PDT) [EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10246
>
>Summary: "in" after successful ioperm() results in SEGV after kvm
> use
>Product: Memory Management
>Version: 2.5
>
24 matches
Mail list logo
