API tools faq
paste
Advertisement
Guest User

weird boot order

a guest
Mar 21st, 2013
63
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.04 KB | None | 0 0
raw download clone embed print report
  1. dmesg output...interpreted as I believe, beware not know...
  2.  
  3. Now I look at dmesg and believe to see what I tried to describe:
  4. ...
  5. [ 12.911519] openvswitch: Open vSwitch switching datapath 1.10.0, <<openvswitch starts here
  6. [ 12.961889] init: libvirt-bin main process (1420) terminated with status 6 <<I guess libvirt tries to start here but can not tap in the virtual network plugs since the network has not even finished booting
  7. [ 12.961918] init: libvirt-bin main process ended, respawning
  8. [ 12.980319] init: libvirt-bin main process (1457) terminated with status 6
  9. [ 12.980353] init: libvirt-bin main process ended, respawning
  10. [ 12.998478] init: libvirt-bin main process (1473) terminated with status 6
  11. [ 12.998506] init: libvirt-bin main process ended, respawning
  12. [ 13.019997] init: libvirt-bin main process (1490) terminated with status 6
  13. [ 13.020025] init: libvirt-bin main process ended, respawning
  14. [ 13.039021] init: libvirt-bin main process (1506) terminated with status 6
  15. [ 13.039057] init: libvirt-bin main process ended, respawning
  16. [ 13.057364] init: libvirt-bin main process (1535) terminated with status 6
  17. [ 13.057399] init: libvirt-bin main process ended, respawning
  18. [ 13.074709] init: libvirt-bin main process (1551) terminated with status 6
  19. [ 13.074743] init: libvirt-bin main process ended, respawning
  20. [ 13.092467] init: libvirt-bin main process (1567) terminated with status 6
  21. [ 13.092502] init: libvirt-bin main process ended, respawning
  22. [ 13.111538] init: libvirt-bin main process (1587) terminated with status 6
  23. [ 13.111567] init: libvirt-bin main process ended, respawning
  24. [ 13.130578] init: libvirt-bin main process (1613) terminated with status 6
  25. [ 13.130605] init: libvirt-bin main process ended, respawning << well it gives up here
  26. [ 13.131653] device ovs-system entered promiscuous mode << now ovs can boot, since it got resources
  27. [ 13.135076] device ovsbr0 entered promiscuous mode
  28. [ 13.151577] device eth0 entered promiscuous mode
  29. [ 13.151768] device eth1 entered promiscuous mode
  30. [ 13.155033] device bond0 entered promiscuous mode
  31. [ 13.157097] init: libvirt-bin main process (1667) terminated with status 6
  32. [ 13.157135] init: libvirt-bin respawning too fast, stopped
  33. [ 13.224100] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  34. [ 13.226401] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
  35. [ 13.248288] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
  36. [ 13.249102] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
  37. [ 13.374120] device ovsbr1 entered promiscuous mode
  38. [ 13.387922] device eth3 entered promiscuous mode
  39. [ 13.388543] device eth2 entered promiscuous mode
  40. [ 13.391113] device bond1 entered promiscuous mode
  41. [ 13.400233] r8169 0000:05:06.0: eth2: link down
  42. [ 13.400268] r8169 0000:05:06.0: eth2: link down
  43. [ 13.401210] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
  44. [ 13.541498] r8169 0000:07:00.0: eth3: link down
  45. [ 13.541537] r8169 0000:07:00.0: eth3: link down
  46. [ 13.542225] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
  47. [ 15.938765] r8169 0000:07:00.0: eth3: link up
  48. [ 15.939404] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
  49. [ 16.236743] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  50. [ 16.237547] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  51. [ 16.580684] r8169 0000:05:06.0: eth2: link up
  52. [ 16.581312] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready <<< I guess the open virtual switch finished here and now
  53. [ 29.010987] Bridge firewalling registered <<< here I start the libvirt-bin service manually from console...tip tip and voila it runs
  54. [ 29.030915] device virbr0-nic entered promiscuous mode
  55. [ 29.102636] ip_tables: (C) 2000-2006 Netfilter Core Team
  56. [ 29.172368] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  57. [ 29.195011] virbr0: topology change detected, propagating
  58. [ 29.195018] virbr0: port 1(virbr0-nic) entered forwarding state
  59. [ 29.195039] virbr0: port 1(virbr0-nic) entered forwarding state
  60. [ 29.204545] virbr0: port 1(virbr0-nic) entered disabled state
  61. [ 29.959122] ip6_tables: (C) 2000-2006 Netfilter Core Team
  62. [ 30.823071] device tap4 entered promiscuous mode
  63. [ 31.198194] device tap1 entered promiscuous mode
  64. [ 38.722021] kvm: 2624: cpu0 unhandled rdmsr: 0xc0010001
  65. [ 39.075797] kvm: 2643: cpu0 unhandled rdmsr: 0xc0010001
  66. [ 1148.661715] EXT4-fs (md126): Cannot change data mode on remount
  67. [ 1157.513447] EXT4-fs (md126): Cannot change data mode on remount
  68. [ 1191.700724] device tap4 left promiscuous mode
  69. [ 1194.298823] device tap1 left promiscuous mode
  70. [ 1263.492011] EXT4-fs (md126): Ignoring removed nobh option
  71. [ 1263.504644] EXT4-fs (md126): barriers disabled
  72. [ 1263.547396] EXT4-fs (md126): mounted filesystem with writeback data mode. Opts: data=writeback,barrier=0,nobh,errors=remount-ro
  73. [52896.962555] CE: hpet increased min_delta_ns to 20113 nsec
  74. [84416.311393] device tap4 entered promiscuous mode
  75. [84416.610739] device tap1 entered promiscuous mode
  76. [84424.078541] kvm: 6087: cpu0 unhandled rdmsr: 0xc0010001
  77. [84424.416958] kvm: 6105: cpu0 unhandled rdmsr: 0xc0010001
  78. ...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!