action #32593
closedMultiple ttySx consoles for qemu
Description
For some testing it could be useful to have a possibility to create some more ttyS devices.
Would it be useful to have another variable, say MSERIALDEV, where test writer could specify how many ttyS devices he or she needs?
Or would it be better to play with SERIALDEV, so it could do the job of starting more than one ttyS devices?
Updated by okurz about 6 years ago
- Category set to Feature requests
The variable "SERIALDEV" is used only to note how the device is called within 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.
Updated by sebchlad about 6 years ago
- Status changed from Feedback to In Progress
- Target version set to 448
Updated by coolo about 6 years ago
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.
Updated by sebchlad about 6 years ago
- Related to action #32968: [kernel][tools] Refactor QEMU backend - Create QEMU process manager and save configuration state added
Updated by sebchlad about 6 years ago
Conman service is using ttyS so does openQA connecting to quemu vm, so Anton was blocked with his HPC test.
Updated by sebchlad about 6 years ago
@Anton: given Richie work and your changes to the conman test I would suggest closing this ticket (ufff I worked so hard on this ;) ).
Updated by sebchlad about 6 years ago
- Status changed from In Progress to Rejected
Updated by rpalethorpe about 6 years ago
- Target version changed from 448 to Done