thanks to some of the people in ##Windows (civpro,sad_peter_pan), I worked to
some of the permission problems and here's what we came up with:
Determine which partitions are visible to Windows. The virtual box manual says
to use a command like:
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>"c:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe"
internalcommands listpartitions -rawdisk \\.\PhysicalDrive0
but usually, you can't because of security features in Windows. You'll get an
error like
Error opening the raw disk: VERR_ACCESS_DENIED
but if you go to the Windows 7 start button, enter 'cmd' into the search box,
you will see 'cmd' listed in the "programs" section. Right-click, run as
administrator. The command window will come up, you can then run the VBoxManage
command as shown above and you'll get the following output (if you have a disc
that looks exactly like mine)
VirtualBox Command Line Management Interface Version 3.0.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0x83 0 /1 /1 1023/254/63 70001 63
2 0x83 1023/254/63 1023/254/63 320813 143364060
3 0x07 1023/254/63 1023/254/63 80199 800391168
5 0x82 1023/254/63 1023/254/63 5922 964639053
C:\Windows\system32>
in my environment partition 2 is my home partition. Following the instructions
in virtual box manual Chapter 9.10.2
C:\Windows\system32>"c:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe" interna
lcommands createrawvmdk -filename c:\Users\esj\.VirtualBox\HardDisks\linuxhost.v
mdk -rawdisk \\.\PhysicalDrive0 -partitions 1,2
VirtualBox Command Line Management Interface Version 3.0.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
RAW host disk access VMDK file c:\Users\esj\.VirtualBox\HardDisks\linuxhost.vmdk
created successfully.
C:\Windows\system32>
at this point, the partitions are now visible as a drive in virtual box. Select
the drive, add it to the virtual machine. Now this is where I got a surprise.
first was that my root partition had been moved off of /dev/sda to /dev/sdb and
my new mapping of the raw partitions is on "/dev/sda" I also don't understand
why the entire disc was mapped through. I'm not happy with only exporting the
two partitions I wanted because while I like to think I'm smart enough not to do
something stupid with the other partitions, there's no guarantees that I won't
make a mistake.
r...@fortyau:~# fdisk /dev/sda
The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0006a898
Device Boot Start End Blocks Id System
/dev/sda1 1 8924 71681998+ 83 Linux
/dev/sda2 8925 49822 328513185 83 Linux
/dev/sda3 * 49823 60046 82123776 7 HPFS/NTFS
/dev/sda4 60047 60801 6064537+ 5 Extended
/dev/sda5 60047 60801 6064506 82 Linux swap / Solaris
follow the usual rules for mounting and, you should be all set.
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
