Re: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Rohit Yadav
Thanks, I was already exploring a solution using qemu guest agent since morning today. It just so happened that you also thought of the approach, and I could validate my script to work with qemu ev 2.12 by the end of my day. A proper fix might require some additional changes in

Re: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Marcus
Wow, that was fast. Good work. The script seems to work for me. There was one case where I rebooted the router and got the old link local IP somehow. I'm not sure if that was a timing issue in seeing the existing /var/cache/cloud/cmdline before the new one was written or what, but if it was a

Re: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Rohit Yadav
Hi Marcus, Simon, I explore two of the short term solutions and I've a working (work in progress) script that replaces the patchviasocket script to use the qemu guest agent (that is installed in 4.11+ sytemvmtemplate). This was part of a scoping exercise for solving the patching problem for

Re: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Marcus
Long ago it was a disk. The problem was that these disks had to go somewhere, a place where they could survive migrations, which didn't work well for block based primary storage... at least for the code base at the time. Using virtio socket was seen as a fairly standard way to communicate

Re: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Rohit Yadav
Hi Simon, I'm exploring a solution for the same, I've found that the python based patching script fails to wait for the message to be written on the unix socket before that the socket is closed. I reckon this could be related to serial port device handling related changes in qemu-ev 2.12, as

RE: Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Paul Angus
Hi Simon, We're actually looking at it too right now. The problem seems to be here: https://github.com/apache/cloudstack/blob/4.11/scripts/vm/hypervisor/kvm/patchviasocket.py#L56-L59 s = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) s.connect(sock_file) s.sendall(msg)

Latest Qemu KVM EV appears to be broken with ACS

2019-04-12 Thread Simon Weller
All, After troubleshooting a strange issue with a new lab environment yesterday, it appears that the patchviasocket functionality we rely on for key and ip injection into our router/SSVM/CPVM images is broken with qemu-kvm-ev-2.12.0-18.el7 (January 2019 release). This was tested on Centos 7.6.

AW: Where to start to reuse API integration tests as functional test from CS codebase?

2019-04-12 Thread peter.muryshkin
Hi, Wei Zhou, thank you very much for providing your setup.cfg, I get exactly same error: nosetests: error: Error reading config file 'setup.cfg': File contains no section headers. file: 'setup.cfg', line: 1 '{\n' (I have copied your email to the bash editor "nano") kind regards Peter

Re: Where to start to reuse API integration tests as functional test from CS codebase?

2019-04-12 Thread Wei ZHOU
Hi Peter, Can you check the setup.cfg ? Here is an example of setup.cfg on my platform (kvm). { "zones": [ { "name": "zone118-4", "guestcidraddress": "192.168.10.0/24", "dns1": "8.8.8.8", "physical_networks": [ {

AW: Where to start to reuse API integration tests as functional test from CS codebase?

2019-04-12 Thread peter.muryshkin
Hi, all, the following Dockerfile: https://github.com/pmury/cloudstack/blob/marvin-101/test/integration/Dockerfile.python27 and setup.cfg both adopted, either 1:1 copied from the installation instructions, produces the following error: