yahoo-eng-team team mailing list archive

[Alan Pevec <1155842@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/grizzly
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1155842

Title:
  config drive not visible to windows

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) grizzly series:
  Fix Released

Bug description:
  When I boot a windows 2008 server image in libvirt/kvm with --config-
  drive True, the config drive isn't usable by the windows guest as far
  as I can tell.

  I start with devstack, load a windows 2008 server image into glance,
  and boot it with an appropriately large flavor. When I go to "My
  Computer", only C: is available.  "Disk Management" in "Server
  Manager" shows a Disk 0 (C:), and a Disk 1, which I assume is the
  config drive, but it's status is "Unknown/Not Initialized".

  The XML for the domain looks shows the disk is presented to the guest:

      <disk type='file' device='disk'>
        <driver name='qemu' type='qcow2' cache='none'/>
        <source file='/opt/stack/data/nova/instances/21499a0c-d65e-4d9b-9040-2a54edf10b1f/disk'/>
        <target dev='vda' bus='virtio'/>
        <alias name='virtio-disk0'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
      </disk>
      <disk type='file' device='disk'>
        <driver name='qemu' type='raw' cache='none'/>
        <source file='/opt/stack/data/nova/instances/21499a0c-d65e-4d9b-9040-2a54edf10b1f/disk.config'/>
        <target dev='vdz' bus='virtio'/>
        <alias name='virtio-disk25'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
      </disk>

  I can mount the disk.config as an iso on the host linux system.

  I expect that on Windows I'd be able to see a D: and be able to open
  it up and see the config drive files.

  As another experiment, I tried setting config_drive_format = vfat in
  nova.conf. The result was pretty much the same but the drive showed up
  in "Disk Management" in "Server Manager" as "Basic/64 MB", but it
  still didn't show up as a D: drive.

  The XML for the domain looks shows the disk is presented to the guest:

      <disk type='file' device='disk'>
        <driver name='qemu' type='raw' cache='none'/>
        <source file='/opt/stack/data/nova/instances/a924026f-e3eb-4ecc-a276-2875fa4f11d4/disk.config'/>
        <target dev='vdz' bus='virtio'/>
        <alias name='virtio-disk25'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
      </disk>

  I'm wondering if OpenStack needs to present the config drive
  differently so that it's usable by the Windows guest when running
  under kvm.

  
  I'm running OpenStack/devstack on Ubuntu 12.04.2 LTS. libvirtd --version shows 0.9.8. nova is from github master, the latest commit is this one:

  commit 0ca55dcccdd76181a3b9311945e0b99ae6381e53
  Merge: 9dac4e6 7f1b1b6
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Fri Mar 15 22:18:26 2013 +0000

      Merge "Revert 1154253 causes XenServer image compat issue"

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1155842/+subscriptions