From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image
	file handling
Date: Tue, 8 Jun 2010 11:53:34 +0100
Message-ID: <C833DFBE.1702D%keir.fraser@eu.citrix.com>
References: <4C0E15C7.9020606@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4C0E15C7.9020606@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Michal Novotny <minovotn@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 08/06/2010 11:04, "Michal Novotny" <minovotn@redhat.com> wrote:

> I also tried to decrease the memory for dom0 as advised on the list
> (using the `xm mem-set 0 2048`) but still the same result but I saw
> something in the qemu-dm log file about -vcpu-avail option is invalid:
> 
> # cat /var/log/xen/qemu-dm-rhel5-32fv.log
> domid: 1
> qemu: the number of cpus is 1
> /usr/lib64/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
> #

Stale qemu-dm binary hanging around, perhaps. I find that kind of thing
happens when trying out different version sof Xen on a single test system.
Either your new qemu-dm binary did not get installed, or it did but in a
different location to the stale one, and it happens that the stale one
dominates.

In particular, Xen 3.4 qemu does not support the -vcpu_avail cmdline option,
but 4.0 and 4.1 (unstable) do. And 4.0/4.1 xend depends on that.

 -- Keir