On 11/18/2015 01:48 AM, Olaf Hering wrote:
Likely a bug in grub2. Bug #955493 will track this. I dont have an EFI
capable system at hand, so cant help much with the issue.
Grub-related, it seems. Missing/incorrectly populated `startup.nsh` is
the problem. Details at bug, with manual workaround.
But, AFTER the manual workaround, on system boot, network's down -- no
xen bridge -- and there appears to be a launch problem with xen init:
With the aformentioned edit/repair to `startup.nsh`, I can reliably boot
the machine.
But, network, as mentioned, is offline.
After boot, the physical interfaces exist
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 68:1c:a2:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 68:1c:a2:XX:XX:XY brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 0c:c4:7a:XX:XX:XZ brd ff:ff:ff:ff:ff:ff
There's no longer any xen bridge, or properly-named eth interface, here eno1
cat /etc/sysconfig/network/ifcfg-br0
NAME='br0'
BRIDGE='yes'
BRIDGE_PORTS='eno1'
STARTMODE='auto'
BOOTPROTO='static'
BRIDGE_STP='off'
BRIDGE_FORWARDDELAY='0'
BRIDGE_AGEINGTIME='0'
IPADDR0='XX.XX.XX.2/22'
ETHTOOL_OPTIONS=''
MTU='1500'
NETWORK=''
BROADCAST=''
REMOTE_IPADDR=''
USERCONTROL='no'
POST_UP_SCRIPT=/etc/sysconfig/network/scripts/br0-config.sh
cat /etc/sysconfig/network/scripts/br0-config.sh
#!/bin/sh
ethtool -K br0 tso off gso off
ethtool -K eno1 tso off gso off
cat /etc/sysconfig/network/ifcfg-eno1
STARTMODE='auto'
BOOTPROTO='none'
only
ifconfig
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:65536 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:980 (980.0 b) TX bytes:980 (980.0 b)
a try at manual ifup also fails
ifup br0
wicked: ifcfg-br0: unable to qualify post-up script - unknown script
type '(null):/etc/sysconfig/network/scripts/br0-config.sh'
`dmesg` reports no obvious network errors,
dmesg | egrep -i "eth|br0|eno"
[ 6.789845] Initialising virtual ethernet driver.
[ 6.954169] FUJITSU Extended Socket Network Device Driver - version
1.0 - Copyright (c) 2015 FUJITSU LIMITED
[ 7.030614] e1000e: Intel(R) PRO/1000 Network Driver -
3.2.6-k
[ 7.203574] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 7.204301] r8169 0000:0a:00.0 eth0: RTL8168evl/8111evl at
0xffffc9000006a000, 68:1c:a2:XX:XX:XX, XID 0c900800 IRQ 60
[ 7.204303] r8169 0000:0a:00.0 eth0: jumbo features [frames: 9200
bytes, tx checksumming: ko]
[ 7.204339] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 7.205000] r8169 0000:0b:00.0 eth1: RTL8168evl/8111evl at
0xffffc9000006c000, 68:1c:a2:XX:XX:XY, XID 0c900800 IRQ 61
[ 7.205002] r8169 0000:0b:00.0 eth1: jumbo features [frames: 9200
bytes, tx checksumming: ko]
[ 7.214583] igb: Intel(R) Gigabit Ethernet Network Driver - version
5.3.0-k
[ 7.324135] igb 0000:10:00.0: added PHC on eth2
[ 7.324136] igb 0000:10:00.0: Intel(R) Gigabit Ethernet Network
Connection
[ 7.324138] igb 0000:10:00.0: eth2: (PCIe:2.5Gb/s:Width x1)
0c:c4:7a:XX:XX:XZ
[ 7.324204] igb 0000:10:00.0: eth2: PBA No: 011A00-000
[ 7.576496] e1000e 0000:00:19.0 eth3: registered PHC clock
[ 7.576499] e1000e 0000:00:19.0 eth3: (PCI Express:2.5GT/s:Width
x1) 0c:c4:7a:XX:XX:XW
[ 7.576500] e1000e 0000:00:19.0 eth3: Intel(R) PRO/1000 Network
Connection
[ 7.576556] e1000e 0000:00:19.0 eth3: MAC: 11, PHY: 12, PBA No:
0110FF-0FF
[ 17.948864] e1000e 0000:00:19.0 rename5: renamed from eth3
[ 17.999474] igb 0000:10:00.0 eth3: renamed from eth2
[ 18.049069] e1000e 0000:00:19.0 eth2: renamed from rename5
[ 169.255750] igb 0000:10:00.0: removed PHC on eth3
Taking a look at console output, there a problem with xen init
...
[ 23.759860] xen:evtchn: Event-channel device installed
[ 23.821839] No iBFT detected.
[ 24.009822] usbcore: registered new interface driver usbback
[ 24.015940] pciback: backend is vpci
[ 24.024580] blktap_device_init: blktap device major 252
[ 24.024583] blktap_ring_init: blktap ring major: 243
[ 24.037250] systemd[1]: Received SIGRTMIN+21 from PID 447
(plymouthd).
[ 77.512048] systemd[1]: systemd-journald.service watchdog timeout!
[ 114.500062] systemd[1]: xenstored.service start operation timed out.
Terminating.
[ 114.500207] systemd[1]: Failed to start The Xen xenstore.
[ 114.500217] systemd[1]: Dependency failed for xencommons.
[ 114.500229] systemd[1]: Dependency failed for qemu for xen dom0 disk
backend.
[ 114.500235] systemd[1]: Dependency failed for xen-init-dom0,
initialise Dom0 configuration (xenstore nodes, JSON configuration stub).
[ 114.500242] systemd[1]: Dependency failed for Xenconsoled - handles
logging from guest consoles and hypervisor.
[ 114.500248] systemd[1]: Dependency failed for Xendomains - start and
stop guests on boot and shutdown.
[ 114.500265] systemd[1]: Unit xenstored.service entered failed state.
[ 114.500616] systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such
file or directory.
[ 114.500716] systemd[1]: Mounted Mount /proc/xen files.
[ 114.500727] systemd[1]: Starting The Xen xenstore...
[ 137.500071] systemd[1]: [email protected] holdoff time over,
scheduling restart.
[ 137.500350] systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such
file or directory.
[ 137.500443] systemd[1]: Stopping Serial Getty on xvc0...
[ 137.500509] systemd[1]: Starting Serial Getty on xvc0...
[ 137.501048] systemd[1]: Started Serial Getty on xvc0.
[ 167.750050] systemd[1]: systemd-journald.service stop-sigterm timed
out. Killing.
[ 167.750567] systemd[1]: systemd-journald.service: main process
exited, code=killed, status=9/KILL
[ 167.750701] systemd[1]: Unit systemd-journald.service entered failed
state.
[ 167.750771] systemd[1]: systemd-journald.service has no holdoff
time, scheduling restart.
[ 167.750817] systemd[1]: Stopping Journal Service...
[ 167.750843] systemd[1]: Starting Journal Service...
[ 167.823905] systemd-journald[1493]: File
/var/log/journal/ff2dfa896235475385422eea2cb7fe4b/system.journal
corrupted or uncleanly shut down, renaming and replacing.
[ 168.840182] systemd-journald[1493]: Failed to open runtime journal:
Device or resource busy
[ 169.104166] systemd[1]: Started Journal Service.
[ 169.253804] Unable to read sysrq code in control/sysrq
[ 169.255750] igb 0000:10:00.0: removed PHC on eth3
[ 169.264906] pciback 0000:10:00.0: seizing device
[ 169.328047] systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such
file or directory.
[ 170.224153] systemd-journald[1493]: Received request to flush
runtime journal from PID 1
[ 172.004051] systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such
file or directory.
xl list
Name ID Mem VCPUs State
Time(s)
(null) 0 2988 1 r-----
35.0
ps ax | grep -i xen
14 ? S 0:00 [xenwatch]
15 ? S 0:00 [xenbus]
1451 ? S< 0:00 [xen_pciback_wor]
1483 ? Ss 0:00 /usr/sbin/xenstored --no-fork
3310 xvc0 R+ 0:00 grep --color=auto -i xen
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
