Windows in a VM, HDD formatted in EXT4

Sherri is a Cat

Well-Known Member
Joined
May 8, 2021
Messages
2,200
Reaction score
1,535
Credits
18,230
My hard drive is formatted using EXT4. I have Virtual box installed in Linux Mint.

  1. It seems to me that since the hard drive format is incompatible with Windows I wouldn't be able to install Windows in a VM. Is this correct?
  2. Can a partition have a different format?
  3. Is it possible to install a VM on the hard drive as a Type I hypervisor along side Linux like you would use dual booting for 2 OS's on the same hard drive?
    1. If yes, how should the HDD or SSD be formatted or does it matter?
  4. How is a Type I Hypervisor different than a virtual machine?
Thank you!

This is from my text book for a class I'm taking.

1749931852389.png
 
Last edited:


My hard drive is formatted using EXT4. I have Virtual box installed in Linux Mint.
  1. It seems to me that since the hard drive format is incompatible with Windows I wouldn't be able to install Windows in a VM. Is this correct?

No, it's not correct.

Several years ago, I set up my wife's Linux Mint machine to run Windows XP, so she could use QuickBooks. I'm sure that Virtualbox took care of everything.

That Mint install uses an EXT4 filesystem. We don't need to concern ourselves with either a Windows NTFS file system or an EXT4 FS when using Virtualbox.
 
1. I am having LMDE and it formats the HD to the Linux's needs, yet I run Win11 in a VM. That is what the VM is for.
2. Yes, also having a separate partition with music, mounted to my Linux music player as /mnt/music.
That's all I know and can answer. :D

I plan to have data on a completely separate SSD drive in the future, will figure out how to make the two hard discs work together.
 
I am having LMDE and it formats the HD to the Linux's needs

Someone can correct me if I'm wrong here...

LMDE can be installed on an EXT4 OR NTFS formatted drive. Windows can ONLY be installed on an NTFS formatted drive. When LMDE is installed it will not change the formatting of the HDD/SSD unless you direct it to do so.

@Condobloke Would you check me on this bit of information? Thanks!
 
Last edited:

Technically, yes. In reality, no. There are no file permissions and the file format isn't really going to work with Linux. NTFS doesn't have the capacity to support Linux's file permissions. You could install Linux but it'd be absurd to do so and downright dangerous in a world where malware exists. Those file permissions save your system from doing things you did not authorize.
 
Someone can correct me if I'm wrong here...

LMDE can be installed on an EXT4 OR NTFS formatted drive. Windows can ONLY be installed on an NTFS formatted drive. When LMDE is installed it will not change the formatting of the HDD/SSD unless you direct it to do so.

@Condobloke Would you check me on this bit of information? Thanks!
This is the first time I am reading such a claim. Nobody gave me a choice how to format the HD when installing LMDE, so probably no. LMDE is Debian based, not sure whether you can install Debian with NTFS formatting. The installer handles it all.
 
I was going to say something similar,
 
Can a partition have a different format?
The current ext4 partition won't be touched, it'll stay the same. VirtualBox or similar programs create a virtual (not physically existing as such but made by software to appear to do so) disk where the OS will be installed. So you can have several virtual machines using VBox and those VMs can have different file systems themselves, but the real, physical disk won't be touched.
 
This is the first time I am reading
In my vain effort to prove myself right I now realize I was mistaken. Both Windows and Linux are compatible with FAT32 and EXFAT. In the case of HDD/SSD's I assumed incorrectly that the same is true of NTFS.

I stand corrected.
 
I have a w7 VM in Virtualbox in both Mint Cinnamon 21.1 and 22.1 and never had to format anything...the same would apply if it was windoze.
 
The Virtual Machine, will have a Virtual Disk associated with it. Your Linux hard drive might be 2TB. The virtual disk might be 20GB in a file on the main hard drive. You can format the virtual hard disk with any format you want to. It doesn't have to be the same as the main hard drive. It's just a file that "pretends" to be a hard drive on your main hard drive.
 
Last edited:
When you install a Linux Distro or windoze...in to Virtualbox you format nothing...the only thing you create is the Virtual Disk which for me is my w7 VM is 50GB.

In Linux we don't have Disks...so my w7 VM is actually a file.
1750054946937.gif
 
The Virtual Machine, will have a Virtual Disk associated with it. Your Linux hard drive might be 2TB. The virtual disk might be 20GB in a file on the main hard drive. You can format the virtual hard disk with any format you want to. It doesn't have to be the same as the main hard drive. It's just a file that "pretends" to be a hard drive on your main hard drive.
Just 20GB probably won't suffice Windoze these days. I tried Win11 on a 32GB usb key and soon ran out of space for just updates, that after uninstalling over 300MB of onedrive application.
 
Just 20GB probably won't suffice Windoze these days. I tried Win11 on a 32GB usb key and soon ran out of space for just updates, that after uninstalling over 300MB of onedrive application.

That's why my w7 VM is 50GB...still fills with temp files and other windoze rubbish...it's not connected to the net.
1750116764258.png

1750116821501.gif
1750116845697.gif
 
My hard drive is formatted using EXT4. I have Virtual box installed in Linux Mint.

  1. It seems to me that since the hard drive format is incompatible with Windows I wouldn't be able to install Windows in a VM. Is this correct?
  2. Can a partition have a different format?
  3. Is it possible to install a VM on the hard drive as a Type I hypervisor along side Linux like you would use dual booting for 2 OS's on the same hard drive?
    1. If yes, how should the HDD or SSD be formatted or does it matter?
  4. How is a Type I Hypervisor different than a virtual machine?
Thank you!

This is from my text book for a class I'm taking.

View attachment 26550
1. Wrong. Whole point of virtualization is to emulate compatibility 100%, so what one OS can do - other MUST ALLOW(through emulation) or PASS THROUGH to real hardware. In other words, I had all sort of windows and as such windows partitions in VM container file on ext4 partition. Generally whole idea of VM container file, is that it acts like hardware to OS inside of VM. VM OS does not know nor cares it stores files in a file, as far as it is concerned - it is accessing drive directly.(by issuing SATA/PCI-E calls, that HOST catches and translates to read/write operations on VM container file).
2. Typically there is only one file system per partition. One drive can have MANY partitions, hence many file systems can be on same drive. They don't overlap. Example: if physically size of disk is A to D, then partition A to B can be one third and it will have its own file system. B to C will have one third and have its own filesystem that is different from A to B partition. Same goes C to D partition. Example: A ext4 B btrfs C fat32 D
3. Types of hypervisors are now irrelevant and obsolete from practical perspective, at least on Linux. KVM virtualisation is so good that it allows full pledge Linux run VM as dedicated host and/or do something else. Linux KVM is THAT GOOD.
On Linux KVM host you can pass through a partition or even whole drive to a gues VM, so guest VM will access partition/HDD and not know difference. That partition will be at mercy of Guest, Host wont manage nor touch it(unless explicetly forced by admin). So hypothetically it may even be possible to run OS from said partition or drive, assuming you can manage bootloader load from Gues partition. But in practicality it will be hard, due to difference in drivers in "guest mode" and "OS directly run" mode. Since Host does some driver emulation, like GPU emulation for example. As well you need to know UEFI well, which is pretty tough stuff on it's own.

In most cases VM guests read and write their data to VM containers like QCOW2 or somethin similar. Those containers are just files contained on Linux file system like BTRFS or Ext4 or XFS or something.

I avoided talking about LVM, it would just add extra complexity for no added benefit.
 


Follow Linux.org

Members online


Top