Can I setup Linux on a VM and then swap to that setup permanently if it works well for me?
-
no dual boot. just jump in, the water is fine.
-
There's not really a simple way to make a VM setup permanent. You could try it out in a VM, and then use a backup tool to save your home directory and system configuration to transfer your settings to a "real" hard drive installation.
-
Piracy seems harder, like whats the alternative to vfxmed for stuff like houdinifx
-
What is that
-
Maybe. If you can create the partition and set your hypervisor to use it as the virtual disk, then yes. But it might actually require a whole drive to do that. I can't promise that it would easily convert from one to the other though. I would just go right for the dual-boot and use it as much as you can.
-
My recommendation would be to use clonezilla or a similar tool to make an image of your windows install and save that on the external ssd.
Then I would install Fedora KDE or whatever's your poison on the internal drive.
If you wanna switch back to windows then you can always use clonezilla, or your tool of choice, to restore the image.
You could also use KVM/Qemu in your linux distro to restore the image into a windows vm.
virt-manager gives you a desktop gui while cockpit + cockpit-machines gives you a nice webui for handling virtual machines in linux.Clonezilla guide, for both linux and windows
https://www.linuxbabe.com/backup/how-to-use-clonezilla-liveBoth Cockpit and Virt-Manager are available in Fedora KDE's Discover app if you prefer GUI installs:
Cockpit
Virt-Manager
-
Hollywood vfx, 3d procedural modeling software, I enjoy using it, might someday buy it, but its only a hobby I make no money off so I pirate it
-
Used to play videogames now I spend days making reusable vfx that I never end up using, need to buy some interesting mocaps because I dont like hand animating ive come to find
-
I'll look into this, thank you!
-
I can't help with pirating software, your options are going to be heavily limited because most people running Linux would just prefer open source alternatives (like Blender), so it's far less likely you will find cracked software specifically made for Linux (plus, there is a far smaller userbase). On some quick searching, I did find someone who had issues running Houdini in a VM (for multiple distros), but it worked fine when it was installed natively. I'm not seeing an entry in the WINE database for Houdini, so while you could always try running a Windows version through WINE, given the type of program it is, I highly doubt it would run without issue. I have no recommendations on how to get ahold of a Linux compatible version without a license.
-
Yeah I'd definitely dual booting while you wet your toes if you want to go full linux, then run a windows vm of you cant find anyway to replace that.
I run a windows vm on my server for my 360 tour and editing stuff but everything else is on my main linux machine now
-
Probably possible but highly technical. Might be better to just run Windows or Linux in a VM whichever system you won't use much. Exception is gaming or other apps that need hardware video acceleration. I aleays found dual booting annoying unless you have to do it.
Be aware. you may have to buy a specific Windows version to run it in a VM. OEM versions historically were not licensed for VM use. Also changing hardware configs for Windows historically has been a nightmare.
-
That would definitely be a technical challenge, but also it's absolutely possible.
I used to do dual-boot Windows + Linux and I could run the Linux installation from a VM in Windows as well as the Windows installation from a VM in Linux.
When rebooting between metal and VM, Windows would always spend a few minutes "doing things" before continuing to boot, but it worked.
Linux would not even fret. It would just boot normally without any complaints.
I don't remember exactly which distro I had at the time, but probably it was Linux Mint.
-
Houdini FX has a Linux version, you'd just have to find a copy of it for Linux.
-
This is good advice imo. Some further comments:
- Its easier to make a vm out of a bare metal or “real” install. It’s much harder to go the other way.
- you seem to have some fear about installing or reinstalling OSs. It’s much easier than redeploying vms. I’d banish those thoughts and jump in. Again the above advice is solid because you can mess up or change your mind, and you can always revert. Cloning a drive and redeploying that image to the original drive is simple.
- dual booting gets a lot of flak. Most of that comes from windows not playing nice with boot partitions when windows is installed on the same drive. Another source of issues is secure boot. If you have two internal drives, installing an os on each one works great. I like turning secure boot off and simply pressing F8 upon boot up if I want to switch. (But you totally can get it working with secure boot and adding other OSs to grub.
-
yup, I did the "linux running metal" and using the same partition with a VM in Windows and it worked fine. It was years ago, certainly Ubuntu or MX Linux. IIRC the linux partition cannot be on the same drive than the linux partition, it needs to be a different drive.
-
Regarding HoudiniFX it seems they have Linux installs, and a free (with watermark) version for hobbyists - https://www.sidefx.com/products/houdini-apprentice/
Other than that I'd say Blender is the goto app, showing up as one of the most popular apps in the Discover app. -
Interesting. Does modern Windows allow booting OEM version into VM? Historically it was a) not allowed by license, b) not possible because Windows tended to hard configure to your motherboard hardware for example.
Also, I agree. Linux generally can boot into changing environments without issue. Windows, always a question.
-
Iirc I had a Windows 7 (maybe 8 or 10) Home OEM, original (not cracked), but it still worked. Perhaps if I had kept using it for long periods in the VM it would have started complaining? Anyways I booted it baremetal from time to time, so maybe that's why it kept working.
-
By the way, how one might do this at the high level.
First, you have to choose virtualization method. Could be any, but if starting with Windows, maybe VirtualBox. When setting up your initial OS you have to figure out how big to make the disk images and what format. If a virtualization format then you'll have to convert them later when you copy them into a real partition, if in real disk partition to start, one can just copy by imaging partition. In either case, think carefully about the size of the partition your configuring as it is going to have to be smaller or equal to the final partition your going to use for dual booting at the end. In the VM image, probably best to install Linux as a partition of the VM image not partitioned.
Linux should not have an issue with booting in multiple configurations. That is either direct/dual boot or in a VM. It generally just works. Windows on the other hand, you may have more issues.
When fiddling with low level disk and partition layouts and copying. You want to backup everything maybe both at the file system level, and as full disk images so you can easily undo mistakes. Also on Windows secure boot and Bitlocker can present additional issues if your booting with maintenance media. Make sure you have your Bitlocker emergency unlock codes and know how to use them before doing anything other then windows.
Other then that moving to dual boot from VM should be basically creating a partition into which to place the Linux image, then doing and image copy from your VM image (just the partition, not the whole image), into the new partition perhaps doing the format conversion if your VM image is not using a partition to start with. Then you'd have to setup the boot loader based on some sort of dual booting how to. Too long ago for me to remember the details of that. If the partition is going to be on the drive Windows is filling, you'll have to figure out how your going to shrink one or more of the existing partitions, and then create space for Linux. There are tools that can do that.
Caution is doing partition layout changes, low level image copies, and fiddling with boot loader and maybe BIOS configs is all quite technical. You have to be prepared for this to take some time, and to be able to restore your original setup if things go poorly.
If you doing this on a workstation, not a laptop. Another safer way to do this is hot mountable drive drives (do not actually have to be hot mountable). Just have windows on one drive, Linux on another. Pop the drive in you want to boot from and go. The other more expensive method, just have two different computers purchased with the OS preinstalled. As you suggest another method that is not that technical is just run Linux under virtualization in Windows, say with VirtualBox.
Someone who has recently done this should feel free to make any corrections to the above. Thanks.
