procedure for restoring to a virtual machine

[DrTeeth]

On Mon, 27 Feb 2012 09:53:37 PST, just as I was about to take a herb,
a1pcfixer disturbed my reverie and wrote:

>Again, the process of activation/re-activation is not the core focus here, but rather a TB image restored to
>a VM on a different PC

The point is that a VM even on the *same* PC is seen as different
hardware and would trigger the activation.

From TBU earlier in the thread "Taking an image of a computer and then
restoring that image to a VM on the same computer will not get around
these problems. The VM is still a different computer. In other words,
it doesn't usually make a difference if the VM source image came from
the source computer or a completely different computer".
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose to dance
in the puddles (Jewish proverb).

[a1pcfixer]

DrTeeth,

> From TBU earlier in the thread "Taking an image of a computer and then
> restoring that image to a VM on the same computer will not get around
> these problems. The VM is still a different computer. In other words,
> it doesn't usually make a difference if the VM source image came from
> the source computer or a completely different computer".

Exactly, and like I already said, 'PP' and I already got all that
settled. Good to know you're finally on the same page as us.

Your turn.{g}

--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[DrTeeth]

AISI, you asked if an image restored to a different PC as a VM would require activation. You got two 'yeses' and the additional info that even restoring to a VM on the same PC would trigger activation - as a VM is effectively always seen as different hardware .

What have I missed or misunderstood ? Am I having a massive senior moment ?

DrT

[a1pcfixer]

DrTeeth,

> What have I missed or misunderstood?

Well, since 'PP' and I had this settled 2 days ago,
I'd have to say.....a lot!{LOL!}
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[tanstaafl]

TeraByte Support wrote:
> just use copyp2v in the pro version of tbosdt. runtbs copyp2v.tbs

Sorry to reply to such an old thread, but I have an old XP system that I use to access/control our old security card access system, but I want to run this as a VM on my new workstation (want to do this before the thing dies) under VirtualBox...

Is there a detailed knowledgebase article or other documentation with details on how to do this?At least, something more than just 'just use

Thanks,

Charles

[TeraByte Support(PP)]

Basically, you have to run the copyp2v script to either copy the existing drive to a virtual drive or restore a backup image of the existing drive to a virtual drive. I would suggest using the "VMWare Monolithic Sparse IDE file" option (this will be a VMDK virtual disk). Also, make sure to select "Uniprocessor" or "Multiprocessor" depending on whether or not the VM will be configured with a single-core CPU or multi-core CPU (this will configure the correct HAL).

I usually use Workstation so I don't have much on the specifics of converting to VirtualBox. However, you should be able to create a new VM in VirtualBox that will use the VMDK file. When creating the VirtualBox VM, if you created a SCSI VMDK you may need to remove the IDE Controller and add the SCSI Controller. Also, you may need to enable the "Enable IO APIC" option.

[tanstaafl]

Thanks Paul -

VirtualBox does indeed support vmdk files - but what about the controller? I'm more worried about compatibility than performance on this machine, but I wouldn't want to take an unnecessary hit on performance, so how about SATA? Would I have to do anything special (you mentioned 'removing the IDE controller and adding the SCSI controller) for SATA? And, *how* would I 'remove' the IDE and 'add' the SATA (or SCSI)?

Thanks again, your help/hand-holding is much appreciated...

[TeraByte Support]

it's in the storage options area for the VM you create, you can add/remove
attachments (drives) or controllers.

"tanstaafl" wrote in message news:6277@public.image...

Thanks Paul -

VirtualBox does indeed support vmdk files - but what about the controller?
I'm more worried about compatibility than performance on this machine, but I
wouldn't want to take an unnecessary hit on performance, so how about SATA?
Would I have to do anything special (you mentioned 'removing the IDE
controller and adding the SCSI controller) for SATA? And, *how* would I
'remove' the IDE and 'add' the SATA (or SCSI)?

Thanks again, your help/hand-holding is much appreciated...

[TeraByte Support(PP)]

I would recommend trying the easiest method first, especially if you're not familiar with using a VM. The default VirtualBox XP VM will be IDE. You would just need to enable the "Enable IO APIC" option (System section, Motherboard tab) and adjust the RAM amount up. When prompted, select to use your existing virtual disk and browse to the VMDK created by the copyp2v script.

If you do decide to use the SCSI controller, you'll probably need to add the driver since XP doesn't include it. The driver you use (Lsilogic or BusLogic) and the SCSI Controller type in settings need to match. For example, I can have copyp2v script install the vmscsi driver (included with Workstation) and then set the VM to use BusLogic.

The speed difference between IDE and SCSI or SATA is probably minimal. In my experience, the host's speed plays a much more important role -- if the host's disk access is fast the guest will also be fast.

While testing and getting the VM configured how you want, you may wish to disable the Network adapter (Network section, uncheck Enable Network Adapter) so the VM won't go online.

[tanstaafl]

Excellent, thanks Paul... may not have time to get to this until this weekend, but am looking forward to it.

I've done a bit with VirtualBox VMs, but this is the first time I've ever attempted to do a P2V conversion...

Thanks again!

Charles