Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi!

I had the exact same issue with the cloudbase image when I was testing Windows a few weeks back. I didn't find a real solution, but I found a workaround really quickly, so I stopped looking for one

For me the workaround was to not assign a private key, when launching a windows instance. This way it could boot up. Then I used the noVNC console to setup an administrator account(I think the cloudbase version doesn't have a password for administrator at first boot up, but when you try to login it asks for creating one). After this everything worked as expected.

I hope this can help you, although it isn't a real solution.