H,E'R E WE GO AGAI_N!
T-H-E B+I*G O,N.E BE*FORE T+H'E S.E.PTEMBER.RALLY!
T_H E MARKE-T IS ABO.UT TO P-O_P+, A_N_D SO IS E.X+M,T_!
Fir.m: EXC. HANGE MOB ILE T'E,L*E (Ot_her O-T+C-: EXM-T.PK)
Tick,: E+X,M T
A+s.k-: 0'. 1.0 (+25.00+_%) (+U-P TO 2_5 % in 1 d'a,y')
5 -day po,t,ential: 0*.'4-
On 8/18/07, Christian MICHON <[EMAIL PROTECTED]> wrote:
> there's a typo line 1432 on vl.c after applying all 4 patches
> (missing ';')
Ops...
> beyond this small typo, I managed to include this in a win32 qemu build.
> is there a specific practical test to see the improvement in a linux guest
>
On 8/18/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
> Hello,
> in reply to this mail I will send a serie of 4 patches that cleans up and
> expands the alarm timer handling in QEMU. Patches have been rebased on QEMU
> CVS.
>
> Patch 1 is mostly a cleanup of the existing code; instead of having mu
If DYNAMIC_TICKS is defined qemu does not attepmt to generate SIGALRM at a
constant rate. Rather, the system timer is set to generate SIGALRM only
when it is needed. DYNAMIC_TICKS reduces the number of SIGALRMs sent to
idle dynamic-ticked guests.
Original patch from Dan Kenigsberg <[EMAIL PROTECTED
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 72 +++
1 file changed, 72 insertions(+)
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 287 +++-
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
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands the alarm timer handling in QEMU. Patches have been rebased on QEMU
CVS.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
#ifdefs to handle different timers scattered all over the c
On Fri, 2007-08-17 at 05:21 -0700, Avi Kivity wrote:
> I don't thing 'd |= Mov' is necessary any more to force writeback.
> Please check.
>
Hi Avi,
You are right, it was a bit stale code.
> Also, please keep opcodes in sorted order.
It is now.
Resending the updated "push reg" emulation patch.
Pl
On Fri, 2007-08-17 at 05:24 -0700, Avi Kivity wrote:
> A file scope function would indeed be uglier. But the macro has more
> serious problems; it's impossible to understand how variables are
> affected since nobody expects function local variables whose address
> is
> not taken to change after so
On Fri, 2007-08-17 at 05:18 -0700, Avi Kivity wrote:
> Applied, thanks.
>
> Please keep opcodes in sorted order, and don't post patches in dos
> format.
>
>
Hi Avi,
Attached is the patch, doing code cleanup. It keeps the emulation of
op-codes in sorted order. Also removes the white-space befor
Looking forward to it:-)
2007/8/17, Anthony Liguori <[EMAIL PROTECTED]>:
>
> On Thu, 2007-08-16 at 16:32 +0200, Gunther Persoons wrote:
> > Hey,
> >
> > Is there already paravirtualizaton support in KVM? If so how can I enable
> > it?
>
> I've got a new series that I'll be posting in a couple of
On Thu, 2007-08-16 at 16:32 +0200, Gunther Persoons wrote:
> Hey,
>
> Is there already paravirtualizaton support in KVM? If so how can I enable it?
I've got a new series that I'll be posting in a couple of days.
Regards,
Anthony Liguori
> Thankx
>
> --
Hi all,
here is a list of Supported Guests:
http://kvm.qumranet.com/kvmwiki/Guest_Support_Status
The tables are a bit unclear to me, I will explain using the 'Debian
Etch' example.
The top line of the table states:
Guest: Debian Etch
Guest bitness: 32/64
Host version: kvm-29
Host cpu: Intel
Hos
On 8/13/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Luca Tettamanti wrote:
> > The patch stops the "unhandled wrmsr", but reboot is still not working
> > (guest is stuck using 100% of the CPU). The last working userspace is
> > KVM-28, and I tested it with recent kernel modules. Any idea on this
>
Hi All,
Below is how I installed kvm-35 on my debian etch installation, it may
be included in the wiki :)
I installed the amd64 version of debian 4.0 r0 on my amd4800+
I did all 'apt-get update' and 'apt-get upgrade' steps to get the system
updated with all latest patches.
And off course I did
H E.R,E WE GO A'GAIN!
T H-E B I'G O.N.E BE,FORE T,H-E SEPTEMB E*R.RALLY!
T*H'E MARKE*T IS A'BOUT TO P.O'P_, A-N,D SO IS E+X+M-T_!
Fir,m: EX*CH.ANGE MO,BILE T*E_L,E (Oth.er O,T C': E.XMT.PK)
Tic.k: E*X+M,T
A*s-k+: 0-.,0-8
5--day pote-ntial : 0'.,4-0
T'h,i*s a gre_at opport_unit'y to at le*ast
On 8/16/07, Clive Stewell <[EMAIL PROTECTED]> wrote:
> I have been attempting to get Windows Server 2003 running under KVM and
> am having some difficulty in doing so. I have tried it on both AMD and
> Intel-based machines and it crashes on each. Below is some basic
> information about my setup fol
On Fri, 2007-08-17 at 22:38 +0800, Weiyang Chen wrote:
> Hi,
>
> I build kvm-35 from tarball successfully on my Macbook core2due with
> a 2.6.22.3 kernel, Ubuntu 7.04. But when I try to start kvm with a
> Windows XP image, it gets crushed with a "unhandled vm exit: 0x9"
> error. Here are the la
Hi,
I build kvm-35 from tarball successfully on my Macbook core2due with a
2.6.22.3 kernel, Ubuntu 7.04. But when I try to start kvm with a Windows XP
image, it gets crushed with a "unhandled vm exit: 0x9" error. Here are the
last 2 lines from dmesg:
kvm: guest NX capability removed
kvm_handle
Avi Kivity wrote:
[...]
>
> The normal user/system accounting has the same issue, no? Whereever we
> happen to land (kernel or user) gets the whole tick.
>
> So I think it is okay to have the same limitation for guest time.
>
So this is how it looks like.
PATCH 1 and 2 are always a prerequisit
On Fri, 2007-08-17 at 17:43 +1000, Rusty Russell wrote:
> Sure, these discussions can get pretty esoteric. The question is
> whether you want a point-to-point transport (as we discuss here), or an
> N-way. Lguest has N-way, but I'm not convinced it's worthwhile, as
> there's some overhead
Am Freitag, 17. August 2007 schrieb Laurent Vivier:
> > The normal user/system accounting has the same issue, no? Whereever we
> > happen to land (kernel or user) gets the whole tick.
>
> Yes... but perhaps I should rewrite this too ;-)
If you look further, you will see, that this was actually r
Avi Kivity wrote:
> Laurent Vivier wrote:
>> KVM updates vtime in task_struct to allow account_guest_time() to modify
>> user,
>> system and guest time in cpustat accordingly.
>>
>
>> --- kvm.orig/drivers/kvm/Kconfig 2007-08-17 10:24:46.0 +0200
>> +++ kvm/drivers/kvm/Kconfig 2007-
On 8/17/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> That page doesn't work for me -- it probably expects some HTTP POST
> data. Can you set down instructions to reproduce? (i.e. starting from
> java.sun.com or similar)
Sure.
1) go to http://java.com
2) click the big green "FREE JAVA DOWNLOAD"
Avi Kivity wrote:
> Laurent Vivier wrote:
>>>
- remove PATCH 3, and add in task_struct a "ktime vtime" where we
accumulate
guest time (by calling something like guest_enter() and guest_exit() from
the
virtualization engine), and when in account_system_time() we have
Laurent Vivier wrote:
> KVM updates vtime in task_struct to allow account_guest_time() to modify user,
> system and guest time in cpustat accordingly.
>
> --- kvm.orig/drivers/kvm/Kconfig 2007-08-17 10:24:46.0 +0200
> +++ kvm/drivers/kvm/Kconfig 2007-08-17 10:25:25.0 +020
Laurent Vivier wrote:
> This is another way to compute guest time... I remove the "account modifiers"
> mechanism and call directly account_guest_time() from account_system_time().
> account_system_time() computes user, system and guest times according value
> accumulated in vtime (a ktime_t) in ta
[EMAIL PROTECTED] wrote:
> Hi,
> I would like to ask a question about how Qemu handle interrupt in user space.
> I would like to understand how Qemu catch hardware interrupt generated by
> real (host) peripheral.
> I look at the Qemu code, (vl.c : main_loop and main_loop_wait) and I can't
> identif
Laurent Vivier wrote:
>>
>>> - remove PATCH 3, and add in task_struct a "ktime vtime" where we accumulate
>>> guest time (by calling something like guest_enter() and guest_exit() from
>>> the
>>> virtualization engine), and when in account_system_time() we have cputime >
>>> vtime we substrat
He, Qing wrote:
> I'm updating this patch, by doing this, UP booting of 32bit ACPI MP HAL
> Windows is fixed.
>
>
Amended previous commit -- thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
Luca Tettamanti wrote:
> Hello,
> in reply to this mail I will send a serie of 4 patches that cleans up and
> expands
> the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
> but I think I can rebase it to QEMU svn if desired.
>
>
I would really like to see this go in
Duncan McQueen wrote:
> According to the Guest OS status, all Windows OSes seem to fail on
> AMD64. Is this still the case?
>
>
I regularly run Windows on AMD machines.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
Ben Taylor wrote:
> "Jorge Lucángeli Obes" <[EMAIL PROTECTED]> wrote:
>
>> I've been giving some thought to Anthony's idea:
>>
>> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>>
>> However, maybe I'm just too much on vacations, but I don't seem to
>> come up with a nice
Yang, Sheng wrote:
> this allows running 64-bit Windows.
>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
This SF.net email is sponsored by: Splunk Inc.
Still
This kernel option is already set unfortunately :(
On 8/17/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> Daniel Paquet wrote:
> > Well im still playing with this darn error, and in fact I am even
> > starting to think that this is my cause of kicker crash. Im getting my
> > logs filled with
> > rt
Daniel Paquet wrote:
> Well im still playing with this darn error, and in fact I am even
> starting to think that this is my cause of kicker crash. Im getting my
> logs filled with
> rtc: lost some interrupts at 1024Hz when I sed the max freq to 1024 as
> per request of kvm when I start it.
>
> Im
Nitin A Kamble wrote:
> Avi,
> In my opinion converting this small function to file-scope function,
> would make code look ugly. I think the earlier Macro definition was
> better.
>
>
A file scope function would indeed be uglier. But the macro has more
serious problems; it's impossible t
Nitin A Kamble wrote:
> Hi Avi,
> Attached is a patch to implement instruction:
> push reg (opcode 0x50 - 0x57)
> Please apply or comment.
>
>
> + case 0x50 ... 0x57: /* push reg */
> + if (op_bytes == 2)
> + src.val = (u16) _regs[b & 0x7];
> +
Nitin A Kamble wrote:
> Hi Avi,
> Attached is the patch to implement "and al imm8", "and ax imm16" & "
> and eax imm32" instructions.
> Please apply or comment.
>
Applied, thanks.
Please keep opcodes in sorted order, and don't post patches in dos format.
--
Do not meddle in the internals
Jindrich Makovicka wrote:
>
> On Mon, 13 Aug 2007 12:09:46 +0300
> Avi Kivity wrote:
>
>>> get_msr_entry should be fine, cpu_save/cpu_load (used by savevm -
>>> qemu/vl.c) may need a similar fix.
>>>
>>> The patch stops the "unhandled wrmsr", but reboot is still not
>>> working (guest is stuck
KVM updates vtime in task_struct to allow account_guest_time() to modify user,
system and guest time in cpustat accordingly.
Index: kvm/drivers/kvm/Kconfig
===
--- kvm.orig/drivers/kvm/Kconfig2007-08-17 10:24:46.0 +0200
This is another way to compute guest time... I remove the "account modifiers"
mechanism and call directly account_guest_time() from account_system_time().
account_system_time() computes user, system and guest times according value
accumulated in vtime (a ktime_t) in task_struct by the virtual machi
Hi,
I would like to ask a question about how Qemu handle interrupt in user space.
I would like to understand how Qemu catch hardware interrupt generated by
real (host) peripheral.
I look at the Qemu code, (vl.c : main_loop and main_loop_wait) and I can't
identify where Qemu listens and catches the
Rusty Russell wrote:
> On Fri, 2007-08-17 at 09:35 +0200, Laurent Vivier wrote:
>> Rusty Russell wrote:
>>> Hi Laurent,
>> Hi Rusty,
>> how are your puppies ?
>
> They're getting a little fat, actually. Too many features ...
>
>> - remove PATCH 3, and add in task_struct a "ktime vtime" where we
Hi, all,
This is today's KVM test result against kvm.git
9bcbb7df435e154b148662df3721f71847a9342c and kvm-userspace.git
c7fcfd9cb8bae04a16545d67edec5582fe084246.
We found host crash issues on both PAE and IA32e.
1. Host crash when Save/Restore 64bits guest at 64bits platform
https://sourceforge.
On Fri, 2007-08-17 at 09:35 +0200, Laurent Vivier wrote:
> Rusty Russell wrote:
> > Hi Laurent,
>
> Hi Rusty,
> how are your puppies ?
They're getting a little fat, actually. Too many features ...
> - remove PATCH 3, and add in task_struct a "ktime vtime" where we accumulate
> guest time (by ca
Bugs item #1776079, was opened at 2007-08-17 16:25
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=1776079&group_id=180599
Please note that this message will contain a full copy
Bugs item #1776078, was opened at 2007-08-17 16:24
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=1776078&group_id=180599
Please note that this message will contain a full copy
Bugs item #1776069, was opened at 2007-08-17 15:55
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=1776069&group_id=180599
Please note that this message will contain a full copy
On Fri, 2007-08-17 at 01:26 -0400, Gregory Haskins wrote:
> Hi Rusty,
>
> Comments inline...
>
> On Fri, 2007-08-17 at 11:25 +1000, Rusty Russell wrote:
> >
> > Transport has several parts. What the hypervisor knows about (usually
> > shared memory and some interrupt mechanism and possibly "DM
Rusty Russell wrote:
> On Thu, 2007-08-16 at 17:58 +0200, Laurent Vivier wrote:
>> [PATCH 3/3] introduce "account modifiers" mechanism in the kernel allowing a
>> module to modify the collected accounting for a given task. This
>> implementation
>> is based on the "preempt_notifier". "account_syst
> If DYNAMIC_TICKS is defined qemu does not attepmt to generate SIGALRM at a
> constant rate. Rather, the system timer is set to generate SIGALRM only
> when it is needed. DYNAMIC_TICKS reduces the number of SIGALRMs sent to
> idle dynamic-ticked guests.
> Original patch from Dan Kenigsberg <[EMAIL
53 matches
Mail list logo