search for: virtioblk

Hi, I migrated a physical CentOS 4.8 server into a VM on a CentOS 5 KVM host. Everything works fine, I even can use the paravirt drivers for network and disk. However the required kernel modules are not put into initrd somehow. Of course I can call "mkinitrd --with virtioblk ..." manually but that's too easy to forget. I searched the web but I didn't find any similar reports... I found some references to /etc/sysconfig/mkinitrd/ but this doesn't work for me. So how can I make sure that the initrd always includes the virtio stuff? fs

...ol driver f9d129e68a45 to set a DMA access attribute > >> and methods to > >> allocate, free, map and unmap the DMA memory for the master bus devices > >> > >> In this patch series, I have tried to enable the IOMMU_PLATFORM > >> feature for > >> VirtioBlkDevice. I am sending this as RFC to seek feedback before I > >> extend the support > >> for other Virtio devices. The patch has been tested in SEV guest - > >> mainly because > >> IoMmuDxe driver installs the IOMMU protocol for SEV guest only. If > >> nee...

...ol driver f9d129e68a45 to set a DMA access attribute > >> and methods to > >> allocate, free, map and unmap the DMA memory for the master bus devices > >> > >> In this patch series, I have tried to enable the IOMMU_PLATFORM > >> feature for > >> VirtioBlkDevice. I am sending this as RFC to seek feedback before I > >> extend the support > >> for other Virtio devices. The patch has been tested in SEV guest - > >> mainly because > >> IoMmuDxe driver installs the IOMMU protocol for SEV guest only. If > >> nee...

E820 definitions copied from IntelFrameworkModulePkg/Csm/ LegacyBiosDxe/LegacyBiosInterface.h. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> --- OvmfPkg/Include/IndustryStandard/E820.h | 46 +++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode