RE: [Xen-users] Missing eth0 in Domu

["Venefax" <venefax@xxxxxxxxx>]

linux-tlxs:~ # brctl show

bridge name     bridge id               STP enabled     interfaces

eth0            8000.001ec9e9e883       no              peth0

                                                        vif56.0

                                                        vif73.0

                                                        vif50.0

                                                        vif74.0

                                                        vif53.0

                                                        vif70.0

                                                        vif18.0

                                                        vif22.0

                                                        vif23.0

                                                        vif24.0

                                                        vif25.0

                                                        vif26.0

linux-tlxs:~ #

 

From: Daniel Kao [mailto:dkao@xxxxxxxxxxxx]
Sent: Wednesday, December 10, 2008 7:55 PM
To: Venefax
Cc: 'Xen List'
Subject: Re: [Xen-users] Missing eth0 in Domu

 

Hi Venefax,

First, as root in a shell on your dom0, run a "brctl show" and paste the contents to the list.

Second,

    (device

        (vif

            (mac 00:16:3e:2c:88:81)

            (uuid 837dcbd1-61ab-fc78-a0f1-f8679e4688d9)

        )

    )

Should look more like this:

    (device

        (vif

            (bridge eth0)

            (mac 00:16:3e:2c:88:81)

            (script vif-bridge)

            (uuid 837dcbd1-61ab-fc78-a0f1-f8679e4688d9)

            (backend 0)

        )

    )

... This is under the assumption you are bridging eth0 from dom0 to your domU's.

Cheers,
Daniel

-- 

Daniel Kao

Übermind, Inc.

Seattle, WA, U.S.A.

Venefax wrote:

I have SUSE SP2 with Xen 3.2, but all my DomU's are Centos 64 5.2. One of my

Domu's cannot find the eth0, and prints this error:

ifconfig eth0

   eth0: error fetching interface information: Device not found

yet the machine configuration file is identical to other VM's that do work.

Is there a part of the VM that I need to change to make it "find" the device

eth0?

(domain

    (on_crash destroy)

    (uuid 1ccb0f31-8e77-64d5-3248-22c1078d0ddc)

    (bootloader_args

'--entry=xvda1:/vmlinuz-2.6.18-92.1.18.el5xen,/initrd-2.6.18-92.1.18.el5xen.

img'

    )

    (vcpus 2)

    (cpus 1-15)

    (name asterisk-3)

    (on_poweroff destroy)

    (on_reboot restart)

    (bootloader /usr/lib/xen/boot/domUloader.py)

    (maxmem 1024)

    (memory 1024)

    (shadow_memory 0)

    (features )

    (on_xend_start ignore)

    (on_xend_stop ignore)

    (image

        (linux (kernel ) (args ' ') (device_model

/usr/lib64/xen/bin/qemu-dm))

    )

    (status 0)

    (device

        (vif

            (mac 00:16:3e:2c:88:81)

            (uuid 837dcbd1-61ab-fc78-a0f1-f8679e4688d9)

        )

    )

    (device

        (vbd

            (uuid 41dcfe9a-2d95-dd16-69ff-35ae9be8d401)

            (bootable 1)

            (driver paravirtualised)

            (dev xvda)

            (uname file:/xen/images/switch-3)

            (mode w)

        )

    )

    (device

        (vbd

            (uuid 88172eab-b08b-895e-7ee1-0fb00cf95715)

            (bootable 0)

            (driver paravirtualised)

            (dev xvdb:cdrom)

            (uname file:/suse/CentOS-5.2-x86_64-bin-DVD.iso)

            (mode r)

        )

    )

    (device (vkbd (uuid 64b95846-8966-b6ce-1aaf-f67b71f03ea5)))

    (device

        (vfb

            (vncunused 1)

            (type vnc)

            (xauthority /root/.Xauthority)

            (uuid 7769691f-9200-e1fb-c944-7095ff2696ce)

        )

    )

)

_______________________________________________

Xen-users mailing list

Xen-users@xxxxxxxxxxxxxxxxxxx

http://lists.xensource.com/xen-users

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