1. 09 May, 2014 9 commits
  2. 08 May, 2014 2 commits
    • Mike Hibler's avatar
      Add elabinelab role attributes for setting number of cores and amount of RAM. · d28d263a
      Mike Hibler authored
      XEN_CORES and XEN_MEMSIZE, which default to 1 and 1000 for backward compat.
      d28d263a
    • Mike Hibler's avatar
      Support for MBR v3 images in Xen VMs. · ef69e78a
      Mike Hibler authored
      If the Xen dom0 base image is properly (1M) aligned and the VM images
      are properly aligned as well, we should avoid or at least minimize any
      anomolous effects due to mismatches along the path involving the guest OS,
      guest disk layout, LVM LVs, LVM PVs, and the underlying physical disks.
      
      Also, random change to add a min size parameter to the findSpareDisks
      function. I was going to use this to avoid sucking up the little 3GB
      unused partition in MBR 3, but then decided against it.
      ef69e78a
  3. 07 May, 2014 4 commits
    • Mike Hibler's avatar
      Look for foo.sha1 before foo.ndz.sha1. · c1d1aa29
      Mike Hibler authored
      c1d1aa29
    • Mike Hibler's avatar
      Prepare for the coming of MBR version 3. · b4fdf8e0
      Mike Hibler authored
      Ironic. After all that hoo-haw about dynamically-created MBRs in the
      previous commit, we introduce a new hardcoded static MBR...
      
      Goals:
       * Single OS partition, in the fast area of rotating disks
       * Proper alignment for 4k sector drives and SSDs (1MB alignment)
       * Still works on 40GB disk (aka, pc850s)
       * P1 16 GiB: goldilocks FS: not too small (> 10GB), but not too big (< 30GB)
       * P2  3 GiB: can hold a co-loaded MBR 1 image (e.g., FBSD410 delay node OS)
       * P3  3 GiB: at least as much swap at currently (>= 1GB)
      
      The partition table:
        P1:     2048	33554432	FS, 16GiB
        P2: 33556480	 6291456	possible delay-node OS or additional swap, 3GiB
        P3: 39847936	 6291456	swap, 3GiB
        P4: 46139392	34278848+	extrafs, 16+GB
      
      The larger size and partition alignment are why I pushed this through despite
      my noble intentions.
      b4fdf8e0
    • Mike Hibler's avatar
      Introducing TMCD version 38! Returns additional "loadinfo" info. · 4a8604b1
      Mike Hibler authored
      New loadinfo returns:
      
      IMAGELOW, IMAGEHIGH: range of sectors covered by the image.
          This is NOT the same as what imageinfo or imagedump will show.
          For partition images, these low and high values are adjusted
          for the MBR offset of the partition in question. So when loading
          a Linux image, expect values like 6G and 12G. The intent here
          (not yet realized) is that these values will be used to construct
          an MBR/GPT on the fly, rather than using hardcode magic MBR versions.
          You can get the uncompressed size of the image with (high - low + 1).
      
      IMAGESSIZE: the units of the low/high values.
          Always 512 right now, may be 4096 someday.
      
      IMAGERELOC: non-zero if the image can be placed at an offset other
          than IMAGELOW (i.e., it can be relocated). This may or may not
          prove useful for dynamic MBR construction...we will see.
      
      Probably didn't need to bump the version here, but I am playing it safe.
      4a8604b1
    • Kirk Webb's avatar
      Merge branch 'pnet-www' · 75c8443a
      Kirk Webb authored
      75c8443a
  4. 06 May, 2014 23 commits
  5. 05 May, 2014 2 commits
    • Jonathon Duerig's avatar
      Really fix menu and whitespace bugs. · 010e3723
      Jonathon Duerig authored
      010e3723
    • Mike Hibler's avatar
      Fix the "dark magic" used to overwrite an existing partition. · 24cb6595
      Mike Hibler authored
      The old way worked...sorta. When we deleted the old partition and then
      recreated it with gpart, it would create the new one at the end of the
      disk, not likely where the old partition was previously.
      
      In elabinelab setup the combo:
      
         mkextrafs -s 2 ... /usr/testbed
         mkextrafs -s 4 ... /q
      
      resulted in slice 2 getting created at the end of the disk (where slice 4
      would normally be) and then slice 4 getting created in the only remaining
      available space (where slice 2 would normally be). Very confusing to my
      Monday morning brain...
      24cb6595