similar to: centos 6 domU doesn't see all memory?

Solved. For the archives: Noticed in xl info output that only 1 core was recognised, even though nr_cpus should show 16 on this box. Tried rebooting and selecting the old .34 kernel, console printed "smpboot: do_boot_cpu failed(-1) to wakeup CPU#1" and CentOS failed to boot. Powered down the box fully and started back up with the latest .44 kernel and everything is working fine

I want to give my clients access to their Xen domU consoles using VNC. This works great using vfb device configured as type=vnc. However I have 2 problems: * I can't figure out how I can add a vfb device to a running domain without restarting it (I have 100+ domU's I want to enable this on, and want to avoid restarting them all if possible) * Related, I can't figure out how I can

We tried to get CentOS 8 domU working in PV mode as well but did not have any success and ended up deploying it in HVM mode. The reason OP have was lack of hardware support for HVM. This wasn't our rationale for wanting to run in PV mode. Our rationale was that we prefer to deploy CentOS 7 VMs on LVs which are formatted and deployed from an image on dom0 and don't have any partition

I just did a yum update on a CentOS 7 / Xen 4.6 server which took me from kernel-3.18.34-20.el7.x86_64 -> kernel-3.18.44-20.el7.x86_64 After rebooting, the following notice is printed immediately upon xl create'ing a domain: libxl: notice: libxl_numa.c:499:libxl__get_numa_candidate: NUMA placement failed, performance might be affected Indeed performance is significantly degraded. This

Wondering if anyone has managed to get Xen to boot from UEFI? We have a relatively new server with a Supermicro X11SSH-F mainboard with an M.2 SSD. If we switch the boot mode to Legacy in the BIOS no boot devices show up. The vendor says this is because M.2 SSD is only supported in UEFI mode. We even tried installing some spinning SATA drives and a USB thumb drive but those don't show up as

I may have run into this issue before too, but in my case the VMs ran fine with only 1 vcpu so I booted them that way and left them like that. It was just a few small legacy VMs and I didn't spend any more time on it. Did you try booting with only 1 vcpu? Chris -- Chris?Wik Anu?Internet?Services www.anu.net?|?www.cwik.ch From: isdtor <isdtor at gmail.com> To:

Hello Dovecot list, We've been running a really old CentOS 5 server with the stock dovecot from yum (1.0.7) for years and years with absolutely no problems. If it ain't broke, don't fix it, or something like that. Well it finally broke, but only due to the server no longer being able to handle the load of the increasing user base (many thousands now, with hundreds of concurrent

Hi, I'm running CentOS 6.2 x86_64 as xen guest on a CentOS 5.7 dom0. The host is running 2.6.18-274.7.1.el5xen, the guest 2.6.32-220.2.1.el6.x86_64. Memory for domU is set to 1024 MB and "xm list" shows these 1024 MB. But "free -m" on the guest system shows only 652 MB. When I set up a CentOS 5.x guest with 1024 MB "free -m" shoes 1024 MB. Anyone else seeing

Dear List, I've compiled asterisk (both 0.9.0 and the CVS-04/19/04 source trees). I'm using the oh323 channel driver version 0.5.10, OpenH323 v1.12.2, PWlib v1.5.2 When run on a RedHat 9 system, I am constantly getting seg faults. This happens even when I tried removing the oh323 channel driver, so it appears to be something with asterisk. I get crashes either when attempting to

more /etc/xen/scalix2 kernel="/boot/vmlinuz-2.6.18-8.1.6.el5xen" memory = 512 name = "hating-xen" vif = [''ip = "10.0.1.150", bridge=xenbr0''] disk = [ ''/dev/XEN/scalixroot,sda1,w'', ''/dev/XEN/scalixvar,sda3,w'', ''/dev/XEN/scalixswap,sda2,w'' ] It

Hi, In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled. I am curious why you are trying PV. -yoctozepto On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt <centos-virt at centos.org> wrote: > > All, > > Just

We've got the following set up: Local Phone <-SIP(no reinvite)-> Local * <-IAX-> Central * <-SIP(no reinvite)-> Remote Phone I've got calls working just fine between Local and Remote phones. All of the outgoing calls / voicemail / Music on Hold are done on the Central * server. I would like to configure it so that the Local Phone can use the Transfer facilities on

Hey, I was looking for step by step installation for RHEL5 as dom0 and RHEL5 as domU, but could not find it.I put some instructions, hope it will save some time for somebody. If you will find some errors please fix them :) I assume that you already have rhel 5 up and running (webserver as well).I will install guest system in paravirtualized mode (mine processor does not support full

Hi, on one of our systems I see that while the time on the Centos 5.4 Host is correct it lags behind on two of the 5.5 guests by almost 5 minutes but is correct for the third domU. From what I understand the clock of the system is controlled by the host and and guest cannot write to it (and because of that not change it). Does anyone now what the cause could be and how I can fix the time for

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

I have migrated KVM VMs from a CentOS 6 to a CentOS 7 host. All work fine post-migration, CentOS 3 (don't ask ...), CentOS 6, CentOS 7, Windows. But the CentOS 5 VMs failed. At some point during the boot process, they became unpingable and also inaccessible. I have correlated this to the start of the irqbalance service and was wondering if it is generally considered best practice to turn it

Hello, i will describe my approach 1) I have downloaded Centos5-64bit xen image from jailtime.org 2) I have created own swap image with 512MB file size 3) I have used same as dom0 kernel 2.6.18-53.1.19.el5xen 4) I have mounted my image file and copied /lib/modules/2.6.18-53.1.19.el5xen 5) I have created custom ramdisk for domU with mkinitrd --with=xennet --preload=xenblk

I'm trying to get a PVR-150 PCI card imported into a Xen DomU, however the driver blows up the kernel when loaded. The work around for this mentioned in various places is to use swiotlb=force on the DomU kernel. That leads to a fast and furious kernel panic. I've tried this with all Dom0 & DomU running kernel-xen-2.6.18-53.el5 kernel-xen-2.6.18-53.1.6.el5, bot x86 and 86_64

Hi, how can i make actual xen kernel to work under my domU virtual machines? When i will provide as kernel /boot/vmlinuz-2.6.18-53.1.14.el5xen as ramdisk /boot/initrd-2.6.18-53.1.14.el5xen.img , it will not work becouse of error that root device does not exists. And when it is booting it is showing that raid md0 and my logical volumes does not exists - like those on dom0. I believe it is becouse

Hello, I am currently trying to move my VMs from running on local host storage to a shared storage (trying out iSCSI) but I am facing a bit of a booting dilemma. The domUs are a mix of paravirtualized and fully-virtualized VMs. They all boot and run like clockwork when on local storage. The paravirtualized domUs appear not to have a problem when I relocate and boot them from the shared storage