Re: Lauch UOS without blocking current terminal
Geoffroy Van Cutsem
I am not well versed on CI tools and how they work. Our CI team is in China, and hence on holiday this week.
Do you have full control of your test image? If so, you could build it so that it does not ask for a password, and/or run the tests automatically (via a system service file for example).
From: acrn-users@... <acrn-users@...> On Behalf Of Pan, Fengjunjie
Sent: Friday, October 1, 2021 2:00 pm
Subject: Re: [acrn-users] Lauch UOS without blocking current terminal
Thank you for your reply.
We would like to use CI tools to start UserVM in background and then run some tests there.
Thank you and best regards,
There is no option to provide the user name and credentials for the User VM OS in the launch script. However, I believe there are ways to set-up the OS to auto-login for a specific user. But can you tell me a bit more about what you want to achieve? I’m wondering why you would want to be automatically logged in?
I have not played with this yet but I think you should be able to modify the “-s 5,virtio-console,@stdio:stdio_port” line in your launch script to redirect this elsewhere (e.g. PTY) – see also https://projectacrn.github.io/latest/developer-guides/hld/virtio-console.html
In the service VM, we launch an User VM with its launch file. In the console version, the standard way is that we need to use the user name and password to log in the system.
Is there any other option to directly write these information (user name and password ) inside the launch file, so that no additional manual step is required. Or How can we put the program in the background, and use the same terminal for launching the second User VM.
Thank you for support in advance.