[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Problem with 2.6.30 domU
- To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
- From: Jia Rao <rickenrao@xxxxxxxxx>
- Date: Mon, 30 Nov 2009 00:29:51 -0500
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Sun, 29 Nov 2009 21:30:34 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eys4dYZ51oBTgVx8BcK9DAkCM0kIvNzqUdAbHSYGjoM2h58AbN+WeNuzZjJ2pjv/q2 wEj2x23JE6T4wM0S0xwA3J+Mv0suRLd2K6EEHkoeTg5B0znUPp35BLkIhVN7+VmAB5LN OoAYfHXNAbSLBj2EaRpbsfcYRytgQh8BwAmnY=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
In domUï I tried to compile the newest 2.6.31.6 kernel.
It can not boot. I configured the domU to be 4 vcpu, but shortly after creation the domU was shrinked to 1 vcpu and the cpu seemed to be 100% busy from xm top.
can not ping or xm console to the domU.
On Mon, Nov 30, 2009 at 12:23 AM, Jia Rao <rickenrao@xxxxxxxxx> wrote:
Wowï any workaroundïOn Mon, Nov 30, 2009 at 12:19 AM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
On Mon, Nov 30, 2009 at 12:13 PM, Jia Rao < rickenrao@xxxxxxxxx> wrote:
> When I ran the domU (2.6.30) with xen 3.1, 2.6.18 dom0, there was a problem.
>
> I can not change the memory configuration of the domU on the fly.
short recap of what I found so far of various kernel when used as PV domU:
kernel 2.6.18:
- can change memory/CPU on the fly, with the correct domU config
- can live migrate
suse's kernel-xen (I use 2.6.29):
- can change memory/CPU on the fly
- can't migrate (to be exact: "xm save" part failed)
pv_ops (including Fedora and Ubuntu's kernel):
- can't change memory/CPU on the fly (you can shrink, but you can't grow)
- can't migrate
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
