Re: [Xen-users] network configuration on DomUs

[Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx>]

Please keep the list in CC if you want further help.
I'm no expert either and have not installed Windows in a VM yet.

You could start by providing the xen scripts for both your VMs ?

Maybe some XEN logs as well ?

Pierre

On Thu, Aug 28, 2014 at 4:19 PM, Hernan <bajopalabra@xxxxxxxxxxxx> wrote:

Hi Pierre
Thanks for your answer

In VM Arch, in the Network screen of Windows, I see just one interface: Xen driver

In the VM Sql, I see two cards for each bridge. Even when I set it to use only xenbr2, I see: "Xen driver" and "Realtek ..." interfaces

That is why I think there is a Xen problem, not because of Xen, but with the config script

By the other side, the person who write these scripts, no longer works with us. There was a shutdown of the powerline last week. Before that all worked. After that it began to fail. I think some configuration was hot-made, I mean volatile, not scripted. So, perhaps could there be more than one issue.

I don't where to begin. I tested almost everything. I've recently realize that there are some difference between versions. My Xen is 4.0.2

Another things are. When the server starts, it gives an error on screen "XENBUS can not read memory" - two lines. Also, before that, there is another error like "system don't have the required support to run KVM". But I checked out the BIOS, the hardware actually has that support for hypervisor, and it is enabled. It is an Ibm 3500.

That errors don't seem to be determinant. I don't know... Maybe one thing leads to another...

That's the whole scene

Where can I start to get it into work ?!

Thanks

