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

[Xen-users] Re: Xen 3.3 domU Networking


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ricardo Tiago" <rtiago@xxxxxxxxx>
  • Date: Mon, 13 Oct 2008 16:41:55 +0200
  • Delivery-date: Mon, 13 Oct 2008 07:42:40 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=D8SCoejic0DWTMwKnfYrIQB/g/FNKUJ2+p/KgsUij2GDg+Wc4rOx84TWEj9+jw80qZ HrzTVvFxBlCTS/mdqQu9vPZipQjIVT9pn/ms/oG5nkt7a5WGxsUIOWZPHs9946sRzCOP H9H/UNDf2o8tc86xhFome1hPj8A4sH9yrqyg4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

In case this helps anyone else, I was missing netloop, I just rebuilt
the kernel and choose..

Networking  --->
  Networking options  --->
    <*> 802.1d Ethernet Bridging
    Only required by bridged networking.

Regards,
Ricardo

On Mon, Oct 13, 2008 at 3:25 PM, Ricardo Tiago <rtiago@xxxxxxxxx> wrote:
> Hi All,
>
> I compiled xen3.3 on a rhel 5 machine and the dom0 booted ok without
> problems but when i start a rhel5 dom0 i don't get networking.
> During the domU boot process the message 'Networking not configured -
> exiting' appears. Did i miss something in the configuration file or
> loading a module?
>
> == config file ==
>
> name = "vm1-gen-1"
> ip = "xx.xx.xx.xx"
> hostname = "gen-1"
> memory = "256"
> disk = 
> ['phy:/dev/vg1/xen-root-gen1,xvda1,w','phy:/dev/vg1/xen-swap-gen1,xvda2,w']
> root = "/dev/xvda1 ro"
> vif = ['mac=00:16:3e:aa:aa:aa,ip=xx.xx.xx.xx']
> cpus = '0'
> vcpus = '1'
> gateway = "xx.xx.xx.xx"
> netmask = "255.255.0.0"
> on_reboot = 'restart'
> on_crash = 'restart'
> on_poweroff = 'restart'
> bootloader = '/usr/bin/pygrub'
>
> == dom0 brctl show  ==
> bridge name     bridge id               STP enabled     interfaces
> eth0            8000.001e4f3dbe83       no              vif3.0
>                                                        peth0
>
> === boot - domU ===
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> ide-floppy driver 0.99.newide
> usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> TCP bic registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Using IPI No-Shortcut mode
> XENBUS: Device with no driver: device/vbd/51713
> XENBUS: Device with no driver: device/vbd/51714
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/console/0
> Freeing unused kernel memory: 168k freed
> Write protecting the kernel read-only data: 360k
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Loading uhci-hcd.ko module
> USB Universal Host Controller Interface driver v3.0
> Loading ohci-hcd.ko module
> Loading ehci-hcd.ko module
> Loading jbd.ko module
> Loading ext3.ko module
> Loading dm-mod.ko module
> device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: 
> dm-devel@xxxxxxxxxx
> Loading dm-mirror.ko module
> Loading dm-zero.ko module
> Loading dm-snapshot.ko module
> Loading xenblk.ko module
> Registering block device major 202
> Loading xennet.ko module
> netfront: Initialising virtual ethernet driver.
> netfront: device eth0 has copying receive path.
> Creating root device.
> Mounting root filesystem.
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> Setting up other filesystems.
> Setting up new root fs
> no fstab.sys, mounting internal defaults
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> SELinux:  Disabled at runtime.
> audit(1223903723.862:2): selinux=0 auid=4294967295
> .......
> Setting hostname localhost:  [  OK  ]
> No devices found
> Setting up Logical Volume Management:   No volume groups found
> [  OK  ]
> Checking filesystems
> Checking all file systems.
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
> /dev/xvda1: clean, 51585/655360 files, 381138/1310720 blocks
> [  OK  ]
> Remounting root filesystem in read-write mode:  [  OK  ]
> Mounting local filesystems:  mount: none already mounted or /sys busy
> mount: according to mtab, sysfs is already mounted on /sys
> [FAILED]
> Enabling local filesystem quotas:  [  OK  ]
> Enabling /etc/fstab swaps:  [  OK  ]
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> Applying Intel CPU microcode update: [FAILED]
> There is not any 3945 hardware, not starting ipw3945dStarting
> KnConfig: [NO DATA]
> Starting auditd: [  OK  ]
> Starting system logger: [  OK  ]
> Starting kernel logger: [  OK  ]
> Starting irqbalance: [  OK  ]
> Networking not configured - exiting
> Starting NFS statd: [  OK  ]
> Starting RPC idmapd: [  OK  ]
> Starting system message bus: [  OK  ]
> [  OK  ] Bluetooth services:[  OK  ]
> Starting PC/SC smart card daemon (pcscd): [  OK  ]
> Starting hidd: [  OK  ]
> Starting autofs:  Loading autofs4: [  OK  ]
> Starting automount: [  OK  ]
>
> Regards,
> Ricardo
>

_______________________________________________
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®.