Hi,
Could qemu/VERSION get updated with each KVM release? Currently it
seems there is no way to determine the KVM version from the binaries.
Putting it in MODULE_VERSION for the kernel modules would also be
useful.
-jim
-
Forgot the attachment :-(
[EMAIL PROTECTED] wrote:
>APIC_TMCCT is a dynamically running count which always
>need to be recalculated at the time it is read. Setting
>intermediate value is meaningless.
>
>Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
>
>
> diff --git a/dr
Jorge Lucángeli Obes wrote:
> Hi all,
>
> >From what I've gathered, it seems that we have basically four options
> at hand. I think it's important to notice, however, that whatever
> comes out of this will probably be, as Avi said, a "low-end" solution.
> IMHO there's room to have both the high-end
introduce a new field, "guest", in cpustat to store the time used by the CPU to
run virtual CPU. Modify /proc/stat to display this new field.
Signed-Off-by: Laurent Vivier <[EMAIL PROTECTED]>
--
- [EMAIL PROTECTED] --
"Software is hard" - Donald Knuth
Index: kvm
modify account_system_time() to add cputime to cpustat->guest if we are running
a VCPU. We add this cputime to cpustat->user too instead of cpustat->system
because this part of KVM code is in fact user code although it is executed in
the kernel. We duplicate VCPU time between guest and user to allo
[EMAIL PROTECTED] wrote:
>Add back pending irqs for apic timer to get precise guestAPIC
> timer interrupt.
>
>Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
>
>
a typo, please use this one.
With above patches, now guest timer is much accurate! sleep 60
get exactly 60 second
Gregory Haskins wrote:
>>>
>>>
>> Yes, you can pass through any gva. There are couple of things to be
>> aware of though. When passing a gva, you have to be sure that the gva
>> is actually mapped in memory as KVM cannot cause Linux to fault in a
>> page.
>>
>
> Cool! Ya, I tot
Jim Paris wrote:
> Hi,
>
> Could qemu/VERSION get updated with each KVM release? Currently it
> seems there is no way to determine the KVM version from the binaries.
>
> Putting it in MODULE_VERSION for the kernel modules would also be
> useful.
>
>
There will be a version string for the exter
You can find attached to this email the patch to apply to procps-3.2.7[1] to
allow "top(1)" to display the cpu guest time.
Laurent
[1] http://procps.sf.net/procps-3.2.7.tar.gz
--
- [EMAIL PROTECTED] --
"Software is hard" - Donald Knuth
Index: procps-3.2.7/top.c
Add back pending irqs for apic timer to get precise guest
APIC timer interrupt.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/irq.h b/drivers/kvm/irq.h
index ed6d20a..8867c82 100644
--- a/drivers/kvm/irq.h
+++ b/drivers/kvm/irq.h
@@ -110,7 +110,7
cleanup:
last_update should precisely reflect the time
when an hrtimer is fired, and store the period
of apic timer to avoid calculation each time.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/irq.h b/drivers/kvm/irq.h
index
APIC_TMCCT is a dynamically running count which always
need to be recalculated at the time it is read. Setting
intermediate value is meaningless.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/lapic.c b/drivers/kvm/lapic.c
index d59b69f..fc53e8
Avi Kivity wrote:
>> This is a big effort but a config file is the right long term solution.
>>
>>
>
> For which use case? management-full or management-less?
>
Both. A config file will be useful not just for expressing the
functionality we have today, but also for describing the guest's
Anthony Liguori wrote:
> Jorge Lucángeli Obes wrote:
>> Hi all,
>>
>> >From what I've gathered, it seems that we have basically four options
>> at hand. I think it's important to notice, however, that whatever
>> comes out of this will probably be, as Avi said, a "low-end" solution.
>> IMHO there's
Dong, Eddie wrote:
> Add back pending irqs for apic timer to get precise guest
> APIC timer interrupt.
>
Can you explain the problem and the solution in more detail?
-
This SF.net email is sponsored by: Splunk Inc
The aim of these two patches is to measure the CPU time used by a virtual
machine. All comments are welcome... I'm not sure it's the good way to do that.
[PATCH 1/2] introduce a new field, "guest", in cpustat to store the time used by
the CPU to run virtual CPU. Modify /proc/stat to display this n
Without this, memory is leaked and later attempts fail with
"Migration already active".
Signed-off-by: Jim Paris <[EMAIL PROTECTED]>
---
qemu/migration.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu/migration.c b/qemu/migration.c
index bbeed86..ed1fd29 100644
---
Anthony Liguori wrote:
> Avi Kivity wrote:
>>> This is a big effort but a config file is the right long term solution.
>>>
>>>
>>
>> For which use case? management-full or management-less?
>>
>
> Both. A config file will be useful not just for expressing the
> functionality we have today,
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
This is a big effort but a config file is the right long term
solution.
>>>
>>> For which use case? management-full or management-less?
>>>
>>
>> Both. A config file will be useful not just for expressing
Gregory Haskins wrote:
> On Fri, 2007-08-10 at 19:59 +0300, Avi Kivity wrote:
>
>
>> Note that passing a virtual address is highly discouraged as its meaning
>> can change from vcpu to vcpu, it might not be mapped, translation is
>> slow, etc. Just let the guest do the translation.
>>
>
Linux operates the HPET timer in legacy replacement mode, which means that the
periodic interrupt of the CMOS RTC is not delivered (qemu won't be able to use
/dev/rtc). Add support for HPET (/dev/hpet) as a replacement for the RTC; the
periodic interrupt is delivered via SIGIO and is handled in the
Gregory Haskins wrote:
> Hi All,
> I am working on some PV stuff and had some questions about the ability
> to share memory across the Guest/Host boundary.
>
> It seems that most examples of how to do this always involve starting
> with a *page, converting it to a gfn via page_to_gfn(), and using
On Fri, 2007-08-10 at 19:59 +0300, Avi Kivity wrote:
> Note that passing a virtual address is highly discouraged as its meaning
> can change from vcpu to vcpu, it might not be mapped, translation is
> slow, etc. Just let the guest do the translation.
Yeah, Hollis and Anthony straighted me out
Hi,
On 10/08/07, Paolo Ornati <[EMAIL PROTECTED]> wrote:
> Just got this warning during suspend2ram (2.6.23-rc2-gac078602).
>
> Config and full dmesg attached.
>
>
> [ 756.707601] Disabling non-boot CPUs ...
> [ 756.712034] kvm: disabling virtualization on CPU1
> [ 756.712037] WARNING: at arch/
On Fri, 2007-08-10 at 09:32 -0500, Anthony Liguori wrote:
> Gregory Haskins wrote:
> > Hi All,
> > I am working on some PV stuff and had some questions about the ability
> > to share memory across the Guest/Host boundary.
> >
> > It seems that most examples of how to do this always involve starti
On Fri, 10 Aug 2007 00:09:18 -0400, Gregory Haskins wrote:
>
> If so, how would I do this: E.g. can I just pass the pointer, and then
> do gva_to_hpa() on the host? Or do I need to prep the pointer before
> sending it?
We've talked about this a little in the
past: see the discussion around http
Hi Avi,
I have been collected quiet a few patches in my tree now. They are all
in dirty(style, debug) state. Now I started cleaning some of the code in
my tree, and cutting patches again. I plan to send you steady stream of
patches now. so you can expect lots of patches coming from me in coming
d
Hi Avi,
The patch to implement "jmp rel" emulation is attached.
Thanks & Regards,
Nitin
Open Source Technology Center, Intel Corporation.
-
The mind is like a parachute; it works much better when it's open.
commit 1d77b7
Hi Avi,
Attached is the patch for the instruction "jmp rel short", opcode
0xeb.
This patch goes on top of last patch (jmp rel).
Thanks & Regards,
Nitin
Open Source Technology Center, Intel Corporation.
-
The mind
From: Chuan-kai Lin <[EMAIL PROTECTED]>
This patch is based on the one Anthony Liguori submitted to kvm-devel
on July 2nd, which fixes PXE booting with KVM enabled but breaks PXE
booting when not using KVM. I simplified Anthony's patch and
duplicated the cpu_register_physical_memory call to ensur
Avi Kivity wrote:
> Dong, Eddie wrote:
>> Add back pending irqs for apic timer to get precise guest
>> APIC timer interrupt.
>>
>
> Can you explain the problem and the solution in more detail?
Today guest sleep 10 seconds only get about 5-6 seconds in host time.
A design philosiphy in v
> > My feeling is that config files are outdated. When used with a gui,
> > you end up writing silly parsers and stuff and still wrecking things
> > horribly when the the gui writer's expectations don't match reality.
> > When used without a gui, they increase the amount of details one has
> > to
Chuan-kai Lin wrote:
> From: Chuan-kai Lin <[EMAIL PROTECTED]>
>
> This patch is based on the one Anthony Liguori submitted to kvm-devel
> on July 2nd, which fixes PXE booting with KVM enabled but breaks PXE
> booting when not using KVM. I simplified Anthony's patch and
> duplicated the cpu_regist
Hi, I was currently using kvm-24, and I decided to try to upgrade to
the latest.
My guest is XP-SP2 Home full edition.When I tried to boot it under
kvm-33, I eventually got a blue screen and a IRQL_NOT_LESS_OR_EQUAL error.
I removed 33, and installed kvm-26.I was able to boot the VM
34 matches
Mail list logo