similar to: Xen Doc Day: Guide to setting up bridging on CentOS 6 / 7

If you'd like to extend that a little bit, here's example configs on how to do LACP and vlan tagging on c6: host network-scripts # cat ifcfg-eth0 DEVICE=eth0 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host network-scripts # cat ifcfg-eth1 DEVICE=eth1 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host

Hi - I''ve searched around and haven''t found anyone who''s implemented a type+provider for configuring network interfaces in puppet. Does anyone have such a thing already running that''s just not on forge / github? I found some prior art (aside from the old ''interface'' type which was deleted in 0.24) but most people seem to use definitions +

Hello, I posted a question over at xenproject.org but it was recommended that I send out a message here for help. My post there: http://www.xenproject.org/help/questions-and-answers/vanilla-pv-centos-guest-via-kickstart-centos-6-6,-xen-4-4.html The TL;DR is: Everything I've found to kickstart a new vanilla rhel/centos guest points to specifying a kernel & and initrd- for RHEL/Centos 5.

Hi, I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server which uses UEFI. So far so good CentOS 7.4 works fine so then I went on to install the Xen hypervisor by following the instructions from the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). Unfortunately when I reboot after having installed the xen package the system does not boot into "CentOS Linux, with Xen

Hi, Actually, we study virtualization on CentOS with Xen, our goal is to test if the migration of Xen with SLES 11 to CentsOS. Our first tests are ok except for one problem and I don't find any solutions on the net. I hope, you can help me. The problem is that I can't connect to my vm desktop with Virt-Viewer. I follow the installation guide available for centos?:

Hi, after migrating to libvirt/libxl according to: https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt I've noticed that my Xen PV domains are being launched by qemu-system-i386 running under root privileges. I am wondering why is this? Previously no qemu process was used. If qemu is needed for some reason, are there any guidelines for non-root operation? Thanks -- Karel

I see the announcement from February that it's available, but is it considered to be safe for Production use? The documentation in the SIG still only references CentOS 6. https://wiki.centos.org/Manuals/ReleaseNotes/Xen4-01 https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

Hello, we have a strange problem on a fresh install of CentOS 6.5. On the server we want to use Xen to host paravirtualised guests (the system has no hardware virtualization support). To manage the domain we would like to use libvirt. Xen and libvirt are set up as described here: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt When

Hi all, I'm trying to install libvirt for xen on a brand new, minimal installation of CentOS 7.5.1804. After installing the OS, I did a 'yum update' and followed the basic how-tos at https://wiki.centos.org/HowTos/Xen/Xen4QuickStart and https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt From previous experience, I know that the above steps worked fine. However,

Hi, spot on! On 6.9.2015 12:56, Pasi K?rkk?inen wrote: > On Sun, Sep 06, 2015 at 09:08:50AM +0200, Karel Hendrych wrote: >> Hi, after migrating to libvirt/libxl according to: >> > > Hi, > >> https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt >> >> I've noticed that my Xen PV domains are being launched by >> qemu-system-i386 running

Am 28.03.16 um 12:12 schrieb Leon Fauster: > Am 28.03.2016 um 11:27 schrieb G?tz Reinicke <goetz.reinicke at filmakademie.de>: >> We have three supermicron servers with two 10Gb Ports each, connected to a cisco switch stack 1Gb ports. All are on auto speed. >> >> I configured a LACP bond on both sides on all servers, first with citrix xen server. >> >> On

I'm trying create a virtual machine using Xen as hypervisor and virt-manager (libvirt) as the management module. When trying to create the virtual machine I am getting the following error: " Unable to complete install: 'internal error: unsupported input bus usb' " ERROR DETAILS: Unable to complete install: 'internal error: unsupported input bus usb' Traceback

On Mon, Sep 07, 2015 at 05:47:39PM +0200, Karel Hendrych wrote: > ... > > changing from: <driver name='file'/> to: <driver name='tap2'/> makes > the domain start without QEMU. > > However I see much better performance with QEMU (close to dom0, > tested using simple dd writes) than with tap2 driver. Is that > expected? > How did you measure

I normally use the network-script parameter in the '/etc/xen/xend-config.sxp' configuration file to configure network bridges. However, the latest release of Xen4CentOS (which comes with Xen 4.4.1) has xend disabled by default. Can I continue to use network-script without xend? If not what is the recommended method for automatically configuring network bridges with the latest release of

Hi, After following the instructions here http://wiki.centos.org/HowTos/Xen/Xen4QuickStart and installing the kernel from Xen4 CentOS project (kernel-3.4.61-9.el6.centos.alt.x86_64) I can't use any networking because the firmware for my NIC is not available: Bringing up interface eth0.3: bnx2x 0000:02:00.0: firmware: requesting bnx2x/bnx2x-e1h-7.2.51.0.fw bnx2x:

On Fri, Feb 21, 2020 at 09:16:01AM +0100, Ján Tomko wrote: > [adding Anthony PERARD to cc since his name is next to > xen-4.12.2-1.el7's ChangeLog entry] > > Hi, Anthony! > > On Thu, Feb 20, 2020 at 07:10:38PM +0100, Christoph wrote: > > https://wiki.centos.org/HowTos/Xen/Xen4QuickStart > > > > configure:53501: checking for LIBXL > >

Hi, I have a server with Supermicro X7DVL-3 (P9) motherboard, 16G ECC RAM and LSI SAS 1068e RAID controller. I installed CentOS 6.5 64bit on the machine without any problems, but after following the Xen setup steps at http://wiki.centos.org/HowTos/Xen/Xen4QuickStart which installed me the kernel 3.10.32-11.el6.centos.alt.x86_64, I encountered a problem: After "Starting certmonger

https://wiki.centos.org/HowTos/Xen/Xen4QuickStart configure:53501: checking for LIBXL configure:53508: $PKG_CONFIG --exists --print-errors "xenlight >= 4.6.0" Package xenblktapctl was not found in the pkg-config search path. Perhaps you should add the directory containing `xenblktapctl.pc' to the PKG_CONFIG_PATH environment variable Package 'xenblktapctl', required by

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device