-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows starts after 20/30 seconds after container has been started #25
Comments
As I can see everything is working correctly. Performance depends on
hardware and resources available for the container. Please note that qemu
starts virtual machine with windows it takes some time, 20 sec is good
result...
вс, 24 нояб. 2019 г., 12:53 Toni Moreno <[email protected]>:
… Hi @everybody <https://github.com/everybody> I'm running windows image as
described in this repo ( rigth now outside selenoid running command with a
CI/CD tool) and recording with selenoid/video-recorder, I've noted that
qemu starts too late as you can see in this video.
VIDEO
<https://drive.google.com/file/d/11sPQYxd2xXJC8TaQi1BYeMwJqmZE_GA5/view?usp=sharing>
When the CI/CD tool execute docker with windows image this output is shown.
Waiting xvfb...
--- x11vnc loop: 1 ---
--- x11vnc loop: waiting for: 30
PORT=5900
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: TSC frequency mismatch between VM (1992000 kHz) and host (2194710 kHz), and TSC scaling unavailable
qemu-system-x86_64: warning: TSC frequency mismatch between VM (1992000 kHz) and host (2194710 kHz), and TSC scaling unavailable
qemu-system-x86_64: warning: guest updated active QH
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25?email_source=notifications&email_token=AAKY23NAAUVJ7EDAMUDEH43QVJFHZA5CNFSM4JQ6JMYKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3TVNOQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKY23IP3NUS2HBDD2AKTIDQVJFHZANCNFSM4JQ6JMYA>
.
|
Hi @aandryashin , thank you for the fast response. I've been comparing with my laptop where vm start takes 1 or 2 seconds... is because of that I believed that is not as good result as you say. Anyway I was wondering about "TSC frequency " errors , and if this could impact on the vm start time and if there is any way to accelerate with the docker run command or qemu parameters. |
I never seen that vm starts in one second, especially on laptop... Those
warnings are about cpu capabilities, you can play with qemu options to
enable/disable some of them...
вс, 24 нояб. 2019 г., 20:15 Toni Moreno <[email protected]>:
… Hi @aandryashin <https://github.com/aandryashin> , thank you for the fast
response.
I've been comparing with my laptop where vm start takes 1 or 2 seconds...
is because of that I believed that is not as good result as you say. Anyway
I was wondering about "TSC frequency " errors , and if this could impact on
the vm start time and if there is any way to accelerate with the docker run
command or qemu parameters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25?email_source=notifications&email_token=AAKY23MJZLZ7FGDGTCJBOATQVKZBVA5CNFSM4JQ6JMYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFAQE3A#issuecomment-557908588>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKY23LB6PMY7WZKO7IXRB3QVKZBVANCNFSM4JQ6JMYA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @everybody I'm running windows image as described in this repo ( rigth now outside selenoid running command with a CI/CD tool) and recording with selenoid/video-recorder, I've noted that qemu starts too late as you can see in this video.
VIDEO
When the CI/CD tool execute docker with windows image this output is shown.
The text was updated successfully, but these errors were encountered: