<div dir="ltr">Hi Michael,<div><br></div><div>Thanks. I have found the root cause of it. I need to replace USER with my own account "liu-xiao-guo". I think USER is different from my account name in the Ubuntu One.</div><div><br></div><div>Best regards,</div><div>XiaoGuo</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 4, 2016 at 3:10 PM, XiaoGuo Liu <span dir="ltr"><<a href="mailto:xiaoguo.liu@canonical.com" target="_blank">xiaoguo.liu@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Michael,<div><br></div><div>First, thanks for your detailed instructions. I just followed your steps to install the QEMU to test the Ubuntu Core. However, I have to problems in logging into the Ubuntu Core. The captured screen is like <a href="http://imgur.com/a/Qyfc9" target="_blank">http://imgur.com/a/Qyfc9</a>. May I know what the correct password for logging into the Ubuntu core. Is it the one for Ubuntu One? or the one for the ssh?</div><div><br></div><div>Thanks & best regards,</div><div>XiaoGuo</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Thu, Nov 3, 2016 at 11:47 PM, Michael Vogt <span dir="ltr"><<a href="mailto:michael.vogt@canonical.com" target="_blank">michael.vogt@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> The Snappy team is happy to announce the release of Ubuntu Core 16.<br> <br> Ubuntu Core is an operating system entirely based on snaps, including<br> its foundation. Applications, kernel, core operating system, and<br> gadget components are all managed as snaps and are installed and<br> refreshed by snapd, the daemon and tooling responsible for making it<br> all dance.<br> <br> The images are available currently for PC (amd64, i386) and<br> for Pi2/Pi3 and Dragonboard. These images can be downloaded from:<br> <br> <a href="http://releases.ubuntu.com/ubuntu-core/16/" rel="noreferrer" target="_blank">http://releases.ubuntu.com/ubu<wbr>ntu-core/16/</a><br> <br> Once unpacked, the images are bootable, the PC image can be booted<br> directly in qemu-kvm, virtualbox or on real hardware. When running the<br> images in qemu-kvm it is helpful to use the "-redir" feature of<br> qemu-kvm. e.g.:<br> <br> $ kvm -smp 2 -m 1500 -redir tcp:10022::22 ubuntu-core-16-amd64.img<br> <br> The message from console-conf is a bit misleading in this setup. It<br> will say "ssh <a href="mailto:USER@10.0.2.15" target="_blank">USER@10.0.2.15</a>". However due to the way that the<br> qemu-kvm user networking behaves, you will actually have to run the<br> following to ssh into the images:<br> <br> $ ssh -p 10022 USER@localhost<br> <br> or if you have the following snippet in ~/.ssh/config<br> <br> Host kvm.snappy<br> Hostname localhost<br> Port 10022<br> User USER<br> UserKnownHostsFile /dev/null<br> StrictHostKeyChecking no<br> <br> then you can just<br> <br> $ ssh kvm.snappy<br> <br> into it.<br> <br> The Pi2/Pi3/Dragonboard image can be written to a sdcard via dd. An<br> alternative way to write the image is to use "go-dd", e.g. on Ubuntu<br> 16.04:<br> <br> $ sudo snap install --devmode --beta godd<br> $ sudo /snap/bin/godd ubuntu-core-16-pi2.img.xz<br> [this will print a message showing what devices are removable]<br> $ xzcat ubuntu-core-16-pi2-rc2.img.xz | sudo /snap/bin/godd - /dev/sdXX<br> <br> After booting the image you can enter your Ubuntu One email and it<br> will automatically create a matching user with the right ssh keys. If<br> you do not have an Ubuntu SSO account yet please create one at:<br> <br> <a href="https://login.ubuntu.com/" rel="noreferrer" target="_blank">https://login.ubuntu.com/</a><br> <br> (don't forget to add your public ssh keys to that account).<br> <br> Known issues:<br> - pi3 wlan can not be initially configured, wired network needs to be<br> used for the initial setup (you can re-run "sudo console-conf" at<br> any later point to re-configure the device for wlan only<br> operation).<br> <br> Bug references for the pi3 known issues:<br> - <a href="http://pad.lv/1637153" rel="noreferrer" target="_blank">http://pad.lv/1637153</a><br> plugging in network cable during configuration can cause a traceback<br> on pi3<br> - <a href="http://pav.lv/1624322" rel="noreferrer" target="_blank">http://pav.lv/1624322</a><br> no wlan0 device at all on first boot on pi3<br> - <a href="http://pad.lv/1632387" rel="noreferrer" target="_blank">http://pad.lv/1632387</a><br> wifi setup times out on pi3 devices on first boot<br> <br> These images follow the "stable" channel. If you find any issues,<br> please let us know via:<br> <br> <a href="https://bugs.launchpad.net/snappy/" rel="noreferrer" target="_blank">https://bugs.launchpad.net/sna<wbr>ppy/</a><br> <br> Ubuntu Core 16 follows a rolling release model, security updates and<br> bug fixes will come to you via regular over the air updates for the<br> lifetime of the release.<br> <br> Enjoy this release!<br> <br> Cheers,<br> Michael Vogt (on behalf of the Snappy team)<br> <span class="m_-3841816910670961935HOEnZb"><font color="#888888"><br> <br> --<br> Devices mailing list<br> <a href="mailto:Devices@lists.snapcraft.io" target="_blank">Devices@lists.snapcraft.io</a><br> Modify settings or unsubscribe at: <a href="https://lists.snapcraft.io/mailman/listinfo/devices" rel="noreferrer" target="_blank">https://lists.snapcraft.io/mai<wbr>lman/listinfo/devices</a><br> </font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_-3841816910670961935gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">XiaoGuo, Liu </div></div></div></div> </font></span></div> </blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">XiaoGuo, Liu </div></div></div></div> </div>