Debugging hvmloader and vmxassist

Debugging hvmloader and vmxassist

[Sanjeepan, Vivekananthan]

[-- Attachment #1.1: Type: text/plain, Size: 485 bytes --]

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. 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


[-- Attachment #1.2: Type: text/html, Size: 2462 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Debugging hvmloader and vmxassist

[Andrew D. Ball]

I thought they were already redirected there or to the regular xend
logs, but can't check on this until I get back from vacation.

Peace.
Andrew

On Wed, 2007-01-03 at 10:26 -0800, 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. 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

Re: Debugging hvmloader and vmxassist

[Anthony Liguori]

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

RE: Debugging hvmloader and vmxassist

[Li, Xin B]

[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]

you can use this patch to get the log in your qemu log file.
-Xin


________________________________

	From: Sanjeepan, Vivekananthan 
	Sent: Thursday, January 04, 2007 2:27 AM
	To: xen-devel@lists.xensource.com
	Subject: Debugging hvmloader and vmxassist
	
	

	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. 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


[-- Attachment #1.2: Type: text/html, Size: 3516 bytes --]

[-- Attachment #2: qemu_debug.patch --]
[-- Type: application/octet-stream, Size: 1242 bytes --]

diff -r 463bda167715 tools/ioemu/target-i386-dm/helper2.c
--- a/tools/ioemu/target-i386-dm/helper2.c	Wed Nov 29 12:43:11 2006 +0000
+++ b/tools/ioemu/target-i386-dm/helper2.c	Wed Nov 29 14:25:16 2006 +0800
@@ -299,6 +299,10 @@ static inline void write_physical(uint64
     return cpu_physical_memory_rw((target_phys_addr_t)addr, val, size, 1);
 }
 
+#define DEBUG_BUF_SIZE 1024
+unsigned char debug_buf[DEBUG_BUF_SIZE];
+unsigned int debug_buf_idx = 0;
+
 void cpu_ioreq_pio(CPUState *env, ioreq_t *req)
 {
     int i, sign;
@@ -319,7 +323,16 @@ void cpu_ioreq_pio(CPUState *env, ioreq_
             }
         }
     } else if (req->dir == IOREQ_WRITE) {
-        if (!req->data_is_ptr) {
+        if (req->addr == 0xe9) {
+            unsigned char c = (unsigned char)req->data;
+            debug_buf[debug_buf_idx++] = c;
+            if ((debug_buf_idx == (DEBUG_BUF_SIZE - 1)) || (c == '\n'))
+            {
+                debug_buf[debug_buf_idx] = 0;
+                fprintf(logfile, "HVM DEBUG: %s", debug_buf);
+                debug_buf_idx = 0;
+            }
+        } else if (!req->data_is_ptr) {
             do_outp(env, req->addr, req->size, req->data);
         } else {
             for (i = 0; i < req->count; i++) {

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Debugging hvmloader and vmxassist

[henanwxr]

Hi, I think it is impossible to send the print message of hvmloader to qemu
directly. 
Becuase before qemu could work(such as show message in screen with its VGA
driver), the VGA bios must be installed, but as wo konw, the installiation
VAG bios is done by hvmloader.Until hvmloader and bios(including system
bios, vga bios, etc) have done, then the qemu can work.

Although we can not do this directly, you can store the message of hvmloader
in a big buffer, when the qemu can work, then let qemu get buffer to its
screen or logfile.

--
View this message in context: http://xen.1045712.n5.nabble.com/Debugging-hvmloader-and-vmxassist-tp2499660p4412817.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: Re: Debugging hvmloader and vmxassist

[Keir Fraser]

On 20/05/2011 16:21, "henanwxr" <henanwxr@163.com> wrote:

> Hi, I think it is impossible to send the print message of hvmloader to qemu
> directly. 
> Becuase before qemu could work(such as show message in screen with its VGA
> driver), the VGA bios must be installed, but as wo konw, the installiation
> VAG bios is done by hvmloader.Until hvmloader and bios(including system
> bios, vga bios, etc) have done, then the qemu can work.
> 
> Although we can not do this directly, you can store the message of hvmloader
> in a big buffer, when the qemu can work, then let qemu get buffer to its
> screen or logfile.

Why are you reviving a 4-year-old thread?

 -- Keir

> --
> View this message in context:
> http://xen.1045712.n5.nabble.com/Debugging-hvmloader-and-vmxassist-tp2499660p4
> 412817.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re:Re: Debugging hvmloader and vmxassist

[henanwxr]

[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]

I just register in this website yesterday, and I am not very clear about the rules, could not I reply a post 4-year-old?

At 2011-05-20 23:33:36，"Keir Fraser-5 [via Xen]" <ml-node+4412837-644895373-210084@n5.nabble.com> wrote:
On 20/05/2011 16:21, "henanwxr" <[hidden email]> wrote:


> Hi, I think it is impossible to send the print message of hvmloader to qemu
> directly.
> Becuase before qemu could work(such as show message in screen with its VGA
> driver), the VGA bios must be installed, but as wo konw, the installiation
> VAG bios is done by hvmloader.Until hvmloader and bios(including system
> bios, vga bios, etc) have done, then the qemu can work.
>
> Although we can not do this directly, you can store the message of hvmloader
> in a big buffer, when the qemu can work, then let qemu get buffer to its
> screen or logfile.

Why are you reviving a 4-year-old thread?

 -- Keir


> --
> View this message in context:
>http://xen.1045712.n5.nabble.com/Debugging-hvmloader-and-vmxassist-tp2499660p4
> 412817.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-devel mailing list
>[hidden email]
>http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel



If you reply to this email, your message will be added to the discussion below:
http://xen.1045712.n5.nabble.com/Debugging-hvmloader-and-vmxassist-tp2499660p4412837.html
To unsubscribe from Debugging hvmloader and vmxassist,click here.

--
View this message in context: http://xen.1045712.n5.nabble.com/Debugging-hvmloader-and-vmxassist-tp2499660p4412925.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

[-- Attachment #1.2: Type: text/html, Size: 3797 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: Debugging hvmloader and vmxassist

[Ian Jackson]

Keir Fraser writes ("Re: [Xen-devel] Re: Debugging hvmloader and vmxassist"):
> Why are you reviving a 4-year-old thread?

The OP is using "nabble" which is a web archive with a posting
interface.  The posting interface sends emails which end up on our
list.

Lars, can we block this somehow ?  We do not want people using a web
form to email xen-devel.

Ian.

Can we block "nabble" from posting to xen lists

[Lars Kurth]

Ian,
Not sure. This would be one for Andrew
Lars

-----Original Message-----
From: Ian Jackson 
Sent: 23 May 2011 17:44
To: Keir Fraser; Lars Kurth
Cc: henanwxr; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: Debugging hvmloader and vmxassist

Keir Fraser writes ("Re: [Xen-devel] Re: Debugging hvmloader and vmxassist"):
> Why are you reviving a 4-year-old thread?

The OP is using "nabble" which is a web archive with a posting
interface.  The posting interface sends emails which end up on our
list.

Lars, can we block this somehow ?  We do not want people using a web
form to email xen-devel.

Ian.