regarding running a portable OS

[drpepper]

I am in the initial stages of creating a network inside of a virtual machine (VirtualBox, if it makes any difference) to run from an external drive. I ran into some conflicting information for initial configuration of Windows Server 2008R2. In an attempt to cause myself the least work, I am asking questions here before proceeding.

Here are the basics as things stand now. After the initial install of the OS, certain default configurations were not available until after the first round of updates. (These are configurations necessary for establishing an deafult IP addressing, etc.) I copied the vdi file with only the initial round of updates to my external drive and renamed it before proceeding. I began implementing the default configurations and discovered that this was not the ideal order for doing things. I can launch the OS (with some configurations applied) from within VirtualBox or from the external drive (with only the initial round of updates installed) successfully.

I think I can delete the vdi file on the host computer. (the one with some configurations applied) Then copy the vid file on the external drive to the proper path on the host machine. Then I think the file without any configurations can be launched by VirtualBox to begin configuration again. I am not sure whether or not I need to rename the file to the original name for VirtualBox to recognize it.

Do I need to rename the file? Will this work the way I think it will?

Thanks for your replies.

drpepper

 

[kado897]

I'm not sure what the solution is but you may have a problem. The virtual disks are identified by GUID (or UUID to be precise) not name within VBox.

Thinking about it you may be able to remove the original disk within settings and add the new one in. Not sure what having two disks in the network with the same UUID will do though. There is a utility called CloneVDI which can copy a VDI and give it a new UUID. There is a link to it on the VirtualBox forums. https://forums.virtualbox.org/viewtopic.php?f=6&t=22422

 

[drpepper]

Thanks for replying.

I merely want to move backward a little on my configuration and do things a little differently. The deal about the vdi file is the VirtualBox version of this tutorial: http://www.sevenforums.com/tutorials/276540-portable-os-carry-your-os-external-drive.html The tutorial uses VMWare.

I am not experiencing a problem. I believe the GUID is part of the file or some other part of the VirtualBox installation and configuration. I have two copies of the OS in vdi files. One is on an external drive and has only the first round of updates. The on the is on the host machine and contains some configurations. Either of the vdi files can be launched to run the OS at the state represented by the individual file. I don't think I would be able to launch and run each of the states represented by the different files if that were a problem. Additionally one of my teachers says he saves vdi files to another location rather than creating snapshots to save a state. He won't go into detail. He says play with it, and see how it works.

In the absence of someone who has done this and can give input, I will experiment to see how it works. I was just looking for an easy way to do it on the first attempt. --- I could be wrong. We'll see.

drpepper

 

[kado897]

No problem drpepper. I'm in favor of experimentation myself.

 

[drpepper]

 

[kado897]

Excellent.

 

[drpepper]

just a little feedback ... it works ... here are a few details ...

With caution in mind, I employed some redundancy. I transferred data as follows:

• copied entire VirtualBox VMs folder on host machine to external drive (>12GB)
• moved vdi file from within VirtualBox VMs folder on host machine to external drive (>12GB)
• copied vdi file from external drive to VirtualBox VMs folder on host machine (>7GB)

I can launch the VM state with only the first round of updates from the VirtualBox program on the host machine as well as all the vdi files on the external drive independently. I can now proceed with the better method of server configuration. I have enough saved states to fall back to a state of my choice. (Gee, a 1TB external allows me plenty of room for doing this.)

The only inconvenience was data transfer speed because of hardware restrictions. My laptop provides only USB2.0 ports. The external drive's USB 3.0 capability could not be used to my advantage. Also the external drive only spins at 5400RPM. Data transfer rate averaged a little over 30MBps with a couple of peaks around 36MBps. I guess that is the best I can hope for with the hardware bottleneck.

drpepper

 

[kado897]

That's good news. I actually run my VMs on a USB2 attached drive. They are a bit slow but work fine.

 

[drpepper]

I just saw your network configuration found here: http://www.sevenforums.com/virtualization/284015-vbox-4-2-10-crashing.html#post2352867

This the default established by either VirtualBox or Windows Server 2008R2. I don't know which. I suspect it is the server. I'll have to consult the user manual to verify. I could not help noticing that you have Bridged, and I have NAT.

drpepper

 

[kado897]

If I remember correctly with NAT you have internet access, with Bridged you have access to the Host Network. The help file explains the difference.

 

[drpepper]

