xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: jim burns <jim_burn@bellsouth.net>
Cc: xen-devel@lists.xen.org
Subject: Re: Fwd: Openindiana, using -machine pc, accel=xen in qemu
Date: Thu, 22 Sep 2016 12:22:02 +0100	[thread overview]
Message-ID: <20160922112202.GA3278@perard.uk.xensource.com> (raw)
In-Reply-To: <2925218.0UPpxnAMxp@insp3847>

On Wed, Sep 21, 2016 at 06:20:16PM -0400, jim burns wrote:
> I didn't get any responses in xen-users, so I'm posting here. My use case is 
> as below, but the jist of it is is the qemu option -machine pc,accel=xen meant 
> to be usable in standalone qemu, or is it only available from a guest launched 
> by xl, or libvirtd via libxl? If the latter, are there any plans to make it 
> available as a standalone qemu option? 

Hi,

-machine pc,accel=xen is to be used by libxl (used by xl or libvirt).
libxl takes care of creating a guest and launch QEMU when needed.

There are some QEMU options to start a xen guest with standalone qemu,
but I don't know if they works. Look for -xen-create. But I don't think
that is what you would need.

What is your xen config file for OI ?

Also, how do you start OI with KVM/tcg? (qemu command line)

> I have not been able to run OpenSolaris / openindiana (OI) in xen. OI is very 
> sensitive to the -machine parm in qemu. You can get grub to come up with hvm, 
> and add -v to the kernel line, and see that for -machine xenfv, the messages 
> stop / hang right after the printing of the cpuid features, and just before 
> pci bus enumeration. Qemu's -machine q35 is not much better. After the cpuid 

q35 won't work with Xen.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-09-22 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 22:20 Fwd: Openindiana, using -machine pc,accel=xen in qemu jim burns
2016-09-22 11:22 ` Anthony PERARD [this message]
2016-09-22 14:37   ` Fwd: Openindiana, using -machine pc, accel=xen " jim burns
2016-09-26 11:32     ` Anthony PERARD
2016-09-26 15:02       ` jim burns
2016-09-26 16:21         ` Anthony PERARD
2016-09-26 19:27           ` jim burns
2016-10-05 18:46             ` Fwd: Openindiana, using -machine pc, accel=xen in qemu - Success! jim burns
     [not found]               ` <339333DD-C225-4648-98A5-68A7F75496D9@netgate.net>
2016-10-05 19:21                 ` [Xen-users] " jim burns

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=20160922112202.GA3278@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=jim_burn@bellsouth.net \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).