Glauber Costa wrote:
> This is not exactly what kvm does. For us, wallclock read and system
> time reads are decoupled operations, controlled by different msrs.
Same for xen. Although both live in the shared_info page they are
updated independently (and the wall clock is updated much less freque
This release adds support for the ppc 44x embedded processors. Like s390
and ia64, it is only provided in the git tree, not in the tarball.
Linux guests are supported.
Changes from kvm-66:
- s390/ia64: compile fix (Christian Borntraeger)
- s390: change virtio interrupt to follow arch specificati
Yang, Sheng wrote:
> The updated patch also moved ept_load_pdptrs() from critical region to
> kvm_handle_vmexit().
>
>
Thanks; applied all EPT patches.
--
error compiling committee.c: too many arguments to function
-
T
Harvey Harrison wrote:
> arch/x86/kvm/x86.c:3484:25: warning: cast truncates bits from constant value
> (100 becomes 0)
> arch/x86/kvm/x86.c:3510:24: warning: cast truncates bits from constant value
> (100 becomes 0)
>
> The problem:
> cseg_desc.type &= ~(1 << 8); //clear the B flag
Bugs item #1850037, was opened at 2007-12-13 14:25
Message generated for change (Comment added) made by ravpl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1850037&group_id=180599
Please note that this message will contain a full copy of the comment thr
Bugs item #1953353, was opened at 2008-04-28 13:50
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=1953353&group_id=180599
Please note that this message will contain a full copy
Avi Kivity wrote:
> The patches look good, but pleasy copy Jeremy and virtualization@ for
> patches which touch things outside kvm.
Will do for the next round.
> It's perhaps better to reverse the order: first fix kvm to be
> compatible, then merge the Xen and kvm implementations into a single on
On Fri, Apr 25, 2008 at 02:43:19PM -0400, Chris Lalancette wrote:
> Unfortunately, we can't just "fake emulate" MSR_K7_PERFCTR[0-3] like we are
> doing for MSR_K7_EVNTSEL[0-3]; if they are there, linux expects to be able to
> put values into them. I think the correct solution here is to emulate
>
Joerg Roedel wrote:
> We already discussed the emulation of the performance counter registers
> in the past. The conclusion is, that we loose live migration with that
> emulation because performance monitoring is implemented differently
> between AMD and Intel systems. Maybe discarding _any_ writes
Be a better lover by strengthening your manhood for the good of womankind.
http://www.driksil.com/
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time
Бухгалтеру o дoгoвoрнoй рабoте oрганизации - правoвые oснoвы и налoгoвый аспект
7 мая 2008, г. Мoсква
Прoграмма семинара
1. Как правильнo oфoрмить дoгoвoр, oбязательные и дoпoлнительные услoвия
дoгoвoрoв. Кoгда мoжнo считать сoблюденнoй прoстую письменную фoрму дoгoвoра.
Кoгда дoгoвoр требует
Hi Andrea,
Looks good.
Acked-by: Marcelo Tosatti <[EMAIL PROTECTED]>
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority
Avi Kivity wrote:
> Harvey Harrison wrote:
>> arch/x86/kvm/x86.c:3484:25: warning: cast truncates bits from constant
>> value (100 becomes 0)
>> arch/x86/kvm/x86.c:3510:24: warning: cast truncates bits from constant
>> value (100 becomes 0)
>>
>> The problem:
>> cseg_desc.type &= ~(1 << 8);
On Mon, Apr 28, 2008 at 10:17:37AM -0400, Chris Lalancette wrote:
> Joerg Roedel wrote:
> > We already discussed the emulation of the performance counter registers
> > in the past. The conclusion is, that we loose live migration with that
> > emulation because performance monitoring is implemented
Izik Eidus wrote:
> Avi Kivity wrote:
>
>> Harvey Harrison wrote:
>>
>>> arch/x86/kvm/x86.c:3484:25: warning: cast truncates bits from constant
>>> value (100 becomes 0)
>>> arch/x86/kvm/x86.c:3510:24: warning: cast truncates bits from constant
>>> value (100 becomes 0)
>>>
>>> The problem:
Joerg Roedel wrote:
>> OK, yeah, I read some of those threads over the weekend. It is a larger
>> problem than just this crash, and probably one to be solved later.
>> I have attached a patch which just discards all writes, as you
>> suggested;
>> this allows my RHEL-4 guest to successf
Chris Lalancette <[EMAIL PROTECTED]> writes:
> this allows my RHEL-4 guest to successfully boot, although obviously the NMI
> watchdog which it thinks it set up is not actually working.
That's fine. On a virtualized environment you don't really need a NMI watchdog
because you can always debug from
Attached is a patch that fixes a guest crash when booting older Linux kernels.
The problem stems from the fact that we are currently emulating
MSR_K7_EVNTSEL[0-3], but not emulating MSR_K7_PERFCTR[0-3]. Because of this,
setup_k7_watchdog() in the Linux kernel receives a GPF when it attempts to wri
Hi!
I'm preparing kvm-67 for debian. While testing i noticed a problem:
When booting the debian installer from the official CD [1] this problem:
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Compat vDSO mapped to e000.
CPU: Intel QEMU Virtual CPU version 0.9.1 stepping 03
Checki
Hollis Blanchard wrote:
> This reduces host CPU usage when the guest is idle. However, the guest must
> set MSR[WE] in its idle loop, which Linux did not do until 2.6.26.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
Here's my thinking as to why we don't want to destroy the VM in the mmu
notifiers ->release method. I don't have a valid use-case for this but
my argument depends on the fact that this is something that should
work. Daemonizing a running VM may be a reasonable use-case. It's
useful to wait t
* Avi Kivity <[EMAIL PROTECTED]> [2008-04-26 02:23]:
>
> Please reuse qemu_mutex for this, no need for a new one.
I'm having a little trouble wrapping my head around all of the locking
here. If I avoid qemu_mutex and use a new one, I've got everything
working. However, attemping to use qemu_mut
Hi,
sorry, the test environment is not really reproducible (stock kvm-66,
yet unpublished NMI support by Sheng Yang and me, special guest), but
I'm just fishing for some ideas on what may cause the flood of the
following warning in my kernel log:
[ cut here ]
WARNING: at /
Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> Valgrind caught this:
>>
>> ==11754== Conditional jump or move depends on uninitialised value(s)
>> ==11754==at 0x50C9BC: kvm_create_pit (libkvm-x86.c:153)
>> ==11754==by 0x50CA7F: kvm_arch_create (libkvm-x86.c:178)
>> ==11754==by 0x50AB31:
On Mon, Apr 28, 2008 at 11:11:56AM -0500, Anthony Liguori wrote:
> Here's my thinking as to why we don't want to destroy the VM in the mmu
> notifiers ->release method. I don't have a valid use-case for this but my
> argument depends on the fact that this is something that should work.
> Daemo
On Fri, Apr 25, 2008 at 11:33:18AM -0600, David S. Ahern wrote:
> Most of the cycles (~80% of that 54k+) are spent in paging64_prefetch_page():
>
> for (i = 0; i < PT64_ENT_PER_PAGE; ++i) {
> gpa_t pte_gpa = gfn_to_gpa(sp->gfn);
> pte_gpa += (i+offset) * siz
1 file changed, 25 insertions(+), 13 deletions(-)
kernel/Makefile | 38 +-
This patch removes static x86 entries and makes things work for multiple archs.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff --git a/kernel/Makefile b/kernel/Makefile
--- a/ke
On Thu, Apr 24, 2008 at 10:37:04AM +0200, Gerd Hoffmann wrote:
> Hi folks,
>
> My first attempt to send out a patch series with git ...
>
> The patches fix the kvm paravirt clocksource code to be compatible with
> xen and they also factor out some code which can be shared into a
> separate sour
Ryan Harper wrote:
> * Avi Kivity <[EMAIL PROTECTED]> [2008-04-26 02:23]:
>
>> Please reuse qemu_mutex for this, no need for a new one.
>>
>
> I'm having a little trouble wrapping my head around all of the locking
> here. If I avoid qemu_mutex and use a new one, I've got everything
> worki
On Mon, Apr 28, 2008 at 06:50:22PM +0200, Jan Luebbe wrote:
> Hi!
>
> I'm preparing kvm-67 for debian. While testing i noticed a problem:
>
> When booting the debian installer from the official CD [1] this problem:
>
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 2048K
> Compat vDSO ma
Bugs item #1895893, was opened at 2008-02-18 01:44
Message generated for change (Comment added) made by alfmel
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1895893&group_id=180599
Please note that this message will contain a full copy of the comment th
On Sun, 27 Apr 2008, Andrea Arcangeli wrote:
> Talking about post 2.6.26: the refcount with rcu in the anon-vma
> conversion seems unnecessary and may explain part of the AIM slowdown
> too. The rest looks ok and probably we should switch the code to a
> compile-time decision between rwlock and rw
On Mon, Apr 28, 2008 at 07:35:10PM +0200, Jan Kiszka wrote:
> Hi,
>
> sorry, the test environment is not really reproducible (stock kvm-66,
> yet unpublished NMI support by Sheng Yang and me, special guest), but
> I'm just fishing for some ideas on what may cause the flood of the
> following warni
Hi, great work.
While playing with kvm-qemu I noticed a few points that might be of interrest:
1/ -loadvm and -snapshot don't work together. It works as if -loadvm wasn't
passed as argument
2/ two instances of kvm can be passed the same -hda. There is no locking
whatsoever. This messes up thin
1 file changed, 4 insertions(+)
qemu/hw/ppc440_bamboo.c |4
This fixes a issue where the amount of memory is not properly being defined in
the device tree. It currently is hardcoded for 144MB. The result is that if you
specify a memory size below the hardcoded size, the guest crashes. T
2 files changed, 18 insertions(+)
qemu/hw/device_tree.c | 16
qemu/hw/device_tree.h |2 ++
This patch adds function dt_cell_multi to allow for manipulation of device tree
properties that contain mulitiple 32bit values.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff -
This set of patches contain fixes for bamboo board model, as well as provides
more functionality for device tree manipulation.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
3 files changed, 22 insertions(+), 1 deletion(-)
qemu/hw/device_tree.c | 16
qemu/hw/device_tree.h
1 file changed, 1 deletion(-)
qemu/hw/ppc440_bamboo.c |1 -
In 2.6.26 wait is now enabled by default. With this the /hypervisor node will
not be need to be idetified to enable the guest to go into wait state while
idle.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff --git a/qemu/hw/p
Bugs item #1952988, was opened at 2008-04-27 18:25
Message generated for change (Comment added) made by mtosatti
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1952988&group_id=180599
Please note that this message will contain a full copy of the comment
We hold qemu_mutex while machine->init() executes, which issues a VCPU create.
We need to make sure to not return from the VCPU creation until the VCPU
file descriptor is valid to ensure that APIC creation succeeds.
However, we also need to make sure that the VCPU thread doesn't start running
unti
Hey.
I've been trying Microsoft Windows 2003 a couple of times. The wiki
tells me that "everything" should work okay. It does, when using -smp 1,
but gets ugly when using -smp 2 or so.
SO might it be useful, to add the column "smp" to the "Guest Support
Status" Page in the wiki?
- fabian
smime
Hi Marcelo:
mmu_recycled is always 0 for this guest -- even after almost 4 hours of uptime.
Here is a kvm_stat sample where guest time was very high and qemu had 2
processors at 100% on the host. I removed counters where both columns have 0
value for brevity.
exits 45937979 758
On Mon, Apr 28, 2008 at 01:34:11PM -0700, Christoph Lameter wrote:
> On Sun, 27 Apr 2008, Andrea Arcangeli wrote:
>
> > Talking about post 2.6.26: the refcount with rcu in the anon-vma
> > conversion seems unnecessary and may explain part of the AIM slowdown
> > too. The rest looks ok and probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> @@ -369,6 +372,10 @@ static void *ap_main_loop(void *_env)
> sigfillset(&signals);
> sigprocmask(SIG_BLOCK, &signals, NULL);
> kvm_create_vcpu(kvm_context, env->cpu_index);
> +pthread_mutex_lock(&vcpu_mutex);
> +vcpu->created =
On Tue, 29 Apr 2008, Andrea Arcangeli wrote:
> Frankly I've absolutely no idea why rcu is needed in all rmap code
> when walking the page->mapping. Definitely the PG_locked is taken so
> there's no way page->mapping could possibly go away under the rmap
> code, hence the anon_vma can't go away as
Fabian Deutsch wrote:
> Hey.
>
> I've been trying Microsoft Windows 2003 a couple of times. The wiki
> tells me that "everything" should work okay. It does, when using -smp 1,
> but gets ugly when using -smp 2 or so.
>
> SO might it be useful, to add the column "smp" to the "Guest Support
> Statu
46 matches
Mail list logo