On Tue, 21 Dec 2021, Al Slater wrote:
> Hi, > > I am trying to start an omnios r151040g instance in AWS using a t3.micro > instance type to test out the new ena driver. > > On boot, I am getting the following panic > > panic[cpu0]/thread=fffffe00033f0c20: timed out waiting for admin response I just tried booting a t3.micro instance using the latest r151040g cloud image ( https://downloads.omnios.org/media/r151040/cloud-151040g.vmdk.zst ) and saw the same as you - it paniced and rebooted three times but then is up and working. There's obviously something to fix here but does yours ever stabilise? I think what's happening with mine is that the cloud-init that's in the cloud images is playing with interfaces (ephemeral DHCP interfaces etc.) and triggering the problem with teardown that Peter saw. After three reboots, I'm here: OmniOS r151040 Version omnios-r151040-d75907718a 64-bit Copyright (c) 2012-2017 OmniTI Computer Consulting, Inc. Copyright (c) 2017-2021 OmniOS Community Edition (OmniOSce) Association. WARNING: illegal PCI request: offset = 100, size = 4 WARNING: illegal PCI request: offset = 100, size = 4 Hostname: ip-172-31-11-21 ip-172-31-11-21 console login: root Password: Last login: Tue Dec 21 18:20:13 2021 on console OmniOS r151040 omnios-r151040-d75907718a December 2021 root@ip-172-31-11-21:~# root@ip-172-31-11-21:~# ipadm ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 ena0/dhcp dhcp ok 172.31.11.21/20 lo0/v6 static ok ::1/128 root@ip-172-31-11-21:~# ping 1.1.1.1 1.1.1.1 is alive root@ip-172-31-11-21:~# I could publish this AMI if you'd like to experiment with it. Andy ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/Ta838d1d97b3f9153-Mcb742ee251f1660c8c03a2fa Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
