From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Problem with 2.6.30 pv-ops domU Date: Mon, 30 Nov 2009 16:25:04 -0800 Message-ID: <4B146260.7070205@goop.org> References: <994429490911292136o39c37116m7761de6f647b363d@mail.gmail.com> <4B143431.2040804@goop.org> <994429490911301344s761d245bs2fd2f4f8bf57aa24@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <994429490911301344s761d245bs2fd2f4f8bf57aa24@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jia Rao Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 11/30/09 13:44, Jia Rao wrote: > 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. What do you mean by "shrinked to 1"? > 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. What happens if you run with one vcpu? What messages are printed when it boots? Any? Do you have "earlyprintk=xen" on the kernel command line? Does it respond to sysrq? Can you get any info about the domain with xenctx? > Do I need some special configuration for pv_ops kernel to use as a domU? No. J