config drive not visible to windows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Tony Yang | ||
Grizzly |
Fix Released
|
Medium
|
Matt Riedemann |
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='/
<target dev='vda' bus='virtio'/>
<alias name='virtio-
<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='/
<target dev='vdz' bus='virtio'/>
<alias name='virtio-
<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='/
<target dev='vdz' bus='virtio'/>
<alias name='virtio-
<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 0ca55dcccdd7618
Merge: 9dac4e6 7f1b1b6
Author: Jenkins <email address hidden>
Date: Fri Mar 15 22:18:26 2013 +0000
Merge "Revert 1154253 causes XenServer image compat issue"
Changed in nova: | |
status: | Incomplete → New |
tags: | added: libvirt |
tags: | added: folsom-backport-potential grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-3 → 2013.2 |
Which version of libvirt, which os and which version of openstack?