cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Peterson <>
Subject RE: Recreating SystemVM's
Date Tue, 06 Jun 2017 21:31:06 GMT
Ok so I pulled this from Sunday morning.

errorInfo: [HOST_CANNOT_ATTACH_NETWORK, OpaqueRef:65d0c844-bd70-81e9-4518-8809e1dc0ee7, OpaqueRef:0093ac3f-9f3a-37e1-9cdb-581398d27ba2]

XenServer error.

Now this still gets me because all of the other VM's launched just fine.

Going into XenCenter I see an error at the bottom This PIF is a bond slave and cannot be plugged.


If I go to networking on the hosts I see the storage vlans and bonds are all there.

I see my GUEST-PUB bond is there and LACP is setup correct.

Any suggestions ? 


-----Original Message-----
From: Jeremy Peterson [] 
Sent: Tuesday, June 6, 2017 9:23 AM
Subject: RE: Recreating SystemVM's

Thank you all for those responses.

I'll comb through my management-server.log and post a pastebin if I'm scratching my head.


-----Original Message-----
From: Rajani Karuturi [] 
Sent: Tuesday, June 6, 2017 6:53 AM
Subject: Re: Recreating SystemVM's

If the zone is enabled, cloudstack should recreate them automatically.

~ Rajani

On June 6, 2017 at 11:37 AM, Erik Weber (

CloudStack should recreate automatically, check the mgmt server logs for hints of why it doesn't


tir. 6. jun. 2017 kl. 04.29 skrev Jeremy Peterson

I had an issue Sunday morning with cloudstack 4.9.0 and xenserver 6.5.0.
My hosts stop sending LACP PDU's and caused a network drop to iSCSI primary storage.

So all my instances recovered via HA enabled.

But my console proxy and secondary storage system VM's got stuck in a boot state that would
not power on.

At this time they are expunged and gone.

How do I tell cloudstack-management to recreate system VM's?

I'm drawing a blank since deploying CS two years ago and just keeping things running and adding
hosts and more storage everything has been so stable.

View raw message