Topics

Failing to boot Clear guest


Ross Burton
 

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script
I've fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross


Geoffroy Van Cutsem
 

Is this with an acrn.efi that you have compiled yourself (using Yocto) or a pre-built version?

The reason I'm asking is we had a bug that we closed very recently whereby you couldn't launch Guest OS if you were running a compiler that had been built on Ubuntu - see https://github.com/projectacrn/acrn-hypervisor/issues/2410. There isn't much detail in the issue description, and the little that's in there does not sound like the same issue as yours but it would be interesting to know if this is generic or potentially specific to the binary as built by your environment.

Geoffroy

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Thursday, January 31, 2019 6:03 PM
To: acrn-users@lists.projectacrn.org
Subject: [acrn-users] Failing to boot Clear guest

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script I've
fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross


Ross Burton
 

My own, but built from the 2019w05.2 tag so should have those fixes in.

The kernel is booting, it just can't mount for some reason. Entirely
possibly that it's user error..

Ross

On Thu, 31 Jan 2019 at 17:13, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote:

Is this with an acrn.efi that you have compiled yourself (using Yocto) or a pre-built version?

The reason I'm asking is we had a bug that we closed very recently whereby you couldn't launch Guest OS if you were running a compiler that had been built on Ubuntu - see https://github.com/projectacrn/acrn-hypervisor/issues/2410. There isn't much detail in the issue description, and the little that's in there does not sound like the same issue as yours but it would be interesting to know if this is generic or potentially specific to the binary as built by your environment.

Geoffroy

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Thursday, January 31, 2019 6:03 PM
To: acrn-users@lists.projectacrn.org
Subject: [acrn-users] Failing to boot Clear guest

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script I've
fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross




Ross Burton
 

So good news/bad news. The good news is that this doesn't appear to
be an acrn issue right now. The bad news is that I'm now debugging
mkfs.ext4...

Ross

On Thu, 31 Jan 2019 at 17:02, Burton, Ross <ross.burton@intel.com> wrote:

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script
I've fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross


Yin, Fengwei
 

Hi Ross,

On 2/1/19 5:41 PM, Ross Burton wrote:
So good news/bad news. The good news is that this doesn't appear to
be an acrn issue right now. The bad news is that I'm now debugging
mkfs.ext4...
Could you please share the platform you are using?

Regards
Yin, Fengwei

Ross
On Thu, 31 Jan 2019 at 17:02, Burton, Ross <ross.burton@intel.com> wrote:

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script
I've fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross


Ross Burton
 

On Fri, 1 Feb 2019 at 09:46, Yin, Fengwei <fengwei.yin@intel.com> wrote:
Could you please share the platform you are using?
The images were built using the Yocto Project, but the bug is actually
corrupted files in the file system which I can replicate using
Debian's mkfs.

Ross


Yin, Fengwei
 

On Fri, Feb 01, 2019 at 09:47:39AM +0000, Ross Burton wrote:
On Fri, 1 Feb 2019 at 09:46, Yin, Fengwei <fengwei.yin@intel.com> wrote:
Could you please share the platform you are using?
The images were built using the Yocto Project, but the bug is actually
corrupted files in the file system which I can replicate using
Debian's mkfs.
I meant the hardware platform? Is it MRB, UP2 or NUC?

Regards
Yin, Fengwei


Ross



Ross Burton
 

Oh, NUC. My current issue is definitely unrelated to acrn though.

On Fri, 1 Feb 2019 at 09:55, Yin, Fengwei <fengwei.yin@intel.com> wrote:

On Fri, Feb 01, 2019 at 09:47:39AM +0000, Ross Burton wrote:
On Fri, 1 Feb 2019 at 09:46, Yin, Fengwei <fengwei.yin@intel.com> wrote:
Could you please share the platform you are using?
The images were built using the Yocto Project, but the bug is actually
corrupted files in the file system which I can replicate using
Debian's mkfs.
I meant the hardware platform? Is it MRB, UP2 or NUC?

Regards
Yin, Fengwei


Ross




Ross Burton
 

More good news: fixed e2fsprogs and now I'm looking at a Clear login
on the guest I started.

Ross

On Fri, 1 Feb 2019 at 09:41, Burton, Ross <ross.burton@intel.com> wrote:

So good news/bad news. The good news is that this doesn't appear to
be an acrn issue right now. The bad news is that I'm now debugging
mkfs.ext4...

Ross

On Thu, 31 Jan 2019 at 17:02, Burton, Ross <ross.burton@intel.com> wrote:

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script
I've fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows that
the third partition is a ext4 rootfs. Any ideas?

Ross


Geoffroy Van Cutsem
 

Yeah, congrats!!

-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-
users@lists.projectacrn.org] On Behalf Of Ross Burton
Sent: Friday, February 1, 2019 2:03 PM
To: acrn-users@lists.projectacrn.org
Subject: Re: [acrn-users] Failing to boot Clear guest

More good news: fixed e2fsprogs and now I'm looking at a Clear login on the
guest I started.

Ross

On Fri, 1 Feb 2019 at 09:41, Burton, Ross <ross.burton@intel.com> wrote:

So good news/bad news. The good news is that this doesn't appear to
be an acrn issue right now. The bad news is that I'm now debugging
mkfs.ext4...

Ross

On Thu, 31 Jan 2019 at 17:02, Burton, Ross <ross.burton@intel.com> wrote:

Hi,

I've downloaded the Clear kvm image (27230) and iot kernel and am
attempting to boot them as a guest. Taking the launch_uos.sh script
I've fixed the paths for the kernel and rootfs, but now on boot:

...
EXT4-fs error: (device vda3): ext4_iget:4851: inode #8: comm
swapper/0: checksum invalid
EXT4-fs (vda3): no journal found
...
List of all partitions:
fd00: 8946688 vda
fd01 523264 vda1
fd02 32768 vda2
fd0 8388603 vda3
No filesystem could mount root

I'm setting root=/dev/vda3, and loopback mounting the image shows
that the third partition is a ext4 rootfs. Any ideas?

Ross