> >> 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?
^^^^^^^^^^^^^^^
Did that make a change?
> >>
> >> Does it crash if you use 'xl mem-set 0 1024'?
> >>
> >>
> >
> > [root@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@localhost ~]# xm list
> > Name ID Mem VCPUs State Time(s)
> > Domain-0 0 3584 4 r----- 40.4
> > [root@localhost ~]#
> >
> >
> > [root@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
Ok, did 'xl list' show a new value? What does this command give you:
find /sys -name target_kb | xargs cat
> > [root@localhost ~]#
> >
> >
> > had to reboot after xm mem-set 0 1024
Why?Did it crash? Was it running to slow? If you ran:
while (true)
do
xl list | grep Domain-0
done
Did you see the numbers go up/down? Can you be more specific please?
> >
> >
>
> also virt-manager doesn't recognize it as dom0, I see some messages in log
Hm, as in.. you can't see Xen in it? If so, we need to rope in the
Xen libvirt expert from Novell. Can you send another email with details
and I will (once I recall his name) CC him.
>
> [ 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
Ok, those are a different issue - and you can ignore that.
>
>
>
> --
> ------------
>
> Itamar Reis Peixoto
> msn, google talk: itamar@xxxxxxxxxxxxxxxx
> +55 11 4063 5033 (FIXO SP)
> +55 34 9158 9329 (TIM)
> +55 34 8806 3989 (OI)
> +55 34 3221 8599 (FIXO MG)
--
xen mailing list
xen@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/xen
