WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Cannot configure ethernet-cards for IPCop in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Cannot configure ethernet-cards for IPCop in domU
From: "Jaroslaw Zdrzalek" <Jaroslaw.Zdrzalek@xxxxxxxxxxxxxxxx>
Date: Tue, 23 Jan 2007 15:54:27 +0100
Delivery-date: Wed, 24 Jan 2007 02:02:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45B274F3.2010708@xxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <45B274F3.2010708@xxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
Am Samstag 20 Januar 2007 21:00 schrieb Morten Christensen:
> With Qemu I have created an IPCop 1.4.13 domU. Qemu found and configured 
> a NE2000 pci-card (ne2k-pci) as green.
> 
> I can start the image both in Qemu and as a hvm in Xen, but the netvork 
> is not working in any of the instances. Inside Ipcop on Xen it comes 
> with this error:
> 
> /lib/modules/2.4.34/kernel/drivers/net/ne2k-pci.o.gz: init_module: No 
> such device
> /lib/modules/2.4.34/kernel/drivers/net/ne2k-pci.o.gz: insmod
>    /lib/modules/2.4.34/kernel/drivers/net/ne2k-pci.o.gz failed
> /lib/modules/2.4.34/kernel/drivers/net/ne2k-pci.o.gz: insmod ne2k-pci failed
> 
> Can I configure the domU in Xen in a way so Ipcop can find 2 
> ethernet-devices ?
yes, I tested this on debian sid with ipcop 1.4.11, two bidges on xen-3.0.3 
debian release.
here the config:

name = "cop1"
cpus = ""
vcpus = 1
vif = [ 'type=ioemu, bridge=xenbr0', 'type=ioemu, bridge=xenbr1' ]
#disk = [ 'phy:/dev/sdb1,ioemu:hda,w', 'phy:/dev/scd0,hdb:cdrom,r', 
'phy:/dev/sdc,fda,w' ]
#disk = [ 'phy:/dev/sdb1,ioemu:hda,w', 'phy:/dev/sdc,ioemu:fda:floppy,w' ]
disk = [ 'phy:/dev/sdb1,ioemu:hda,w' ]
#disk = [ 'phy:/dev/sdb1,ioemu:hda,w', 'phy:/dev/loop/0,hdb:cdrom,r', 
'phy:/dev/sdc,fda,w' ]
boot='c'
device_model = 'qemu-dm'
#ne2000=0
kernel = "hvmloader"
builder='hvm'
memory = 128
shadow_memory = 8
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
sdl=1
vnc=0
stdvga=0
#apic=1
#acpi=1
pae=0
#serial='pty'
#usb=1
#usbdevice="host:0644:0000"
#fda="/dev/sdc"

I used the whole partition to emulate a harddisk inside of ipcop,
but you can use a file as well.

The only problem I have had is to get the floppy emulation to work.

> 
> ( I don't think it is by important now, but in dom0 my eth0-driver is 
> forcedeth and the eth1-driver is fealnx.)
> 
it is less important, because the whole network is emulated to ipcop hvm guest.

Your problems might result from a newer version of ipcop and/or xen or 
host-system.
I will test it again, when I finish my custom ipcop-build with the new release 
1.4.13

cheers
Jaroslaw

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

<Prev in Thread] Current Thread [Next in Thread>