Re: [Xen-devel] [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling

[M A Young <m.a.young@xxxxxxxxxxxx>]

On Tue, 8 Jun 2010, Keir Fraser wrote:

> On 08/06/2010 11:04, "Michal Novotny" <minovotn@xxxxxxxxxx> 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.
qemu-dm was at /usr/lib64/xen/bin/qemu-dm in 3.4 on 64-bit builds but for 
some reason it moved to /usr/lib/xen/bin/qemu-dm in 4.0 and presumably 4.1.
        Michael Young

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