Hi Mohamed,
On Sun Sep 01, 2024 at 14:26:55 +0300, Mohamed Dawod wrote:
Thank you for the information. but I couldn't find anything about the RTC package, how to use and configure it in the ned script ?
Please find attached an example how to start a VM on amd64 using the RTC service, including ned script and io config. The entry in the modules.list file is as follows:
entry[arch=amd64] VM-rtc moe vm-rtc.cfg module l4re module ned module cons module io module rtc.io module rtc module uvmm module dtb/virt-pc.dtb module[fname=linux,nostrip] https://l4re.org/download/Linux-kernel/x86-64/bzImage-6.6.8 module https://l4re.org/download/ramdisks/ramdisk-amd64.rd
I hope it is useful.
Adam
On Thu, Aug 29, 2024 at 8:54 PM Adam Lackorzynski adam@l4re.org wrote:
Hi Mohamed, indeed, accessing the same device by two or more clients is not good. There is an rtc package for exactly this: giving multiple clients/VMs access to the rtc.
Adam On Mon Aug 26, 2024 at 13:48:39 +0300, Mohamed Dawod wrote:
Hi, I was trying to pass the RTC device from the host machine (qemu-arm46) to the guest machine linux VM on top of L4. and it was done successfully. Now I'm trying to share the same device between 2 linux VMs on top of L4. by duplicating the virtual device that describes the same physical
device
and also duplicating the virtual bus and passing one for each new vm.
The issue if that one of the VMs is terminated because of the disability
of
binding the same IRQ as described in the screenshot below : [image: image.png]
Please find attached all ned scripts I'm using for this experiment.
Thank you, Regards
-- Mohamed Dawod *Software Engineer, *Avelabs Egypt *Cell Phone : (+20) 1117311726*
--
--
*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@os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave@os.inf.tu-dresden.de