<div class="gmail_quote">On Wed, Sep 28, 2011 at 3:11 PM, Itamar Reis Peixoto <span dir="ltr"><<a href="mailto:itamar@ispbrasil.com.br">itamar@ispbrasil.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Sep 28, 2011 at 4:32 PM, Itamar Reis Peixoto<br>
<<a href="mailto:itamar@ispbrasil.com.br">itamar@ispbrasil.com.br</a>> wrote:<br>
> On Wed, Sep 28, 2011 at 4:21 PM, Konrad Rzeszutek Wilk<br>
> <<a href="mailto:konrad.wilk@oracle.com">konrad.wilk@oracle.com</a>> wrote:<br>
>> On Wed, Sep 28, 2011 at 04:16:52PM -0300, Itamar Reis Peixoto wrote:<br>
>>> hi.<br>
>>><br>
>>> I have a fedora 16 with all updates.<br>
>>><br>
>>> when I run xm mem-set 0 1024 the machines crashes after some seconds.<br></div></blockquote><div><br>xm mem-set 0 1536<br>worked fine for me.<br>(My KDE workstation, so 1024 is too little RAM to do day-job :-)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
>><br>
>> What is the crash (serial log please)? How much memory do you have initially?<br>
>> Does it crash if you have 'dom0_mem=max:2G' on your Xen hypervisor line?<br>
>><br>
>> Does it crash if you use 'xl mem-set 0 1024'?<br>
>><br>
>><br>
><br>
> [root@localhost ~]# uname -a<br>
> Linux localhost.localdomain 3.1.0-0.rc6.git0.3.fc16.x86_64 #1 SMP Fri<br>
> Sep 16 12:26:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux<br>
><br>
> [root@localhost ~]# xm list<br>
> Name ID Mem VCPUs State Time(s)<br>
> Domain-0 0 3584 4 r----- 40.4<br>
> [root@localhost ~]#<br>
><br>
><br>
> [root@localhost ~]# xl mem-set 0 1024<br>
> libxl: error: libxl.c:2114:libxl_set_memory_target cannot get memory<br>
> info from /local/domain/0/memory/static-max<br>
> : No such file or directory<br>
> [root@localhost ~]#<br>
><br>
><br>
> had to reboot after xm mem-set 0 1024<br></div></blockquote><div><br>You previously said crash - which is it? They are two different things.<br>Did you wait a fair amount of time? <br>Check for disk activity? It may just need some swapping...<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
also virt-manager doesn't recognize it as dom0, I see some messages in log<br></div>
<br>
[ 22.531841] XENBUS: Unable to read cpu state<br>
[ 22.531981] XENBUS: Unable to read cpu state<br>
[ 22.532213] XENBUS: Unable to read cpu state<br>
[ 22.532350] XENBUS: Unable to read cpu state<br>
<br></blockquote><div class="h5"> <br>virt-manager does not log to messages, so those two things are unrelated. <br>What happens when you try virt-manager?<br>What is in /root/.virt-manager/virt-manager.log?<br><br>jerry<br>
</div></div><br>