Hi Gary,
     Thanks for your tips~
      I think I should add the uefi parameters to the scripts and try again.

On Saturday, 30 July 2016 03:53:23 UTC+8, Gary Grebus wrote:
>
>
>
> On Thursday, July 28, 2016 at 4:25:59 AM UTC-4, [email protected] wrote:
>>
>> Hi Nick,
>>     It's great that you can help :-)
>>     I will wait for the newer version of CoreOS which has newer version 
>> of Docker.
>>     Another question, Geoff said that you can boot CoreOS via PXE. I have 
>> tried to 
>> boot image with PXE but met some problem. 
>>     I has used the CoreOS 1122 and the scrpit : coreos_production_pxe.sh, 
>> and run
>>  the command:
>> *./coreos_production_pxe.sh -nographic -append 'console=tty0 
>> console=ttyAMA0'*
>> But no response and console no output. 
>> I use below command, no response either.... and ssh 127.0.0.1 -p 2222 no 
>>  response...
>> *./coreos_production_pxe.sh -curses *
>>
>
> Are you getting a blank qemu console?    I found I needed to add a EFI 
> BIOS image to the qemu command in the script.   Google to find a copy of 
> the  QEMU_EFI.fd file, and then add '-bios QEMU_EFI.fd'  to the qemu 
> command in the script.
>
> Note that script will directly boot the kernel/initrd used for PXE into a 
> qemu virtual machine.   If you have a real machine you want to PXE boot, 
> you need to set up your PXE server to deliver 
> *coreos_production_pxe_grub.efi,* and then use the appropriate grub 
> commands to fetch the kernel and initrd (I think the latest version of that 
> grub supports tftp and http).
>
>  
>
>>      I am not sure what happened ,so kindly need your help. My test 
>> environment is AMD 
>> Seattle ARM64 server chip(SoftIron Machine), ubuntu 16.04 baremetal.
>>      Really appreciated for your help :-)
>>
>> On Thursday, 28 July 2016 03:19:03 UTC+8, Nick Owens wrote:
>>>
>>> hi kevin, 
>>>
>>> it would appear this was fixed by 
>>> https://github.com/docker/containerd/pull/226, however, unfortunately 
>>> containerd has no tagged releases which have the fix. hopefully they 
>>> will make a tag, and we can bump the containerd version then. 
>>>
>>> nick 
>>>
>>> On 07/26/2016 08:25 PM, Kevin Zhao wrote: 
>>> > Hi All, 
>>> >     After launching CoreOS image: 
>>> > 
>>> https://alpha.release.core-os.net/arm64-usr/1109.1.0/coreos_production_image.bin.bz2
>>>  
>>> >  with libvirt, I run the command: 
>>> > $docker ps 
>>> > But the command is blocked and I see the output below: 
>>> > ===================================================================== 
>>> > audit: type=1006 audit(1469589592.992:3): pid=2751 uid=0 
>>> > old-auid=4294967295 auid=500 old-ses=4294967295 ses=1 res=1 
>>> > containerd[2883]: syscall 1069 
>>> > Code: f94023e4 f94027e5 f9400fe8 d4000001 (b13ffc1f) 
>>> > CPU: 1 PID: 2883 Comm: containerd Not tainted 4.6.4-coreos #1 
>>> > Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 
>>> > task: ffff80002e721a00 ti: ffff80002e8c8000 task.ti: ffff80002e8c8000 
>>> > PC is at 0x4ea280 
>>> > LR is at 0x4ea260 
>>> > pc : [<00000000004ea280>] lr : [<00000000004ea260>] pstate: 60000000 
>>> > sp : 00000048200327c0 
>>> > x29: 0000ffffa2b7e950 x28: 0000004820166780 
>>> > x27: 0000000000d7ba68 x26: 0000000000000000 
>>> > x25: 0000000000800000 x24: 0000000000000000 
>>> > x23: 0000ffffa4f05000 x22: 0000ffffd079470f 
>>> > x21: 0000000000000000 x20: 000000000046bc68 
>>> > x19: 0000000000439f78 x18: 0000000000000000 
>>> > x17: 0000000000b6f970 x16: 0000004820032eb0 
>>> > x15: 0000000000000040 x14: 0000000000000000 
>>> > x13: 0000000000000000 x12: 0000000000000008 
>>> > x11: 0000000000000000 x10: 000000482005c540 
>>> > x9 : 0000004820032fa0 x8 : 000000000000042d 
>>> > x7 : 00000048200f6180 x6 : 0000000000533518 
>>> > x5 : 0000000000000000 x4 : 0000000000000000 
>>> > x3 : ffffffffffffffff x2 : 0000000000000080 
>>> > x1 : 00000048200328b8 x0 : 0000000000000003 
>>> > 
>>> > containerd[2886]: syscall 1069 
>>> > Code: f94023e4 f94027e5 f9400fe8 d4000001 (b13ffc1f) 
>>> > CPU: 1 PID: 2886 Comm: containerd Not tainted 4.6.4-coreos #1 
>>> > Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 
>>> > task: ffff80002e724100 ti: ffff80002e8d4000 task.ti: ffff80002e8d4000 
>>> > PC is at 0x4ea280 
>>> > LR is at 0x4ea260 
>>> > pc : [<00000000004ea280>] lr : [<00000000004ea260>] pstate: 60000000 
>>> > sp : 00000048200377c0 
>>> > x29: 0000ffff9888e950 x28: 000000482005d080 
>>> > x27: 0000000000d7ba68 x26: 0000000000000000 
>>> > x25: 0000000000800000 x24: 0000000000000000 
>>> > x23: 0000ffff99415000 x22: 0000fffff70ea36f 
>>> > x21: 0000000000000000 x20: 000000000046bc68 
>>> > x19: 0000000000439f78 x18: 0000000000000000 
>>> > x17: 0000000000b6f970 x16: 0000004820037eb0 
>>> > x15: 0000000000000040 x14: 0000000000000000 
>>> > x13: 0000000000000000 x12: 0000000000000008 
>>> > x11: 0000000000000000 x10: 0000004820066540 
>>> > x9 : 0000004820037fa0 x8 : 000000000000042d 
>>> > x7 : 0000004820000d80 x6 : 0000000000533518 
>>> > x5 : 0000000000000000 x4 : 0000000000000000 
>>> > x3 : ffffffffffffffff x2 : 0000000000000080 
>>> > x1 : 00000048200378b8 x0 : 0000000000000003 
>>> > 
>>> > random: nonblocking pool is initialized 
>>> > ==================================================================== 
>>> > I am not sure what happened. Need your kindly help :-) 
>>> > 
>>>
>>

Reply via email to