Latest prebuilt qemu vmdk not booting in VirtualBox
Description
Environment
Activity
Tom Rini September 1, 2020 at 2:21 PM
At this point I believe this issue should be closed. Any further problems using the prebuilt images with current AGL releases on VirtualBox should be filed as a new issue at this point, and include both the VirtualBox release used as well as the underlying host OS used.
Walt Miner September 1, 2020 at 2:03 PM
Is this still an open issue? Can this be closed?
Parth Dode January 2, 2020 at 8:06 AM
I get the same message except that I downloaded the prebuilt image from here-
location:"https://mirrors.edge.kernel.org/AGL/release/halibut/8.0.3/qemux86-64/deploy/images/qemux86-64/"
File:"agl-demo-platform-crosssdk-qemux86-64.wic.vmdk"
I dont understand what to do next , searching for solutions got me this error .
I dont understand the patch provided by @Martin Kelly
Please Help .
Loïc Collignon [ IoT.bzh ] November 2, 2017 at 3:48 PM
Ok, so this time my VirtualBox version was 5.2.0 r118431 and it worked perfectly.
I also tried with a VMWare Workstation Pro v14.0.0 build-6661328, and same result, it worked well whatever I choose when I'm ask about keeping or converting the disk file format.
Seems fixed to me!
Loïc Collignon [ IoT.bzh ] November 2, 2017 at 1:30 PM
I'll give it a try as soon as the download of the latest image is done.
As long as it's not compressed and I don't have a very good bandwidth, expect no update before few hours.
Details
Details
Assignee
Reporter
Labels
Affects versions
Priority
Minor
Hello,
Today I tried to use a prebuilt dab image in VirtualBox so I downloaded this file : https://download.automotivelinux.org/AGL/snapshots/master/latest/qemux86-64/deploy/images/qemux86-64/agl-demo-platform-crosssdk-qemux86-64-20170919062351.vmdk
(by the way, note that the prebuilt images in the snapshot folder are not compressed, while they are in the release folder)
The image seem to freeze very early in the boot process, after grub.
No error report on VirtualBox's screen, but on the serial window I have this:
[ 1.139658] VFS: Unable to mount root fs on unknown-block(0,0) [ 1.149741] User configuration error - no valid root filesystem found [ 1.160826] Kernel panic - not syncing: Invalid configuration from end user prevents continuing [ 1.186645] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.10.17-yocto-standard #1 [ 1.194421] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 1.250834] Call Trace: [ 1.263848] dump_stack+0x63/0x83 [ 1.282863] panic+0xd5/0x202 [ 1.284189] ? printk+0x48/0x50 [ 1.285917] mount_block_root+0x209/0x237 [ 1.293263] ? set_debug_rodata+0x12/0x12 [ 1.294326] mount_root+0x101/0x10a [ 1.295104] ? SyS_unlink+0x16/0x20 [ 1.301138] prepare_namespace+0x164/0x19c [ 1.302775] kernel_init_freeable+0x21a/0x231 [ 1.303973] ? rest_init+0x90/0x90 [ 1.305212] kernel_init+0xe/0x100 [ 1.305966] ret_from_fork+0x2c/0x40 [ 1.320876] Kernel Offset: disabled [ 1.323935] ---[ end Kernel panic - not syncing: Invalid configuration from end user prevents continuingThis happen no matter what my VirtualBox drive's setup (IDE/SATA/SCSI, etc...).
But images in the release folder works like a charm.