similar to: intel_iommu=on => No root device found

I have been following these instructions: https://www.centos.org/forums/viewtopic.php?t=501 to put a bunch of utilities (Clonezilla, SystemRescue, CentOS netinstall/rescue, etc.) on a single USB key. It works great for everything (including Ubuntu Live) except the CentOS 6.4 LiveCD. (You can see my postings at the bottom of the forum.) When booting the LiveCD, I got: Kernel panic - not syncing:

I had an old server die; we had another, same model, sitting around lightly used, so I did what I've done before: swap the RAID card into that, swap the drives, even putting them in the same bays as the dead one, and boot. Nope. 100% of the time, when it hits switching roots, it kernel panics. Adding rdshell to the kernel line does nothing, I get no grub rdshell. Booting from a flash

here is my problem: Parsing config file vir2.cfg Daemon running with PID 11570 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.0.0 (root@localhost.localdomain) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Oct 28 00:35:01 CST 2013 Command line: root=/dev/hda1 ro ACPI in unprivileged domain disabled released 0 pages

Hi. Im trying to set intel_iommu=on on kernel parameters at grub but for some reason it doesnt work. I edit /etc/default/grub file and i add the parameter. then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then i reboot. when i run virt-host-validate i get QEMU: Checking if IOMMU is enabled by kernel: WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel

Hi all, Is anyone successfully running/has succesfully upgraded to 2.6.32-220 from, say, 2.6.32-71.29.1? (i.e. done a normal run-of-the-mill yum update on, say a 6.0 instance all the way up cleanly to 6.2? Reason I ask is that booting into -220 (and I think also into -131 as well) results in a kernel panic for me. Some digging around and the new kernel seems to be enumerating the drives with the

> -----Original Message----- > From: Wes James [mailto:comptekki at me.com] > Sent: Wednesday, January 27, 2016 7:04 PM > To: CentOS mailing list > Subject: Re: [CentOS] CentOS 7, 327 kernel still crashing > > > > On Jan 27, 2016, at 1:47 PM, m.roth at 5-cent.us wrote: > > > > I've just added the following to the CentOS bugtracker for CentOS-7 > >

I am trying to create a CF card that boots 686 CentOS 6.3 On boot I get a message about /dev/disk/by-label/\x2f where \x2f is "/" cannot be found. Adding rdshell to the boot line and booting up sure enough the /dev/disk directory does not exist. What "creates" that early on in the boot process? My CF card was changed from UUID to LABEL. So I edited grub.conf and make

greetings, had problems burning a dvd for 6.4, so i burned a livecd and installed it from boot menu to ext4 /dev/sdb3. during install, i defined mounting of /dev/sdb5 as /home and a second partition /dev/sdb6. both are ext4. first boot went well, set up user, rebooted. rebooted level 5, logged in as user, all looked good. rebooted level 5, logged in as root, made changes to

Just installed CentOS 6.3 from a minimal install disc. All was well, so I ran a yum update, as well as installed some additional packages (mysql, httpd, libjpeg, libpng, and more that I don't remember off the top of my head). Went to reboot the machine and now it won't book up. As it starts to boot, says: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not

Hi, I'm trying to get to the bottom of a problem using the combination of tboot (http://tboot.sf.net, trusted boot kernel for Intel TXT) and extlinux. TBOOT loads using the multiboot protocol, where the tboot "kernel" is loaded as the kernel, and the actual linux kernel and initrd are specified as modules. A working grub configuration looks something like:

On Wed 14.Sep'16 at 7:17:45 -0600, Alex Williamson wrote: > On Wed, 14 Sep 2016 15:00:37 +0200 > Paolo Bonzini <pbonzini at redhat.com> wrote: > > > On 14/09/2016 14:35, Sandro Bonazzola wrote: > > > FYI > > > > > > > > > ---------- Forwarded message ---------- > > > From: *C. L. Martinez* <carlopmart at gmail.com

On Fri, Apr 03, 2020 at 07:37:10PM +0300, Georgios wrote: > > Hi. > Im trying to set intel_iommu=on on kernel parameters at grub but for > some reason it doesnt work. > > I edit /etc/default/grub file and i add the parameter. > > then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then i > reboot. > > when i run virt-host-validate i get > >

I think i might have solve it. For some reason grub2-mkconfig doesnt work. (Have no idea why) I manage to solve it with grubby. sudo grubby --args="intel_iommu=on" --update-kernel=ALL For some reason it works. I dont know if it works if my kernel gets upgraded.

Yes dmesg | grep "EFI v" [ 0.000000] efi: EFI v2.70 by American Megatrends On Fri, 2020-04-03 at 14:29 -0400, Jonathan Billings wrote: > On Fri, Apr 03, 2020 at 07:37:10PM +0300, Georgios wrote: > > Hi. > > Im trying to set intel_iommu=on on kernel parameters at grub but > > for > > some reason it doesnt work. > > > > I edit

Hi, I am trying to recover data from my old system which had LVM. The disk had two partitions - /dev/sda1 (boot, Linux) and /dev/sda2 (Linux LVM). I had taken a backup of both partitions using dd. Now I am booting of CentOS live cd for system restore. I recreated partitions like previous system using fdisk and then used dd to dump all the data onto it. I would like to mount sda2 as LVM, but I

On Fri, Sep 21, 2012 at 01:02:23PM +1000, John Krstev wrote: > Hi Konrad, Hey John, Please next time also include xen-devel on the To header. I''ve done that for you. > > I refer to your patch at: > http://lists.xen.org/archives/html/xen-devel/2012-01/msg01927.html > which I found reading > http://www.gossamer-threads.com/lists/xen/devel/256197 > > I have a

Hi, This is regarding SRIOV in Rhel7. I have added intel_iommu=on in grub.cfg file. When I attach Virtual Function to VM and I try to poweron the VM, I get the below error: [root@Dell-Rhel7 ~]# virsh start rhel64x64GA error: Failed to start domain rhel64x64GA error: internal error: early end of file from monitor: possible problem: qemu-kvm: -device

I'm trying to get PCI passthrough working by passing through a DVB-T TV card to a VM running MythTV. When I assign the PCI devices in virt-manager and attempt to start the VM I get this error: Error starting domain: internal error: process exited while connecting to monitor: 2015-09-06T12:41:09.725990Z qemu-kvm: -device vfio-pci,host=05:02.0,id=hostdev0,bus=pci.0,addr=0x9: vfio: error, group

Most of the upgrades to CentOS 6.8 have gone smoothly. Thanks, as always, for all the work that goes into making it so easy to upgrade. On a few machines, however, all of them curiously: Dell Inc. OptiPlex 780 /0C27VV, BIOS A15 08/06/2013 There is something wrong with their interaction with grub (?). I noticed this after adding '3' to the module line to get it to

From: Joerg Roedel <jroedel at suse.de> Convert the Intel IOMMU driver to use the probe_device() and release_device() call-backs of iommu_ops, so that the iommu core code does the group and sysfs setup. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- drivers/iommu/intel-iommu.c | 67 ++++--------------------------------- 1 file changed, 6 insertions(+), 61 deletions(-) diff