openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #23505
Re: [Devstack] [Hyper-V] Instance fails to launch on Hyper-V server
Hi Peter,
Yeah, that's exactly it, I had originally created the vm as a VHDX.
I've just used the Hyper-V "Edit Disk" feature to convert it from
VHDX to VHD, re-uploaded it (glance image-create) and then everything
went smoothly. Just a while ago I managed to deploy it from my
devstack to the hyper-v host.
thank you a lot! good to know that's on the roadmap too :)
regards,
--
Bruno de Oliveira
System Analyst, Developer
brunnop.oliveira@xxxxxxxxx
On Thu, May 9, 2013 at 4:42 PM, Peter Pouliot <ppouliot@xxxxxxxxxxxxx> wrote:
> Did you explicitly create the vm as a VHD. If not it was created as VHDX. VHDX isn't currently supported, it's on our roadmap for Havana.
>
> p
>
> Peter J. Pouliot, CISSP
> Senior SDET, OpenStack
>
> Microsoft
> New England Research & Development Center
> One Memorial Drive,Cambridge, MA 02142
> PPOULIOT@xxxxxxxxxxxxx | Tel: +1(857) 453 6436
>
> -----Original Message-----
> From: Openstack [mailto:openstack-bounces+ppouliot=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Bruno Oliveira
> Sent: Thursday, May 9, 2013 12:42 PM
> To: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: [Openstack] [Devstack] [Hyper-V] Instance fails to launch on Hyper-V server
>
> Hi guys,
>
> I'm having an issue deploying a vm to a hyper-v host, i wont boot
> note: the disk_image itself was built by that very hyperv host
>
> I'm currently using openstack (devstack) build grizzly within a Ubuntu 12.04 LTS.
>
> And my HyperV has got the "Hyper-V Nova-Compute Driver"
>
> please, check it out:
>
> I have successfully uploaded (glance image-create) a WinServer virtual machine from a Hyper-V host with the property "hypervisor_type=hyperv". Here are the stats:
>
>
> $ /opt/stack/keystone/etc$ glance image-list
> +--------------------------------------+---------------------------------+-------------+------------------+------------+--------+
> | ID | Name
> | Disk Format | Container Format | Size | Status |
> +--------------------------------------+---------------------------------+-------------+------------------+------------+--------+
> | d9fbe5db-b852-4832-9deb-c558d559eadf | Windows-Server-2008-R2-x64
> | vhd | bare | 7486832640 | active |
> +--------------------------------------+---------------------------------+-------------+------------------+------------+--------+
>
> $ glance image-show d9fbe5db-b852-4832-9deb-c558d559eadf
>
> +----------------------------+--------------------------------------+
> | Property | Value |
> +----------------------------+--------------------------------------+
> | Property 'hypervisor_type' | hyperv |
> | checksum | 202700a9b2b4f662b62ac5acebc09860 |
> | container_format | bare |
> | created_at | 2013-05-09T13:33:48 |
> | deleted | False |
> | disk_format | vhd |
> | id | d9fbe5db-b852-4832-9deb-c558d559eadf |
> | is_public | True |
> | min_disk | 0 |
> | min_ram | 0 |
> | name | Windows-Server-2008-R2-x64 |
> | owner | 670f5dd4070d44b6a8308277a236d1af |
> | protected | False |
> | size | 7486832640 |
> | status | active |
> | updated_at | 2013-05-09T14:01:02 |
> +----------------------------+--------------------------------------+
>
> But for some reason, it won't ever boot.
> "nova --boot" is not being able to start it in my HyperV...
>
> $ nova boot hyperv-deploy-test \
> --image d9fbe5db-b852-4832-9deb-c558d559eadf \
> --flavor 3
> +------------------------------------+--------------------------------
> | Property | Value
> +------------------------------------+--------------------------------
> | status | BUILD
> | updated | 2013-05-09T16:09:28Z
> | OS-EXT-STS:task_state | scheduling
> | OS-EXT-SRV-ATTR:host | None
> | key_name | None
> | image | Windows-Server-2008-R2-x64
> | hostId |
> | OS-EXT-STS:vm_state | building
> | OS-EXT-SRV-ATTR:instance_name | instance-0000001c
> | OS-EXT-SRV-ATTR:hypervisor_hostname| None
> | flavor | m1.medium
> | id | 2ee4e176-1824-4557-ab60-eb32659f7e4c
>
> | security_groups | [{u'name': u'default'}]
> | user_id | d920fc85ecd9426ebd9e3f8c7300f5d4
> | name | hyperv-deploy-test
> | adminPass | q6NxDMXyq7NM
> | tenant_id | 670f5dd4070d44b6a8308277a236d1af
> | created | 2013-05-09T16:09:28Z
> | OS-DCF:diskConfig | MANUAL
> | metadata | {}
> | accessIPv4 |
> | accessIPv6 |
> | progress | 0
> | OS-EXT-STS:power_state | 0
> | OS-EXT-AZ:availability_zone | nova
> | config_drive |
> +------------------------------------+--------------------------------
>
> I can see that disk_image file within my folder C:\OpenStack\Instances of the Hyper-V server, that means the transfer to the server was done, right? Am I missing anything ?
>
> But for some reason, it never goes up to ACTIVE. If crashes to ERROR
>
> $ /opt/stack/keystone/etc$ nova list
> +--------------------------------------+--------------------+--------+---------------------+
> | ID | Name | Status |
> Networks |
> +--------------------------------------+--------------------+--------+---------------------+
> | 2ee4e176-1824-4557-ab60-eb32659f7e4c | hyperv-deploy-test | ERROR |
> public=172.x.y.z |
> +--------------------------------------+--------------------+--------+---------------------+
>
>
> I made sure to have added to the Scheduler filters in my /etc/nova/nova.conf, as below:
>
>
> ## Setting up Custom Filters
> scheduler_available_filters=nova.scheduler.filters.all_filters
> schedule_default_filters=ImagePropertiesFilter
>
> --
>
> Thanks a lot!
>
> --
>
> Bruno Oliveira
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
References
