Re: merge bouyer-xenpvh to HEAD

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

On Sat, 25 Apr 2020 at 18:16, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
>
> On Sat, Apr 25, 2020 at 03:08:44PM +0100, Chavdar Ivanov wrote:
> > On Sat, 25 Apr 2020 at 14:35, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
> > >
> > > On Sat, Apr 25, 2020 at 02:29:49PM +0100, Chavdar Ivanov wrote:
> > > > I am not aware if this is possible at all;
> >
> > Didn't think a lot here...
> >
> > >
> > > As of Xen 4.11 is has to be explicitely enabled in the guest config file.
> > > What does your config file looks like ?
> >
> > It is a database; the requisite parameter is platform:viridian.
> >
> > #  xe vm-param-set uuid=c8c8b530-3474-61be-9d4a-a2f3e82cfc9a
> > platform:viridian=false
> >
> > Got me further - now GENERIC_XENPVH boots showing in the console the
> > usual kernel configuration messages, one can see the Xen devices,
> > including xennet, but then it doesn't go further; perhaps the console
> > definition is wrong.
>
> Ha, maybe it's because of the way the devices are defined.
> For me, with
> disk = [ 'file:/domains2/meaban-hvm.vnd,ioemu:hda,w', 'file:/domains2/boot-netbsdc-amd64-serial.iso,ioemu:hdc:cdrom,r' ]
>
> I get a hang similar to what you describe.
> With
> disk = [ 'file:/domains2/meaban-hvm.vnd,xvda,w', 'file:/domains2/boot-netbsdc-amd64-serial.iso,xvdb,r' ]

I get:
..
]# xe vbd-param-list uuid=e43f463d-688c-c586-19f0-91e3cbd1db07
uuid ( RO)                        : e43f463d-688c-c586-19f0-91e3cbd1db07
                     vm-uuid ( RO): ce92d1de-aa1d-7b4f-97d4-d56da032339c
               vm-name-label ( RO): n999-pvhvm
                    vdi-uuid ( RO): 7930785d-c40e-4372-9ab1-31e4e1cfdb42
              vdi-name-label ( RO): n99959-pvhvm
          allowed-operations (SRO): attach
          current-operations (SRO):
                       empty ( RO): false
                      device ( RO): xvda      <-----
                  userdevice ( RW): 0
                    bootable ( RW): true
                        mode ( RW): RW
                        type ( RW): Disk
                 unpluggable ( RW): false
          currently-attached ( RO): false
                  attachable ( RO): true
                storage-lock ( RO): false
                 status-code ( RO): 0
               status-detail ( RO):
          qos_algorithm_type ( RW):
        qos_algorithm_params (MRW):
    qos_supported_algorithms (SRO):
                other-config (MRW): owner:
                 io_read_kbs ( RO): <unknown>
                io_write_kbs ( RO): <unknown>

I presume this is the equivalent to the text file you show.

The linked vdi is as follows:
...
# xe vdi-param-list uuid=7930785d-c40e-4372-9ab1-31e4e1cfdb42
uuid ( RO)                    : 7930785d-c40e-4372-9ab1-31e4e1cfdb42
              name-label ( RW): n99959-pvhvm
        name-description ( RW): NetBSD-current try
           is-a-snapshot ( RO): false
             snapshot-of ( RO): <not in database>
               snapshots ( RO):
           snapshot-time ( RO): 20200426T09:23:16Z
      allowed-operations (SRO): update; forget; destroy; snapshot;
resize; copy; clone
      current-operations (SRO):
                 sr-uuid ( RO): e7367c91-e374-7f7b-cc05-f22b4137ef75
           sr-name-label ( RO): sdb
               vbd-uuids (SRO): e43f463d-688c-c586-19f0-91e3cbd1db07
         crashdump-uuids (SRO):
            virtual-size ( RO): 34359738368
    physical-utilisation ( RO): 34435235840
                location ( RO): 7930785d-c40e-4372-9ab1-31e4e1cfdb42
                    type ( RO): User
                sharable ( RO): false
               read-only ( RO): false
            storage-lock ( RO): false
                 managed ( RO): true
     parent ( RO) [DEPRECATED]: <not in database>
                 missing ( RO): false
            is-tools-iso ( RO): false
            other-config (MRW): content_id: db1625a8-e287-1a00-5925-2ff6528593bb
           xenstore-data (MRO):
               sm-config (MRO): vhd-parent:
a509e33d-f898-476f-a74f-5428e5096f6a; vdi_type: vhd; vmhint:
                 on-boot ( RW): persist
           allow-caching ( RW): false
         metadata-latest ( RO): false
        metadata-of-pool ( RO): <not in database>
                    tags (SRW):
             cbt-enabled ( RO): false
...

>
> it boots

>

I did a complete new installation of 9.99.59 under XCP-NG, in efi mode
with gpt labels; before rebooting I replaced the kernel with the one
from your repo. When platform:viridian is set, it works as fine as
ever; if I unset it, it boots, displays all the kernel configuration
messages in the console window and enters idle loop, never starting
init; one can enter the debugger here. I took screenshots of the
kernel configuration messages - it appears everything is recognized,
but it sees two disks - xbd0 and xbd1, the former containing all the
gpt slices reported further down. xennet0 is also reported with its
mac address.

I can attach the screenshots if they are of interest.


> --
> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>      NetBSD: 26 ans d'experience feront toujours la difference
> --


Chavdar

--
----