Re: [Xen-devel] Xen does not work after changing scheduler's code

[tutu sky <ooohooo_u@xxxxxxxxxxx>]

yeah i tried, attaching a serial console was not possible for me, so i tried 
vmware and i tried match the information in link with some links on do the same 
using vmware. actually when using vmware for doing so, i changed: 
GRUB_CMDLINE_XEN line of grub to "loglvl=all guest_loglvl=all 
com1=115200,8n1,0x3e8,5 console=com1,vga"  as mentioned in that link and it 
caused a kernel panic (blinding num lock and scroll lock together).
if using two VM in vmware which one contains xen and other just does monitoring 
another, i think it must be possible to monitor xen.

by the way, thanks a lot. 

________________________________________
From: Juergen Gross <jgross@xxxxxxxx>
Sent: Friday, April 22, 2016 8:46 AM
To: tutu sky; Xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen does not work after changing scheduler's code

On 22/04/16 10:18, tutu sky wrote:
> thanks Juergen,
> i tried attaching serial console before in vmware (according 
> http://wiki.xenproject.org/wiki/XenSerialConsole) but it was not successful, 
> does your mentioned link need any command line options which must be added 
> for it to work correctly? or any extra compile and configuration steps before 
> installing xen?

Huh, what?

Did you even try to understand the information in the mentioned wiki
article? This has nothing to do with vmware and all needed command
line options are discussed.

In case you don't have a second computer to hook up the serial line
you can add the "noreboot" option to the hypervisor command line. It
will avoid rebooting the computer in case of a hypervisor crash in case
the crash isn't happening before the boot options are being parsed.


Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel