Unfortunately, we can’t do it as quickly as in the VMware workstation.įew commands and hard drive mapping are involved in mounting and using the physical disk partition in VirtualBox. This step by steps method explains how to access the physical disk in VirtualBox. But in some cases, if you want to access/mount a physical drive partition to a virtual machine’s settings, you need to follow the steps to accomplish it. Once the VirtualBox guest additions are correctly installed, this can be enabled easily by doing additional steps. Or is it VMWare? I would think the folks that built this virtualization system would have encountered this, and know what it means and what to do about it.VirtualBox has a shared folder feature that allows accessing the host computer’s physical hard drive partition and folders from the virtual machine.
How can I copy, say, /dev/sdc1 to /dev/sdb1 with the dd command, if I get this particular VMWare popup on sector 0? Is it Windows that is refusing to let me do this? Is it some Windows admin policy? I'm running as admin. So this is a much better-defined problem. And while my previous problem involved complaints about an inability to write to a few sectors that I never explicitly asked it to write to, and don't know what was trying to write to them, and now find I can ignore anyway, I now have a situation where I can't write anything at all to a partition, when I'm trying to copy an entire image of a partition from one disk to another.
It wouldn't surprise me in the least if the ultimate cause of this problem is the same as the ultimate cause of my previous problem, but I don't know that for sure. But now I can get into Linux and do useful work.īut now I'm coming up against a complete inability to do some specific thing in Linux, which is raw writes to unmounted partitions. I sort of have to stand on my head to do it, going to the grub console and issuing a couple of commands, and I still get a few of the PhysicalDrive1 errors which I just "Continue" until they stop. These are both about the same error message, I suppose, but I managed to solve the other thread's problem, which was an inability to boot a VM from a physical disk.
0 kommentar(er)
