On Wednesday 14 October 2009 08:55:47 pm NoOp wrote:
> On 10/13/2009 05:07 PM, NoOp wrote:
> > In the past I've always created the VM on the same drive w/o major
> > issues. However I have several machines that are dual boot (linux on 
one
> > drive WinXP on the other) & have hesitated to try using those 
machines
> > to test using the 2nd drive as the VM. I've now aquired 2 recycled 
test
> > machines that have WinXP drives on them & now would like to give 
this a try.
> > 
> > Environment:
> > - test machine
> > - 40Gb sda WinXPPro
> > - 40Gb sdb linux (Ubuntu 9.04)
> > - Dual-boot works w/o issue
> > 
> > What I'd like to do is create a WinXPPro VirtualBox VM on the linux
> > drive (sdb), and rather than do it on the same drive, have it use 
the
> > WinXPPro installed on sda.
> > 
> > I'm quite familiar with running Win2KPro guests from the same linux
> > drive & not afraid of RTFM. But older instructions from the 
web/forums,
> > etc, new docs, new versions of VirtualBox have me a little confused 
on
> > how to go about this.
> > 
> > Note: I'm not worried about screwing up the test machine installs - 
I
> > currently have two of these machines to test with & can easily dd 
the
> > WinXP drive to a spare. So I would appreciate if someone can point 
me to
> > some relatively simple instructions on how I can go about this.
> 
> No takers eh? Anything that I need to clarify on what I'd like to do?
> 
> 
> 
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users
> 
I don't really know all that much about VirtualBox -- but you are not 
making sense to me!

What (and where) is the host system?  
What (and where) is the guest system?
These issues, of course, are REALLY "basic".

Furthermore, if you imagine that you are going to use the existing XP as 
a guest system within the existing Linux host system (or vice versa), 
then you sound as if you don't understand VirtualBox at all.  Within the 
host system, it stores and maintains a ".vdi" file which IS the guest 
system -- which is installed under VirtualBox on the host system.  That 
presents certain obvious and functional limitations that just MIGHT be 
in conflict with your undefined plans.


Bruce   Mac Arthur
15875 Switzer
Overland Park, KS  66221
     913-897-4157
     [email protected]


_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to