Aaron Johnson's profile - activity

Thank you, Alin. Can you offer any info on why the Hyper-V VM is not being attached to the Hyper-V virtual switch when it is created?

Grrr. Where are my line breaks? What I want to achieve is Nova-compute creating a VM and attaching it to a Hyper-V virtual switch instead of "not connected" From there, I want to create a port on my Open vSwitch config and attach the VM to that. And from that point, talking to the rest of my Neutron networks would be stupendous. One step at a time, though...

Installed are: * Cloudbase HyperVNovaCompute_Juno_2014_2_1 revision {A66D13E0-CE61-47E0-8692-CD1DEA3AC082} dated 12/12/2014 4:10AM. * Cloudbase Open vSwitch for Hyper-V revision {901E9957-BDE3-4140-9750-93919011F52B} dated 1/26/2015 12:15AM (rev number and content date pulled from the MSI file's properties in Windows Explorer) * Running on Windows Server 2012r2 with the Hyper-V role. Up to date as far as Windows Update is concerned) I can create and launch an instance. It runs. However, the Hyper-V VM's virtual NIC is not attached to a Hyper-V virtual switch when it is created. (Virtual switch is set to "Not connected" in the Hyper-V manager.) I have checked nova.conf file's hyperv vswitch_name setting. It matches the name of the Hyper-V virtual switch. neutron_hyperv_agent.conf's physical_network_vswitch_mappings setting matches the name of the Hyper-V virtual switch as well. At this point, all I want to acheive is nova-compute attaching the VMs it created to a Hyper

Running Cloudbase Nova Compute (and Open vSwich) on a Windows Server 2012R2 compute node. Instances launch, but looking at the VMs in the Hyper-V manager shows network adpaters not connected to a virtual switch. Looking up the VMs ports in The neutron cli looking at the VM's port shows me that virtual interface binding has failed (binding:viftype is bindingfailed) and its status is DOWN.

I think I followed the directions for the Open vSwitch setup correctly. But I haven't had much luck deciphering the logs. Could someone give me a hint as to what I should be looking for in the nova-compute log? Much obliged...

Rather than changing my standard flavors, I created a smaller (by 1Gbyte) image and successfully launched an image that way.

Description of relevant parts of our environment: * OpenStack Juno from Ubuntu running on controller, neutron, and some KVM nodes. * One Hyper-V system running Cloudbase OpenStack Hyper-V Nova Compute ver {A66D13E0-CE61-47E0-8692-CD1DEA3AC082} installed a couple of weeks ago

Created an Ubuntu Server 14.04 image by making a new VM in Hyper-V, installing from an attached ISO image, saving. Hyper-V disk size was set to 20Gibytes. After installing and turning off this VM, I've uploaded VHD file to glance.

Trying to launch an instance from this image on my Hyper-V machine, I get this:

VHDResizeException: Cannot resize a VHD to a smaller size, the original size is 21474836480, the newer size is 21441282048

in my nova-compute log. Now, 21474836480 is exaclty 20 * 2 * 30 or 20Gibytes. And 21441282048 is exactly 32 * 2 * 20 less than that. Where are the missing 32 Mibytes going? Is this a Glance issue?

Any possible workarounds? Like create the VM by hand with a 19Gibyte VHD, upload that to Glance, then create instances from it? Manually change my instance sizes, adding 32Mibytes to the disk somewhere?