Hi,
I was investigating the behaviour of the -s option and I'm not sure if the
behaviour of xs_open() is exactly as
intended. In my case I am running xenstored in the dom0. Running a strace on
xenstore-read with/without the -s
option shows the tool always using xenstore socket. The flag whi
Hi,
We are migrating from xen 4.4 to xen 4.8. At the moment we boot our
system with a xen command line that includes
"dom0_mem=8192m,min:1728m,max:8192m". We have autoballoon of dom0
disabled in xl.conf and instead call xl mem-set 0 to
change the dom0 memory allocation. (We shrink before
On Wed, Oct 11, 2017 at 05:00:45PM +0100, Wei Liu wrote:
> On Tue, Oct 10, 2017 at 04:03:32PM +0100, James Dingwall wrote:
> > Hi,
> >
> > We are migrating from xen 4.4 to xen 4.8. At the moment we boot our system
> > with a xen command line that includes "do
Hi,
>From xl.cfg(5):
maxmem=MBYTES
Specifies the maximum amount of memory a guest can ever see. The
value of maxmem= must be equal or greater than memory=.
In combination with memory= it will start the guest "pre-ballooned",
if the values of memory= and maxmem= differ.
On Tue, Aug 15, 2017 at 05:36:52AM +0100, James Dingwall wrote:
> Hi,
>
> From xl.cfg(5):
>
> maxmem=MBYTES
>Specifies the maximum amount of memory a guest can ever see. The
> value of maxmem= must be equal or greater than memory=.
>
>In
Hi,
I am trying to migrate my domU instances from v4.1.44 to v4.4.88 and it
seems that whether or not e820_host = 1 in the domU configuration is the
cause of the following stack trace. Please note I have #define MC_DEBUG
1 in arch/x86/xen/multicall.c so the failed hypervisor call is logged.
Hi,
I am trying to use the libxl python bindings but having mixed levels of
success. I assume that the current
status of this is unsupported as the build of the xl.so is disabled by default
but perhaps completing the
missing parts could be quite trivial? I have managed to enabled the build w
Hi,
I am trying to get a nested virtualisation environment working where it is
started with bios='ovmf'. When my
hvm configuration is bios='seabios' and I use the xen.gz everything starts
correctly. Using the xen.efi from
the same build when bios='ovmf' causesthe guest Linux kernel to block
On Fri, Sep 04, 2015 at 03:17:38AM -0600, Jan Beulich wrote:
> >>> On 04.09.15 at 10:47, wrote:
> > I am trying to get a nested virtualisation environment working where it is
> > started with bios='ovmf'. When my
> > hvm configuration is bios='seabios' and I use the xen.gz everything starts
>
On Fri, Sep 04, 2015 at 06:06:30AM -0600, Jan Beulich wrote:
> >>> On 04.09.15 at 13:35, wrote:
> > I was worried about spamming the list by sending the full logs but if that
> > is likely to have the most useful
> > information then here we go...
>
> And indeed not all of it would have been ne
10 matches
Mail list logo
