From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Mon, 07 Jun 2010 17:00:31 +0200 Message-ID: <4C0D098F.9070905@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/07/2010 03:46 PM, Keir Fraser wrote: > On 07/06/2010 14:36, "Michal Novotny" wrote: > > >> For HVM guests it's: >> >> # xm create rhel5-32fv >> Using config file "./rhel5-32fv". >> Error: Not enough memory is available, and dom0 cannot be shrunk any further >> >> and also the xend.log fragment relevant to the issue: >> > Try no-tmem on Xen command line. > > -- Keir > > > Keir, I did try: title Red Hat Enterprise Linux Server (2.6.31.13-xen HV, nolog) root (hd1,6) kernel /xen-4.1-unstable.gz no-tmem module /vmlinuz-2.6.31.13 ro root=LABEL=/rhel2 rhgb quiet selinux=0 module /initrd-2.6.31.13.img and I was even unable to do `xm list` because of the issue with memory and also I found out that it's not working when I reboot the system and even when I put modprobe for xen-evtchn to xend init script so I need to `modprobe xen-evtchn` manually, then run xenstore daemon and then restart the xen daemon. Also, the /var/log/xen/xend.log file is completely empty and I am now unable to see what's going on and I cannot run `xm list` at all so it was working a little until I restarted but I'm having many issues here. Michal -- Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat