From: "Yocto" <yocto@optimcloud.com>
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto - meta-anaconda installer gives "An unknown error has occurred"
Date: Thu, 18 Jun 2020 23:12:33 +0700 [thread overview]
Message-ID: <ddd6238faab99c6a0e5cf5edfa27915e@optimcloud.com> (raw)
In-Reply-To: <zfUG.1592494100488823620.BO2C@lists.yoctoproject.org>
On 2020-06-18 22:28, srijan.nandi@gmail.com wrote:
> Hello all,
>
> I created a core-image-full-cmdline for genericx86-64 machine. I am
> trying to configure meta-anaconda with it. I have used the following
> bblayers.conf file and added the requirements in the local.conf file.
>
I was recently able to build and boot an x86_64 image and install it via
anaconda from dunfell layer on real hardware and in XenServer
i did notice depending on the vm template used some would error,
centos/ununtu templates appeared ok, though not sure if you have
templates for os installs in vmware, never used it.
> 1. Target Build:
> bblayers.conf:
> BBLAYERS ?= " \
> /opt/graylog-poky/meta \
> /opt/graylog-poky/meta-poky \
> /opt/graylog-poky/meta-yocto-bsp \
> /opt/graylog-poky/meta-graylog \
> /opt/graylog-poky/meta-openembedded/meta-oe \
> /opt/graylog-poky/meta-openembedded/meta-python \
> /opt/graylog-poky/meta-openembedded/meta-networking \
> /opt/graylog-poky/meta-openembedded/meta-gnome \
> /opt/graylog-poky/meta-openembedded/meta-filesystems \
> /opt/graylog-poky/meta-openembedded/meta-initramfs \
> /opt/graylog-poky/meta-anaconda \
> "
> local.conf file:
> PACKAGE_CLASSES ?= "package_deb package_rpm"
> DISTRO_FEATURES_append = " systemd keyboard ldconfig pam"
> EXTRA_IMAGE_FEATURES_append = " package-management ssh-server-openssh"
>
> CORE_IMAGE_EXTRA_INSTALL_append = " kernel-modules iptables bash vim
> parted tcpdump dhcp-server dhcp-client"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> VIRTUAL-RUNTIME_initscripts = ""
> IMAGE_FSTYPES = "ext4 iso wic wic.vmdk"
>
> The target directory is /opt/graylog-poky/build.
>
> Then I created the install build with the following bblayers.conf and
> local.conf with the following customizations
>
> bblayers.conf:
> BBLAYERS ?= " \
> /opt/graylog-poky/meta \
> /opt/graylog-poky/meta-poky \
> /opt/graylog-poky/meta-yocto-bsp \
> /opt/graylog-poky/meta-graylog \
> /opt/graylog-poky/meta-openembedded/meta-oe \
> /opt/graylog-poky/meta-openembedded/meta-python \
> /opt/graylog-poky/meta-openembedded/meta-networking \
> /opt/graylog-poky/meta-openembedded/meta-gnome \
> /opt/graylog-poky/meta-openembedded/meta-filesystems \
> /opt/graylog-poky/meta-openembedded/meta-initramfs \
> /opt/graylog-poky/meta-anaconda \
> "
> local.conf:
> MACHINE ??= "qemux86-64"
> PACKAGE_CLASSES ?= "package_ipk"
> PACKAGE_CLASSES = "package_rpm"
> DISTRO = "anaconda"
> INSTALLER_TARGET_IMAGE = "core-image-full-cmdline"
> INSTALLER_TARGET_BUILD = "/opt/graylog-poky/build"
>
> It gave me an iso, when I try to boot in a vmware or on a virtualbox
> with the iso, it boots up and then after opening up the anaconda
> installer it comes up with the error message "An unknown error has
> occurred" and it hangs on the screen.
>
> Any help will be highly appreciated.
>
> Also would like to know if it is possible to boot an x86-64 using the
> above method.
>
next prev parent reply other threads:[~2020-06-18 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 15:28 #yocto - meta-anaconda installer gives "An unknown error has occurred" srijan.nandi
2020-06-18 16:12 ` Yocto [this message]
2020-06-19 4:24 ` srijan.nandi
2020-06-19 10:10 ` srijan.nandi
2020-06-19 11:10 ` srijan.nandi
2020-06-19 12:53 ` srijan.nandi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ddd6238faab99c6a0e5cf5edfa27915e@optimcloud.com \
--to=yocto@optimcloud.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.