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.
You cannot simply boot a normal setup using a hypervisor. The virtual hardware presented is different, the NIC MACs will change... it's just not something to be done, and this is not what virtualization is intended for.
I can't see any reason why you would want to do it
If you had read the URLs I supplied (and the links therefrom) you will see that you *can* boot an existing setup using a hypervisor - with limitations. It *is* possible to make the existing installation aware of the differences in the virtual hardware, or adjust these - including the NIC MAC. I admit - it's not simple - but it can be done, according to these postings.
Why would I want to do it?
Because I have an IBM desktop with the usual arrangement of recovery OS supplied on a protected partition. I don't have a full set of installation CDs, so I can't use my method 1.
Because very comprehensive and useful software for maintaining the system, including updating the BIOS, is included with the machine - but it only runs under native Windows.
Because before I commit totally, I need to ensure that all of my attached devices (USB etc.) and applications will work in the virtual space - currently they don't and I have to reboot. Which is a pain.
If you had read the URLs I supplied (and the links therefrom) you will see that you *can* boot an existing setup using a hypervisor - with limitations. It *is* possible to make the existing installation aware of the differences in the virtual hardware, or adjust these - including the NIC MAC. I admit - it's not simple - but it can be done, according to these postings.
Why would I want to do it?
Because I have an IBM desktop with the usual arrangement of recovery OS supplied on a protected partition. I don't have a full set of installation CDs, so I can't use my method 1.
Because very comprehensive and useful software for maintaining the system, including updating the BIOS, is included with the machine - but it only runs under native Windows.
Because before I commit totally, I need to ensure that all of my attached devices (USB etc.) and applications will work in the virtual space - currently they don't and I have to reboot. Which is a pain.
Mike G.
If you want to discuss this, open a new thread, lets leave this one clean of offtopic discussions
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
