cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Linas Žilinskas <li...@host1plus.com>
Subject Re: patchviasocket seems to be broken with qemu 2.3(+?)
Date Thu, 20 Oct 2016 13:30:40 GMT
Nope, we're using CentOS 7 with python 2.7.


And the script itself seems to work, it just gets stuck when trying to 
connect to the socket ( s.connect(..) )



On 2016-10-20 12:38, Rohit Yadav wrote:
> If you're using CentOS6 based KVM hosts, can you make sure you've 
> argparse installed? The patchviasocket script was changed from perl 
> based implementation to a Python based installation that uses a 
> library that is not available with Python 2.6.
>
> Try this on kvm host(s):
> sudo pip install --upgrade argparse
>
> See, if this fixes the issue.
>
> Regards.
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
> ------------------------------------------------------------------------
> *From:* Linas Žilinskas <linas@host1plus.com>
> *Sent:* 20 October 2016 15:29:08
> *To:* dev@cloudstack.apache.org
> *Subject:* patchviasocket seems to be broken with qemu 2.3(+?)
>
> Hi.
>
> We have made an upgrade to 4.9.
>
> Custom build packages with our own patches, which in my mind (i'm the 
> only one patching those) should not affect the issue i'll describe.
>
> I'm not sure whether we didn't notice it before, or it's actually 
> related to something in 4.9
>
> Basically our system vm's were unable to be patched via the qemu 
> socket. The script simply error'ed out with a timeout while trying to 
> push the data to the socket.
>
> Executing it manually (with cmd line from the logs) resulted the same. 
> I even tried the old perl variant, which also had same result.
>
> So finally we found out that this issue happens only on our HVs which 
> run qemu 2.3.0, from the centos 7 special interest virtualization 
> repo. Other ones that run qemu 1.5, from official repos, can patch the 
> system vms fine.
>
> So i'm wondering if anyone tested 4.9 with kvm with qemu >= 2.x? Maybe 
> it something else special in our setup. e.g. we're running the HVs 
> from a preconfigured netboot image (pxe), but all of them, including 
> those with qemu 1.5, so i have no idea.
>
>
> Linas Žilinskas
> Head of Development
> website <http://www.host1plus.com/> facebook 
> <https://www.facebook.com/Host1Plus> twitter 
> <https://twitter.com/Host1Plus> linkedin 
> <https://www.linkedin.com/company/digital-energy-technologies-ltd.>
>
> Host1Plus is a division of Digital Energy Technologies Ltd.
>
> 26 York Street, London W1U 6PZ, United Kingdom
>

Linas Žilinskas
Head of Development
website <http://www.host1plus.com/> facebook 
<https://www.facebook.com/Host1Plus> twitter 
<https://twitter.com/Host1Plus> linkedin 
<https://www.linkedin.com/company/digital-energy-technologies-ltd.>

Host1Plus is a division of Digital Energy Technologies Ltd.

26 York Street, London W1U 6PZ, United Kingdom


Mime
View raw message