Displaying 20 results from an estimated 10000 matches similar to: "XEN Virtualization & Isolation of Guest using ebtables"
2009 Jul 16
0
xen-3.0.3-80.el5_3.3 on RHEL 5.3 -- peth0 and xenbr0 don''t exist
Has anyone ran into this issue before?
2 physical nics:
eth0 hooked up to 10.175.8.0/21
eth1 hooked up to 10.150.8.0/24
Ifconfig -a looks like this:
[root@mgixen1 ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3
inet addr:10.175.8.158 Bcast:10.175.15.255
Mask:255.255.248.0
inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link
UP
2008 Feb 28
1
Networking problems with fresh install
I just did a fresh install of centos 5.0 from cd, followed by yum update
which installed 399 packages. No failures or errors that I can see.
I have three nics in the box, but am only setting up one at the moment.
The box can ping others in my network, but if I try ssh, telnet, ftp, etc
I get this:
[root at cm network-scripts]# ftp watchdog
ftp: connect: No route to host
ftp>
[root at cm
2009 May 11
1
vif0.0: received packet with own address as source address
Hi all,
Has anyone seen this before? I''m running a CentOS 5.3 with xen 3.0 and the
server has been running fine for a long time. In fact, it was up for 186
days before I had to reboot after the "network died", and I couldn''t fix it.
The server has multiple domU''s on it, which all still works when the host
node (dom0)''s network dies with these
2010 Jul 31
1
Arp Flip Flops make machine inaccessible.
CentOS 5.5 Xen "standard" Xen Installation.
I have two nics. I just put the second one to DHCP and modified the
ifcfg-et01 and so far I am holding, but I am not confident. Prior they
were sequential IP Addrs on same subnet.
arpwatch has indicated flip flips. I can find no rhyme or reason to
predict them. I know I missed I must have missed a step somewhere.
I want to keep the
2007 Jul 22
0
Network configuration after upgrade
Hello,
A bit of history
================
1) I''ve got a normal 2.6.20 x64 Fedora 6 Linux server running several things
2) I''ve downloaded and installed the XenSource Administrator Console for
Windows
3) I''ve added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux
server
4) I rebooted the Linux server, and started xend as per user guide
Configuration
2008 Feb 20
0
network-routing
Dear Xen-Users,
I use Xen 3.1.0_15042 on my OpenSuSE-10.3-computer. Without starting the
xen-kernel I can connect my second computer via my native computer to
the internet. After starting the xen-kernel the xen-bridge came
automatically up.
How can I configure the xen-bridge or the xen-devices?
I get routing problems:
Feb 20 18:31:36 intel6550 kernel: martian source 217.237.149.142 from
2007 Apr 18
1
[Bridge] Ip traffic not bridged
Hi, I am trying to set up a bridge that connects 2 user mode linux
(UML) machines. The bridge lets ARP traffic through, but not the IP
traffic.
linux:~ # brctl showmacs br0
port no mac addr is local? ageing timer
2 00:ff:7d:86:06:47 yes 0.00
3 00:ff:bc:de:07:76 yes 0.00
2 fe:fd:c0:a8:00:03 no
2017 Nov 01
2
Centos and xen network bridge issue
Hi All,
We have a single Centos 5.11 server running a xen hypervisor that went
down hard after an extended power outage this weekend. I'm mostly
familiar for KVM as that is the majority of what our guests run under
and have tried getting up to speed on xen bridging to no avail.
The problem is that after the xen server spun back up, the previously
defined xen bridges were lost. I've
2006 Aug 30
0
ping out of domU OK ping in to domU not OK
I''ve setup Xen 3.0.2-2 (binary install) on Ubuntu 6.06, got my domUs up
and running, got them connected to the Internet but I can''t even ping to
any of these VMs.
Now I''m not linux/xen genious but could the problem be that xen-br0
doesn''t have an IPv4 address? (it''s got an IPv6 address)
Since I don''t use IPv6 on my network this seems a
2008 May 28
6
SSH ping etc not working between dom0 and domU''s
Hi!
I have a problem with my new Xen setup. I have installed Debian etch
with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and
3.0.3-0-4 version xen hypervisor. I''m using four network cards on my
system and using three of them as xen bridges and dom0 is using the
fourth one only for it''s own. So basicly both of my virtual servers use
a network card
2014 Aug 25
0
network configuration on DomUs
Hi
I'm very new with Xen (/Debian)
I have 2 VMs running Windows: "Arch" and "Sql" -- static IPs
VM Arch: is ok, accessible thru VNC, Remote Desktop, see the network, etc
VM Sql : - just accessible thru VNC
- once I log in, I don't see the network
- pings don't reach peer
- appear 4 network ports on Windows
the server has 4
2011 May 24
0
Multicast problems when VM are located on different Xen servers
XenServer build date: 2010-11-30
XenServer build number: 39265p
XenServer version: 5.6 Feature Pack 1
Guest OS: CentOS 5.6
Guest Kernel: 2.6.18-238.9.1.el5xen
Hi everyone,
we have set up several Xen servers with the version mentioned above. The version is the same on all servers, the kernel is the default one, not patches or self compiled versions. Each Xen server has 6 network interfaces (eth0
2009 Sep 21
0
received packet with own address as source address
Hi,
we''re running 4 xen servers on our network with multiple network cards.
During HighLoad we experince degeneration of inbound network traffic
through our loadbalancer. I might found a reason for it, in Dom0 dmesg
output looks as follows:
[1157421.975910] eth0: received packet with own address as source address
[1157421.975957] eth0: received packet with own address as source
2008 Dec 15
1
Xen Dom0 network fails to start at boot
I have a server running Centos 5.2 as a Xen host. A problem that's
shown up recently is that at boot, the dom0 interface eth0 doesn't come
up properly, with the result that the host is only accessible via remote
console. If I execute 'service network restart', eth0 comes up
normally, with an IP address and the correct routing.
Three guests have been created via virt-manager
2009 Feb 11
0
TWO NIC WITH TWO BRIDGE NOT WORKS XEN 3.0.3 -- WHAT AM I WRONG ?
Hello everyone.
I just installed Xen 3.0.3 in a debian etch box.
Linux server1.example.com 2.6.18-6-xen-686 #1
This server1 has two real nic (eth0 with real MAC 00:13:72:57:7B:AE and eth1
with real MAC00:13:72:57:7B:AF).
I made a network-bridge custom like this:
-----------------------------------------------------------------------
#!/bin/bash
dir=$(dirname "$0")
2009 Nov 06
1
dome domU''s can''t connect to the internet, while others can
Hi all,
I have a very strange situation, which I can''t explain.
On a Core 2Quad server with 8GB RAM, we have 10 xen domU''s, as follows:
vps.animalsaregreat.info login: root@zaxen01:[~]$ xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 512 4 r----- 232.2
actionco.vm
2006 May 04
2
No networking in DomU - Ubuntu
Well where do I start...I have a domU (ubuntu) booting and appears well
but I don''t have an eth0 listed at all, dom) looks good.
DomU:
eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B
inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248
inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
2008 Nov 26
0
cannot enable sound on domU (centos5.1) and cannot change virbr0 bridge to xenbr0 bridge
Hi all,
my dom0 is centos5.2 and domU paravirtualized is centos5.1
I can play sound on dom0 but not in domU (name: gasphar), moreover I use
wifi as my inet connection and on installing domU cento5.1, I used
virt-manager.
I know that libvirtd made virbr0 and when changing to xenbr0, I cannot
connect to internet but ssh to dom0 is fine!
so how do I enable sound device on domU and changing to
2008 May 28
0
Strange dom0 networking error with Debian "Etch" amd64
Hi,
We''re trying to run Xen on a Debian "Etch" base system (kernel
2.6.18-6-xen-amd64), but have come across a strange networking error
whenever bridging (vif-bridge/network-bridge) is in operation. The
symptom is that the dom0 base system loses all network connectivity to
the outside world while the two guest instances function perfectly well.
As far as we can tell, we
2011 Feb 16
1
NIC bonding - missing eth0?
I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5
In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports.
It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port