Thomas Karsten
2006-Jul-25 12:08 UTC
[Xen-users] Own network for domU, how to connect to dom0?
Dear all,
I would like to setup my domU''s to be in an own network. But when I do
this,
then I am unable to reach the domU''s from dom0 and vice versa. However,
I am
able to ping each domU from each domU. Here is the setup:
domU (eth0): 192.168.2.xxx/24
dom0 (eth0): 192.168.1.58/24
dom0 (dummy0): 192.168.2.1/24
(It works well, if the domU''s are also in 192.168.1.0/24.)
From this point on I am not sure what I can do to let the system send all the
packets going to 192.168.2.0 to the proper interfaces (vifx.0). I tried to
add the dummy device to the bridge xenbr0, but it did not help:
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.a22af5b58606 no vif0.0
peth0
dummy0
vif9.0
vif10.0
I also tried to add the dummy0 device to the routing table, but without
success:
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 dummy0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
The configuration of each domU is as follows (the IP address is different for
each domU):
domU120# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
domU120# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:16:3E:1C:AB:FF
inet addr:192.168.2.120 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe1c:abff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2323 (2.2 KiB) TX bytes:510 (510.0 b)
How can I manage reaching dom0 from the domU''s and vice versa? What am
I
doing wrong in the configuration? Do I have to change the networking scripts
of Xen, and if so, which one and how?
Thank you very much,
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Thomas Karsten
2006-Jul-26 09:49 UTC
Re: [Xen-users] Own network for domU, how to connect to dom0?
Hello,
I finally found a solution for my scenario. Actually it is very simple to
realise this configuration, just use the script
''network-bridge'' to create a
new bridge and to set the virtual device as required. In my example I use the
dummy device that is in a different network (192.168.2.0/24) than my physical
device (192.168.1.0/24):
# /etc/xen/scripts/network-bridge start vifnum=1 netdev=dummy0
# ...
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif1.0
xenbr1 8000.feffffffffff no vif0.1
pdummy0
vif2.0
Now each bridge is "responsible" for an own network. Since dom0 has
interfaces in both networks (eth0 in 192.168.1.0/24 and dummy0 in
192.168.2.0/24), I can access all domU''s in both networks from dom0 and
vice
versa. That''s what I wanted. I just have to take care to use the
correct
bridge and the correct network settings when creating a domU.
For those who are interested, the introduction in
http://wiki.xensource.com/xenwiki/XenNetworking helped me a lot to understand
Xen''s handling of the network interfaces much better.
Thanks,
Thomas
On Tuesday 25 July 2006 20:08, Thomas Karsten wrote:> Dear all,
>
> I would like to setup my domU''s to be in an own network. But when
I do this,
> then I am unable to reach the domU''s from dom0 and vice versa.
However, I am
> able to ping each domU from each domU. Here is the setup:
>
> domU (eth0): 192.168.2.xxx/24
> dom0 (eth0): 192.168.1.58/24
> dom0 (dummy0): 192.168.2.1/24
>
> (It works well, if the domU''s are also in 192.168.1.0/24.)
>
> From this point on I am not sure what I can do to let the system send all
the
> packets going to 192.168.2.0 to the proper interfaces (vifx.0). I tried to
> add the dummy device to the bridge xenbr0, but it did not help:
>
> # brctl show
> bridge name bridge id STP enabled interfaces
> xenbr0 8000.a22af5b58606 no vif0.0
> peth0
> dummy0
> vif9.0
> vif10.0
>
> I also tried to add the dummy0 device to the routing table, but without
> success:
>
> # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
Iface
> 192.168.2.0 * 255.255.255.0 U 0 0 0
dummy0
> 192.168.1.0 * 255.255.255.0 U 0 0 0
eth0
> default 192.168.1.1 0.0.0.0 UG 0 0 0
eth0
>
> The configuration of each domU is as follows (the IP address is different
for
> each domU):
>
> domU120# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
> 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0
eth0
>
> domU120# ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:16:3E:1C:AB:FF
> inet addr:192.168.2.120 Bcast:192.168.2.255 Mask:255.255.255.0
> inet6 addr: fe80::216:3eff:fe1c:abff/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:30 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2323 (2.2 KiB) TX bytes:510 (510.0 b)
>
> How can I manage reaching dom0 from the domU''s and vice versa?
What am I
> doing wrong in the configuration? Do I have to change the networking
scripts
> of Xen, and if so, which one and how?
>
> Thank you very much,
> Thomas
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, Am getting this error on trying to boot a guest domain over NFS . Are there any network settings that must be done ? I dont see /dev/nfs present on my system too. Thanks, Dakshina This is the log : Linux version 2.6.13-15f-xen (geeko@buildhost) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #1 SMP Wed Nov 16 14:01:46 UTC 2005 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000004000000 (usable) 0MB HIGHMEM available. 72MB LOWMEM available. ACPI in unprivileged domain disabled IRQ lockup detection disabled Built 1 zonelists Kernel command line: ip=129.158.239.225:129.158.239.223:::suse-xen:eth0:off root=/dev/nfs nfsroot=129.158.239.223:/dvdstore1 3 Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Xen reported: 1799.793 MHz processor. Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Software IO TLB disabled vmalloc area: c5000000-fb7fe000, maxmem 34000000 Memory: 59744k/73728k available (2360k kernel code, 5652k reserved, 828k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled Brought up 1 CPUs NET: Registered protocol family 16 xenbus_probe_init Brought up 1 CPUs ACPI: Subsystem revision 20050408 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. PCI: Using ACPI for IRQ routing PCI: If a device doesn''t work, try "pci=routeirq". If it helps, post a report PCI: System does not support PCI PCI: System does not support PCI TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca) Grant table initialized audit: initializing netlink socket (disabled) audit(1153930103.626:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API vesafb: abort, cannot ioremap video memory 0x0 @ 0x0 vesafb: probe of vesafb.0 failed with error -5 PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize loop: loaded (max 8 devices) Xen virtual console successfully installed as tty1 Event-channel device installed. Successfully initialized TPM backend driver. xen_net: Initialising virtual ethernet driver. xen_tpm_fr: Initialising the vTPM driver. mice: PS/2 mouse device common for all mice md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 3.38 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NET: Registered protocol family 1 NET: Registered protocol family 8 NET: Registered protocol family 20 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) ==============================My configuration file : # Kernel image file. kernel = "/boot/vmlinuz-xen" # Optional ramdisk. #ramdisk = "/boot/initrd-xen" # The domain build function. Default is ''linux''. #builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. memory = 64 # A name for your domain. All domains must have different names. name = "suse-dom" # Set the hostname. hostname = "suse-xen" ip = "129.158.239.225" # Set root device. root = "/dev/nfs" nfs_server=''129.158.239.223'' nfs_root="/dvdstore" # Sets runlevel 3. extra = "3" __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/26/06, dasari dakshina <dakshi80@yahoo.com> wrote:> Hello, > Am getting this error on trying to boot a guest domain > over NFS . > > Are there any network settings that must be done ? > [...]Did you enable kernel level IP autoconfiguration (CONFIG_IP_PNP) and nfs root file system (CONFIG_ROOT_NFS) Kernel features? To get them you need to build xen from source, the binaries and the default source config don''t have theses features. (don''t know if some distribution-specific packages have these features by default. Henning BTW: please don''t post full logfiles without being asked to do so. ( I wonder why everybody does this here - is there some info on subscribing that with each request one should post a full logfile?) In most cases, the last 10 lines would have been enough. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users