On Wed, Nov 26, 2008 at 11:14:51AM -0700, Jim Fehlig wrote:
> Daniel P. Berrange wrote:
> > On Fri, Nov 21, 2008 at 11:13:04PM +0100, Guido G?nther wrote:
> >
> >> Hi,
> >> I just ran across these oddities when using a bit more libvirt+xen:
> >>
> >> 1.) virsh setmaxmem:
> >>
> >> On a running d
Daniel P. Berrange wrote:
> On Fri, Nov 21, 2008 at 11:13:04PM +0100, Guido G?nther wrote:
>
>> Hi,
>> I just ran across these oddities when using a bit more libvirt+xen:
>>
>> 1.) virsh setmaxmem:
>>
>> On a running domain:
>> # virsh setmaxmem domain 256000
>> completes but virsh dumpx
On Tue, Nov 25, 2008 at 11:39:57AM +, Daniel P. Berrange wrote:
> On Fri, Nov 21, 2008 at 11:13:04PM +0100, Guido G?nther wrote:
> > Hi,
> > I just ran across these oddities when using a bit more libvirt+xen:
> >
> > 1.) virsh setmaxmem:
> >
> > On a running domain:
> > # virsh setmax
On Fri, Nov 21, 2008 at 11:13:04PM +0100, Guido G?nther wrote:
> Hi,
> I just ran across these oddities when using a bit more libvirt+xen:
>
> 1.) virsh setmaxmem:
>
> On a running domain:
> # virsh setmaxmem domain 256000
> completes but virsh dumpxml as well as the config.sxp still show
Hi,
I just ran across these oddities when using a bit more libvirt+xen:
1.) virsh setmaxmem:
On a running domain:
# virsh setmaxmem domain 256000
completes but virsh dumpxml as well as the config.sxp still shows the
old amount of memory. Looks as the set_maxmem hypercall simply gets
ignor
