Sorry to jump on an old thread but I'm having the same issue. The machine is physical with 8GB of RAM so I can't simply add more.
I am also using the production links above. Thanks On Wednesday, November 23, 2016 at 4:05:59 AM UTC, Arnaud Brunet wrote: > > Ok I found my problem. > > I had more RAM on the virtual machine. And now it's good. > > Thanks > > > Le mercredi 23 novembre 2016 12:04:01 UTC+11, Arnaud Brunet a écrit : >> >> Thanks Brandon, >> >> I followed https://coreos.com/os/docs/latest/booting-with-pxe.html. So I >> downloaded them from >> >> https://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuzhttps://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe_image.cpio.gz >> >> I downloaded them from my brower and I copied them with a VirtualBox shared >> folders. >> >> >> >> >> >> Le mercredi 23 novembre 2016 11:47:27 UTC+11, Brandon Philips a écrit : >>> >>> What version of CoreOS Linux are you using? Looks like something might >>> be messed up with our rootfstype=tmpfs setup. >>> >>> Can you provide the URL you downloaded coreos_production_pxe.vmlinuz and >>> coreos_production_pxe_image.cpio.gz from? >>> >>> On Tue, Nov 22, 2016 at 4:45 PM Arnaud Brunet <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> I try to start CoreOS via PXE in VirtualBox. >>>> >>>> I setup my PXE server. It works with a debian installer >>>> >>>> Then I follow the >>>> https://coreos.com/os/docs/latest/booting-with-pxe.html documentation. >>>> But I can not start my server. >>>> >>>> >>>> First I have an error stating that 'baselayout.conf' is missing. View >>>> screenshot 'missing_baselayout.png' >>>> Then I have a failure on switch-root. View screenshot >>>> 'failed_to_start_switch_root.png' >>>> >>>> My PXE boot options >>>> >>>> LABEL coreos >>>> kernel coreos_production_pxe.vmlinuz >>>> initrd coreos_production_pxe_image.cpio.gz >>>> append cloud-config-url=http://192.168.1.1/pxe-cloud-config.yml >>>> >>>> >>>> >>>> My config.yml >>>> >>>> coreos: >>>> units: >>>> - name: etcd2.service >>>> command: start >>>> - name: fleet.service >>>> command: start >>>> ssh_authorized_keys: >>>> - ssh-rsa AAAAB3NzaC1yc2EAAAADAQAB...== root@pxe >>>> >>>> >>>> Did I miss something ? >>>> >>>> Regards, >>>> Arnaud >>>> >>>
