Announcement

Collapse
No announcement yet.

Understanding Network Interface Configuration in vmc file for VirtualPC 2004

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Understanding Network Interface Configuration in vmc file for VirtualPC 2004

    I am trying to modify the .vmc XML file manually to change the network configuration of a VM running in VirtualPC 2004.

    Each network interface of the VM has a corresponding entry in the .vmc file. The entry looks like:

    <ethernet_controller id="0">
    <virtual_network>
    <id type="bytes">7137E3C1432611DE830BC1E8633C617A</id>
    <name type="string">Microsoft Loopback Adapter</name>
    </virtual_network>
    <ethernet_card_address type="bytes">0003FF3FC5BA</ethernet_card_address>
    </ethernet_controller>

    Somehow, the name and id fields are linked together... so if I want to change the configuration of the network interface 0 from "Microsoft Loopback Adapter" to "Microsoft Loopback Adapter #2", I need to know what is the ID associated with "Microsoft Loopback Adapter #2".

    My question is how is the id computed (is it related to the name or is it just a random number)?

    Here's the experiment I have done so far:

    I created two VM on the same host. For each VM, I tried every possible configuration for its network interface (using VirtualPC GUI settings) and I recorded the resulting ID/name resulting association of the .vmc file. Both VM produce the same associations which are:


    7137E3C1432611DE830BC1E8633C617A (Microsoft Loopback Adapter)

    AECE82A3432611DE8159D4FA667DABEA (Microsoft Loopback Adapter #2)

    C5E3BE5D43B311DE810EF809BC6844D9 (Microsoft Loopback Adapter #3)

    C5E3BE5E43B311DE810EF809BC6844D9 (Microsoft Loopback Adapter #4)

    C5E3BE5F43B311DE810EF809BC6844D9 (Microsoft Loopback Adapter #5)

    C5E3BE6043B311DE810EF809BC6844D9 (Microsoft Loopback Adapter #6)

    C5E3BE6143B311DE810EF809BC6844D9 (Microsoft Loopback Adapter #7)

    EE0E9991E36111DD82E7D2FA5D917038 (Local only)

    EE0E9992E36111DD82E7D2FA5D917038 (Intel(R) PRO/100 VM Network Connection)

    01010101010101010101010101010101 () This is the NAT setting

    FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF (Not connected)

    From loopback 3 to 7, the ID is almost identical, but the other two loopback are totally different.

    Both "local only" and "Intel ..." (which is my host network card) have the same ID.

    "NAT" and "Not Connected" seem to use specific constants.



    I'll try later this week the same experiment with the same two VM but on a different physical host to see if the ID change... but if you have knowledge, I'd like to hear about it.

  • #2
    Re: Understanding Network Interface Configuration in vmc file for VirtualPC 2004

    Not to answer your question but to ask one of my own. Why are you using VPC 2004? Is there any good reason for that?
    Cheers,

    Daniel Petri
    Microsoft Most Valuable Professional - Active Directory Directory Services
    MCSA/E, MCTS, MCITP, MCT

    Comment


    • #3
      Re: Understanding Network Interface Configuration in vmc file for VirtualPC 2004

      I am working on a research project to automate the execution of security sensitive network experiments in a virtual environment. see vnec.sourceforge.net

      So far we were using VMWare workstation (which is great) to support the virtualization.

      The next step is to allow multiple virtualization tecnology to coexist in the same experiment.

      On our way there, we are "evaluating" some virtualization technologies to see which ones we could support in our tool.

      We are also looking at other virtualization technologies such as VirtualBox and VirtualPC 2007.

      So the short answer is probably, I am using VirtualPC 2004 in order for my study to be as complete as possible and to understand the limitation of our tool.

      Comment

      Working...
      X