similar to: migrated RHEL7/CentsOS7 VMs fail to boot

On Mon, Mar 20, 2017 at 10:18:35AM +0100, Daniel Pocock wrote: > >I migrated a CentOS7 VM (the fedrtc.org site) from an XCP environment to >a libvirt/KVM environment. > >This involved using qemu-img to convert the image from VHD to qcow2 and >then using virt-install --import to define the VM in libvirt. > I have little to no idea how to help with the rest, but have you tried

Howdy, I hit a snag trying to install Xen4CentOS on a Supermicro based system (X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on this today, I'm posting this here in case it helps anyone else and saves them the frustration I dealt with. On this system I did a fresh install of CentOS 7, updated it, rebooted it, then installed Xen. The system was booting fine using the

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

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

> > But, what happens if you let the kernel post install scripts do the work > or setting up the initrd things? Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do their job with the defaults, but unfortunately, boot process stops at initrd (dracut) stage with the following error: [ 197.768159] localhost.localdomain dracut-initqueue[252]: Warning: Could > not

Hi Everyone, I have a server that I recently applied all updates to to bring it to 1804. After rebooting the server, it would no longer boot and is instead dropping into a dracut shell. Here's a snippet of the output printed to the console (lines will likely wrap): [ 184.163787] dracut-initqueue[256]: Warning: dracut-initqueue timeout - starting timeout scripts [ 184.672525]

Package: release.debian.org Severity: normal Tags: wheezy User: release.debian.org at packages.debian.org Usertags: pu X-Debbugs-CC: pkg-xen-devel at lists.alioth.debian.org If somebody is still running wheezy for their dom0 (host) environment and they are using jessie or other systems with grub2 in their VMs, they can't boot their VM. A rather trivial 1-line fix in the dom0 (host) system

I've just tried putting usr in a subvol. Installation proceeds normally, no errors, but I'm dropped to a dracut prompt which indicates mount of /usr failed. dmesg follows: [ 14.025215] systemd[1]: Starting dracut initqueue hook... [ 14.077890] Btrfs loaded [ 14.129987] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 14.313607] device label fedora_f18v devid 1 transid 31

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error:

Guys, I have a Packer build procedure, that works like a charm, when with CentOS 6.7. Exemplifying: 1- Packer (with virtio disk) + QEmu + CentOS 6.7 ISO; 2- Create a RAW image; 3- Convert the RAW image into QCOW2 for KVM hypervisors (okay); 4- Convert the RAW image into VMDK for ESXi hypervisors (okay). However, when doing the very same procedure, with CentOS 7.2 ISO, it does not boot

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru >

Just did an in-place update from 6.1 to 6.2 on my eeepc 901 (Atom CPU). during boot, (if I hit ESC to see the boot messages) it says "starging udev" then nothing else for a few seconds, then a huge register dump scrolls by. it's too big to see the beginning of it. If I boot from the prior kernel and look in /var/log/messages, I don't see any evidence of the failed boot.

Hi, On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way it always has worked for other versions, incl. Fedora 22 VM's), does not work for me. I use virt-install with a local copy of the "images/pxeboot" tree. It all stops with: ... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. dracut-initqueue[551]: Warning: Could not boot.

Send CentOS mailing list submissions to centos at centos.org -----Original Message----- From: CentOS <centos-bounces at centos.org> On Behalf Of centos-request at centos.org Sent: Tuesday, July 31, 2018 5:30 PM To: centos at centos.org Subject: (EXT) CentOS Digest, Vol 162, Issue 29 Send CentOS mailing list submissions to centos at centos.org To subscribe or unsubscribe via the World

Hi All, We've had a report[1] of the virt_blk driver causing a lot of spew because it's calling a sleeping function from an invalid context. The backtrace is below. This is with kernel v3.16-rc2-69-gd91d66e88ea9. The reporter is on CC and can give you relevant details. josh [1] https://bugzilla.redhat.com/show_bug.cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for

Hi All, We've had a report[1] of the virt_blk driver causing a lot of spew because it's calling a sleeping function from an invalid context. The backtrace is below. This is with kernel v3.16-rc2-69-gd91d66e88ea9. The reporter is on CC and can give you relevant details. josh [1] https://bugzilla.redhat.com/show_bug.cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for

On 4/5/2017 5:56 ??, Marcelo Roccasalva wrote: > dracut -f /boot/initramfs-<kernel_version>.img <kernel_version> I did: # dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img 3.10.0-514.10.2.el7.x86_64 and it ended without reporting any error. However, when I rebooted, nothing changed ("no such device: <UUID>. Entering rescue mode..."). Am I missing

Dear fellow CentOS users, I have never experienced this problem with hard disk management before and cannot explain it to myself on any rational basis. The setup: I have a workstation for testing, running latest CentOS 7.3 AMD64. I am evaluating oVirt and a storage-ha as part of my bachelors thesis. I have already been running a RAID1 (mdraid, lvm2) for the system and some oVirt 4.1 testing.