Windows ISO won't detect ephemeral drive with virtio driver

Bug #1597502 reported by Kevin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Environment:

Fuel 9.0 deployed Mitaka, ceph backs everyone except ephemeral drives.

Procedure:

Download en_windows_server_2012_r2_x64_dvd_2707946.iso from MSDN.

Download https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso

Extract contents of en_windows_server_2012_r2_x64_dvd_2707946.iso to C:\Images\ISO

Extract contents of virtio-win.iso (virtio-win-0.1.118.iso) to C:\Images\virtio-win-0.1.118

copy virtio-win-0.1.118/ folder into .\ISO folder.

Run the following command:

oscdimg -n -m -bc:\Images\ISO\boot\etfsboot.com C:\Images\ISO C:\Images\en_windows_server_2012_r2_x64_dvd_
2707946_Openstack.iso

At this point if I look at the contents of en_windows_server_2012_r2_x64_dvd_
2707946_Openstack.iso I see a folder inside with the name "virtio-win-0.1.118" (which contains all of the virtio drivers).

Upload image to OS through Horizon. Boot a VM with Horizon, when the Windows installation asks "Where do you want to install Windows?" the box is blank (there is no disk drive detected to install the OS). I select "Load driver" select "Browse..." select the virtio driver viostor\2k12R2\amd64 no driver is found. If I uncheck the box that says "Hide drivers that aren't compatible with this computer's hardware." I see "Red Hat VirtIO SCSI controller (D:\VIRTIO-WIN-0.1.118\VIOSTOR\2k12R2\AMD64\VIOSTOR.INF)" show up. If I click "Next" it installs the driver but I still see a blank box on where to install the operating system.

From everything I can find the virtio drivers are the correct drivers I need for Windows to install on OS.

Revision history for this message
Sean Dague (sdague) wrote :

It is really not clear this is a nova bug, all the reproduce are about Fuel and Horizon. If you can boil this down to a Nova bug where something is passing data to Nova (outside of these tools), and it's not doing the expected thing then we can probably start to figure out what the issue is.

Changed in nova:
status: New → Invalid
Revision history for this message
Kevin (kvasko) wrote :

I'm not sure what product this would be in. The problem exhibits itself when the VM is running, so I assumed that it would be a nova issue.

If you boot a Windows ISO image with nova, (I assume nova) won't utilize the correct drivers to connect to the ephemeral/block storage drive with a Windows ISO. I'm not sure what other product this would be in, if you can tell me I would gladly file a report there.

In other words, I shouldn't have to perform these instructions to get a Windows image to work. I should be able to boot the ISO, install the drivers within the OS and then continue on with the OS installation. http://docs.openstack.org/image-guide/windows-image.html. My OS install is using KVM, what makes those instructions different than booting the ISO image in OS and installing the drivers?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.