[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] OpenSUSE 11.4 (2.6.39-30.1), Xen 4.0.2 - Device 0 (vif) Could not be connected


  • To: Mark Pryor <tlviewer@xxxxxxxxx>
  • From: Steven Altsman <steven.altsman@xxxxxxxxx>
  • Date: Thu, 2 Jun 2011 06:46:21 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 02 Jun 2011 06:09:01 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=g8PpMEU039sU7nNkPXeCT5mKlxqA/WR0iSM5cQ2Um6Zp16QmeVZaYVx941rgAEvw5R HLkEJjCi/PbQJQeay8/6m8ks58ggBgo7Qx3c9D1YFnPwHROrzFvZ6WnBtszdTnB6f0RQ 5ViXdjIWsU/2WTe58oSpDPF+dAkQZk5fWzOYM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Thanks to Mark and Dustin, I have made it a bit further.  I had to
modify the xend-configure.sxp to have (network-script 'network-bridge
bridge=br0 netdev=eth0') plus making the br0 device manually in
/etc/sysconfig/network/ifcfg-br0.

Now I have a VM (OpenSUSE 11.4, again) but I am getting

"Unable to configure the network card because the kernel device (eth0,
wlan0) is not present.  This is mostly caused by missing firmware (for
wlan devices).  See dmesg output for details."

Ibis redibis nunquam per bella peribis


On Tue, May 31, 2011 at 11:42 AM, Mark Pryor <tlviewer@xxxxxxxxx> wrote:
>
> --- On Mon, 5/30/11, Steven Altsman <steven.altsman@xxxxxxxxx> wrote:
>
> From: Steven Altsman <steven.altsman@xxxxxxxxx>
> Subject: [Xen-users] OpenSUSE 11.4 (2.6.39-30.1), Xen 4.0.2 - Device 0 (vif) 
> Could not be connected
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Date: Monday, May 30, 2011, 3:17 PM
>
> 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.
>
> The bit in the config file says:
> # SuSE users note:# On openSUSE >= 11.1 and SLES >= 11, networks should be 
> configured using# native platform tool - YaST.  vif-bridge and qemu-ifup can 
> be used to
> # connect vifs to the YaST-managed networks.#(network-script network-bridge)
> So... how exactly is YaST supposed to do this...?
>
> -------------
>
> you could try uncommenting
> (network-script network-bridge)
>
> chances are, you'll get a working network compatible with xen.
>
> If you want to make a manual bridge,
>
> ----------------------- ifcfg-br0 ------------------
> > sudo cat /etc/sysconfig/network/ifcfg-br0
> BOOTPROTO='dhcp'
> BRIDGE='yes'
> BRIDGE_FORWARDDELAY='0'
> BRIDGE_PORTS='eth0'
> BRIDGE_STP='off'
> BROADCAST=''
> ETHTOOL_OPTIONS=''
> IPADDR=''
> MTU=''
> NETMASK=''
> NETWORK=''
> REMOTE_IPADDR=''
> STARTMODE='auto'
> USERCONTROL='no'
> #ETHTOOL_OPTIONS='wol g'
> ---------------- snip -----------
>
> backup/archive the ifcfg-eth0
>
> Only one should be active at a time.
>
> --
> Mark

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.