This contains just some minutes. Main project page here.
October 2, 2018
Participants
- Bernhard Rill
- Philippe
- Sang-Bum Suh
- Kai Lampka
- Anup Patel
- Artem Mygaiev
- Dmitry Morozov
- Gunnar
Discussing the tech summit
The overall plan for working session is at:
HVWS Workshop Schedule at Bangalore Tech Summit
A few people asked for a more exact agenda...
The first hour (10.30 CEST, if we have calculated correctly)
will be on GPU sharing.
At 11.30 approximately, switch to Security Block with ARM leading. Up to
45 minutes ARM intro/presentation, followed by Q&A / discussion
After that, follow-up topics.
(later in meeting) Kai offered to prepare some presentation on block devices.
Bernhard: What will be the planned for conferencing?
Philippe/Gunnar: Zoom is our assumed default. If we need to change to Skype or Hangout we will let you know. Details will be sent by Philippe.
Bernhard: We would like to have more questions in advance to cover in presentation.
Gunnar: Collecting at the bottom of this page - please add to it!
Artem: We could discuss my questions on implementation of OPTEE and support for virtualization ARMv8 and prior...
Virtual Platform Definition:
Crypto
Gunnar: Can we start HSM discussion by evaluating crypto support topic listed in table? Sang-Bum?
Sang-Bum: I have too many other engagements. I will be busy until 20th October at least. Maybe after that.
Block devices
Gunnar: We have discussed various aspect I'd like to bring down to some concrete results. Let's document it. Is VIRTIO good enough or what is the remaining gap?
Kai: Still investigating more
... but I think VIRTIO is not concrete enough. I think it needs more specialized descriptions
...That's why I want to investigate the TRIM command to see how well it works.
Kai: Persistence mgmt (stack) is not fully sorted out. (Not clear where in the software stack you should do what). What about Transaction/Commit
semantics for storage? Should that (API) be defined?
Gunnar: Experience from XVisor?
Anup: XVisor provides the VIRTIO block device standard and that's about it.
...It's up to each system to decide
... Where/when can dedicated memory per VM be used (pass-through), and where not?
Kai: For cost reason, one chip per VM is usually not realistic
Anup: Agreed.
General
Anup: The virtual platform specification, will it need to define the exact memory layout \[for memory-mapped devices\]? QEMU basically does this...
... some discussion
... conclusion that presumably yes this is needed if a VM is going to be fully portable? Let's return to this question.
Next meeting in 2 weeks, (with the Tech Summit working session in between).
September 25, 2018
Minutes TBD
September 18, 2018
Participants:
...