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: Tue, 08 Jun 2010 12:54:54 +0200 Message-ID: <4C0E217E.4050108@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/08/2010 12:53 PM, Keir Fraser wrote: > On 08/06/2010 11:04, "Michal Novotny" 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 > > > Ok, I did use some HVM example configuration file from the examples in the repo so I was able to make it working. Michal -- Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat