LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud
User Name
Password
Linux - Virtualization and Cloud This forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.

Notices


Reply
  Search this Thread
Old 11-23-2017, 08:47 PM   #1
PeterSchueler
LQ Newbie
 
Registered: Nov 2017
Location: Hannover, Germany
Distribution: debian (+ fedora + ubuntu)
Posts: 1

Rep: Reputation: Disabled
No network for bridged Windows HVM on debian 9 + xen 4.8


Hi experts,

(sorry in advance for this lengthy input)

My host juergen with debian 9.1 and xen 4.8.1 has working LAN and internet access.
On an older setup of ubuntu and xen-3.1 on the same MB, everything has been working smoothly, but after a harddisk failure I had to setup everything anew, and now Windows-HVMs lack LAN support. Hopefully, somebody can drop me a hint to explain.

One Example (I tried several VMs): bridged Windows-HVM w8.1e64 (Windows 8.1, 64-bit) is running but reaches no network (except vnc). Windows reports: not connected to any network; according to Wireshark run on the host, packets from the VM get through to vif3.0-emu and to the bridge. ARP-requests ("who has...") get even through to the gateway and are answered, but these answers do not pass the bridge back to th VM. Other packets, e.g.:ICMP, don't even get this far.

On the host, network-manager is disabled (was enabled by default, but to no success). I have assigned appropriate mac and ipv4 addresses to the VM and also to xenbr0.
In Windows, standard gateway is given as 192.168.8.1 (defining the host-address 192.168.8.14 makes no difference). NIC (RTL 8139C+ as NIC #2) is reported by Windows to be running flawlessly. I am puzzled by the fact that my choice of ipv4-address is honored in xenstore, but not in ifconfig. In ifconfig, I see ipv6-addresses for vifx.0-emu, but not for vifx.0. No idea where this is declared. vifx.0 remains untouched endlessly.

Could PLEASE anybody enlighten me?

Here ist whatever info I can imagine as being relevant:

w81e64.cfg:
[..]
builder = 'hvm'
memory = 2560
xen_platform_pci=1
shadow_memory = 16
name = 'w8.1e64'
vif = [ 'type=ioemu, gatewaydev=xenbr0, bridge=xenbr0, ip=192.168.8.31, mac=00:16:3e:72:06:ae, script=vif-bridge' ]
[..]


ifconfig:
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether bc:5f:f4:08:d7:21 txqueuelen 1000 (Ethernet)
RX packets 1286534 bytes 512500041 (488.7 MiB)
RX errors 3 dropped 0 overruns 0 frame 3
TX packets 398608 bytes 32794133 (31.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 822

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Lokale Schleife)
RX packets 78968 bytes 209057662 (199.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 78968 bytes 209057662 (199.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vif3.0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:16:3e:72:06:ae txqueuelen 32 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vif3.0-emu: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::216:3eff:fe72:6ae prefixlen 64 scopeid 0x20<link>
ether 00:16:3e:72:06:ae txqueuelen 1000 (Ethernet)
RX packets 5332 bytes 473839 (462.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1218071 bytes 408552774 (389.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

xenbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.14 netmask 255.255.255.255 broadcast 192.168.8.255
inet6 fe80::be5f:f4ff:fe08:d723 prefixlen 64 scopeid 0x20<link>
ether bc:5f:f4:08:d7:23 txqueuelen 1000 (Ethernet)
RX packets 308111 bytes 42324046 (40.3 MiB)
RX errors 0 dropped 794 overruns 0 frame 0
TX packets 391187 bytes 32085371 (30.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


brctl show:
bridge name bridge id STP enabled interfaces
xenbr0 8000.bc5ff408d723 no enp10s0
vif3.0
vif3.0-emu

(I also tried stp on, no difference)


ip route list table all:
default via 192.168.8.1 dev xenbr0 onlink
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
local 192.168.8.14 dev xenbr0 table local proto kernel scope host src 192.168.8.14
broadcast 192.168.8.255 dev xenbr0 table local proto kernel scope link src 192.168.8.14
fe80::/64 dev xenbr0 proto kernel metric 256 pref medium
fe80::/64 dev vif3.0-emu proto kernel metric 256 pref medium
unreachable default dev lo proto kernel metric 4294967295 error -101 pref medium
local ::1 dev lo table local proto none metric 0 pref medium
local fe80:: dev lo table local proto none metric 0 pref medium
local fe80:: dev lo table local proto none metric 0 pref medium
local fe80::216:3eff:fe72:6ae dev lo table local proto none metric 0 pref medium
local fe80::be5f:f4ff:fe08:d723 dev lo table local proto none metric 0 pref medium
ff00::/8 dev xenbr0 table local metric 256 pref medium
ff00::/8 dev vif3.0-emu table local metric 256 pref medium
unreachable default dev lo proto kernel metric 4294967295 error -101 pref medium


/etc/network/interfaces:
[..]
# The loopback network interface
auto lo
iface lo inet loopback

# auto dummy0
# iface dummy0 inet manual
# address 192.168.8.14
# pre-up ifconfig $IFACE up
# post-down ifconfig $IFACE down

auto enp10s0
iface enp10s0 inet manual

auto xenbr0
iface xenbr0 inet static
bridge_fd 0
bridge_maxage 0
bridge_ageing 0
bridge maxwait 0
address 192.168.8.14
netmask 255.255.255.255
network 192.168.8.0
broadcast 192.168.8.255
gateway 192.168.8.1
dns-nameserver 192.168.8.1
bridge_ports enp10s0
post-up ip link set xenbr0 address bc:5f:f4:08:d7:23


xl network-list w8.1e64:
Idx BE Mac Addr. handle state evt-ch tx-/rx-ring-ref BE-path
0 0 00:16:3e:72:06:ae 0 1 -1 -1/-1 /local/domain/0/backend/vif/3/0


iptables -L:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0-emu --physdev-is-bridged
ACCEPT all -- 192.168.8.31 anywhere PHYSDEV match --physdev-in vif3.0-emu --physdev-is-bridged
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0-emu --physdev-is-bridged
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif3.0-emu --physdev-is-bridged udp spt:bootpc dpt:bootps
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0-emu --physdev-is-bridged
ACCEPT all -- 192.168.8.31 anywhere PHYSDEV match --physdev-in vif3.0-emu --physdev-is-bridged
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0 --physdev-is-bridged
ACCEPT all -- 192.168.8.31 anywhere PHYSDEV match --physdev-in vif3.0 --physdev-is-bridged
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0 --physdev-is-bridged
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif3.0 --physdev-is-bridged udp spt:bootpc dpt:bootps
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0 --physdev-is-bridged
ACCEPT all -- 192.168.8.31 anywhere PHYSDEV match --physdev-in vif3.0 --physdev-is-bridged

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


/var/log/messages:
[..]
Nov 21 23:21:50 juergen kernel: [ 2727.590615] xenbr0: port 2(vif3.0) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.590617] xenbr0: port 2(vif3.0) entered disabled state
Nov 21 23:21:50 juergen kernel: [ 2727.590699] device vif3.0 entered promiscuous mode
Nov 21 23:21:50 juergen kernel: [ 2727.592074] IPv6: ADDRCONF(NETDEV_UP): vif3.0: link is not ready
Nov 21 23:21:50 juergen kernel: [ 2727.678014] xenbr0: port 3(vif3.0-emu) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.678016] xenbr0: port 3(vif3.0-emu) entered disabled state
Nov 21 23:21:50 juergen kernel: [ 2727.678070] device vif3.0-emu entered promiscuous mode
Nov 21 23:21:50 juergen kernel: [ 2727.679499] xenbr0: port 3(vif3.0-emu) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.679501] xenbr0: port 3(vif3.0-emu) entered forwarding state
[..]


/var/log/syslog:
[..]Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/3/51712
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/node /dev/loop0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/physical-device 7:0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/physical-device-path /dev/loop0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/hotplug-status connected to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/3/0
Nov 21 23:21:50 juergen kernel: [ 2727.590615] xenbr0: port 2(vif3.0) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.590617] xenbr0: port 2(vif3.0) entered disabled state
Nov 21 23:21:50 juergen kernel: [ 2727.590699] device vif3.0 entered promiscuous mode
Nov 21 23:21:50 juergen kernel: [ 2727.592074] IPv6: ADDRCONF(NETDEV_UP): vif3.0: link is not ready
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif3.0, bridge xenbr0.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Writing backend/vif/3/0/hotplug-status connected to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/3/0
Nov 21 23:21:50 juergen kernel: [ 2727.678014] xenbr0: port 3(vif3.0-emu) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.678016] xenbr0: port 3(vif3.0-emu) entered disabled state
Nov 21 23:21:50 juergen kernel: [ 2727.678070] device vif3.0-emu entered promiscuous mode
Nov 21 23:21:50 juergen kernel: [ 2727.679499] xenbr0: port 3(vif3.0-emu) entered blocking state
Nov 21 23:21:50 juergen kernel: [ 2727.679501] xenbr0: port 3(vif3.0-emu) entered forwarding state
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif3.0-emu, bridge xenbr0.
[..]


/var/log/debug:
[..]
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/3/51712
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/node /dev/loop0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/physical-device 7:0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/physical-device-path /dev/loop0 to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/block: Writing backend/vbd/3/51712/hotplug-status connected to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/3/0
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif3.0, bridge xenbr0.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Writing backend/vif/3/0/hotplug-status connected to xenstore.
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/3/0
Nov 21 23:21:50 juergen peter: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif3.0-emu, bridge xenbr0.
[..]


xenstore-ls:
tool = ""
xenstored = ""
local = ""
domain = ""
0 = ""
control = ""
feature-poweroff = "1"
feature-reboot = "1"
feature-suspend = "1"
domid = "0"
name = "Domain-0"
device-model = ""
0 = ""
backends = ""
console = ""
vkbd = ""
qdisk = ""
qusb = ""
vfb = ""
qnic = ""
state = "running"
3 = ""
backends = ""
console = ""
vkbd = ""
qdisk = ""
qusb = ""
state = "running"
physmap = ""
9f800000 = ""
start_addr = "f0000000"
size = "800000"
name = "vga.vram"
memory = ""
target = "30176000"
static-max = "17179869180"
backend = ""
vbd = ""
3 = ""
51712 = ""
frontend = "/local/domain/3/device/vbd/51712"
params = "/home/peter/xenimages/w8.1e64.img"
script = "/etc/xen/scripts/block"
frontend-id = "3"
online = "1"
removable = "0"
bootable = "1"
state = "2"
dev = "xvda"
type = "phy"
mode = "w"
device-type = "disk"
discard-enable = "1"
feature-max-indirect-segments = "256"
multi-queue-max-queues = "8"
max-ring-page-order = "4"
node = "/dev/loop0"
physical-device = "7:0"
physical-device-path = "/dev/loop0"
hotplug-status = "connected"
console = ""
3 = ""
0 = ""
frontend = "/local/domain/3/console"
frontend-id = "3"
online = "1"
state = "1"
protocol = "vt100"
vkbd = ""
3 = ""
0 = ""
frontend = "/local/domain/3/device/vkbd/0"
frontend-id = "3"
online = "1"
state = "2"
feature-abs-pointer = "1"
hotplug-status = "connected"
vif = ""
3 = ""
0 = ""
frontend = "/local/domain/3/device/vif/0"
frontend-id = "3"
online = "1"
state = "2"
script = "/etc/xen/scripts/vif-bridge"
mac = "00:16:3e:72:06:ae"
ip = "192.168.8.31"
gatewaydev = "xenbr0"
bridge = "xenbr0"
handle = "0"
type = "vif_ioemu"
feature-sg = "1"
feature-gso-tcpv4 = "1"
feature-gso-tcpv6 = "1"
feature-ipv6-csum-offload = "1"
feature-rx-copy = "1"
feature-rx-flip = "0"
feature-multicast-control = "1"
feature-dynamic-multicast-control = "1"
feature-split-event-channels = "1"
multi-queue-max-queues = "8"
feature-ctrl-ring = "1"
hotplug-status = "connected"
3 = ""
vm = "/vm/3f6a21c9-8b20-47e7-b441-455f54212d14"
name = "w8.1e64"
cpu = ""
0 = ""
availability = "online"
memory = ""
static-max = "2621440"
target = "2613248"
videoram = "8192"
device = ""
suspend = ""
event-channel = ""
vbd = ""
51712 = ""
backend = "/local/domain/0/backend/vbd/3/51712"
backend-id = "0"
state = "1"
virtual-device = "51712"
device-type = "disk"
vkbd = ""
0 = ""
backend = "/local/domain/0/backend/vkbd/3/0"
backend-id = "0"
state = "1"
vif = ""
0 = ""
backend = "/local/domain/0/backend/vif/3/0"
backend-id = "0"
state = "1"
handle = "0"
mac = "00:16:3e:72:06:ae"
control = ""
shutdown = ""
feature-poweroff = ""
feature-reboot = ""
feature-suspend = ""
feature-s3 = ""
feature-s4 = ""
platform-feature-multiprocessor-suspend = "1"
platform-feature-xs_reset_watches = "1"
hvmloader = ""
bios = "seabios"
allow-memory-relocate = "0"
data = ""
drivers = ""
feature = ""
attr = ""
domid = "3"
store = ""
port = "1"
ring-ref = "1044476"
platform = ""
acpi = "1"
acpi_s3 = "1"
acpi_s4 = "1"
console = ""
backend = "/local/domain/0/backend/console/3/0"
backend-id = "0"
limit = "1048576"
type = "xenconsoled"
output = "pty"
tty = "/dev/pts/4"
port = "2"
ring-ref = "1044479"
vnc-listen = "127.0.0.1"
vnc-port = "5900"
image = ""
device-model-pid = "5649"
serial = ""
0 = ""
tty = "/dev/pts/5"
vm = ""
00000000-0000-0000-0000-000000000000 = ""
memory = "29468"
3f6a21c9-8b20-47e7-b441-455f54212d14 = ""
name = "w8.1e64"
uuid = "3f6a21c9-8b20-47e7-b441-455f54212d14"
rtc = ""
timeoffset = ""
image = ""
ostype = "hvm"
start_time = "1511302910.37"
libxl = ""
3 = ""
device = ""
vbd = ""
51712 = ""
frontend = "/local/domain/3/device/vbd/51712"
backend = "/local/domain/0/backend/vbd/3/51712"
params = "/home/peter/xenimages/w8.1e64.img"
script = "/etc/xen/scripts/block"
frontend-id = "3"
online = "1"
removable = "0"
bootable = "1"
state = "1"
dev = "xvda"
type = "phy"
mode = "w"
device-type = "disk"
discard-enable = "1"
console = ""
0 = ""
frontend = "/local/domain/3/console"
backend = "/local/domain/0/backend/console/3/0"
frontend-id = "3"
online = "1"
state = "1"
protocol = "vt100"
vkbd = ""
0 = ""
frontend = "/local/domain/3/device/vkbd/0"
backend = "/local/domain/0/backend/vkbd/3/0"
frontend-id = "3"
online = "1"
state = "1"
vif = ""
0 = ""
frontend = "/local/domain/3/device/vif/0"
backend = "/local/domain/0/backend/vif/3/0"
frontend-id = "3"
online = "1"
state = "1"
script = "/etc/xen/scripts/vif-bridge"
mac = "00:16:3e:72:06:ae"
ip = "192.168.8.31"
gatewaydev = "xenbr0"
bridge = "xenbr0"
handle = "0"
type = "vif_ioemu"
dm-version = "qemu_xen"


ls /proc/sys/net/bridge:
0 bridge-nf-call-arptables 0 bridge-nf-filter-pppoe-tagged
0 bridge-nf-call-ip6tables 0 bridge-nf-filter-vlan-tagged
0 bridge-nf-call-iptables 0 bridge-nf-pass-vlan-input-dev


cat /proc/sys/net/ipv4/bridge/*:
0
0
0
0
0
0


additional info for the asking...

Greetings, Peter
 
Old Yesterday, 06:50 AM   #2
Hostech_Support
LQ Newbie
 
Registered: Oct 2017
Location: India
Posts: 13

Rep: Reputation: Disabled
Hello PeterSchueler,
Yes, as per your above information, if the settings are related to OS, then I would suggest you, reinstall the setup.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Xen Nest HVM Windows Host Archangelmscj Linux - Virtualization and Cloud 5 06-17-2016 06:29 AM
HVM vs PV (Xen Full virtualization (HVM) Xen Paravirtualization (PV)) Nemus Linux - Virtualization and Cloud 9 02-27-2016 11:07 AM
[SOLVED] Debian Win 2008 xen HVM starts but doesn't do anything, pulling hair out! scheidel21 Linux - Virtualization and Cloud 3 06-11-2010 12:21 PM
[SOLVED] Windows 2003 won't boot on XEN with HVM mr51m0n Linux - Server 2 06-11-2010 10:24 AM
LXer: Install Oracle 11g on HVM VM (CentOS 5) under Xen 3.1 on Debian Etch (x86_64) LXer Syndicated Linux News 0 09-12-2007 10:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Virtualization and Cloud

All times are GMT -5. The time now is 01:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration