similar to: Xen PVH Support in libvirt

Hi Ian, after our conversation on IRC in #debian-xen today, I updated the packaging to the latest 4.10-stable commit (since there's no 4.10.1 release yet) and smoke-tested the package on a testing/unstable dom0 running a PVHv2 guest. Can you please review and sponsor the upload of a first Xen 4.10 package to Debian unstable? The work which has been done to arrive at this point from the

We want to detect if a Linux kernel is Xen PV only ("PV-only"). Such a kernel will not boot on KVM, and if a guest has only PV-only kernels, it will not be able to boot at all on the target. Our previous test was wrong. It tested whether the xennet.ko module exists. This module was renamed in more recent kernels (to xen-netfront.ko), so it happened to not detect modern kernels as

We want to detect if a Linux kernel is Xen PV only ("PV-only"). Such a kernel will not boot on KVM, and if a guest has only PV-only kernels, it will not be able to boot at all on the target. Our previous test was wrong. It tested whether the xennet.ko module exists. This module was renamed in more recent kernels (to xen-netfront.ko), so it happened to not detect modern kernels as

From: Mukesh Rathor <mukesh.rathor@oracle.com> Use .ascii and .asciz to define xen feature string. Note, the PVH string must be in a single line (not multiple lines with \) to keep the assembler from putting null char after each string before \. Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> ---

On Mon, Dec 02, 2013 at 05:11:49PM +0100, Roger Pau Monn? wrote: > Hello, > > I''ve yet updated the PVH work one more time, regarding some comments > from emaste in order to try to make this work easier to merge with the > UEFI changes. In this regard, the parse_memmap hook now fetches and > parses the memmap, so UEFI can define it''s own hook and do the fetching

Hi it is meanwhile possible to use pvgrub/grub2 inside a pvh domU? -- ------ Greetz

Hi it is meanwhile possible to use pvgrub/grub2 inside a pvh domU? -- ------ Greetz

MTRR is not available for PVH Dom0, so prevent cpuid from reporting it as an available feature. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: George Dunlap <george.dunlap@eu.citrix.com> Cc: Mukesh Rathor <mukesh.rathor@oracle.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fraser <keir@xen.org> --- This should go in after Mukesh Dom0 series, or merged

Hi, I'm instresting with the PVH mode, is there any wiki available to boot up a PVH guest? I used the following source code to compile the xen and dom0. I have tried adding pvh=1 in xl.cfg file as pv mode, but guest still uses qemu device model. This patch series can also be pulled from this git tree: git://xenbits.xen.org/people/gdunlap/xen.git out/pvh-v15 The kernel code for PVH guests

In this patch, we change read_segment_register to take vcpu and regs parameters for PVH (in upcoming patches). No functionality change. also, make emulate_privileged_op() public for later. Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com> diff -r 93d95f6dd693 -r 0339f85f6068 xen/arch/x86/domain.c --- a/xen/arch/x86/domain.c Fri Jan 11 16:22:57 2013 -0800 +++ b/xen/arch/x86/domain.c

On Mon, Jan 07, 2019 at 08:44:50AM +0000, Colin Watson wrote: > On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote: > > Ok great. Since I'm not using (and probably not going to use) the > > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen

On 1/7/19 2:13 PM, Hans van Kranenburg wrote: > On 1/7/19 12:48 PM, Colin Watson wrote: >> [...] > >> Would you mind trying out the temporary pvh branch of >> https://salsa.debian.org/grub-team/grub ? I'd like to know whether the >> resulting grub-xen-host binary package does the right thing, when built >> in the ordinary way (I've test-built this

It was decided during xen patch review that xen map the iomem transparently, so remove xen_set_clr_mmio_pvh_pte() and the sub hypercall PHYSDEVOP_map_iomem. --- arch/x86/xen/mmu.c | 14 -------------- arch/x86/xen/setup.c | 16 ++++------------ include/xen/interface/physdev.h | 10 ---------- 3 files changed, 4 insertions(+), 36 deletions(-) diff --git

On Sun, Jan 06, 2019 at 01:45:53AM +0100, Hans van Kranenburg wrote: > Hm, so I have a PV (or PVH) domU in a test environment here, and I tried > to use it in the Debian way of booting it. > > If I install grub-xen-bin inside the domU then I get some stuff, but not > update-grub. When I just also install grub2 it drags in more stuff, and > then I end up with update-grub and a

George, since you asked on Friday, I though about the situation some more over the weekend. On PV, the requirement to trap all INs and OUTs is a result from us needing the enforce two levels of restrictions - Xen''s and the guest kernel''s. I.e. we can''t make use of the hardware''s access control mechanisms, as we can''t put two I/O bit maps in place, and

Hi Debian Grub maintainer, In december, Xen PVH support has been committed in grub master: https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html The last pieces needed in the Linux kernel to boot PVH with grub2 landed in Linux 4.20. I asked our kernel team to carry those patches on top of the Linux 4.19 kernel that is going to ship in Buster, and that wish was granted:

On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?

Hello, I''ve had a look at PVH support, and I have a few questions: - events are still dispatched the PV way through the callback, right? - I guess FPU errors don''t trigger an INT13, so I don''t need to handle that? - How about the console and store MFNs from the boot info? Are they still MFNs, or actually PFNs? - How about PV network in non-copy mode? It used to be

Christoph, I understand this is the better option if HVM is available.. Im not sure how to make use of this kernel in a non-HVM, PV environment. I'm a little disturbed by the fact that there isnt PV support in CentOS 8, I hope it comes later so at least PVH becomes an option. As for using this kernel in a PV only environment, the only route would be attempting an in place upgrade and try to

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support