Posts: 1,843
Threads: 20
Joined: Feb 2011
Reputation:
0
Why are you letting the VM access the hard disk directly? You shouldn't do that- letting two OSes access the hard disk raw at the same time is a recipe for disaster. The VM should only have access to the disk image it's confined in and share files with the host over a reliable and safe method, ie network or VM-proprietary protocol. Giving both OSes access to the hard disk = bad.
The Best Medicine > Magic. Because SCIENCE! can prove the former.
Posts: 1,843
Threads: 20
Joined: Feb 2011
Reputation:
0
So it wasn't accessing the main OS drive then?
The Best Medicine > Magic. Because SCIENCE! can prove the former.
Posts: 1,843
Threads: 20
Joined: Feb 2011
Reputation:
0
Well, either way, I still won't trust a VM with a direct connection to the hard drive. Typically I use drag and drop if available, otherwise shared folders or even network shares will have to do. This comes down to VMs having inconsistent timing, I'm a bit paranoid that a timing skew would be enough to mess up the hard drive.
To be honest, the last time I let a VM write to a USB stick, said stick is now a piece of paperweight- for some reason, it got write-locked and everything I've tried to do to unlock it is in vain. The stick is stuck in read-only mode. And I can't low-level format it because the stick's partition table is changed to GPT with Linux partitions and none of the stick repair programs could detect it anymore (yeah, I was messing with a bootable Linux stick).
The Best Medicine > Magic. Because SCIENCE! can prove the former.
Posts: 1,843
Threads: 20
Joined: Feb 2011
Reputation:
0
Mentlegen, behold!
I have had the Emily-NG refactored for POSIX compliance!
In retrospect, I ask why.
The Best Medicine > Magic. Because SCIENCE! can prove the former.