Jump to content

Search the Community

Showing results for tags 'virtual-qemu'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 2 results

  1. I'm trying to get the armbian x86-64 generic image to run in virtualbox. I can successfully convert the *.img file to qcow2 and qemu will run it just fine. However, virtualbox fails to boot it in any format (qcow2, vmdk, vhd, vdi, etc). The grub menu comes up, but when trying to boot Linux then it just sits at a blinking cursor. I've tried converting this a variety of ways, such as using `qemu-img convert`, `vboxmanage convertfromraw` and `vboxmanage convertdd`. None of them yield an image that virtualbox will boot. Has anybody else had success with this, and/or know how to fix it? Thanks.
  2. Hi there, let's assume I have two custom extra packages which have a dependency in extras-buildpkgs. 10-package1.conf 20-package2.conf 20-package2 has a package_builddeps to 10-package1. It is marked in the .conf file as in package2/debian/control@Build-Depends. Package 10-package1 is build properly and stored under output/deps/extra/jammy_utils. While building package 20-package2 it does install resolve 10-package1 before and in the logs I see the `Bad package name` (general.sh:1290) message. Also the adjustment of package20's rules to use apt-get during build prep does not find the package. Is there anything I have to configure/consider to resolve this or is this an unsupported case? Thanks, Max
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines