Hi, I already found out the error which was that I did not enable intel_iommu on the target linux which is why I could not proceed, hence I edited /boot/EFI/BOOT/grub.cnf and everything is ok(sorry I did not update earlier) . However I have an additional problem, I see some of the steps that GRUB_CMDLINE_LINUX="memmap=XXX" needs to be configured in /etc/default/grub however my target machine does not have that so can I just append memmap="0x4200000\\\$0x3b000000" in /boot/EFI/BOOT/grub.cnf and then update the grub and finally reboot?
Regards, Swaraj Dube. -----Original Message----- From: Jan Kiszka [mailto:[email protected]] Sent: Tuesday, June 28, 2016 4:58 PM To: Dube, Swaraj <[email protected]>; Jailhouse <[email protected]> Subject: Re: DMAR region size cannot be identified on Intel architecture On 2016-06-28 03:54, [email protected] wrote: > G'Day jailhouse folks, > > I am trying to install jailhouse on a real hardware (x86 intel architecture), > I enabled VT-d in the BIOS to enable virtualization which allowed me to > obtain the data.tar by doing the following: > > $ sudo tools/jailhouse config collect data.tar $ mkdir myboard $ tar > -xvf data.tar -C myboard $ tools/jailhouse config create -r > path/to/untarred/data configs/myboard.c If you are on the same machine, you can go for config create directly (just leave out "-r path/to/untarred/data"). > > in this case "path/to/untarred/data" is "myboard/" , however when I enter the > last command, it gives out the following error: > > RuntimeError: DMAR region size cannot be identified. > Target Linux must run with Intel IOMMU enabled. > > I did enable VT-d in the BIOS and furthermore I also tried to run the > following command in the terminal : "intel_iommu=on", I also tried turning it > off as mentioned in the github page however I still get the same error. I > have attached a screenshot to make it easier to understand. > > Am I missing a package?, do I need to re-configure or configure > something like a file. Any advice will be appreciated :) > For collecting informations about the IOMMU, we currently need Linux using it, therefore intel_iommu=on (or, statically, CONFIG_INTEL_IOMMU_DEFAULT_ON). Could you share your /proc/iomem and dmesg output in that case? (Technically, we could remove that dependency as well - jailhouse-hardware-check now demonstrated how we can obtain information also from registers, in this case the region size. Cleanup for the todo list...) Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
