All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Grant McWilliams <grantmasterflash@gmail.com>
Cc: Alexey Eremenko <al4321@gmail.com>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: State of Xen in upstream Linux
Date: Thu, 31 Jul 2008 11:58:23 -0700	[thread overview]
Message-ID: <48920B4F.7010608@goop.org> (raw)
In-Reply-To: <ed123fa30807311148q6460d2d8nb012f1b4edeb042f@mail.gmail.com>

Grant McWilliams wrote:
> Vbox OSE has full source available. I was working on a contract for a
> corporation and was in the stage
> of deciding which virtualization platform to run and installed Vbox in
> a Xen system (running Xen). The installer
> loaded the vbox driver (As well as set it up to load automatically)
> and sent the server into a continuous reboot. Unfortunately this was
> in a Datacenter that I had no physical access to. The Vbox developers
> jumped all over me when I suggested that it was a bug.
> When running Xen the VMware interface will come up and the driver will
> load but the VMs just don't start. It seems like
> that would be a much better situation than causing the entire machine
> to crash. Seems like a Vbox problem. It was run in Dom0.

Yes, that sounds like an inherently unstable configuration.  I don't
know anything about how VBox operates internally, but whatever pagetable
management scheme they're using will quite likely not work under Xen
without a lot of care.  The best we can do in that case is try to make
sure that VBox doesn't attempt to come up.

If they don't rely on VT/SVM, then it may work from within a Xen hvm
domain, but I don't know what benefit that would have.  What were you
trying to achieve by running VBox in dom0?

    J

  reply	other threads:[~2008-07-31 18:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  0:51 State of Xen in upstream Linux Jeremy Fitzhardinge
2008-07-31  7:27 ` Andy Burns
2008-07-31  9:08 ` [Xen-devel] " Daniel P. Berrange
2008-07-31 17:54   ` Grant McWilliams
2008-07-31 18:08     ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:19       ` [Xen-users] Re: [Xen-devel] " Alexey Eremenko
2008-07-31 18:28         ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:48           ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 18:58             ` Jeremy Fitzhardinge [this message]
2008-07-31 20:07               ` Grant McWilliams
2008-07-31 20:14                 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:36       ` [Xen-users] Re: [Xen-devel] " Dr. David Alan Gilbert
2008-07-31 18:45         ` [Xen-users] " Jeremy Fitzhardinge
2008-08-01  8:34     ` Re: [Xen-devel] " Daniel P. Berrange
2008-08-12 11:14 ` Pasi Kärkkäinen
2008-08-12 16:24   ` Jeremy Fitzhardinge
2008-08-26  8:30     ` State of Xen in upstream Linux / pv_ops dom0 Pasi Kärkkäinen
2008-08-26 15:20       ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48920B4F.7010608@goop.org \
    --to=jeremy@goop.org \
    --cc=al4321@gmail.com \
    --cc=berrange@redhat.com \
    --cc=grantmasterflash@gmail.com \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.