We recently setup a virtual K2000 appliance and so far the upload speed for images has been very poor. The first K-Image we created took close to 24 hours for a 20GB image and we have yet to have a WIM upload successfully (it normally says about 30 seconds remaining indefinitely). We successfully NetBooted our first Macs yesterday and after over 12 hours one of the machines is reporting 1% complete with an ASR image. The machine testing the native imaging hung at some point overnight but after several hours the progress bar had barely moved.

We have been performing our testing on a switch with a gigabit uplink and machines are connecting at 100 full duplex. Uploading and downloading through the same switch to our WDS server is much faster so I don't believe it is a throughput problem. Transferring files to the SAMBA share does not seem overly slow so its network connection is probably stable.

I did not create the virtual machine running the appliance so I'm not sure what the settings are on that end. 

We have not been through our JumpStart training so it is possible that there's something simple we're missing but I wanted to see if anyone here had thoughts as to what might be causing this slowness.

Thanks.
2 Comments   [ + ] Show Comments

Comments

  • there are a few things which are very important:
    1. set the virtual NIC of the K2000 to E1000 (if not yet done)
    2. install the vmware tools
    3. there is an issue with SAS hdd which is slowing down the imaging
    4. set the speed to 1000MBit full duplex on both sides of the cable
    5. use multicast if possible
    6. disable include debug output in log for imaging
    • Thanks for the reply, Nico_K. We did not have the VMWare tools installed and that seems to have helped with creating the WIM images. However, it has been saying copying image to the server with about 20 seconds remaining for at least half an hour. Is there any way to check the progress on the server? It doesn't appear that the image files are accessible through the SAMBA shares to see if the filesize is growing.

      As for the Mac imaging the VMWare tools does not seem to have made a difference.

      Can you explain what you mean by "an issue with SAS hdd"?
      • There is an unfixed issue (K2-2046) which is causing the imaging (only imaging, Scripted installs seem not to be affected) very slow if you image to SAS hdd (or from a SAS) > See release notes
        No, unfortunately you don't have a possibility to see the progress.
  • Update: We finally had a WIM image upload successfully. It took only 40 minutes to create the WIM on the local drive but then about 16 hours for it to upload to the appliance. The image is less than 14GB so that isn't great performance. The machine in question is a SATA drive so the K2-2046 issue shouldn't be relevant.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity