Skip to content


Subversion checkout URL

You can clone with
Download ZIP

Comparing changes

Choose two branches to see what's changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: zli/buzzlogs-xcp
base: 1909cab8d3
head fork: zli/buzzlogs-xcp
compare: 2bcde604a8
Checking mergeability… Don't worry, you can still create the pull request.
  • 2 commits
  • 2 files changed
  • 0 commit comments
  • 1 contributor
Showing with 7 additions and 0 deletions.
  1. +5 −0 2012-06-17-irc.log
  2. +2 −0  2012-06-17-twt.log
5 2012-06-17-irc.log
@@ -0,0 +1,5 @@
+11:49:28 * CaCtus491 starts the 1.5 beta ISO mounted via IPMI on 4 machines......
+11:53:22 <CaCtus491> ...previously when testing on these machines, I was experiencing all sorts of weird with network bonding... If I configure a bond with active/active (with two interfaces, each going to a port on physically different, but logically one stackable switches), all would work well until I unplugged power to one switch, then reconnected it. I'd see packet loss until doing an ifconfig down / ifconfig up on one (both?) interfaces making up the b
+11:54:06 <CaCtus491> this time I'll try with 802.3ad even though it doesn't seem to be officially supported - perhaps I'll have more luck this way
+11:55:08 <CaCtus491> is it safe for me to assume that any non-standard config I do will persist across upgrades, provided I do them all with the xe command line tool?
+11:55:24 <CaCtus491> (ie, 802.3ad bonding and placing the management interface on a vlan)
2  2012-06-17-twt.log
@@ -0,0 +1,2 @@
+16:32:49 <bruntonspall> bitfield: It was an older ubuntu installation and they upgraded the xen hypervisor at LiNode, so I suspect the problem lies there somewhere | 214395183557656578
+22:38:08 <vorreicomprare> The Definitive Guide to the Xen Hypervisor | 214487117634605057

No commit comments for this range

Something went wrong with that request. Please try again.