While I'm not sure, the GCE web console probably does the same as gcutil resetinstance, which is equivalent to pressing the hardware reset button on a physical machine.The serial info contains the console log, assuming the settings to do that got preserved in the switch from build-debian-cloud to bootstrap-vz.
I may actually have some time to play with bootstrap-vz this week, finally. Looking forward to trying it.- JimmyOn Mon, Mar 24, 2014 at 2:37 PM, olivier sallou <olivier.sallou@gmail.com> wrote:2014-03-24 18:51 GMT+01:00 Jimmy Kaplowitz <jkaplowitz@google.com>:
You're saying an instance added from the image booted once, but failed to boot after you typed sudo reboot (or equivalent) from within the VM?
I made a reboot from the graphical interface. Boot "looks" ok, but I can't connect anymore via SSH to the instance.That is puzzling, and except if something happened during startup to break the boot loader, I don't know why that would happen.
Do you have steps to reproduce? And does gcutil getserialportoutput reveal anything informative?
I have not yet done serial ouput.VM is shown as started so I think it would rather be a kind of network setup issue at next boot.I will try to get serial info, just in case.- Jimmy
On Mar 24, 2014 6:25 AM, "olivier sallou" <olivier.sallou@gmail.com> wrote:Hi,I made a few tests with latest modifications from Tomazs, here are my remarks/pb:- generated image has the name of the host where image was generated, not the VM instance name- after a reboot, I cannot connect anymore to the VMOlivier--gpg key id: 4096R/326D8438 (keyring.debian.org)Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438--gpg key id: 4096R/326D8438 (keyring.debian.org)Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438