How to Use the AFG with the Virtual Floppy Drive

From DocWiki

Revision as of 21:06, 5 March 2012 by Dosproul (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Go to: Ongoing Virtualization Operations and Maintenance

Go to: Implementing Virtualization Deployments

Contents

Using the AFG and Virtual Floppy

To use the platformConfig.xml file with a virtual machine requires the use of a virtual floppy drive on the virtual machine.

The platformConfig.xml file can be generated here http://www.cisco.com/web/cuc_afg/index.html

Note Note: After the Virtual Floppy image is created with the platformConfig.xml file in it the Virtual Machine boot order should be changed in order to avoid having to manually disconnect the floppy image in the middle of CUCM installation. If the boot order is not change, after the installer ejects the CDROM and reboots the Virtual Machine it will be stuck with "No Boot Disk Found" error while attempting to boot off the still connected Virtual Floppy Image.
Set the boot order to CD-ROM Drive then Hard Drive then Removable Devices and Network boot


Create A New Virtual Floppy Image

Windows

Follow this procedure to create a new virtual floppy image using the Windows platform.

  1. Download and install Winimage (http://www.winimage.com/download.htm).
  2. In Winimage, select File > New.
  3. Select 1.44 MB from Standard format and click OK.
  4. Drag the platformConfig.xml file onto the Winimae window.
  5. Click Yes when prompted to inject the file into Winimage.
  6. Select File > Save As.
  7. Select Virtual floppy image from the Save as type dropdown list.
  8. Enter a file name and click Save.

Linux Virtual Machine

  1. Create an empty floppy image of 1.44 MB as root:
    $ /sbin/mkfs.msdos -C <directory>/<imagefile.img> 1440
  2. Create a new directory called floppy1:
    $ sudo mkdir /media/floppy1/
  3. Mount the directory:
    $ sudo mount -o loop /path/imagefile.img /media/floppy1/
  4. Copy the XML file to the mounted directory:
    $ cp platformConfig.xml /media/floppy1
  5. Unmount the directory:
    $ umount /media/floppy1

Mac OS X

  1. On the terminal
    dd if=/dev/zero bs=1024 count=1440 > floppy.img
  2. Open Disk Utility Application. Go to File -> Open Disk Image -> floppy.img (Command + Option + O)
    You will get an error indicating "no mountable file systems) Click OK
  3. The Floppy Image will be added to the list of disks select it and go to the Erase Tab
  4. Change Format to MS-DOS (FAT) and Click Erase
  5. You can now copy the XML file (platformConfig.xml) to the mounted floppy image and eject it when you are done

Upload a Virtual Floppy Image to a Datastore

Follow this procedure to upload a virtual floppy image to a datastore:

  1. Start the vSphere client.
  2. If the host uses:
    1. Remote storage (for example, SAN), then select View > Inventory > Datastores.
    2. Local storage (for example, internal hard drive), then select the host and click the Summary tab.
  3. Right-click on a datastore and select Browse Datastore.
  4. Navigate to the desired directory and click the Upload files to this datastore icon.
  5. Select Upload File.
  6. Select the Virtual Floppy Image created in the preceding procedure and click Open.
  7. Click Yes when upload/download operation warning window appears.
  8. Close the Datastore Browser window.

Mount a Virtual Floppy Image

Follow this procedure to mount a virtual floppy image:

  1. Start the vSphere client.
  2. Select a virtual machine.
  3. Select Inventory > Virtual Machine > Edit Settings.
  4. Select Floppy drive from the Hardware tab.
  5. Select Use existing floppy image in datastore.
  6. Select Browse.
  7. Select All files from the file type dropdown list, if the virtual floppy image does not use the .flp extension.
  8. Locate the virtual floppy image and click OK.
  9. Enable Connected and Connect at power on under Device Status.
  10. Click OK.
Note Note: As with fresh installs on physical hardware, make sure the CD/DVD device is at the top of the BIOS boot order.

Back to: Unified Communications in a Virtualized Environment

Rating: 5.0/5 (2 votes cast)

Personal tools