From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miguel Clara Subject: Re: [Xen-devel] Fwd: Xen 4.3 Netbsd Date: Sat, 25 May 2013 02:07:52 +0100 Message-ID: References: <519E2C36.10500@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <519E2C36.10500@citrix.com> Sender: port-xen-owner@NetBSD.org To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Cc: "port-xen@netbsd.org" , xen-devel@lists.xensource.com, "chegger@amazon.de" List-Id: xen-devel@lists.xenproject.org Hum... I was looking into how to connect to the serial console, but I don't have the cable, also my laptop doesn't have the serial port, so I guess I will need some adapter, maybe USB... in any case it would be nice if someone else could test this! Thanks On Thu, May 23, 2013 at 3:48 PM, Roger Pau Monn=E9 w= rote: > On 23/05/13 13:09, Miguel Clara wrote: >> I'm testing xen 4.3 on netbsd and I was able to build the kernel and >> tools successfully (after 2 minor fixes see more here: >> http://lists.xen.org/archives/html/xen-devel/2013-05/msg01482.html), I >> was also able to install the tools. >> >> However I'm getting a strange problem and I'm not sure even how to debug= it... >> >> While booting with: >> >> menu=3DNetBSD Xen:load /netbsd.xen console=3Dpc;multiboot /xen.gz dom0_m= em=3D256M >> >> I get a very stange screen with something like: >> >> 08cF60 0000000000000000000d43...... (see attached screenshot, I have >> no other way to "copy it form the console") >> >> Seems to be hexa code.... no panic, no reboot, my guess is that the >> problem is wiht the Dom0 kernel, but this was the one I was using for >> xen-4.1 and xen-4.2, I was downloaded a new file >> (ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.1/amd64/binary/kernel/netbsd-X= EN3_DOM0.gz) >> I wonder if this is not compatible with xen-4.3. >> >> I never saw this kind of error, I wonder if you add any luck booting? >> >> I've tried with netbsd 6.0.1 and them upgrade to 6.1, and get the same r= esult! > > You will have to setup a serial console in order to obtain a log, > without that it is impossible to say what's going on. >