Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
starting on boot is *NOT* starting when a user logs in, they are TOTALLY different things. A user will often never log in to a server after it's booted.
Looks pretty basic to me. As above you have to choose why and how you need to use it but the script seems like it should work. Might ask that in coding section, they do this all the time and it might be a better place for your question.
Every operating-system has the ability to start "services" (a.k.a. "daemons") at boot-time, and you can define your VM as a "service."
Conceptually, you should define a new user-id and group on your Linux box which is "what the VM service-processes run in," and you set up the service definition (in whatever way is appropriate for your particular distro) so that the KVM process is launched under that user-id automagically at startup. You'll need to arrange for logging messages to be recorded (and probably to be handled by "logrotate"), just as with any other service.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.