similar to: KVM, VLAN and Bridges and bonding

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

I am having some problem with partitioning schemes on DomU. I have 10 LV ACTIVE ''/dev/virtualization/domu1-swap'' [4.00 GB] inherit ACTIVE ''/dev/virtualization/domu1-disk'' [146.00 GB] inherit ACTIVE ''/dev/virtualization/domu2-swap'' [4.00 GB] inherit ACTIVE

Hi folks, Host - Debian Etch Workstation Guest01 - mail server for routing Guest02 - mail server, hostname01. localIP01, domain01 Guest03 - mail server, hostname02, localIP02, domain02 Guest04 - mail server, hostname03, localIP02, domain03 etc. all mail servers running postfix as MTA on Debian Etch. single (one) external IP with all ports forwarded to Guest01 except port 53 which is forwarded

Hello all, I'm running a newly installed CentOS 5.4 KVM host and am running into problems setting guests up to autostart. Has anyone seen and/or overcome this issue? [root at virt04 ~]# virsh autostart guest02 error: Failed to mark domain guest02 as autostarted error: internal error cannot set autostart for transient domain Just for kicks I tried symlinking /etc/libvirt/guest02.xml and

Hi, I ran into a Problem when using alias interfaces with vlans on a centos 5 box. When I define such an interface and do a "service network restart" the alias interface doesn't get started. Starting it manually works fine. Also after changing DEVICE=eth0.10:0 to DEVICE=eth0:0 in the config file the interface is started after a network restart. Does anyone have an idea what the

Hi all, I've a little problem with CentOS 6 and EFI on Dell Poweredge R510... My Logical disk (hardware raid) is a little bit greated than 9TB, so i must use EFI in order to see the whole disk space and boot on it, but my box don't want to boot on CentOS 6 x86_64 Install DVD when i'm in EFI boot mode. someone has successfully installed CentOS 6 x86_64 in EFI mode ? Regards.

Hi, Whats the new way of creating sha512 passwords in EL7? In Centos6 I used grub-crypt but that does not exist anymore.

I am working on S5000VSA Intel Server Board with the following cpu spec. XEN-PEER-RHEL5 $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping : 7 cpu MHz : 2327.512 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0

Hi, I am facing issues after upgrading one of the server from rhel5.5. (86_64) to latest rhel5.7 (86_64). The server is under trunk configuraion. I have set the network bridge as follows: #!/bin/bash vconfig set_name_type DEV_PLUS_VID_NO_PAD dir=$(dirname " $0" /etc/xen/scripts/network-bridge $@ vifnum=1 bridge=xenbr2 netdev=bond0.10 /etc/xen/scripts/network-bridge $@

Hi, We have a Dell server with 4 Ethernet interface. I would to aggregate them in a bond. Everything work but the default gateway doesn?t work on the ? bond0 ? interface and I have no links. My configuration: - CentOS 7: :/etc/sysconfig/network-scripts# uname -a Linux nas-mtd2 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - NetworkManager disabled:

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

I figured I should post this because before I went to do it I searched the web for caveats etc and didn''t really find much. So anyway, I set up bonding + vlan for a project. Computer is dell powerdge 350 with 2 intel 82559 10/100 nic running stock 2.4.20. I tried both the eepro100 and the e100 drivers for the nics, both work 802.1q and bonding are modules. Switch is cisco 2924xl-en

Hello, We''ve recently started seeing several domUs on multiple machines losing all network connectivity. At least one of these machines (since they are customer machines I can''t verify it for all of them) give the error: $ sudo ifup eth0 eth0: full queue wasn''t stopped! About the only Google hit for this message is:

Hi, I have two physical machines connected through a switch in a 192.168.1.* subnet. Dom0''s are assigned static ip addresses 192.168.1.100, 192.168.1.101 respectively. Dom0''s can ping each other. Each physical machine has a domu guest and static address assigned to domu''s are 192.168.1.200, 192.168.1.201 respectively. However domu''s can neither ping each other

On 18/04/2017 15:54, Frank Thommen wrote: > 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

Hi, I'm wondering about the impact of using both dom0 and domU's on a server at the same time. I'm worried about the performance impact of running a Mysql server in a domU and now I'm thinking about moving the Mysql part of a LAMP setup into dom0 and running a few Apache guests as domUs. Since the Apaches will serve mostly from an NFS share they won't have much impact on

Hi, In one of our xen server, I am using two bonding. bond0 : Is for trunk, where the vlans are attached , port eth0 & eth1 is attached to bond0 bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the

Hi all, I've a little problem with software cluster provided by CentOS 6.2 (cman, rgmanager & cie), VM cluster services and global cluster resources. Here is my system arch: --------------- ------------------ |clusternode1 |--+---| GFS2:vmimages1 | --------------- | | | | | VM img 1 | | | VM img 2 |

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [