Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> I added the ability to boot from NFSroot, into the xen kernel.
>
> xm create VM1
>
> brctl show shows the virtual interface of the VM1 connected to the xenbr0.
>
> xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 3756 2 r-----
106.9
> VM1 53 256 1 -b----
0.1
>
> brctl show
> bridge name bridge id STP enabled interfaces
> xenbr0 8000.feffffffffff no vif0.0
> peth0
> vif53.0
>
>
> creates my PVM, and it tries to boot:
>
> Linux version 2.6.22.5-31-xen (geeko@buildhost) (gcc version 4.2.1 (SUSE
> Linux)) #1 SMP Wed Feb 13 13:09:35 CET 2008
> Command line:
> ip=192.168.102.204:192.168.102.41:192.168.102.1:255.255.254.0::eth0:off
> nfsroot=192.168.102.41:/export/bootimages/xenppmnode
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> end_pfn_map = 67584
> Zone PFN ranges:
> DMA 0 -> 67584
> DMA32 67584 -> 67584
> Normal 67584 -> 67584
> early_node_map[1] active PFN ranges
> 0: 0 -> 67584
> No mptable found.
> PERCPU: Allocating 24696 bytes of per cpu data
> Built 1 zonelists. Total pages: 66660
> Kernel command line:
> ip=192.168.102.204:192.168.102.41:192.168.102.1:255.255.254.0::eth0:off
> nfsroot=192.168.102.41:/export/bootimages/xenppmnode
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> ...
> and then later
> ...
> md: ... autorun DONE.
> Looking up port of RPC 100003/2 on 192.168.102.41
> rpcbind: server 192.168.102.41 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on 192.168.102.41
> rpcbind: server 192.168.102.41 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
>
>
> when I tcpdump -i vif53.0, then I see the network traffic from the
ordinary
> network is bridged up, e.g. broadcasts, stuff like that, but I do not see
> anything coming from the virtual machine, trying to connect to the NFS
> server. so no firewall is blocking, and forwarding is generally in place.
>
> Shouldn't I see some packets going from 192.168.102.204 to the NFS server?
> Am I missing an important part in my configuration?
>
>
> The dom0 is a opensuse 10.3 x86_64, xen-3.1.0.
>
OK, I figured out that I was missing the drivers for xennet in the kernel of
the domU. Adding these, the kernel was able to mount the NFS root. But short
after that, now it stops with the following:
mice: PS/2 mouse device common for all mice
dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
NET: Registered protocol family 1
xen-vbd: registered block device major 202
blkfront: xvda1: barriers enabled
blkfront: xvda2: barriers enabled
netfront: device eth0 has copying receive path.
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
IP-Config: Complete:
device=eth0, addr=192.168.102.204, mask=255.255.254.0,
gw=192.168.102.1,
host=192.168.102.204, domain=, nis-domain=(none),
bootserver=192.168.102.41, rootserver=192.168.102.41, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Looking up port of RPC 100003/2 on 192.168.102.41
Looking up port of RPC 100005/1 on 192.168.102.41
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 200k freed
and thats all, it seems to hang there forever. Any idea why it stops here?
kind regards
Sebastian
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home