[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
From: Jia Rao <rickenrao@xxxxxxxxx>
Date: Mon, 30 Nov 2009 00:36:53 -0500
Delivery-date: Sun, 29 Nov 2009 21:37:16 -0800
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YxACkMGIOQlHl+hjADO3xpqfJ4b69+Scews++yZ0TyRRkZmBf4ftPrIKabHa1cBbbs FajD4BZF3jMjXnErUj/bLiZIaczMh7dgmiJVkz9Qw6GlAEzMlg7Hmhs+dY/LmXDrHZU1 cdYHevDP2iCCqb/zFOFIzRVioQ21HlREGP/vA=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.

Any ideas?

Thanks.

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

Follow-Ups:
- Re: [Xen-devel] Problem with 2.6.30 pv-ops domU
  - From: Jeremy Fitzhardinge

Prev by Date: [Xen-devel] RE: Intel IOMMU: Assigning IGD device: 00:02.1 on some machines, causes Xen to freeze for >2mins because of RMRR mappings
Next by Date: [Xen-devel] [PATCH] xen: cleanup for xen_pv_domain()/xen_hvm_domain()
Previous by thread: [Xen-users] Xen Pv-Ops DomU Virtualization Support for ChromiumOS64
Next by thread: Re: [Xen-devel] Problem with 2.6.30 pv-ops domU
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.