Filesystem is corrupted when sharing files from host to the Virtual Platform

I am making tests within the FVP and used the below steps to copy files into the FVP

To "bake" files into the target filesystem the following steps need to be followed:

  1. Mount the filesystem image on a local host directory
  2. Edit the mounted filesystem to include the desired files
  3. Unmount it and boot the target as usual

When i create a new file or copy a folder into the filesystem. I get the following error. This error doesn't occur when the existing files are recompiled or changed.

Is there any solution to overcome this issue?

Parents
  • You've invoked:

    lkvm run -k test_mem.flat -m 24 -c 1 --name guest-196

    I am not familiar with "lkvm" command but searching it in the Internet, I've found the git repo at https://github.com/lkvm/lkvm .

    Fatal: Unable to open kernel test_mem.flat

    And, searching the error above in the repo, I've found the code below emits the error.

    lkvm/kvm.c at master · lkvm/lkvm · GitHub

    Calling open() dies with the error below so I suspect the file test_mem.flat has some issue.

    EXT4-fs error (device vda2): ext4_lookup:1838: inode #20: comm lkvm: deleted inode reference: 791

    Searching the ext4_lookup error above in the Internet, a couple of article suggest running fsck to fix this type of filesystem (ext4) issue.


    I hope this helps.

    Kind regards,
    Toshi

Reply
  • You've invoked:

    lkvm run -k test_mem.flat -m 24 -c 1 --name guest-196

    I am not familiar with "lkvm" command but searching it in the Internet, I've found the git repo at https://github.com/lkvm/lkvm .

    Fatal: Unable to open kernel test_mem.flat

    And, searching the error above in the repo, I've found the code below emits the error.

    lkvm/kvm.c at master · lkvm/lkvm · GitHub

    Calling open() dies with the error below so I suspect the file test_mem.flat has some issue.

    EXT4-fs error (device vda2): ext4_lookup:1838: inode #20: comm lkvm: deleted inode reference: 791

    Searching the ext4_lookup error above in the Internet, a couple of article suggest running fsck to fix this type of filesystem (ext4) issue.


    I hope this helps.

    Kind regards,
    Toshi

Children
No data