subscribe kvm
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Monday, 10 August 2009 18:15:17 +0200,
Bernhard Held wrote:
> Hi Daniel!
Hi, Bernhard!
> > I've set in the kernel config:
> >
> > CONFIG_FIRMWARE_IN_KERNEL=y
> And what happened? Are you sure you recompiled and booted the new
> kernel with CONFIG_FIRMWARE_IN_KERNEL=y?
>
> [...]
>
> Here is
Andre Przywara wrote:
> If you happen to stuck with 32bit
> (pity you!) then I agree that a kvm32 would be nice to have.
> Will think about it...
I know that 32-bit is a bit slower for some things due to register
pressure (but it's a bit faster for some things due to less memory
needed for pointe
Avi Kivity wrote:
> On 08/21/2009 12:34 AM, Andre Przywara wrote:
> >In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
> >which is the least common denominator of all KVM-capable x86-CPUs
> >(based on Intel Pentium 4 Prescott). It can be used as a base type
> >for migration
Patch speaks for itself.
commit b5cd58bc3e7bddf0a9735d5c13c36e2221a7f616
Author: Zachary Amsden
Date: Fri Aug 21 14:34:37 2009 -1000
Make vma_kernel_pagesize a kvm compat API; this fixes the build with
new kernels synced to 2.6.31 compiling externally for older systems.
Signed-
Avi Kivity wrote:
On 08/21/2009 12:34 AM, Andre Przywara wrote:
In addition to the TCG based qemu64 type let's introduce a kvm64 CPU
type,
which is the least common denominator of all KVM-capable x86-CPUs
(based on Intel Pentium 4 Prescott). It can be used as a base type
for migration.
>>
Typi
Glauber Costa wrote:
On Fri, Aug 21, 2009 at 12:41 PM, Avi Kivity wrote:
On 08/21/2009 12:34 AM, Andre Przywara wrote:
In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
which is the least common denominator of all KVM-capable x86-CPUs
(based on Intel Pentium 4 Prescott)
Change trace_arg_string() and parse_trace_arg() to probe_arg_string()
and parse_probe_arg(), since those are kprobe-tracer local functions.
Signed-off-by: Masami Hiramatsu
Cc: Jim Keniston
Cc: H. Peter Anvin
Cc: Ananth N Mavinakayanahalli
Cc: Avi Kivity
Cc: Andi Kleen
Cc: Christoph Hellwig
Fix a format typo in kprobe-tracer.
Currently, it shows 'tsize' in format;
$ cat /debug/tracing/events/kprobes/event/format
...
field: unsigned long ip;offset:16;tsize:8;
field: int nargs; offset:24;tsize:4;
...
This should be '\tsize';
$ cat /debug/tracing/events
Check some awk features which old mawk doesn't support.
Signed-off-by: Masami Hiramatsu
Cc: Jim Keniston
Cc: H. Peter Anvin
Cc: Ananth N Mavinakayanahalli
Cc: Avi Kivity
Cc: Andi Kleen
Cc: Christoph Hellwig
Cc: Frank Ch. Eigler
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jason Baron
Cc:
Fix x86 instruction decoder selftest to check only .text because other
sections (e.g. .notes) will have random bytes which don't need to be checked.
Signed-off-by: Masami Hiramatsu
Cc: Jim Keniston
Cc: H. Peter Anvin
Cc: Ananth N Mavinakayanahalli
Cc: Avi Kivity
Cc: Andi Kleen
Cc: Christoph
On Mon, Aug 17, 2009 at 12:35:47PM +0300, Avi Kivity wrote:
> On 08/13/2009 08:19 PM, Gleb Natapov wrote:
> >This removes assumptions that max GSIs is smaller than number of pins.
> >Sharing is tracked on pin level not GSI level.
> >
> >Signed-off-by: Gleb Natapov
> >diff --git a/arch/x86/include/a
On Thu, 20 Aug 2009, Paolo Bonzini wrote:
> On 08/20/2009 07:44 PM, Davide Libenzi wrote:
> > On Thu, 20 Aug 2009, Avi Kivity wrote:
> >
> > > On 08/20/2009 07:20 PM, Davide Libenzi wrote:
> > > >
> > > > I briefly looked at this while in vacation, although I did not reply
> > > > hoping the hor
On Fri, Aug 21, 2009 at 12:41 PM, Avi Kivity wrote:
> On 08/21/2009 12:34 AM, Andre Przywara wrote:
>>
>> In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
>> which is the least common denominator of all KVM-capable x86-CPUs
>> (based on Intel Pentium 4 Prescott). It can be
On 08/19/2009 05:18 PM, Orit Wasserman wrote:
Why remove the check? It's still needed (presuming root_gfn refers to
the guest eptp).
Here the root_gfn refers to the L2 guest CR3, which L0 can't check for
validity.
Ok. There must be a similar check for GUEST_CR3 or EPT_POINTER.
--
On 08/21/2009 12:34 AM, Andre Przywara wrote:
In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
which is the least common denominator of all KVM-capable x86-CPUs
(based on Intel Pentium 4 Prescott). It can be used as a base type
for migration.
Typically users will w
[Adding qemu-devel@ since kvm@ is not interested
and since serial port seems to be qemu thing]
Michael Tokarev wrote:
Is it just me with this issue? Anyone who has serial port
working for anything more than serial console (that is, with
control chars etc, not only text) ?
I just ran a quick
Jamie Lokier wrote:
Andre Przywara wrote:
In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
which is the least common denominator of all KVM-capable x86-CPUs
(based on Intel Pentium 4 Prescott). It can be used as a base type
for migration.
The idea is nice and the name
Andre Przywara wrote:
> In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
> which is the least common denominator of all KVM-capable x86-CPUs
> (based on Intel Pentium 4 Prescott). It can be used as a base type
> for migration.
The idea is nice and the name is right, but t
On Thu, Aug 20, 2009 at 04:38:17PM +0300, Michael S. Tsirkin wrote:
> On Thu, Aug 20, 2009 at 03:10:54PM +0200, Arnd Bergmann wrote:
> > On Thursday 20 August 2009, Michael S. Tsirkin wrote:
> > > On Wed, Aug 19, 2009 at 05:27:07PM +0200, Arnd Bergmann wrote:
> > > > On Wednesday 19 August 2009, Mi
To enable cross-vendor migration we use VMCB external variables to hold
the full 64bit value of the SYSENTER MSRs, which get truncated to 32bit
on AMD hardware. Since we didn't intercept these MSRs, these
variables were only used in the emulation case, but were _always_ used
for migration purposes.
Gregory Haskins wrote:
> Ingo Molnar wrote:
>>
>> We all love faster code and better management interfaces and tons
>> of your prior patches got accepted by Avi. This time you didnt even
>> _try_ to improve virtio.
>
> Im sorry, but you are mistaken:
>
> http://lkml.indiana.edu/hypermail/linux/
Avi Kivity:
> On 08/17/2009 05:27 PM, fka...@googlemail.com wrote:
> > I have the ctrl/caps keys swapped by X in xorg.conf:
> >
> > Option "XkbOptions" "ctrl:swapcaps"
> >
> > The fact that this is not honoured by the guest (win2k)
> > might be intended or acceptable.
> >
> > However, when switchi
Is it just me with this issue? Anyone who has serial port
working for anything more than serial console (that is, with
control chars etc, not only text) ?
Thanks!
Michael Tokarev wrote at Sun, 26 Jul 2009 00:09:57 +0400:
Finally, I'm trying to use serial port in a kvm guest.
And as in my previ
Bugs item #2351676, was opened at 2008-11-26 19:59
Message generated for change (Comment added) made by z-image
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2351676&group_id=180599
Please note that this message will contain a full copy of the comment t
Am Donnerstag 20 August 2009 22:56:16 schrieb Christoph Hellwig:
> Currently virtio-blk doesn't set any QUEUE_ORDERED_ flag by default, which
> means it does not allow filesystems to use barriers. But the typical use
> case for virtio-blk is to use a backed that uses synchronous I/O, and in
> that
Bugs item #2841731, was opened at 2009-08-21 00:19
Message generated for change (Tracker Item Submitted) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2841731&group_id=180599
Please note that this message will contain a full copy of the c
On Wednesday, August 19, 2009 4:09 PM Avi Kivity wrote:
> On 08/19/2009 05:14 AM, Xu, Jiajun wrote:
>> I tried this with latest commit, sometimes linux guest can
> do migration with more than 4G memory.
>> But sometimes I found guest will hang after migration and on
> host console it will print "U
Bugs item #2761920, was opened at 2009-04-14 06:10
Message generated for change (Comment added) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2761920&group_id=180599
Please note that this message will contain a full copy of the comment th
Orit,
First, thank you for this work, it's very interesting. I
tried the patchset but met some problem. It's a kernel panic in
L2 guest, and L1 & L0 remains operable:
BUG: unable to handle kernel paging request at 0104b00d
IP: [] math_state_restore+0xe/0x2f
*pde = 0
30 matches
Mail list logo
