Re: [Xen-devel] Problem with 2.6.30 pv-ops domU

[Jia Rao <rickenrao@xxxxxxxxx>]

OK, the shrinking is working now. What I do now is to set a large initial memory size.

Another problem is with the newest pv_ops kernel.

I downloaded the xen-unstable, and compiled it under fedora 10.

Dom0 booted fine, but when I cp the dom0 to a domU (what I did in the stable xen release, convert physical to virtual), the domU can boot, but immediately the vcpu(i set to 2) shrinked to 1 vcpu and the cpu was 100% busy there.

ping and xm console returned nothing.

The same thing happened when I install a precompiled pv_ops kernel to my old domUs.
I tried xen 3.3.1 (2.6.18.8 dom0) and xen-unstable(2.6.31.6 dom0), same problem.
So I think the problem should be the pv_ops kernel.

Do I need some special configuration for pv_ops kernel to use as a domU?

Thanks !

On Mon, Nov 30, 2009 at 4:08 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

On 11/29/09 21:36, Jia Rao wrote:
> Hi all,
>
> I downloaded a pre-compiled Fedora 11 domU image from
> http://stacklet.com/downloads/images/list/Fedora
>
> When I ran the domU (2.6.30) with xen 3.3.1, 2.6.18 dom0, there was a
> problem.
>
> I can not change the memory configuration of the domU on the fly. I
> used pygrub to boot the PV guest.
> In the 2.6.30 guest, I can not find the /proc/xen/balloon driver but
> in the config file of the kernel, XEN_BALLOON is enabled.

How were you trying to change the memory?  At present, it only supports
shrinking memory, not expanding it beyond its original size.

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel