similar to: Garbled screen after RAM Scrub on boot

Yes I usually work headless, but I have been setting it up from new, so need to see what is going on. Regards Francis From: "Scot P. Floess" <sfloess at nc.rr.com> To: "Francis Greaves" <francis at choughs.net> Cc: "centos-virt" <centos-virt at centos.org> Sent: Monday, 22 February, 2016 17:02:12 Subject: Re: [CentOS-virt] Garbled screen

Dear George, Thanks for the input and ideas. Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! I am asking the xen-users as you suggest Regards, Francis From: "George Dunlap" <dunlapg at umich.edu> To: "Francis Greaves" <francis at choughs.net>, "centos-virt" <centos-virt

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the

Francis, I just rebooted my Precision 470 and watched...nothing :( I see the boot menu, and then everything goes blank - as in just a blinking cursor until I get the login prompt. No idea what it's doing - but I don't even see the scrubbing free memory output... On Mon, 22 Feb 2016, Francis Greaves wrote: > Yes I usually work headless, but I have been setting it up from new, so

When I was running Fedora 23 and using Xen (as the host OS), I saw something similar on my Dell Precision 470. I don't recall seeing it now with CentOS 7, but I tend to boot that machine headless more than not... On Mon, 22 Feb 2016, Francis Greaves wrote: > Dear All > I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 > When the machine boots, after the 'Scrubbing

On Tue, 23 Feb 2016 14:40, Francis Greaves wrote: > Dear George, > Thanks for the input and ideas. > Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! > I am asking the xen-users as you suggest > Regards, Francis > > > From: "George Dunlap" > To: "Francis Greaves" ,

On Mon, Feb 22, 2016 at 4:18 PM, Francis Greaves <francis at choughs.net> wrote: > Dear All > I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 > When the machine boots, after the 'Scrubbing Free RAM' message, I get a > screen filled with little white squares until the login prompt, so I cannot > see what is happening as the machine boots. Also there is nothing

Steffan A. Cline wrote: > I?ve looked and looked and can?t seem to find anything which would > explain why grub.cfg would have been rewritten with a whole new volume > group name. > > Suggestions? > C6 or C7? In either case, have you looked in /etc/default/grub? mark

More information... I have pcifront showing as a module in the DomU and the usb shows in dmesg as: [ 3.167543] usbcore: registered new interface driver usbfs [ 3.167563] usbcore: registered new interface driver hub [ 3.167585] usbcore: registered new device driver usb [ 3.196056] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.196060] usb usb1: New USB device strings:

Hello List, I'm ironing out details to upgrade a few systems to CentOS7. My servers have BMC with Serial over LAN support. In C5 and C6, I determined how to have BIOS/POST, kernel, and serial console access. I'm reading up on the method to accomplish the pieces with C7. Presently SoL output works, so I see BIOS/POST messages and the GRUB boot list. My changes to enable serial

Hi, On my minimal installation of CentOS 7, here's what I have in /etc/default/grub: GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos_amandine/root \ rd.lvm.lv=centos_amandine/swap \

On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >

Suggestion: once it's up, rebuild the initramfs. > > I tried that already, but still the same problem. Aparently dracut does not want to activate the LVs required to boot to the root filesystem, for some reason ... Yannis -- Sent from Gmail Mobile

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

Xen-users, I have what I think is a bug in the serial console interaction of Xen and Ubuntu. Essentially, the serial console appears to work just fine until it is passed off to dom 0 from Xen. Then it stops communicating with dom0, but still communicates with Xen, if I use the control-A escape sequence. Google will not show me anything related to this. I have local RS-232 serial console working

Am 14.03.23 um 12:30 schrieb Rob Kampen: > OK, > > found out the problem as to why it doesn't boot any kernel except 36.2 > > the system reports that it cannot find > > vmlinuz-3.10.0-1160.88.1.el7.x86_64 > > or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 > > hence a manual selection from the grub menu when in front of the machine

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS

I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. For some reason the DomUs (CentOS

>On Mon, May 16, 2016 at 12:00 PM, Francis Greaves <francis at choughs.net> wrote: >> Dear George please find attached the three files as requested. >> I have used >> >> iommu=soft >> >> in the grub command line for the kernel in the domU as explained before. >> many thanks >The options are: >1. Figure out what the other device is and

I have built a CentOS 8 base image from a kickstart, for use in OpenStack. This image boots fine but the problem I have is that I can't stop udev from renaming the network device from eth0 to ens<something>. I have /etc/sysconfig/network-scripts/ifcfg-eth0 with the correct HWADDR defined in it, and have set net.ifnames=0 and biosdevname=0 in the grub configuration, but nothing I have