similar to: dm_mod: no version for "struct_module" found: kernel tainted

I updated a C5 system to 2.6.18-406.el5 (from 404) and the kvm_intel module doesn't load anymore: # dmesg |grep kvm kvm_intel: disagrees about version of symbol struct_module anyone seeing similarities? -- LF

Hello, Some time ago, I noticed that whilst I had upgraded to Xen 3.1 (kernel 2.6.18-xen), I''d forgot to upgrade the paravirt DomU .cfg kernels from 2.6.16-xen to reflect this. So, I upgraded the DomU kernels & ran into issues with mounting devices, and the ext3 module not being available. After a bit of faffing about, I managed to sort this out and load the ext3 module.

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

We're using the stock configuration, the dom0 is limited to 1024MB via grub. ------ Original Message ------ From: "Pasi K?rkk?inen" <pasik at iki.fi> To: "Shaun Reitan" <shaun.reitan at ndchost.com>; "Discussion about the virtualization on CentOS" <centos-virt at centos.org> Sent: 6/26/2016 9:30:57 AM Subject: Re: [CentOS-virt] Cannot

On 01/06/2018 03:16 AM, Dmitry Melekhov wrote: > The same problem with latest centos 6 kernel,i.e. with meltdown fix. > > I can't see console output, because I have it on "cloud" provider > hosting :-) > > > > 06.01.2018 05:13, Shaun Reitan ?????: >> Broken! >> >> For those of you looking for a PV enabled client Kernel for CentOS Linux

When booting a CentOS4 domU, I''m getting some errors in the /etc/sysinit file. I''ve read that some edits are required in this file, but cannot find any specific references. Has anyone seen this before? Is there a workaround? EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel

I've seen this issue on about 15 different servers now. Anybody else seeing this? Screenshot: http://imgur.com/cBcwr8l I also have a video of the boot process if that will be helpful. -- Shaun Reitan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20160222/617097c7/attachment-0002.html>

On 01/08/2018 02:10 PM, Shaun Reitan wrote: > While installing the experemental kernel on a CentOS 7 PV the following > happened. After a reboot of the PV the kernel looks to be installed but > there is no option for booting it in grub. ?I attempted to run yum > reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but > still no entry in grub. No initramfs existed and

Right now xm will return 1 if you run `xm list non_existant_domain` Wouldnt it be a better idea to have a specific error code for this error so that scripts wrapping around xm can better determine if the domain does not exist or if xm just failed for whatever reason? ~Shaun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

My /var/log/messages log is being flooded with kernel messages showing the following messages Aug 1 11:22:52 host43 kernel: System RAM resource 48000000 - 4fffffff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17 Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same

If the guest uses SELinux, then make sure to run a relabel (or at least schedule one) after the image build: this way the template is relabelled, or at least it will do that at the next boot, without the need for the user to ask for a relabel. This just covers the case of building a new image with no additional operations on it though. --- builder/website/centos.sh | 2 ++

Quad core duo 2.4Ghz (Q6600) Kernel 2.6.18-53.1.14.el5PAE #1 SMP 4Gb RAM VirtualBox-1.5.6_28266_rhel5-1.i586.rpm The package installed OK. I did KERN_DIR=/usr/src/kernels/2.6.18-53.1.14.el5-i686 /etc/init.d/vboxdrv setup and the module compiles AOK. BUT... at modprobe time: vboxdrv: disagrees about version of symbol struct_module Am I doing something stupid? -- rgds Stephen

I've been attempting to create a bootable image thats double the size of the 2880 floppy disk. I can do the following to create a image that will boot with memdisk but i cant seam to get it to work with a larger size. What works... dd if=/dev/zero of=floppy288.img bs=1024 count=2880 mkdosfs floppy288.img ms-sys -1 -f floppy288.img mount -o loop floppy288.img /mnt

On 03/21/2017 07:48 AM, PJ Welsh wrote: > On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis > <ricardo at palmtx.com.ar <mailto:ricardo at palmtx.com.ar>> wrote: > > El Lunes 20/03/2017, PJ Welsh escribi?: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks > > PJ > > Edit grub's entry

Broken! [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.0-693.11.6.el7.x86_64 (builder at kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Thu Jan 4 01:06:37 UTC 2018 [ 0.000000] Command line: root=/dev/xvda ro

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

    Question: can dom0 in Xen4.0 be rebooted (from domU or from within dom0) anytime without loosing anything ? If so, please provide details. If not, does Xen.org have this in roadmap ? The closest posting I found (old one) is: http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00885.html The option is parameter as below (but this grub conf) noreboot Debugging Requests that

I encountered same error when use Xen3.0.2(source file) on CentOS4.2, after I downgraded to Xen2.0.7(source file), this error disappeared. now, I am using Xen2.0.7 instead of 3.0.2, it works well. --taylor -----邮件原件----- 发件人: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] 代表 xen-users-request@lists.xensource.com 发送时间: 2006年6月15日 5:24 收件人:

Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC

Hi just a little question. Can I boot FreeBSD over network with pxelinux ?