Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

qemu: pass rootfs image in readonly mode #2477

Merged
merged 3 commits into from
Feb 26, 2020
Merged

Conversation

bergwolf
Copy link
Member

@bergwolf bergwolf commented Feb 19, 2020

  1. update govmm vendor
  2. fix up vhost user device after govmm vendor update
  3. pass guest rootfs image in readonly mode

@bergwolf bergwolf added backport wip Work in Progress (PR incomplete - needs more work or rework) labels Feb 19, 2020
@bergwolf bergwolf changed the title wip: qemu: pass rootfs image in readonly mode qemu: pass rootfs image in readonly mode Feb 21, 2020
@bergwolf bergwolf removed the wip Work in Progress (PR incomplete - needs more work or rework) label Feb 21, 2020
@bergwolf
Copy link
Member Author

/test

@codecov
Copy link

codecov bot commented Feb 21, 2020

Codecov Report

❗ No coverage uploaded for pull request base (master@18b21eb). Click here to learn what that means.
The diff coverage is 70%.

@@            Coverage Diff            @@
##             master    #2477   +/-   ##
=========================================
  Coverage          ?   50.74%           
=========================================
  Files             ?      116           
  Lines             ?    16538           
  Branches          ?        0           
=========================================
  Hits              ?     8392           
  Misses            ?     7120           
  Partials          ?     1026

To include block readonly capability. Included commits:

3700c55 qemu: add block device readonly support
88a25a2 Refactor code to support multiple virtio transports at runtime
2ee53b0 qemu: Don't set ".cache-size=" when CacheSize is 0

Signed-off-by: Peng Tao <bergwolf@hyper.sh>
So that we fobid guest from making changes to it.

Fixes: kata-containers#2476
Signed-off-by: Peng Tao <bergwolf@hyper.sh>
For one thing, we should not make kata's internal device type
exactly as govmm string by string.

For another thing, latest govmm changes the device driver strings
and it breaks kata in such a way but the fault is on kata side IMHO.

Signed-off-by: Peng Tao <bergwolf@hyper.sh>
@bergwolf
Copy link
Member Author

/test

@bergwolf
Copy link
Member Author

centos-8-q-35 failure is unrelated and tracked at kata-containers/tests#2328

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants