cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henry Bonath <he...@thebonaths.com>
Subject SystemVM not reachable on HyperV Host
Date Wed, 02 Jan 2019 22:23:22 GMT
Hello, I am a new Cloudstack user trying to do a POC with Hyper-V as my
Hypervisor.

I have built a new standalone Cloudstack installation on CentOS 7.6.1810
roughly based on the guide posted on this list a few days ago:
https://github.com/apache/cloudstack-documentation/blob/master/source/quickinstallationguide/qig.rst

I have a single host running Hyper-V Server 2012R2 with both SMB and Local
Storage.

I understand based on reading documentation and mailing list archives that
HyperV requires the Zone to be built using "Advanced" Networking, so I have
done so, with all traffic types sharing a single vSwitch, with traffic
being untagged on a single /24 subnet. (192.168.41.0/24)

I successfully built the Hyper-V agent using the instructions here:
http://docs.cloudstack.apache.org/en/4.11.1.0/installguide/hypervisor/hyperv.html
and have added the host to Cloudstack successfully.

Upon enabling the Zone, I get to the point to where the System VMs are
provisioned and powered up, but the network fails to come up on them, and
the Mgmt server logs:
2019-01-02 17:11:21,999 INFO  [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-446:ctx-ad698407) (logid:c70818fe) Trying to connect to
192.168.41.29
2019-01-02 17:11:22,637 INFO  [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-447:ctx-c0bd643b) (logid:ae4c31a0) Trying to connect to
192.168.41.37
2019-01-02 17:11:24,005 INFO  [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-446:ctx-ad698407) (logid:c70818fe) Could] not connect to
192.168.41.29 due to java.net.NoRouteToHostException: No route to host
2019-01-02 17:11:24,643 INFO  [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-447:ctx-c0bd643b) (logid:ae4c31a0) Could] not connect to
192.168.41.37 due to java.net.NoRouteToHostException: No route to host

If I inspect the vNICs provisioned using Hyper-V Manager (in Windows) it is
assigning them to the proper vSwitch on the Host.

If I open up the console on either of the 2 SystemVMs and login with
root/password only the loopback interface is brought up.

After a timeout period the VMs are torn down and restarted but the process
continues.

Please advise as I would really like to get this working.
Thank you!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message