similar to: CentOS-8 QEMU guest won't bring virtio_net interface up.

For those who come across this thread, I've found the exact list of changed and dropped package between rhel:7 and rhel:8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/considerations_in_adopting_rhel_8/index#package-replacements_changes-to-packages Too bad that the "note" column is empty in the dropped package table. NO word about reason or

On Thu, 26 Sep 2019 at 05:24, LAHAYE Olivier <olivier.lahaye at cea.fr> wrote: > > Hi, > > I need to port OSCAR Cluster and SystemImager softwares to centos8, but I miss a lot of package that seems to be built for centos-8. > For example, I cant find docbook-utils and docbook-utls-pdf while I see them here: https://koji.mbox.centos.org/koji/buildinfo?buildID=651 > So what

Hi, I?m running a special initrd generated for SystemImager with a special dracut module that relies on plyouth scripted theme. It works perfectly on CentOS-6, CentOS-7, OpenSUSE-42.3, Fedora-29 (not tested later) and used to work on CentOS-8.0 Since CentOS-8.1 was released, IT chrashes with the following error: Plymouthd crash 913: ply_event_loop_watch_for_timeout: Assertion `seconds >

Hi, I need to port OSCAR Cluster and SystemImager softwares to centos8, but I miss a lot of package that seems to be built for centos-8. For example, I cant find docbook-utils and docbook-utls-pdf while I see them here: https://koji.mbox.centos.org/koji/buildinfo?buildID=651 I?ve installed epel-release and elrepo-release and centos-release-stream. Do I miss something or is it a matter of time

Is there a way to get a NTFS encrypted file using smbclient (even not decrypted) so It can be backed up using backuppc (http://backuppc.sourceforge.net) ? I have exported the NTFS keys in a pfx file. could it help copy the file? the aim is that files must be crypted on laptops hard drive so if it is stolen then no data is compromised. Having the file not crypted on the backup server is not a

Hi, while kickstarting our virtual machines with PXE we often run into kickstart/anaconda failing with [...] [...] dracut-mount[xxx]: Warning: Can't mount root filesystem [...] dracut-mount[xxx]: Warning: /dev/root does not exist [...] dracut-mount[xxx]:/lib/dracut-lib.sh: line 1030: echo write error: No space left on device Starting Dracut Emergency Shell... Warning: /dev/root

> On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: > > Hi, > > My last VM imported in 2 minutes. This one has been sitting for three > hours. I think this is a bug. well, some time it does take a long time. Are you sure it was hung? No I/O going on? adding libguestfs list Thanks, michal > > Just in case it helps, here's a larger piece of

On Tue, 2015-12-01 at 17:02 +0100, Paolo Bonzini wrote: > > On 01/12/2015 00:20, Ming Lin wrote: > > qemu-nvme: 148MB/s > > vhost-nvme + google-ext: 230MB/s > > qemu-nvme + google-ext + eventfd: 294MB/s > > virtio-scsi: 296MB/s > > virtio-blk: 344MB/s > > > > "vhost-nvme + google-ext" didn't get good enough performance. > >

I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8. This instance is used for occasional development projects which require segregation. Thus it is seldom accessed. At some point in the recent past this guest developed an issue with starting. Specifically these messages were found in the system log files: /var/log/messages-20170312:Mar 10 16:31:06 vhost04 kernel: dracut:

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]

On 12/02/2015 12:05 PM, Axel Glienke wrote: > in journalctl i found: > modprobe: FATAL: Module dm-snapshot not found > ... > Can't process LV root_snap: snapshot target support missing from kernel I installed a very simple CentOS 7 system with an LVM root FS. Created a snapshot and rebooted, no problem. Updated dracut, then updated everything else and rebooted, no problem. As

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

On Fri, 2 Mar 2018, Robert P. J. Day wrote: > finishing a week of teaching a comptia linux+ class off of centos > 7.4 and wanted to demo how to boot to "rescue" mode, so i rebooted, > selected "rescue" mode at grub menu, which still booted to full > multiuser, graphical mode. what am i doing wrong? or is this a dumb > question? It's is not what you think

ok, thank you very much Gordon. but you know what the difference? if i do 1. centos7 installation 2. yum upgrade 3. lvcreate -s ... 4. reboot then i got the error. if i do your way 1. centos7 installtion 2. snapshot & reboot 3. yum upgrade 4. reboot then the system start. Zitat von Gordon Messmer <gordon.messmer at gmail.com>: > On 12/02/2015 12:05 PM, Axel Glienke wrote:

Hello listmates, I have encountered a rather peculiar situation. We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It was running just fine until one day I decided to reboot it and it just would not boot up. Effectively, dracut failed to initialize the LVM, much like under the scenario described here:

Hello, I stumbled upon a strange problem with CentOS upgrade on XenServer environment, and I would like to ask if someone has this issue as well: XenServer 7.1, the VM is CentOS7, with kernel 3.10.0-514.26.2.el7.x86_64 running in PV mode When I upgrade the kernel (running with yum update kernel), after reboot in the VM console it says "dracut-pre-udev[212]: modprobe: ERROR: could not insert

Hello Boris, On Tue, 2015-08-25 at 15:59 -0400, Boris Epstein wrote: > We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It > was running just fine until one day I decided to reboot it and it just > would not boot up. Effectively, dracut failed to initialize the LVM, much > like under the scenario described here: > >

On 21/09/17 16:44, Todor Petkov wrote: > Hello, > > I stumbled upon a strange problem with CentOS upgrade on XenServer > environment, and I would like to ask if someone has this issue as > well: > > XenServer 7.1, the VM is CentOS7, with kernel > 3.10.0-514.26.2.el7.x86_64 running in PV mode > When I upgrade the kernel (running with yum update kernel), after >

Jay Hart wrote: > ** WARNING: This mail is from an external source ** > > >> Jay Hart wrote: >>> >>> I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, >>> running >>> Indian Bay Trail, with a i915 chipset. >>> >>> I installed "Server with GUI", but when it boots I get the