I'll check it out. I have to take a week or so off from tinkering with my project to prepare for final exams.

drpepper

 

[kado897]

No problem. I'll stay subscribed to the thread.

 

[drpepper]

Hmm! It sounds like the development of my project may become an interactive blog of sorts.

 

[drpepper]

When final exams wind down later this week, I will continue with my project. Judging by the number of reads for this thread, I think it may be proper for me to frame the topic a little. I don't want anyone to get the wrong idea and try to run with things before they are vetted. An important detail to keep in mind is that this project spans two topics: running a portable OS (using a VM) and networking. Therefore, part of the subject matter is outside of the virtualization topic.

The original intent of this thread was to gain some clarification of how to proceed. Continuation of the thread is motivated by the large audience it has generated. If none of the Moderators or advanced members of the forum ask for a halt, I hope to post my progress as I build the network. Members with advanced experience are welcome to provide input. I am sure that I will have questions. From many hours of research it appears that it is not common to build an entire network inside a VM. Ths provides an opportunity for me to learn and share both successes and failures with the community. Hopefully we can all learn something.

What is the project about?
This is a personal project with several goals in mind. The big picture is to create a functional network inside of VirtualBox and move it to an external drive.

Why did I choose to attempt this?
I have neither the money or physical space to build a network using physical hardware. I think of the project as my poor boy test lab. The best case scenario is that I will learn enough to gain an entry level networking job. Last, but not least, I love a challenge.

Am I experienced with virtualization?
NO. I have only trivial experience. I ran Ubuntu inside VMWare Player for one semester to avoid the necessity of dual booting. I used the VM for practice of classroom topics in an intro to Linux class.

Why did I choose VirtualBox over VMWare?
I need a free program because of the budget. VirtualBox promises to offer anything I need free of charge. VMWare is not free. VMWare Player (free) does not provide all the features I anticipate needing. Additional features have a cost involved.

Do I have any experience with server/client networks?
The best answer is no. My exposure has been limited to using a client computer for point-of-sale (POS) and time clock purposes. The workstation experience in the network has been far more trivial than almost everything I do on my personal computer.

Then what will the network look like?
I will build the network one piece at a time. The initial wok involves basic configuration of Windows Server 2008 R2 Enterprise. I will add two clients: Windows 7 Professional x64 and Windows 8 Professional x64.

What system resources am I going to use?
My i3-2330M (@ 2.2 GHz) has hyperthreading and and virtualization enabled. This allows me to dedicate one processor (2 physical + 2 virtual) for each of the following: Win 7 HP x64 host, Win Server X64, Win 7 Pro x64 guest, and Win 8 Pro x64 guest. With 8GB RAM, 2GB will be allocated to each of the four OSes initially. Research has indicated that the server is best configured with 2GB memory, but can be reduced to 512 MB for actual operation. This will free some memory for the host or allow me to add more clients. The clients' memory allocation may be reduced later (after installation and configuration). That remains to be seen. Storage allocation will be initially set at 35GB for the server and 30GB for the clients. I have plenty of free space on both the host and the external drive where the network will be stored after initial configurations have been tested.

What other challenges do I anticipate?
I have no experience with Windows 8. I will have to learn this OS also.

The bottom line is that I hope this will be challenging and instructive for all who read or contribute.

Thanks in advance to everyone.
drpepper

 

[kado897]

That sounds a good plan. I look forward to following it.

 

[whs]

That's good news. I actually run my VMs on a USB2 attached drive. They are a bit slow but work fine.

Keith, it is slow because you probably run it from a HDD. I notice hardly any difference in speed between the internal SSD and the external SSD - but, of course, I use only SSDs. The external is attached via USB3, but USB2 is not much slower. It's all in the access time.

Have a look at e.g. the boot times comparing Windows 8 and Mint from the external USB3 attached SSD. Disregard the VMware setup time. Boot is from when the OS logo appears.

Booting Windows 8 and Mint - YouTube

 

[kado897]

That's good to know Wolfgang.

 

[drpepper]

test from Windows 7 guest ---
The window is too small for a meaningful post. I don't want to hassle with the scroll bars.
The test is not important enough to manually resize the window.

 

[kado897]

If you install the guest additions you can have whatever size you like.

 

[whs]

I can adjust the screen size before I install the guest additions. That is usually the first thing I do. I wonder why that is not possible for the OP.