Conversation
jarkko

Jarkko Sakkinen

It would be sometimes useful if #QEMU w/o libvirt could interpret domain XML to some level.

Like for instance if you want to CI kernel, that would be one use case for this.

For the sake of example, here’s the QEMU command-line that I use as starting point for any kernel testing/CI:

qemu-system-x86_64 \
  -M pc \
  -monitor unix:monitor.sock,server,nowait \
  -serial unix:serial.sock,server,wait \
  -drive file=disk.img,if=virtio,format=raw \
  -net nic,model=virtio \
  -net user,hostfwd=tcp::10022-:22 \
  -rtc base=localtime \
  -nographic \
  -chardev socket,id=chrtpm,path=${SWTPM_DIR}/swtpm-sock \
  -tpmdev emulator,id=tpm0,chardev=chrtpm \
  -device ${QEMU_TPM_DEVICE},tpmdev=tpm0 \
  -bios /usr/share/edk2/ovmf/OVMF_CODE.fd \
  "$@"
2
0
0
janotomko@hachyderm.io

Jano Tomko

Reply to @jarkko

@jarkko I don't understand. How would XML improve your use case?

Also, why would you want to do it without libvirt? Interpreting domain XML and running QEMU is what using QEMU with libvirt does.

1
0
0
jarkko

Jarkko Sakkinen

Reply to @janotomko@hachyderm.io
@janotomko It would be easier to have a few template configurations and XML can be more easily post-manipulated.
0
0
0
stsquad@mastodon.org.uk

Alex

Reply to @jarkko

@jarkko what exactly do you need XML for? Is this just a carrier for the machine configuration.. in which case why not just use libvirt? You could always use to trigger an edit of the machine description if you want to change the kernel you boot in a particular domain.

1
0
0
jarkko

Jarkko Sakkinen

Reply to @stsquad@mastodon.org.uk
@stsquad I generate the whole operating system for each kernel test build. I don't have a machine description when I start compiling it.

Essentially each test VM is also one shot, deleted after a single test run.

Basis is like https://codeberg.org/jarkko/linux-tpmdd-test
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
I even used to bootstrap qemu and swtpm for every single build at one point ;-) It is great when testing kernel features when you can always start from known state.
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
I guess I could create my own XML parser which then outputs run-qemu.sh.
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: