Re: XENPVHVM

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I also couldn't get the serial console to work in any way, so added

vga0          at isa?
wsdisplay*      at vga? console ?

to XEN3_PVHVM and was able to go further. It boots, but the hypervisor
is not recognised, there is no networking and the console does not
react. The only thing I was able to do is record (with ShareX) the
boot process, so I can describe the dmesg. If anyone is interested,
one of you can download the screengrab from
https://send.firefox.com/download/d572b68084ea64b7/#f2w9lqWFw_hzhC4zw4k8sQ
in the next 24 hours. Basically, it identifies the disk - wd0 on
atabus0 correctly (obviously, as it boots further), but then it
identifies a second disk, wd1, on atabus1 (ST506 type) [it rings a
bell, I think I have seen this before]. Then you get a lot of errors
all from wd1, and that is all, nothing else. If the hypervisor is not
recognised, there is no xennet, ofcourse; likewise no xencons.

If the output  from 'xl dmesg' might be useful, I can post it.

Chavdar

...


On Mon, 10 Jun 2019 at 15:07, Mathew, Cherry G. <cherry%zyx.in@localhost> wrote:
>
> On 10 June 2019 3:48:17 PM GMT+02:00, Stephen Borrill <netbsd%precedence.co.uk@localhost> wrote:
> >On Mon, 10 Jun 2019, Stephen Borrill wrote:
> >> On Sat, 8 Jun 2019, Mathew, Cherry G. wrote:
> >>> Hi Chavdar - the PVHVM console is on the serial port so you'll need
> >to
> >>> connect your domU TTY to it.
> >>>
> >>> On regular xen tools you put a 'serial=pty' line in your config
> >file. xl
> >>> console should normally dtrt but  you can force it like so:
> >>>
> >>> xl console -t serial $domid
> >>
> >> I've not had any joy with this on XenServer (or XCP-NG):
> >>
> >> [root@xenserver4 ~]# list_domains | grep `xe vm-list
> >name-label="NetBSD
> >> PVHVM" --minimal`
> >> 15 | e2d4c021-9303-4264-f5aa-5f88cfbb1679 |    B H
> >> [root@xenserver4 ~]# xl console 15
> >> *nothing*
> >> [root@xenserver4 ~]# xenstore-ls /local/domain/15/serial
> >> 0 = ""
> >> limit = "65536"
> >> tty = "/dev/pts/9"
> >>
> >> Can the console be set to the standard emulated graphics console
> >instead of
> >> serial as Linux PVHVM VMs do?
> >
> >This time I switched to a serial console from the bootloader with
> >"consdev
> >com0". Hypervisor is not detected:
> >
> >[root@xenserver4 ~]# list_domains | grep `xe vm-list name-label="NetBSD
> >PVHVM" --minimal`
> >16 | e2d4c021-9303-4264-f5aa-5f88cfbb1679 |      H
> >[root@xenserver4 ~]# xl console -t serial 16
> >
> >> boot netbsdp
> >4178040+577416 [342312+218025+18488]=0x516d78
> >[   1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
> >2003, 2004, 2005,
> >[   1.0000000]     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
> >2014, 2015, 2016, 2017,
> >[   1.0000000]     2018, 2019 The NetBSD Foundation, Inc.  All rights
> >reserved.
> >[   1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
> >[   1.0000000]     The Regents of the University of California.  All
> >rights reserved.
> >
> >[   1.0000000] NetBSD 8.99.43 (XEN3_PVHVM) #1: Mon Jun 10 14:18:42 BST
> >2019
> >[   1.0000000]
> >root@builder7:/usr/work/obj/current/amd64/sys/arch/amd64/compile/XEN3_PVHVM
> >[   1.0000000] total memory = 1019 MB
> >[   1.0000000] avail memory = 983 MB
> >[   1.0000030] mainbus0 (root)
> >[   1.0000030] cpu0 at mainbus0
> >[   1.0000030] cpu0: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz,
> >id 0x1067a
> >[   1.0000030] cpu0: package 0, core 0, smt 0
> >[   1.0000030] isa0 at mainbus0
> >[   1.0000030] com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working
> >fifo
> >[   1.0000030] com0: console
> >[   1.0000030] wdc0 at isa0 port 0x1f0-0x1f7 irq 14
> >[   1.0000030] atabus0 at wdc0 channel 0
> >[   1.0000030] wdc1 at isa0 port 0x170-0x177 irq 15
> >[   1.0000030] atabus1 at wdc1 channel 0
> >[   1.0000030] hypervisor: Xen HVM mode not identified. Exiting.
> >[   1.0000030] hypervisor at mainbus0 not configured
> >[   4.0599377] wd0 at atabus0 drive 0
> >[   4.0719300] wd0: <QEMU HARDDISK>
> >[   4.0719300] wd0: 5120 MB, 10402 cyl, 16 head, 63 sec, 512 bytes/sect
> >x 10485760 sectors
>
> OK, that is really interesting. can you give me a 'xl dmesg' dump please ?
>
> many thanks,
>
> Cherry
> --
> Sent from my phone. Please excuse my brevity.



-- 
----