All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: "Sanjeepan, Vivekananthan" <vivekananthan.sanjeepan@intel.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Debugging hvmloader and vmxassist
Date: Wed, 03 Jan 2007 13:00:46 -0600	[thread overview]
Message-ID: <459BFD5E.8070208@linux.vnet.ibm.com> (raw)
In-Reply-To: <B1EDF20A6EAAD74EA65E46F774F178457E7EF8@orsmsx413.amr.corp.intel.com>

Sanjeepan, Vivekananthan wrote:
> Hi there,
> 
>  
> 
> I have been trying unsuccessfully to boot FreeBSD on Xen 3.0.4-testing. 
>  From reading the mailing list I understand the problem with emulating 
> big real mode. I would like to debug hvmloader and vmxassist to see if I 
> can fix the issue.

The problem is unfixable as vmxassist uses vm86 mode.

You may have more luck with the V2E tree:

http://xenbits.xensource.com/ext/xen-unstable-hvm.hg

  There are lots of printf statements in hvmloader and
> vmxassist. I am wondering how I can redirect them to the 
> qemu-dm.<pid>.log log file. Please let me know if anyone on the list has 
> a suggestion.
> 
>  
> 
> Thanks,
> 
> Sanjee
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2007-01-03 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 18:26 Debugging hvmloader and vmxassist Sanjeepan, Vivekananthan
2007-01-03 18:47 ` Andrew D. Ball
2007-01-03 19:00 ` Anthony Liguori [this message]
2007-01-04  1:09 ` Li, Xin B
2011-05-20 15:21 ` henanwxr
2011-05-20 15:32   ` Keir Fraser
2011-05-20 16:11     ` henanwxr
2011-05-23 16:43     ` Ian Jackson
2011-05-23 16:45       ` Can we block "nabble" from posting to xen lists Lars Kurth

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=459BFD5E.8070208@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=vivekananthan.sanjeepan@intel.com \
    --cc=xen-devel@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.