On 05/18/2017 03:16 AM, Roger Pau Monné wrote:
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']
Well, huzzah!
amd@sospvclient2:~$ dmesg | grep -i xen
[ 0.000000] Hypervisor detected: Xen
[ 0.000000] Xen version 4.9.
[ 0.000000] Xen Platform PCI: unrecognised magic value
[ 0.000000] ACPI: RSDP 0x00000000000FFFC0 000024 (v02 Xen )
[ 0.000000] ACPI: XSDT 0x00000000FC007FA0 000034 (v01 Xen HVM
00000000 HVML 00000000)
[ 0.000000] ACPI: FACP 0x00000000FC007D70 00010C (v05 Xen HVM
00000000 HVML 00000000)
[ 0.000000] ACPI: DSDT 0x00000000FC001050 006C9B (v05 Xen HVM
00000000 INTL 20140214)
[ 0.000000] ACPI: APIC 0x00000000FC007E80 00006C (v02 Xen HVM
00000000 HVML 00000000)
[ 0.000000] Booting paravirtualized kernel on Xen PVH
[ 0.000000] xen: PV spinlocks enabled
^^^^^^^
This is a temporary interface, and it's not stable.
"Stable" as in syntax and keywords are subject to change?
Long term PVH guest should
be created using "pvh=1", sadly this has not yet been implemented.
Do I understand this to mean that using "pvh=1" in the config file
hasn't been wired
up to do everything needed to create a PVH guest? Is there more to be
done besides
turning that parameter into "builder='hvm" device_model_version="none"?
Or, better yet,
are there any design notes on this?
Hope this helps, Roger.
It seems it did. Thank you very much!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
