Displaying 20 results from an estimated 20000 matches similar to: "HVM vif without bridge"
2009 Jan 20
0
qemu - bridge xenbr0 does not exist
Hi,
I just upgraded the xen-hypervisor-3.2-1 package in Debian etch from the backports (3.2.1-2~bpo4+1) and now my HVM instance won''t boot any more.
The error message in the log is:
-c config qemu network with xen bridge for
tap0 xenbr0
bridge xenbr0 does not exist!
/etc/xen/scripts/qemu-ifup: could not launch network script
Could not initialize device
2006 Jul 10
0
hvm networking with vif-route
Greetings xen gurus...
I''m working with xen-3.0-testing downloaded on July 3, 2006. I have
configured an hvm domain and want to use vif-route and network-route to
configure the communication.
The domU starts up fine. I was able to complete the installation of the OS
(RHES3) and can restart the domain repeatedly. However, I cannot ping the
network interface from dom0 using the
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 Sep 08
0
Disappearing TAP interface
I have a CentOS 5.2 Xen host, running several guest domains. Each guest
domain has a single interface assigned to it. I am using both the
network-bridge and vif-bridge scripts.
On my only windows guest, the tap interface connected to the bridge
keeps getting disabled. If I check "brctl show" the tap0 interface is
not present, and there will be several message log entries indicating
2008 Mar 11
1
arp who-has not answered
Hello,
Fast question: from DomU I cannot ping Dom0, I only get
19:17:33.573370 arp who-has 192.168.10.1 tell 192.168.10.150
19:17:34.573421 arp who-has 192.168.10.1 tell 192.168.10.150
using tcpdump in Dom0. Why?
---------------
Detailed question:
I''m setting up a Xen virtual server. The environment is:
-HVM
-AMD64
-Debian Etch and using Xen from Debian repository (so Xen 3.0.3,
2008 Jul 17
0
[PATCH] stubdom: add example config file
stubdom: add example config file
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -r e69570f85e85 tools/examples/stubdom-ExampleHVMDomain
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/tools/examples/stubdom-ExampleHVMDomain Thu Jul 17 19:31:13 2008 +0100
@@ -0,0 +1,21 @@
+# Not to be started directly,
+# See xmexample.hvm-stubdom and stubdom/README for more details
2006 May 06
2
Bug#366216: vif-bridge: offlining the interface fails because interface already offline
Package: xen-utils-3.0
Version: 3.0.2+hg9656-1
Severity: normal
My setup is a basic one. No changes to the /etc/xen/* files.
Network in a domU works perfectly fine.
But, after shutdowning a domU, I can see the following lines in
/var/log/debug:
May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0
May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge:
2012 Jun 20
0
xen dom0 reboot when windows hvm started
Dear Community,
i have a problem with a new debian XEN 64bit squeeze Server, when i started
a windows hvm domU. I tested with the routed and now in the bridge network
mod.
I start the domU with xm create win.cfg and 1 or 2 second the dom0 is
reboot. I install a debian domU on the system, and this is without any
problems in routed and bridge mod.
In the logfile are no informations, in the routed
2008 Jan 18
0
[PATCH] nicely terminate the device model script
Nicely terminate the device model script, to let it properly clean
resources.
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -u b/tools/python/xen/xend/image.py b/tools/python/xen/xend/image.py
--- b/tools/python/xen/xend/image.py Fri Jan 18 11:53:23 2008 +0000
+++ b/tools/python/xen/xend/image.py Fri Jan 18 12:42:11 2008 +0000
@@ -325,7 +325,7 @@
return
2009 Jan 29
0
Network issue with vif-route method
Hello folks,
I used to work with bridging for my xen networks, but my very last hosting
provider doesn''t support multiple mac address on the switch port.
So I''m trying to configure some virtual servers on xen 3.2.1 using the
network-route and vif-route method instead of bridge.
Everything works well, on the virtual server except the network.
In the VM definition file, I have :
2010 Sep 20
0
Routed Xen HVM on Centos 5.5 64bit
Hello people, first of all this is my first mail and I am new to Xen
so be nice with me :-)
OK, I installed a Centos 5.5 in a system.
Used yum groupinstall "Virtualization" to install anything related to Xen.
Those packages installed:
2006 Jan 05
1
vif''s disappear after dom1 reboot
Today I found I can not ping some of my domU''s. I logged in to dom0,
did a "xm list", all domU are there. Then I did a "ifconfig" and
surprised to find some of vif''s disappeared!
Like for example. "xm list" show dom13 is alive, but "brctl show"
shows no vif13.0.
If I "xm console 13", there''s some message:
WARNING:
2005 Dec 06
1
RE: Hotplug scripts not working... xen/ia64 domU stoppedworking
> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xensource.com]
> Sent: Tuesday, December 06, 2005 9:16 AM
> To: Dave Thompson (davetho)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working...
> xen/ia64 domU stoppedworking
>
> On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson
> (davetho) wrote:
>
> >
2009 Nov 06
1
Bug#554805: patch to enable routed networking in HVM+ioemu
tag 554805 + patch
thanks
The problem to solve is that qemu-ifup assumes the world is always
bridged, and vif-routed does not know of the concept of TAP devices, and
even if it did, it has at this point no way to get at qemu's TAP device
anyway.
The following set of patches help run in the ioemu-HVM situation:
* xend-image.py.diff : modifies the HVM loader so that when running in
2009 Aug 26
0
VIFs disappear from bridge - 3.0.3 Debian Etch
Hi all,
We''ve been using Xen 3.0.3-1 on Debian Etch for around 2 years now using standard Xen bridging. Over the past few months, we''ve experienced the periodic disappearance of VIF macs from the FDB of the bridge. It seems to happen at random, primarily with domUs that typically receive less network traffic. When the VIF stops responding, the mac address for it still shows up
2011 May 30
4
OpenSUSE 11.4 (2.6.39-30.1), Xen 4.0.2 - Device 0 (vif) Could not be connected
All,
This is a fresh, un-f#$ked-with OpenSUSE install after adding the Tumbleweed
repository and doing a dup. I installed the Hypervisor with Tools for which
it prompted me for Xen or QEMU and I chose Xen. No bridge was made.
When I go to create a fully virtualised machine, it nao has the error:
Error: Device 0 (vif) could not be connected. Could not find the bridge,
and none was specified.
2008 Sep 23
0
答复: Re: 答复: RE: 答复:RE:
Hi all,
I have started stubdom, thank all of you. But I still met a problem, that is I found stubdom block when it run 107s. the message in "xm li" :
Domain-0 0 1719 2 r----- 171.9
hvmachine 1 256 1 -b---- 110.6
hvmachine-dm
2011 Aug 26
0
Using of bonded interfaces for xen dom0 (debian)
Hello,
Where can I find a link (or docs) to *working* network config for xen 4.1.2?
My tests (s. below) were not successful.
Thank you in advance for any hints.
Regards, Mark
# ---
root@xen411dom0:~# cat /etc/network/interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
auto bond0
2008 Mar 24
0
Xen3.1 setup-problem: no networking in WinXP-domU
Hi,
I cannot get my network up in WinXP- and winVISTA-domU''s
I need some help, since I got lost in the google-jungle...
My system:
UBUNTU gutsy gibon-AMD64 on a intel core duo-system.
this is my /etc/xen/winxp.cfg:
#########
#
# Configuration file for the Xen instance debian.qwork.test, created
# by xen-tools 3.5 on Sun Mar 16 20:03:26 2008.
#
#
# Kernel + memory size
#
kernel =
2011 Sep 08
15
correct steps to add XEN bridge to Debian squeeze?
Hi all,
Does anyone know what the correct steps are to add a XEN bridge, let''s
say xenbr0 to Debian Squeeze?
I have added the following to /etc/network/interfaces
# XEN Bridge
auto xenbr0
iface xenbr0 inet manual
bridge ports eth0
bridge_stp off
bridge_fd 0
And then rebooted the server but brctl show still shows eth0 as bridge:
newusaxen:~# brctl