Re: [Xen-devel] Questions about PVHv2/HVMlite

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Wed, May 17, 2017 at 07:07:25PM -0500, Gary R Hook wrote:
> On 5/16/2017 12:13 PM, Boris Ostrovsky wrote:
> > On 05/16/2017 11:52 AM, Gary R Hook wrote:
> > A PVH guest's config looks something like
> > > >      kernel="/root/64/vmlinux"
> > > May I ask from whence this kernel came?
> > One of 4.11's rcs. Make sure you set CONFIG_XEN_PVH in your .config file.
> 
> Please excuse my lack of clarity. I meant, on what filesystem
> does this kernel reside? dom0. Got it.
> 
> So here's where I stand:
> 
> I have pulled the torvalds repo, found the "Linux 4.11" commit
> to create a branch, verified that the config parameters suggested
> in a different post are all enabled (CONFIG_XEN, CONFIG_XEN_PVH,
> etc): they're all turned on. Built a kernel. Boot dom0 with it,
> and I have it in my guest, too (by booting the xvda in a PV guest
> and building it there... I'm hoping that's not a problem?). And the
> kernel and initrd are in /root/64 on dom0, per the above.
> 
> 
> I have this configuration (using a logical volume for my raw disk):
> 
> extra = "root=/dev/xvda1 console=hvc0"
> kernel = "/root/64/vmlinuz-4.11.0-pvh+"
> ramdisk = "/root/64/initrd.img-4.11.0-pvh+"
> pvh = 1

This is not yet available, (pvh=1), let me try to clarify the current
situation:

In order to create a PVH guest you need to add the following to your config
file:

builder="hvm"
device_model_version="none"

So using your example, the config file should look like:

extra = "root=/dev/xvda1 console=hvc0"
kernel = "/root/64/vmlinuz-4.11.0-pvh+"
ramdisk = "/root/64/initrd.img-4.11.0-pvh+"
builder="hvm"
device_model_version="none"
memory = 4096
name = "sospv2"
vcpus = 8
vif = ['']
disk = ['phy:/dev/vg0/pvclient2,xvda,w']

This is a temporary interface, and it's not stable. Long term PVH guest should
be created using "pvh=1", sadly this has not yet been implemented.

Hope this helps, Roger.

NB: FWIW, I've tried PVH DomU on AMD hardware in the past and they seemed to
work fine.


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