Virtual Machine (dual-boot) application WITHOUT new installation
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this 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.
Virtual Machine (dual-boot) application WITHOUT new installation
I'm looking for a linux application that acts like a virtual machine, but not apps like VMware where you have to install a new copy of the OS.
I've installed Fedora11 on one hard drive and Windows XP on another. I want to boot up in Linux, open a virtual machine app and boot XP ALREADY installed on my second hdd (without the need to reinstall XP -- like in VMware).
Well, since the VM has a different set of hardware than your "real" machine because, after all, if more than one driver was used to access, e.g., a disk drive, the poor drive would quickly become confused. What you're proposing would entail your Linux system drivers and your Windows system driver both, independently, accessing the same hardware. This is a "recipe for failure."
When a virtual system is set up, a "simulated" set of hardware is defined that "maps" hardware events in the virtual system to different requests to the "real" drivers of the actual hardware. So, to accomplish your goal, you'd need to define your virtual hardware to be identical to the actual hardware you had available when you installed your Windows (or Linux) system. That way the drivers on your already installed system would be able to work together.
It's usually easier to do a fresh install to the virtual machine so the correct drivers for the virtual hardware are installed rather than creating virtual hardware definitions for (the very large number of) real hardware out there "in the wild." If all of your hardware has open specifications and driver, you might be able to create such drivers.
But, for now, without virtual hardware definitions that identically mimic your real hardware, achieving your goal seems at best, problematic.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.