All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Shuklin <george.shuklin@gmail.com>
To: sandr8@gmail.com
Cc: xen-devel@lists.xensource.com
Subject: Re: a ton of kernel issues
Date: Tue, 13 Dec 2011 14:36:04 +0400	[thread overview]
Message-ID: <4EE72A94.6040904@gmail.com> (raw)
In-Reply-To: <CAJeBh4sxdNTxM_oLFAuA6Mw75=LaYysrpS5b8NsZMbkf_swNVw@mail.gmail.com>

On 13.12.2011 14:19, Alessandro Salvatori wrote:
>
>> pv_ops is still have some issues with memory limits, but any
>> new kernel (3.0+) will boot normal and operates with very
>> minor glitches. Older pv_ops (f.e. debian 2.6.32) have some
>> more major issues.
> what glitches should one expect with 3.0+, and having the choice,
> would it be better to go with 3.1 or even 3.2?
>
>
Right now I know about two of them:
When you set up memory for virtual machine using xenballon, value in 
dom0 differ from value in domU. The issue is that -xen kernels 'hide' 
some memory in 'used' memory, and pv-ops just reducing TotalMem to value 
without that memory. Practically that means if you set up memory for 
domain to 2GiB client will saw only 1.95GiB and so on.

The second issue is lack of support of 'pre-inflated balloon', means you 
can not set up memory-static-max to 2GiB, target to 1GiB and do 'memory 
grow' from 1 G to 2 G latter without VM reboot. -xen kernels allow this 
(up to memory-static-max limit).

  reply	other threads:[~2011-12-13 10:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 21:44 a ton of kernel issues Tim Evers
2011-12-12 21:56 ` Konrad Rzeszutek Wilk
2011-12-14  9:00   ` Tim Evers
2011-12-15  1:25     ` Konrad Rzeszutek Wilk
2011-12-13  9:09 ` George Shuklin
2011-12-13 10:19   ` Alessandro Salvatori
2011-12-13 10:36     ` George Shuklin [this message]
2011-12-13 13:17       ` David Vrabel
2011-12-13 13:37         ` Ian Campbell
2011-12-13 20:59           ` George Shuklin
2011-12-13 22:30             ` Ian Campbell
2011-12-13 22:53               ` George Shuklin
2011-12-14  7:25                 ` Ian Campbell
2011-12-14 12:16                   ` Ian Campbell
2011-12-14 12:21                     ` David Vrabel
2011-12-14 13:11                     ` Jan Beulich
2011-12-14 13:48                       ` Ian Campbell
2011-12-14 17:44                     ` Konrad Rzeszutek Wilk
2011-12-15 12:45                     ` George Shuklin
2011-12-15 16:26                       ` Konrad Rzeszutek Wilk
2011-12-13 21:05         ` George Shuklin
2011-12-13 21:45           ` Konrad Rzeszutek Wilk
2011-12-14 12:28             ` David Vrabel
2011-12-14 16:57               ` Konrad Rzeszutek Wilk
2011-12-14  7:47           ` Fajar A. Nugraha
2011-12-14 18:40             ` George Shuklin
2011-12-13 14:18       ` Konrad Rzeszutek Wilk
2011-12-13 21:10         ` George Shuklin
2011-12-13 21:38           ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE72A94.6040904@gmail.com \
    --to=george.shuklin@gmail.com \
    --cc=sandr8@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.