Re: patchviasocket seems to be broken with qemu 2.3(+?)

Thursday, 20 October 2016 at 3:29 PM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto: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 package

Re: patchviasocket seems to be broken with qemu 2.3(+?)

Hi, Update: after a reboot of all hosts during the weekend (resulting in reboot of all VMs), the problematic router VM is OK now. Not sure what had caused it. Thanks. On 2016-12-22 14:03, Syahrul Sazli Shaharir wrote: On 2016-12-21 23:26, Linas Žilinskas wrote: At this point I'm not sure

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On 2016-12-21 23:26, Linas Žilinskas wrote: At this point I'm not sure what the issue for you could be. Did you try recreating the failing vrouter? Yes, multiple times by destroying it and/or restarting the network - failed every time. Also, just in case, check if there's free disk space

Re: patchviasocket seems to be broken with qemu 2.3(+?)

At this point I'm not sure what the issue for you could be. Did you try recreating the failing vrouter? Also, just in case, check if there's free disk space on it. We had some vrouters stuck due to this, and i saw another thread here discussing it. Basically the /var/log/ partition fills up,

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On 2016-12-20 17:53, Wei ZHOU wrote: Hi Synhrul, Could you upload the /var/log/cloud.log ? Sure:- Working router VM: http://pastebin.com/hwwk86ve Non-working router VM: http://pastebin.com/G4nv09ab Thanks. -Wei 2016-12-20 3:18 GMT+01:00 Syahrul Sazli Shaharir : On

Re: patchviasocket seems to be broken with qemu 2.3(+?)

Hi Linas, Good to know it. It looks increase the listening time in /etc/init.d/cloud-early-config will fix it (default is 5 times * 2 seconds). -Wei 2016-12-20 9:23 GMT+01:00 Linas Žilinskas : > I don't think the issue is the same. As i mentioned in the original report >

Re: patchviasocket seems to be broken with qemu 2.3(+?)

Hi Synhrul, Could you upload the /var/log/cloud.log ? -Wei 2016-12-20 3:18 GMT+01:00 Syahrul Sazli Shaharir : > On 2016-12-19 18:10, Syahrul Sazli Shaharir wrote: > >> On 2016-12-19 17:03, Linas Žilinskas wrote: >> >>> From the logs it doesn't seem that the script timeouts.

Re: patchviasocket seems to be broken with qemu 2.3(+?)

I don't think the issue is the same. As i mentioned in the original report and my findings afterwards, this is a specifically qemu issue which was fixed in 2.4.0-rc3. The issue was the way qemu exposes the socket to communicate with VM. It didn't queue data, so unless the VM was listening on

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On 2016-12-19 18:10, Syahrul Sazli Shaharir wrote: On 2016-12-19 17:03, Linas Žilinskas wrote: From the logs it doesn't seem that the script timeouts. "Execution is successful", so it manages to pass the data over the socket. I guess the systemvm just doesn't configure itself for some reason.

Re: patchviasocket seems to be broken with qemu 2.3(+?)

Hi Linas, It seems the issue you mentioned has been fixed by the commits for https://issues.apache.org/jira/browse/CLOUDSTACK-2823 CloudStack-agent will try to pass the boot args 30 times if the console Ip is not accessible. Weird. -Wei 2016-12-19 10:03 GMT+01:00 Linas Žilinskas

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On 2016-12-19 17:03, Linas Žilinskas wrote: From the logs it doesn't seem that the script timeouts. "Execution is successful", so it manages to pass the data over the socket. I guess the systemvm just doesn't configure itself for some reason. You are right, I was able to enter the router VM

Re: patchviasocket seems to be broken with qemu 2.3(+?)

From the logs it doesn't seem that the script timeouts. "Execution is successful", so it manages to pass the data over the socket. I guess the systemvm just doesn't configure itself for some reason. Also, in my personal tests, I noticed some different behaviour with different kernels. Don't

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On 2016-12-16 11:27, Syahrul Sazli Shaharir wrote: On Wed, 26 Oct 2016, Linas ?ilinskas wrote: So after some investigation I've found out that qemu 2.3.0 is indeed broken, at least the way CS uses the qemu chardev/socket. Not sure in which specific version it happened, but it was fixed in

Re: patchviasocket seems to be broken with qemu 2.3(+?)

On Wed, 26 Oct 2016, Linas ?ilinskas wrote: So after some investigation I've found out that qemu 2.3.0 is indeed broken, at least the way CS uses the qemu chardev/socket. Not sure in which specific version it happened, but it was fixed in 2.4.0-rc3, specifically noting that CloudStack 4.2

Re: patchviasocket seems to be broken with qemu 2.3(+?)

Hi Linas Thank you for posting the solution, i've seen this issue in my lab env as well. Much appreciated. Regards ilya On 10/26/16 4:44 AM, Linas Žilinskas wrote: > So after some investigation I've found out that qemu 2.3.0 is indeed > broken, at least the way CS uses the qemu chardev/socket.

Re: patchviasocket seems to be broken with qemu 2.3(+?)

So after some investigation I've found out that qemu 2.3.0 is indeed broken, at least the way CS uses the qemu chardev/socket. Not sure in which specific version it happened, but it was fixed in 2.4.0-rc3, specifically noting that CloudStack 4.2 was not working. qemu git commit:

Re: patchviasocket seems to be broken with qemu 2.3(+?)

www.shapeblue.com @shapeblue *From:* Linas Žilinskas <li...@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

Re: patchviasocket seems to be broken with qemu 2.3(+?)

--upgrade argparse See, if this fixes the issue. Regards. From: Linas Žilinskas <li...@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.

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