Port-xen archive

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

Re: XEN on NetBSD-6.1 amd64.

On Thu, 2013-08-01 at 18:42 +0200, Manuel Bouyer wrote:
> On Thu, Aug 01, 2013 at 11:39:57AM -0300, Adiel de Lima Ribeiro wrote:
> > Good morning.
> > Sorry for my english, it isn't very whell.
> > Let's start.
> > I instaled NetBSD stable from the link:
> > nyftp.netbsd.org/pub/NetBSD-daily/netbsd-6/201307150Z and later I just
> > instaled netbsd-XEN3_DOM0 from the same place. So, then I instaled
> > xenkernel42-4.2.2 and xentools42-4.2.2nb3 with pkg_add from the link:
> > http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.0_2013Q2/
> > I let the /usr/pkg/etc/xen/xend-config.sxp with the default
> > configuration, I'm working with bridge network, so, then I created the
> > bridge in /etc/ifconfig.bridge0.
> > Im working with xl framework. 
> > I created NetBSD and FreeBSD virtual machines, the relevant portion of
> > configuration file is show bellow:
> > vif = [ 'bridge=bridge0, type=ioemu, model=e1000' ]
> > In both virtual machines, I see the network card, but when I configure
> > an ip address, I can't communicate with my network. 
> > When I type brconfig -a, I have these results show bellow: 
> > bridge0: flags=41<UP,RUNNING>
> >         Configuration:
> >                 priority 32768 hellotime 2 fwddelay 15 maxage 20
> >                 ipfilter disabled flags 0x0
> >         Interfaces:
> >                 xvif2i0 flags=3<LEARNING,DISCOVER>
> >                         port 5 priority 128
> >                 tap0 flags=3<LEARNING,DISCOVER>
> >                         port 4 priority 128
> >                 bce0 flags=3<LEARNING,DISCOVER>
> >                         port 1 priority 128
> > Everything appears to be normal, but I still don't have communication
> > with my network from my Vms. What Am I doing wrong?
> are xvif2i0 and tap0 up ?
> what does
> ifconfig bce0
> report ?
> You could also try running tcpdump on these interfaces (not on the bridge
> itself, this won't work) and see how packets are going in and out.

Here is my ifconfig -a output:

        address: 00:18:8b:e1:67:47
        media: Ethernet autoselect (100baseTX
        status: active
        inet netmask 0xffffff00 broadcast
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
        inet netmask 0xff000000
bridge0: flags=41<UP,RUNNING> mtu 1500
        address: f2:0b:a4:fe:b1:01
        media: Ethernet autoselect
mtu 1500
        address: 00:16:3e:3b:8a:4f

And, sending my qemu-dm-freebsd-source.log too:

domid: 3
ifconfig: not found
-videoram option does not work with cirrus vga device model. Videoram
set to 4M.
Using xvda for guest's hda
Using file /xen/domains/freebsd-source/freebsd-source.img in read-write
Using xvdb for guest's hdb
Using file /mnt/isos/freebsd-9.1-i386.iso in read-only mode
Watching /local/domain/0/device-model/3/logdirty/cmd
Watching /local/domain/0/device-model/3/command
Watching /local/domain/3/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 6bc9263e-b6fa-e211-852a-00188be16747
xen be core: xen be core: can't open gnttab device
can't open gnttab device
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
xs_read(): vncpasswd get
error. /vm/6bc9263e-b6fa-e211-852a-00188be16747/vncpasswd.
Using xvdb for guest's hdb
medium change watch on `xvdb' (index: 1): /mnt/isos/freebsd-9.1-i386.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/3/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/3/log-throttling'
medium change watch on `/local/domain/3/log-throttling' - unknown
device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro

tap0 and xvif3i0 appears only when I start my VM.

Adiel de Lima Ribeiro

Home | Main Index | Thread Index | Old Index