OpenBSD Journal

Xen Support Enabled in -current

Contributed by jj on from the puffy-lawless-under-xen-warrior-hypervisor dept.

Those of you who have been following OpenBSD commits have no doubt noticed the recent work on supporting OpenBSD as a guest on the Xen hypervisor.

Mike Belopuhov (mikeb@) has just enabled that code in -current for the amd64 platform.

These are still early days, and no doubt a few bugs to find, but if you have any Xen architecture, now is time to take the S.S. Puffy on a shakedown cruise and sendbug(1) any issues you find.

(Comments are closed)

Comments

  1. By almeida (almeida) on

    Would this mean we could run OpenBSD on AWS at some point?

    Comments
    1. Comments

      1. By rc (160.83.30.199) on

        > > Would this mean we could run OpenBSD on AWS at some point?
        >
        > It means you can run OpenBSD on AWS at right now.

        where`s the build/iso to deploy ?
        (have no current system, but very interested in using it on xen asap)

        Comments

        1. By phessler (phessler) on http://www.openbsdfoundation.org/donations.html

          > > > Would this mean we could run OpenBSD on AWS at some point?
          > >
          > > It means you can run OpenBSD on AWS at right now.
          >
          > where`s the build/iso to deploy ?
          > (have no current system, but very interested in using it on xen asap)

          Any amd64 snapshot dated Jan 12 or later.

          Comments

          1. By Sydney Meyer (80.201.124.47) syd.meyer@gmail.com on

            > > > > Would this mean we could run OpenBSD on AWS at some point?
            > > >
            > > > It means you can run OpenBSD on AWS at right now.
            > >
            > > where`s the build/iso to deploy ?
            > > (have no current system, but very interested in using it on xen asap)
            >
            > Any amd64 snapshot dated Jan 12 or later.

            I tried this with a snapshot from today, but i get still the emulated re0 device. Anything special to know?

            Comments

            1. By Mike (62.224.106.115) on

              > > > > > Would this mean we could run OpenBSD on AWS at some point?
              > > > >
              > > > > It means you can run OpenBSD on AWS at right now.
              > > >
              > > > where`s the build/iso to deploy ?
              > > > (have no current system, but very interested in using it on xen asap)
              > >
              > > Any amd64 snapshot dated Jan 12 or later.
              >
              > I tried this with a snapshot from today, but i get still the emulated re0 device. Anything special to know?

              Apparently I didn't know what's the best practice here wrt. configuration.
              I've committed a change that will make Netfront driver (xnf) attach to
              all virtual NICs and knock off em's and re's, but for now you can add
              a "type=vif" into your vif conf string:

              vif = ['type=vif,mac=00:16:3e:43:25:6b']

              AWS defines type to "front" and we match those and attach to them.

              Cheers,
              Mike

              Comments

              1. By Anonymous Coward (87.67.136.229) on

                > > > > > > Would this mean we could run OpenBSD on AWS at some point?
                > > > > >
                > > > > > It means you can run OpenBSD on AWS at right now.
                > > > >
                > > > > where`s the build/iso to deploy ?
                > > > > (have no current system, but very interested in using it on xen asap)
                > > >
                > > > Any amd64 snapshot dated Jan 12 or later.
                > >
                > > I tried this with a snapshot from today, but i get still the emulated re0 device. Anything special to know?
                >
                > Apparently I didn't know what's the best practice here wrt. configuration.
                > I've committed a change that will make Netfront driver (xnf) attach to
                > all virtual NICs and knock off em's and re's, but for now you can add
                > a "type=vif" into your vif conf string:
                >
                > vif = ['type=vif,mac=00:16:3e:43:25:6b']
                >
                > AWS defines type to "front" and we match those and attach to them.
                >
                > Cheers,
                > Mike
                >

                Thanks, Mike.. defining the device type works indeed. Just today i had installed NetBSD as a virtual router on Xen, because FreeBSD's netfront has issues with routing packets. But i guess, i will replace NetBSD with this snapshot for now then. Again, thank you for letting the hell freeze over.

    2. By Anonymous Coward (110.38.246.59) on

      yes, You're right.

  2. By BSDfan (193.200.119.95) on

    Excellent :)
    There are any plans for support PVH DomU mode?

    Comments

    1. By Mike (62.224.106.115) on

      > Excellent :)
      > There are any plans for support PVH DomU mode?

      No plans so far.

  3. By Anonymous Coward (91.82.31.221) on

    As a guest.
    It should emphasize, that as a guest.
    As a guest.

    Comments

    1. By Anonymous Coward (62.224.106.115) on

      > As a guest.
      > It should emphasize, that as a guest.
      > As a guest.
      >

      perhaps the words "recent work on supporting OpenBSD as a guest on the Xen hypervisor" in the first sentence were not clear enough for you?

      Comments

      1. By Anonymous Coward (91.83.25.26) on

        > > As a guest.
        > > It should emphasize, that as a guest.
        > > As a guest.
        > >
        >
        > perhaps the words "recent work on supporting OpenBSD as a guest on the Xen hypervisor" in the first sentence were not clear enough for you?

        No, because missing from the title, eg. Not emphasized.

      2. By Janne Johansson (jj) on http://www.inet6.se

        > > As a guest.
        > > It should emphasize, that as a guest.
        > > As a guest.
        > >
        >
        > perhaps the words "recent work on supporting OpenBSD as a guest on the Xen hypervisor" in the first sentence were not clear enough for you?

        Nah, that means you have to read the whole article, which of course is the most common issue with undeadly, the very long winded texts.. 8-/

        Comments

        1. By Anonymous Coward (31.46.62.63) on

          > > > As a guest.
          > > > It should emphasize, that as a guest.
          > > > As a guest.
          > > >
          > >
          > > perhaps the words "recent work on supporting OpenBSD as a guest on the Xen hypervisor" in the first sentence were not clear enough for you?
          >
          > Nah, that means you have to read the whole article, which of course is the most common issue with undeadly, the very long winded texts.. 8-/
          >

          The point is that, i'd omit from the title the word "-current", and would write only in body, and would put in the title the words "as a guest".
          Because the latter is more important, more interesting, more essential, more fundemental than the former.
          The new things always appears in current or/and snapshots, so who cares in the title the word "-current"?

          Comments

          1. By Shane J Pearson (59.167.140.218) on

            > The point is that, i'd omit from the title the word "-current", and would write only in body, and would put in the title the words "as a guest".
            > Because the latter is more important, more interesting, more essential, more fundemental than the former.
            > The new things always appears in current or/and snapshots, so who cares in the title the word "-current"?

            It's in the very first line of the body! And the title is not technically inaccurate.

            What is significant here is Xen support, no matter the extent. If that title gets you excited, as it does me, then I'd think you'd want to read the body.

            Comments

            1. By Anonymous Coward (91.83.7.87) on

              I regreted bikesheding, flaming, sorry.









  4. By Keef (95.172.236.54) on

    I installed the latest Snapshot today on a Citrix XenServer 6.5 and apart from a Watchdog error that appeared while the install was running it OpenBSD on XenServer seems to be working great !! and without any editing of QEME related files :>)

    Is there any plans to do something to get XenTools into OBSD so that the XenServer can reboot / shutdown / see the network IP's etc ?

    Thanks again for getting this working.

    Comments

    1. By Mike (62.224.106.115) on

      > I installed the latest Snapshot today on a Citrix XenServer 6.5 and apart from a Watchdog error that appeared while the install was running it OpenBSD on XenServer seems to be working great !! and without any editing of QEME related files :>)
      >

      Nice.

      > Is there any plans to do something to get XenTools into OBSD so that the XenServer can reboot / shutdown / see the network IP's etc ?
      >

      I wanted to look at it, but haven't had time. If you could elaborate
      a bit on what is this and why do we need to support it and what kind
      of support is required, this would be very much appreciated indeed.

      > Thanks again for getting this working.
      >
      >

      You're welcome. Please keep testing the thing. Some changes are
      still in the pipeline, but we're almost done otherwise.

      Comments

      1. By Siyar Erdemli (85.97.189.32) Gobito Enterprise Solutions on www.gobito.com

        Hi.
        We use the OpenBSD on Xenserver 6.5. For testing area Router. Is working very good.

        But i can not get into the production environment without xentools.
        Do you have a study on this subject.

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]