https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-03-01T13:20:09ZopenSUSE Project Management ToolopenQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=973572018-03-01T13:20:09Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li></ul><p>The variable "SERIALDEV" is used only to note how the device is called <em>within</em> the sut so I think MSERIALDEV is a misleading name. I suggest to have a variable NUMSERIALS (equivalent to NUMDISKS) as integer value to note down how many serial devices you want to have. Btw, backend/qemu.pm line 568 is most likely the line you want to take a look into.</p>
openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1093902018-04-04T08:30:08Zsebchladsebastian.chlad@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li><li><strong>Target version</strong> set to <i>448</i></li></ul> openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1093932018-04-04T08:35:04Zcoolocoolo@suse.com
<ul></ul><p>I wonder what these ttySx consoles are supposed to do. If you hard code qemu environment in your tests anyway, you can do fancy things within them.</p>
openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1106562018-04-09T13:18:50Zsebchladsebastian.chlad@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child parent" href="/issues/32968">action #32968</a>: [kernel][tools] Refactor QEMU backend - Create QEMU process manager and save configuration state</i> added</li></ul> openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1106652018-04-09T13:20:58Zsebchladsebastian.chlad@suse.com
<ul></ul><p>Conman service is using ttyS so does openQA connecting to quemu vm, so Anton was blocked with his HPC test.</p>
openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1136682018-04-18T11:28:53Zsebchladsebastian.chlad@suse.com
<ul></ul><p>@Anton: given Richie work and your changes to the conman test I would suggest closing this ticket (ufff I worked so hard on this ;) ).</p>
openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1136742018-04-18T11:31:17Zasmorodskyi
<ul></ul><p>@Seba +1</p>
openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1136772018-04-18T11:32:53Zsebchladsebastian.chlad@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Rejected</i></li></ul> openQA Project - action #32593: Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/32593?journal_id=1160282018-04-26T09:26:51Zrpalethorperichard.palethorpe@suse.com
<ul><li><strong>Target version</strong> changed from <i>448</i> to <i>Done</i></li></ul>