[Fedora-xen] fedora 16 with xen balloning.

[Itamar Reis Peixoto]

On Wed, Sep 28, 2011 at 4:32 PM, Itamar Reis Peixoto
<itamar at ispbrasil.com.br> wrote:
> On Wed, Sep 28, 2011 at 4:21 PM, Konrad Rzeszutek Wilk
> <konrad.wilk at oracle.com> wrote:
>> On Wed, Sep 28, 2011 at 04:16:52PM -0300, Itamar Reis Peixoto wrote:
>>> hi.
>>>
>>> I have a fedora 16 with all updates.
>>>
>>> when I run xm mem-set 0 1024 the machines crashes after some seconds.
>>
>> What is the crash (serial log please)? How much memory do you have initially?
>> Does it crash if you have 'dom0_mem=max:2G' on your Xen hypervisor line?
>>
>> Does it crash if you use 'xl mem-set 0 1024'?
>>
>>
>
> [root at localhost ~]# uname -a
> Linux localhost.localdomain 3.1.0-0.rc6.git0.3.fc16.x86_64 #1 SMP Fri
> Sep 16 12:26:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>
> [root at localhost ~]# xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0  3584     4     r-----     40.4
> [root at localhost ~]#
>
>
> [root at localhost ~]# xl mem-set 0 1024
> libxl: error: libxl.c:2114:libxl_set_memory_target cannot get memory
> info from /local/domain/0/memory/static-max
> : No such file or directory
> [root at localhost ~]#
>
>
> had to reboot after xm mem-set 0 1024
>
>

also virt-manager doesn't recognize it as dom0, I see some messages in log

[   22.531841] XENBUS: Unable to read cpu state
[   22.531981] XENBUS: Unable to read cpu state
[   22.532213] XENBUS: Unable to read cpu state
[   22.532350] XENBUS: Unable to read cpu state



-- 
------------

Itamar Reis Peixoto
msn, google talk: itamar at ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)