Enviado desde mi BlackBerry de Movistar (http://www.movistar.com.ar)

---

From: Pierre Peyronnel <pierre.peyronnel@xxxxxxxxx>

Date: Thu, 28 Aug 2014 15:05:41 +0200

To: HernÃn Castelo<bajopalabra@xxxxxxxxxxxx>

Cc: xen-users@xxxxxxxxxxxxx<xen-users@xxxxxxxxxxxxx>

Subject: Re: [Xen-users] network configuration on DomUs

Hello Hernan,

i'm not sure this is a Xen problem.

By the looks of it, you refer to IPv4 addresses but your ifconfig (on dom0 i guess ?) shows IPv6 addresses for all NICs and bridges except for eth0 and lo where it is also has IPv4.

Your .14, .16, .17 are nowhere to be seen...

My bet would be on a IP and/or routing setup issue. You should check these on SQL VM, but again what makes you think it is Xen related ?

Pierre

On Mon, Aug 25, 2014 at 11:54 PM, HernÃn Castelo <bajopalabra@xxxxxxxxxxxx> wrote:

Hi

I'm very new with Xen (/Debian)

I have 2 VMs running Windows: "Arch" and "Sql" -- static IPs

VM Arch: is ok, accessible thru VNC, Remote Desktop, see the network, etc

VM Sql : - just accessible thru VNC

      - once I log in, I don't see the network

      - pings don't reach peer

      - appear 4 network ports on Windows

the server has 4 NIC cards

the first, eth0, is used just for the server, with IP 10.0.11.13

the VM Arch should use eth1, with IP ...14

and VM Sql should use eth2 with IP 16, and eth3 (as configured in SQLServer) with IP 17

please, guide me

I inherit this problem, and am far from being an expert...

THANKS IN ADVANCE!!

--------------------------------------------------------

root@USR03:~# route -n

Kernel IP routing table

Destination   Gateway     Genmask     Flags Metric Ref  ÂUse Iface

10.0.11.0 Â Â Â 0.0.0.0 Â Â Â Â 255.255.255.0 Â U Â Â 0 Â Â Â0 Â Â Â Â0 eth0

0.0.0.0 Â Â Â Â 10.0.11.1 Â Â Â 0.0.0.0 Â Â Â Â UG Â Â0 Â Â Â0 Â Â Â Â0 eth0

--------------------------------------------------------

root@USR03:~# brctl show

bridge name   bridge id        STP enabled   interfaces

eth0      Â8000.001b21d81f20    no       Âpeth0

xenbr1     Â8000.001b21d81f21    no       Âeth1

                            vif4.0

xenbr2     Â8000.5cf3fc573b8c    no       Âeth2

                            tap12.0

                            tap12.1

                            vif12.0

                            vif12.1

xenbr3     Â8000.5cf3fc573b8e    no       Âeth3

--------------------------------------------------------

root@USR03:~# ip route show

10.0.11.0/24 dev eth0 Âproto kernel Âscope link Âsrc 10.0.11.13

default via 10.0.11.1 dev eth0

--------------------------------------------------------

root@USR03:~# ifconfig

eth0 Â Â ÂLink encap:Ethernet ÂHWaddr 00:1b:21:d8:1f:20

     inet addr:10.0.11.13 ÂBcast:10.0.11.255 ÂMask:255.255.255.0

     inet6 addr: fe80::21b:21ff:fed8:1f20/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:159619 errors:0 dropped:0 overruns:0 frame:0

     TX packets:140984 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:0

     RX bytes:8613734 (8.2 MiB) ÂTX bytes:159007702 (151.6 MiB)

eth1 Â Â ÂLink encap:Ethernet ÂHWaddr 00:1b:21:d8:1f:21

     inet6 addr: fe80::21b:21ff:fed8:1f21/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:37442 errors:0 dropped:0 overruns:0 frame:0

     TX packets:4910 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:1000

     RX bytes:4607800 (4.3 MiB) ÂTX bytes:1810201 (1.7 MiB)

     Memory:97a00000-97a80000

eth2 Â Â ÂLink encap:Ethernet ÂHWaddr 5c:f3:fc:57:3b:8c

     inet6 addr: fe80::5ef3:fcff:fe57:3b8c/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:33055 errors:0 dropped:0 overruns:0 frame:0

     TX packets:852 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:1000

     RX bytes:3446328 (3.2 MiB) ÂTX bytes:79882 (78.0 KiB)

     Interrupt:28 Memory:92000000-92012800

eth3 Â Â ÂLink encap:Ethernet ÂHWaddr 5c:f3:fc:57:3b:8e

     inet6 addr: fe80::5ef3:fcff:fe57:3b8e/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:69385 errors:0 dropped:0 overruns:0 frame:0

     TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:1000

     RX bytes:5844752 (5.5 MiB) ÂTX bytes:1132 (1.1 KiB)

     Interrupt:40 Memory:94000000-94012800

lo    ÂLink encap:Local Loopback

     inet addr:127.0.0.1 ÂMask:255.0.0.0

     inet6 addr: ::1/128 Scope:Host

     UP LOOPBACK RUNNING ÂMTU:16436 ÂMetric:1

     RX packets:146 errors:0 dropped:0 overruns:0 frame:0

     TX packets:146 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:0

     RX bytes:14416 (14.0 KiB) ÂTX bytes:14416 (14.0 KiB)

peth0 Â Â Link encap:Ethernet ÂHWaddr 00:1b:21:d8:1f:20

     inet6 addr: fe80::21b:21ff:fed8:1f20/64 Scope:Link

     UP BROADCAST RUNNING PROMISC MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:186596 errors:0 dropped:0 overruns:0 frame:0

     TX packets:204370 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:1000

     RX bytes:12723915 (12.1 MiB) ÂTX bytes:162430818 (154.9 MiB)

     Memory:97a80000-97b00000

tap12.0 Â Link encap:Ethernet ÂHWaddr d6:fe:ff:61:dd:ce

     inet6 addr: fe80::d4fe:ffff:fe61:ddce/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:38 errors:0 dropped:0 overruns:0 frame:0

     TX packets:9156 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:500

     RX bytes:3592 (3.5 KiB) ÂTX bytes:1003894 (980.3 KiB)

tap12.1 Â Link encap:Ethernet ÂHWaddr 8e:01:08:6d:39:7c

     inet6 addr: fe80::8c01:8ff:fe6d:397c/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:0 errors:0 dropped:0 overruns:0 frame:0

     TX packets:9194 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:500

     RX bytes:0 (0.0 B) ÂTX bytes:1007462 (983.8 KiB)

vif12.0 Â Link encap:Ethernet ÂHWaddr fe:ff:ff:ff:ff:ff

     inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

     UP BROADCAST RUNNING PROMISC MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:0 errors:0 dropped:0 overruns:0 frame:0

     TX packets:0 errors:0 dropped:9194 overruns:0 carrier:0

     collisions:0 txqueuelen:32

     RX bytes:0 (0.0 B) ÂTX bytes:0 (0.0 B)

vif12.1 Â Link encap:Ethernet ÂHWaddr fe:ff:ff:ff:ff:ff

     inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

     UP BROADCAST RUNNING PROMISC MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:0 errors:0 dropped:0 overruns:0 frame:0

     TX packets:237 errors:0 dropped:6884 overruns:0 carrier:0

     collisions:0 txqueuelen:32

     RX bytes:0 (0.0 B) ÂTX bytes:22480 (21.9 KiB)

vif4.0 Â ÂLink encap:Ethernet ÂHWaddr fe:ff:ff:ff:ff:ff

     inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

     UP BROADCAST RUNNING PROMISC MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:3418 errors:0 dropped:0 overruns:0 frame:0

     TX packets:26435 errors:0 dropped:2009 overruns:0 carrier:0

     collisions:0 txqueuelen:32

     RX bytes:1359883 (1.2 MiB) ÂTX bytes:3064684 (2.9 MiB)

xenbr1 Â ÂLink encap:Ethernet ÂHWaddr 00:1b:21:d8:1f:21

     inet6 addr: fe80::21b:21ff:fed8:1f21/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:26594 errors:0 dropped:0 overruns:0 frame:0

     TX packets:17 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:0

     RX bytes:2552297 (2.4 MiB) ÂTX bytes:930 (930.0 B)

xenbr2 Â ÂLink encap:Ethernet ÂHWaddr 5c:f3:fc:57:3b:8c

     inet6 addr: fe80::5ef3:fcff:fe57:3b8c/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:26513 errors:0 dropped:0 overruns:0 frame:0

     TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:0

     RX bytes:2547392 (2.4 MiB) ÂTX bytes:888 (888.0 B)

xenbr3 Â ÂLink encap:Ethernet ÂHWaddr 5c:f3:fc:57:3b:8e

     inet6 addr: fe80::5ef3:fcff:fe57:3b8e/64 Scope:Link

     UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1

     RX packets:69343 errors:0 dropped:0 overruns:0 frame:0

     TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

     collisions:0 txqueuelen:0

     RX bytes:4529117 (4.3 MiB) ÂTX bytes:888 (888.0 B)

--------------------------------------------------------

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users