Displaying 20 results from an estimated 6000 matches similar to: "xend messes up broadcast address on eth2"
2006 Apr 25
0
Dom0 problems on Slackware 10.2
I''m running Xen 3.0.2 on a system that''s based on Slackware 10.2 as Dom0. DomU is also slackware 10.2. Am using the kernel that came with 3.0.2 - no custom config, just a "make world", etc.. Did have to add grub of course.
When I start up xend, I get the following on /var/adm/messages:
Apr 23 21:04:11 rc25 kernel: Bridge firewalling registered
Apr 23 21:04:11 rc25
2011 Aug 03
1
Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Package: xen-hypervisor-4.1-i386
Version: 4.1.1-1
Severity: important
Tags: wheezy
I cannot boot a domU with networking after installing the package.
root at topsail:~# xm create /etc/xen/udevtest.cfg -c
root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts
not working.
[2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2.
[2011-08-03
2007 Jun 19
0
Xen 3.1 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I get the error while starting hvm doms.
Any workarounds... suggestions..
Thanks
/Jd
Some thiings that might be useful are cut-pasted
below.
ifconfig -a
udevmonitor output (as suggested in prev posts)
qemu-dm log
xend.log
xend-debug does not seem to have anything interesting.
ifconfig -a
===========
eth0 Link encap:Ethernet HWaddr
00:0F:EA:53:5C:79
inet addr:192.168.12.103
2008 Nov 07
1
Unable to get Networking on HVM Domain
Hello everyone,
I grabbed xen-3.3.1 sources from the Mercurial repository
(xen-3.3-testing.hg, changeset 475:1cf755387728, from Oct. 23, 2008) and
built Xen from these sources on a 32-core (8 quad core Barcelona CPUs)
SunFire machine, running an Ubuntu 8.04 (Hardyy Heron) distribution.
Everything seemed to be going OK until I booted an HVM (also Ubuntu 8.04)
domain. That domain boots normally but
2008 Dec 12
0
xend nothing to flush, waiting for peth0 to negotiate
Hi,
I would like to ask concerning problems after installing xen 3.3 on Centos
5.2
I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After
done with make world and make install, I did mkinitrd and placing it in
/boot
changing the grub and reboot.. succeded
I do not install libvirt and the domUs from the previous xen 3.0 (built-in
Centos 5.2) are NOT able to start :
[root@wing
2008 Apr 18
1
help--dom0 network goes unpingable when xend starts (fwd)
I am posting the message below again because it did not go through
last night. Help!
Steve Timm
--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
timm@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
2005 Apr 23
6
Problems with domU networking
Moi!
I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly.
I''m still able to boot dom0 and start domUs but networking doesn''t work
anymore.
xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is
used. Interface appears in domU and all seems to be fine, except no any
data doesn''t move in any direction. I can''t even ping
2005 Nov 04
1
RE: Error "Device 0 (vif) could not be connected"
Yes, I saw that problem and removing the vif line or changing it to vif0
fixed it for me.
Aravindh
> -----Original Message-----
> From: wei huang [mailto:huanwei@cse.ohio-state.edu]
> Sent: Friday, November 04, 2005 12:14 PM
> To: Puthiyaparambil, Aravindh
> Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com
> Subject: RE: [Xen-users] Error "Device 0
2010 Apr 30
1
[SPAM] Xen bridge network issue
Hi,
I have taken the long and winding road and indeed it lead me to your door. I
need your help, please.
My Xen includes 2 guests. Xen itself (10.2.0.52) gets free access to the
outside world and to its guests.
Both guests however (10.2.0.54/10.2.0.55) see each other but stay under
house arrest!
Not a single ping manages to go past the bridge (xenbr0) and get an answer
from the default gateway
2006 Dec 11
10
Dom0 network problem
Hello.
I''ve just started with Xen and configuring Dom0.
My hardware is Core2Duo based Xeon server and I installed Debian etch
for amd64 architecture. The Xen related pachages installed are the
following.
linux-image-2.6.17-2-xen-amd64
linux-modules-2.6.17-2-xen-amd64
xen-hypervisor-3.0.3-1-amd64
xen-tools
xen-utils-3.0.3-1
xen-utils-common
My problem is that when xend is
2010 Mar 11
0
Xen problem network dom0
Hello,
I''ve install Xen on a Debian Lenny 5.04 and after reboot on my xen machine
I can''t have the same configuration that documentation.
************************************************************************
***********
Command "uname -r" =
2.6.26-2-xen-686
************************************************************************
************
Command
2005 Jun 05
7
Xen 3.0 Xend loses network - eth0 -> veth0?
Hi list.
I started with Xen yesterday, but I am facing a bit of a problem.
My system had always configure eth0 with 10.0.0.4/8
I am using Xen unstable source (on Debian sid)
Now I installed Xen, rebooted the machine, and first the usual network is
coming up and then the xend will be started.
I''ll end up with this, but I am wondering if this should be the way of
things to be
2007 Sep 07
1
Bug#441249: xen-hypervisor-3.0.3-1-i386-pae: "Problems using XEN when Quagga is running"
Package: xen-hypervisor-3.0.3-1-i386-pae
Version: 3.0.3-0-2
Severity: normal
If quagga is running, and I start & stop a domain, the VIF interface doesn't go
down properly (in addition to other problems).
Here's what I do:
1. Boot the computer. By default, quagga is running (zebra + ospfd).
2. xm create test7.cfg, wait until the domU starts.
3. xm shutdown test7, wait until the domU
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
2015 Jul 27
0
wicd problem 5: wicd restarts itself when as user making terminal commands
greetings,
following are command line problems as user using virtual terminals.
]$ ifconfig;date
eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1419 errors:0 dropped:0
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
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
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
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