Hello,
I'm trying to provide multiple CPUs for a linux VM on top of L4.
I'm using the qemu virt machine and building for aarch64. so I used *-smp*
option to provide more CPUs.
> $ qemu-system-aarch64 -M virt,virtualization=true -cpu cortex-a57 -smp 4
> -m 1024 -kernel ....etc....
Unfortunately, This didn't work. I tried to add more CPU device nodes to
the dts file *virt-arm_virt-64.dts *but it also didn't work.
I think that it's because of the provided interrupt-controller with
*virt-arm_virt-64.dts* in *l4/pkg/uvmm/conf/dts* which mentioned that it
supports only one CPU.
> icsoc {
> compatible = "simple-bus";
> #address-cells = <2>;
> #size-cells = <2>;
> ranges;
>
> /* Uvmm will adapt the compatible string depending on the present
> gic
> * version. It expects reg entries that provide enough space for
> the
> * Cpu/Dist interface for gicv2 (at least 0x1000, 0x1000) or the
> * Dist/Redist interface for gicv3 (0x10000, 0x20000 * number of
> cpus).
> *
> *The entries provided here support any gicv2 setup or a gicv3 setup
> * with one Cpu.*
> */
> gic: interrupt-controller {
> compatible = "arm,gic-400", "arm,cortex-a15-gic",
> "arm,cortex-a9-gic";
> #interrupt-cells = <3>;
> #address-cells = <0>;
> interrupt-controller;
> reg = <0 0x40000 0 0x10000>,
> <0 0x50000 0 0x20000>;
> };
> };
>
My question now, is there any workaround to support multiple CPUs for virt
machine on arm64 ?
Thanks,
Regards
--
Mohamed Dawod
*Software Engineer, *Cairo Egypt
--
*Driving Innovation! Visit our website www.avelabs.com
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow
this link: http://www.avelabs.com/email/disclaimer.html
<http://www.avelabs.com/email/disclaimer.html>
_______________________________________________
l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de
To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de
Hi all,
below is the official CfP for the microkernel devroom at FOSDEM 2025. I am
looking forward to a strong participation from all microkernel/unikernel
research groups and companies, not only in the form of attendance, but
also in the form of great talks :)
Cheers,
Udo
We are happy to announce the CfP for the "Microkernel and Component-Based OS"
devroom at the upcoming FOSDEM 2025.
Developers and users of various free and open-source microkernel-based,
unikernel-based and component-based operating systems will meet again at
FOSDEM (https://fosdem.org) during the weekend of February 1/2, 2025 and
will share a developer room.
The microkernel and component-based OS devroom is currently looking for your
participation in the form of proposals for talks, demos and other related
activities. Possible topics for the devroom include, but are not limited to:
* introduction of a specific OS or framework
* design of subsystems and the general architecture of an OS
* languages, tools and toolchains used
* enabling support for hardware architectures, devices and programming languages
* development processes, debugging
* maintenance, testing and release engineering
* safety, security and robustness
* trends and challenges
* research and open questions
* community and governance
* use cases, experiences and status updates
* best practices and lessons learned
* live demos
Important Dates
The deadline for submitting proposals is December 1, 2024 (23:55 CET).
Please use the FOSDEM website at https://fosdem.org/submit, select the
track "Microkernel and Component-Based OS" and include at least the
following information:
* title of your proposal
* short abstract (one or two paragraphs)
* duration (20 - 40 minutes, including demos and Q&A)
* your full name
* your short bio
The devroom schedule (with accepted talks) will be announced on the
devroom website at https://fosdem.org/2025/schedule/track/microkernel
by December 15, 2024. The schedule will also be posted to the devroom
mailing list and the speakers will be notified via email.
Like previous years, the devroom will take place as an in-person event
at the ULB Campus Solbosch in Brussels, Belgium during the second half
of February 1, 2025 (Saturday).
Due to the high number of submissions that FOSDEM received this year,
our devroom has only been allocated half a day. Therefore, the final
decision on the duration of the talks will be made by the devroom
organizers based on the number of accepted proposals.
Requirements
The communication language of the devroom is English. All content must
relate to free and open-source software. By participating in the event,
you agree to the publication of your talk recordings, slides and other
content provided under the same CC-BY license as all other FOSDEM content.
All participants are expected to adhere to the Code of Conduct:
https://fosdem.org/2025/practical/conduct/
Contact
For the 2025 edition, the organizers of the devroom are
* Udo Steinberg (udo [at] hypervisor.org)
* Alexander van der Grinten (alexander.vandergrinten [at] gmail.com)
For any comments, questions and suggestions, please do not hesitate to
contact us directly or via microkernel-devroom-manager(a)fosdem.org.
About the Devroom
Since the first Microkernel OS Devroom at FOSDEM 2012, this devroom has been
a part of each subsequent FOSDEM (with slight variations of the name). The
focus gradually widened to include component-based, unikernel-based and
other operating systems. It has now become a somewhat institutionalized
tradition for the open-source operating systems community, a kind of
"extended family meeting" and it is one of the places where microkernel
and unikernel enthusiasts meet regularly.
To date, over two dozen projects have participated in one way or another.
Many of the projects face similar challenges but come up with partially
different solutions. Therefore, the goal of the devroom is to bring the
various projects together, let them exchange ideas, cross-pollinate and
socialize.
As in the past, the devroom will offer the stage both to established
community members and to newcomers. Our goal is to select talks in an
inclusive manner and to create a balanced and unbiased schedule, while
keeping the quality of the devroom as high as in previous years.
About FOSDEM
FOSDEM is a two-day conference organized by volunteers to promote the
widespread use of free and open-source software. FOSDEM is widely recognized
as one of the largest and best such events worldwide. FOSDEM covers a wide
spectrum of free and open-source software and hardware projects and offers
a platform for people to collaborate.
To this end, FOSDEM has set up developer rooms (devrooms) where teams can
meet and showcase their projects. Devrooms are a place for teams to discuss,
hack and publicly present new ideas, latest results, lightning talks, news
and proposals. Besides developer rooms, FOSDEM also offers main tracks,
lightning talks, certification exams and project stands.
In recent years, FOSDEM has been hosting more than 8000 developers annually
at the ULB Solbosch Campus in Brussels, Belgium. The participation in FOSDEM
is totally free and requires no registration, although the organizers
gratefully accept donations and sponsorship.
Devroom Dinner
Over the years, it has become a tradition that devroom speakers and
enthusiasts meet for dinner somewhere in Brussels on Saturday evening to
continue discussions, socialize and meet old and new friends. We plan to
follow that tradition in 2025 and will inform you about the exact
arrangements later.
Hope to see all of you in Brussels!
_______________________________________________
l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de
To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de
Hi,
I was trying to run the L4 demo *vm-basic-pci* for *arm64* using the command
$ make qemu E=vm-basic-pci
but It didn't work because of the missing 2 files :
* virt-arm_virt-64_pci.dtb : which is requested by the *modules.list* file
in the line :
> module[arch=arm64,fname=virt-pci.dtb] dtb/virt-arm_virt-64_pci.dtb
* virt-pci.dtbo : which is requested by the *vm-basic-pci.cfg* by the
configuration
> if (L4.Info.arch() == "arm64") then
> dt = "-drom/.fdt"
> overlay = "*-drom/virt-pci.dtbo*"
> else
> dt = "-drom/virt-pci.dtb"
> overlay = ""
> end
I searched for both files in the whole *l4re-snapshot-23.10.1* directory
but I couldn't find them
Where can I find those necessary files to run *vm-basic-pc*i demo?
Thanks in advance,
Regards
--
Mohamed Dawod
*Software Engineer,* Cairo Egypt
--
*Driving Innovation! Visit our website www.avelabs.com
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow
this link: http://www.avelabs.com/email/disclaimer.html
<http://www.avelabs.com/email/disclaimer.html>
_______________________________________________
l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de
To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de
Hello,
I need to pass through the PCIe bus to Linux VM via io and uvmm servers.
First, I generated the corresponding dtb file from qemu for *virt* machine
to get the exact pcie device node.
$ qemu-system-aarch64 -nographic -machine
> virt,virtualization=true,dumpdtb=conf/arm_virt-64-full.dtb
> $ dtc -I dtb -O dts conf/arm_virt-64-full.dtb
Secondly, I copied the following nodes to my dts file (*pcie@10000000*,
*intc@8000000* and *v2m@8020000*) exactly as they are in the original dts
file.
Finally, I modified the ned scripts as mentioned in the comments of the
*pcie_ecam.cc* file.
The issue is that there is no IO driver for the device *v2m@8020000 *which
is responsible for msi-controller.
This device is needed for the PCIe.
The error logs :
> VMM[PCIe ctl]: PCIe host bridge pcie@10000000 refers to invalid MSI
> controller: MSI parent is not an MSI controller
> VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[1]
> (devid=1)
> VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[2]
> (devid=2).
> VMM[ioproxy]: No corresponding IO resource for 'v2m@8020000'.reg[0]
> (0x8020000-0x8020fff).
> VMM[vm]: Device creation for v2m@8020000 failed. Disabling device.
How can I pass through the PCIe device if there is no IO driver for the
needed msi-controller ?
Thanks in advance,
Regards
--
Mohamed Dawod
*Software Engineer, *Cairo Egypt
--
*Driving Innovation! Visit our website www.avelabs.com
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow
this link: http://www.avelabs.com/email/disclaimer.html
<http://www.avelabs.com/email/disclaimer.html>
_______________________________________________
l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de
To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de
Hello,
I was reading this tutorial
<https://github.com/kernkonzept/manifest/wiki/NVMeWithLinux> about using
NVMe server with Linux guest and it works fine. Now I'm trying to apply the
same tutorial but for arm64 instead of AMD64/X86_64.
As expected, it didn't work because arm64 device tree blob/source doesn't
contain the same *PCI* bus with the attached *virtio_disk* device node.
Instead, virt-arm_virt-64.dts file contains only 2 VMM virtual devices for
ARM guests : *virtio_uart* and *virtio_net*.
I need a way to apply the same Tutorial (using NVMe server with Linux
guests) for ARM64 instead of AMD64/X86_64.
Any suggestions?
Thank you,
Regards
--
--
*Driving Innovation! Visit our website www.avelabs.com
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow
this link: http://www.avelabs.com/email/disclaimer.html
<http://www.avelabs.com/email/disclaimer.html>
_______________________________________________
l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de
To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de