Skip to content
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

Unable to boot 100 clickos instances #34

Open
stevepp opened this issue Sep 11, 2016 · 7 comments
Open

Unable to boot 100 clickos instances #34

stevepp opened this issue Sep 11, 2016 · 7 comments

Comments

@stevepp
Copy link

stevepp commented Sep 11, 2016

Recently I have been trying to sequentially boot ClickOS. I can not even create 100 clickos instances.
Starting the 82nd instance, when I try to used clickos-ctl to install a click configuration I got the error "Domain clickos82 does not seem to be a ClickOS domain".

My host has 16GB RAM and 8-core cpu. So in my experiment I fixed 4GB RAM for Xen Dom0 and pin cpus cores 0-2 to Dom0. For each ClickOS vm, I use "xl" to create the vm and then use clickos-ctl to install the configuration.

Does anyone experience the same problem or have any idea what may have caused it?

@fmanco
Copy link

fmanco commented Sep 12, 2016

To indentify a domain as a ClickOS guest, clickos-ctl checks for the existence of /local/domain/<id>/data/clickos. This entry is created by a ClickOS domain upon boot.

What might be happening here is that the guests are booting slower after a certain point and the entry is not there yet. Have you tried wainting and then run clickos-ctl again?

If that doesn't work you need to provide more information. Namely the output of xl console <guest_82> and xenstore-ls /local/domain/<id_guest_82>.

@stevepp
Copy link
Author

stevepp commented Jan 13, 2017

Sorry to reply so late.

Yes, I have tried waiting and then run clickos-ctl again. I checked the output of "xl console guest_82" and could see that the main thread has been created. Then checked the output of "xenstore-ls /local/domain/<id_guest_82>". The entry "/local/domain/82/data/clickos" does have been created.

@fmanco
Copy link

fmanco commented Jan 20, 2017

So, to clarify: even though /local/domain/82/data/clickos exists at the time you run clickos-ctl, it still fails?

@stevepp
Copy link
Author

stevepp commented Jan 20, 2017

Yes, correct. But the weird thing is if I change the domain name from like "ClickOS82" to "p82" in the domain configuration file, then this error message is gone. Do you know why this happens?

@fmanco
Copy link

fmanco commented Jan 20, 2017

Interesting... What is the exact clickos-ctl command you use? Do you use a domain name? Maybe I have a bug in the domain name to domain id conversion code.

@stevepp
Copy link
Author

stevepp commented Jan 20, 2017

Here is the command I used to install a click configuration:

"clickos install -s clickos82 clickos82.click"

I guess so. There might be some bug in the code that converts domain name to domain ID.

@fmanco
Copy link

fmanco commented Jan 20, 2017

Can you give the output of strace -s 512 clickos install -s clickos82 clickos82.click?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants