virtualbox.org

Hi,

I am looking for some documentation on the use of licensed applications within Virtual box, as in I want to install a licensed application onto my guest OS.

Admiralgeek wrote:Hi,

I am looking for some documentation on the use of licensed applications within Virtual box, as in I want to install a licensed application onto my guest OS.

it's no different than it would be with a physical machine.

Hi loukingjr,

Thanks for your response. But would there be an issue with the UUID if i were to mount the virtual hard drive in a different machine?

Admiralgeek wrote:Hi loukingjr,

Thanks for your response. But would there be an issue with the UUID if i were to mount the virtual hard drive in a different machine?

You're welcome. It's a little hard to say since I don't know what software we are talking about.

That depends on what the software in question uses as a hardware signature. You would need to ask the software vendors about that. The exact CPU type for example is visible to software running inside the VM.

The product is Zend Guard. The UUID consists of Motherboard ID, CPU ID, and secondary ID's that consist of, RAM serial #, and HDD/SSD serial #. It would be more productive and mobile if I could mount the virtual HD. Does VirtualBox take an exact replicate of the Host's hardware identification credentials?

The VM doesn't record any of the hosts credentials. The simulation has its own DMI BIOS data. The only host feature visible to the VM is the CPU, because VirtualBox is not a CPU emulator.

Thanks mpack,

Is there any plugins in which the host's hardware credentials can be added to the guest DMI?

Why would you want that? If the software is installed in the VM then the DMI of some other PC (i.e. the host) is irrelevant. I think you're inventing red herrings for yourself. The software will be able to read the CPU type direct from the CPU regardless of what the BIOS has to say. In fact I think there is a way to fiddle the CPU capabilities reflected into the guest, but IMHO that's of little use since you can't expect the guest OS to be stable if it can't properly identify the CPU.

Also, if the software is quite new there's a good chance it can directly detect that it's running in a VM, and that test can't be fooled if the programmer is any good at all.

Hello mpack

mpack wrote:The software will be able to read the CPU type direct from the CPU regardless of what the BIOS has to say. In fact I think there is a way to fiddle the CPU capabilities reflected into the guest, but IMHO that's of little use since you can't expect the guest OS to be stable if it can't properly identify the CPU.

Can you please elaborate mpack? I'm highly interested

Jeff_59

Jeff_59 wrote:Can you please elaborate mpack? I'm highly interested

If you mean fiddling with the CPU identification, see 8.2. Commands overview, especially:

Code: Select all

vboxmanage modifyvm <uuid|vmname> [--cpuidset <leaf> <eax> <ebx> <ecx> <edx>]
                                  [--cpuidremove <leaf>]
                                  [--cpuidremoveall]

For some of the rest you'd fiddle with the BIOS DMI information, see 9.12. Configuring the BIOS DMI information.

Hello rpmurray

Thanks a lot for you message. The changes, thanks to the commands:
vboxmanage modifyvm <uuid|vmname> [--cpuidset <leaf> <eax> <ebx> <ecx> <edx>]
are indeed reflected in the guest.

Just wondering: is it also possible to set configurations regarding the motherboard chipset?

My aim would be that the HW info on the VM "looks" (that is return when questionning) like:
nVidia nForce2 (Crush18) + MCP2
rather than:
Intel 82440FX (Natoma) +PIIX3

I know that VB can emulate ICH9 and PIIX3, but is there a command that allows to
change the brand of the chipset? Indeed, it looks strange to have an AMD CPU with
Intel Chipset

Thanks in advance.

Best regards,

Jeff_59

Oh yeah, lying about the chipset couldn't possibly have an adverse affect on the the guest, could it...

I'm having trouble participating in this thread: that glaring punctuation error in the topic title is very distracting.

Hello mpack

Thanks for your quick answer.

mpack wrote:Oh yeah, lying about the chipset couldn't possibly have an adverse affect on the the guest, could it...

But is it possible to "lie" about the m/b chipset? Is there any VBoxManage command for that? AFAIK, the manual didn't mention any.

mpack wrote:I'm having trouble participating in this thread: that glaring punctuation error in the topic title is very distracting.

I'm not the inital author of this thread, but i guess many people here come from many countries around the world. English is often a
foreign langage for them. It's indeed my case, but i try to do my best to be understandable (although, i do mistake and i apologize for that

)

Best regards,

Jeff_59

virtualbox.org

Software license's

Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's

Re: Software license's