You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2022. It is now read-only.
When there's a problem with the cloud-init file in your workload your instance creation will not complete. As create hasn't completed, you cannot connect to the VM as ccloudvm serialise commands to instances. If you pass the --debug flag to create an SSH connection string will be printed on the screen that you can use to connect to the instance from another shell. What you almost always do after you've connected is to look in the file /var/log/cloud-init-output.log. It would be nice if the tool had a debug mode where this information was retrieved automatically.
The text was updated successfully, but these errors were encountered:
Enabling qemu port shows some of the error messages, but yes, piping all the info from cloud-init-output.log to serial port would be nice. @rbradford somehow the link you have pasted above doesn't seems to be in existence anymore.
When there's a problem with the cloud-init file in your workload your instance creation will not complete. As create hasn't completed, you cannot connect to the VM as ccloudvm serialise commands to instances. If you pass the --debug flag to create an SSH connection string will be printed on the screen that you can use to connect to the instance from another shell. What you almost always do after you've connected is to look in the file /var/log/cloud-init-output.log. It would be nice if the tool had a debug mode where this information was retrieved automatically.
The text was updated successfully, but these errors were encountered: