similar to: ARP problems with xen 4.0 with pvops kernel

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

I have CentOS 7 host. Two guests on bridge network setup by GUI and virt-manager. 1 CentOS 8 guest 1 Win 10 guest Both cannot access the host. They can other machines on the network. Guests can access the internet just not the host. I used virt-manager GUi to set up everything. Selected the eth0:macvtap and Bridge. I "desire" bridge network. If I select something else I get access to

Hi. I have a machine with a local DHCP server and a couple of virtual networks and I've configured the server for each virtual interface, so that I would be able to install VMs on the corresponding subnets using PXE. The problem is that the two DHCP servers (my local server and dnsmasq) are conflicting with each other causing the boot process to either fails or takes ages untill a VM can

On Tue, Jun 20, 2017 at 10:05:19AM +0200, Martin Kletzander wrote: >On Tue, Jun 20, 2017 at 02:26:59AM -0400, Travis S. Johnson wrote: >>Hello, >> >>I came across an interesting problem in my home lab a few weeks ago as I'm >>prepping for my RHCE exam using Michael Jang study guide. I've been at this >>for days now, and I still can't wrap my head around

Hello, I came across an interesting problem in my home lab a few weeks ago as I'm prepping for my RHCE exam using Michael Jang study guide. I've been at this for days now, and I still can't wrap my head around how two or more virtual networks in default NAT configuration are even allowed to communicate with each other despite what the libvirt documentation said. Here's the

Hi everyone. Those are the iptables forwarding rules associated with the two virtual networks on my machine: ----------------------------------------------------------------------------------------- -A FORWARD -d 192.168.100.0/24 -o virbr1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -s 192.168.100.0/24 -i virbr1 -j ACCEPT -A FORWARD -i virbr1 -o virbr1 -j ACCEPT -A FORWARD -o

>Sorry, have to correct myself. Had to much to do today on OpenShift. >There is no Docker involved in what we discuss. The firewall rules for >the host bridge devices get created by libvirtd. Thanks I was using iptables and not converted to firewalld. I am doing so now. Will I need to delete the VM and re-add it ? I am rebooting first. Jerry

Hi all, I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding networking between them. The 2 RHEL4 system's use default bridge virbr0 and get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) I created another bridge (virbr1) with NAT forwarding (no dhcp). The network i choose was 192.168.100.0/24. And the third system (RHEL6) was assigned static ip-addres

Hi, I haven't been to find this (NetworkManager) change documented. On: CentOS Linux release 7.1.1503 (Core) $ /bin/nmcli con NAME UUID TYPE DEVICE ens32 7629e52d-bd42-4cd5-a424-8c58e7e0bf37 802-3-ethernet ens32 On: CentOS Linux release 7.2.1511 (Core) $ /bin/nmcli con NAME UUID TYPE

Hello! Has anybody experienced network latency problems with combination of Windows 7, GPLPV drivers and RDP connection? Any Windows pop-up message(such as "command not found" error message in "Run command:" dialog, or dividing by zero in windows calc) causes a short freeze of RDP session and looks like that from dom0: PING 192.168.44.65 (192.168.44.65) 56(84) bytes of data.

I'm looking for some information regarding the interaction of KVM, VLANs, firewalld, and the kernel's forwarding configuration. I would appreciate input especially from anyone already running a similar configuration in production. In short, I'm trying to figure out if a current configuration is inadvertently opening up traffic across network segments. On earlier versions of CentOS

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

Hi, I have spent a fair amount of time trying to solve this problem and tried things like disabling checksums etc. The problem is like this: 1. I boot my dom0 without xend running and I can resolve and ping google. 2. I start xend (without and domU domains up) and after a while I can no longer resolve domain names, but I can ping the public IP addresses. 3. I start up a domU (xm create -c xyz)

Hi list, i''ve been migrating our RAID1 system onto bigger drives. Therefor I''ve setup a new dom0 with a 2.6.32-5-xen-amd64 kernel and Xen in version 4.0, because there was a 2.6.19 kernel and xen 3.0.1 causing problems time by time. My main problem is, that the domU running our intranet services (webserver, mail, databases etc) is not responding or rejecting each attempt to

Hi all, i have trouble to PXE boot KVM-based (network of Linux-bridge) Virtual Machines: very slow transfer pxelinux.cfg. ====== tcpdump on KVM host system ==== [root at kvm-test01 ~]# tcpdump -i virbr1 | grep -v ssh | grep 10.0.5.187 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on virbr1, link-type EN10MB (Ethernet), capture size 96 bytes 17:57:29.809278

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

I’m running into an issue with libvirt-lxc networking. I have an init program that configures the eth0 interface with an IP and gateway when the container starts. I noticed that programs running in the container encountered “no route to host” errors and looked into it further. What I found is that ARP packets are not making it onto the gateway during the first few seconds of the container’s life.

In usr/src/uts/common/xen/io/xnbu.c, function xnbu_cksum_from_peer() http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/xen/io/xnbu.c#110 we have this: if ((flags & NETTXF_csum_blank) != 0) { /* * The checksum is blank. We must fill it in here. */ mp = xnb_process_cksum_flags(xnbp, mp, 0);

Adding -kd to extra line drops me to kmdb :- root@ServerJaunty:/home/boris/nevada# xm create -c osol.install Using config file "./osol.install". Started domain osol.install (id=4) Loading kmdb... Welcome to kmdb Loaded modules: [ unix krtld genunix ] [0]> I want patch kernel like it happens when adding to /etc/system:- set xnf:xnf_cksum_offload = 0