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

[Michal Novotny <minovotn@redhat.com>]

On 06/08/2010 01:11 PM, M A Young wrote:
>
> On Tue, 8 Jun 2010, Keir Fraser wrote:
>
>> 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.
>
> 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
Oh, ok, thanks Michael. This way I can now understand why is was not 
working with "/usr/lib64/xen/bin/qemu-dm" but it's working with just 
"qemu-dm" since "qemu-dm" makes the path of "/usr/lib/xen/bin/qemu-dm". 
In 4.1 it's /usr/lib/xen/bin/qemu-dm too. When I tried to list it using 
the `ps aux | grep qemu-dm` it was showing the difference here so if the 
path changed it makes sense now.

Thanks a lot,
Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat