Alright, got it! Thanks! -Ilyes Gouta
On Saturday, April 24, 2010, erstazi <[email protected]> wrote: > On 04/24/2010 12:49 PM, Ilyes Gouta wrote: >> Hi, >> >>> The assumption is that if you have to do it as part of the command >>> line, then you likely had to read some documentation. So I'm not >>> going to spoil your fun. Go read some VBoxManage documentation. >> >> Actually I'm just doing that! Cool! I think I'm going to export just >> the needed Linux partitions and not the entire disk. I hope it'll be >> safe enough for a regular usage. >> >> Still one issue though, do I have to change the GRUB >> configuration/location so that the VM picks up the right /boot >> location in order to boot up the kernel. Does VBox keeps giving access >> to the disk's MBR even if I'm going to export just few partitions >> using VBoxManage, and not the entire disk? >> > > With VBoxManage internalcommands createrawvmdk, you would use the -mbr > parameter. > > http://www.virtualbox.org/manual/ch09.html#rawdisk > >> Thanks! >> >> -Ilyes Gouta >> >> On Sat, Apr 24, 2010 at 5:10 PM, Rance Hall <[email protected]> wrote: >>> On Sat, Apr 24, 2010 at 10:05 AM, Ilyes Gouta <[email protected]> wrote: >>>> Hi, >>>> >>>> I had this curious idea for a while now and I am wondering if it's >>>> feasible at all: Is it possible to create a new virtual machine in >>>> VirtualBox and attach to it a real, physical hard disk instead of just >>>> a VDI image, so that the VM will actually boot on the OS installed on >>>> that disk and have access to the user's files. That would be really >>>> cool! Image a VM hosted on Windows and having access to the Linux >>>> distribution installed on the same hard disk (or another one), on a >>>> different partition. Such a solution would save me from rebooting >>>> every time to access my files. >>>> >>>> Is it at all possible? Is security THE argument for not implementing >>>> such a feature? >>>> >>>> -Ilyes Gouta >>> >>> >>> This feature IS part of vbox. It is not part of the GUI for many >>> reasons, not the least of which is the possibility for data corruption >>> if not done correctly. >>> >>> The command line admin tool that is part of vbox DOES have the option >>> you requested. You can create vms, start vms, and a host of other >>> things from this command line tool. >>> >>> >>> The tool is called VBoxManage. >>> >>> >>> The assumption is that if you have to do it as part of the command >>> line, then you likely had to read some documentation. So I'm not >>> going to spoil your fun. Go read some VBoxManage documentation. >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> VBox-users-community mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/vbox-users-community >>> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> VBox-users-community mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/vbox-users-community > > > ------------------------------------------------------------------------------ > _______________________________________________ > VBox-users-community mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/vbox-users-community > ------------------------------------------------------------------------------ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
