similar to: Start xen on UEFI system with grub

I have installed dom0 Wheezy 64 bit on Dell PowerEdge T310 with kernel from package and xen-unstable. System is in Uefi mode and booted with grub-efi-amd64. Booting without xen efibootmgr works, while with xen not, efivars kernel module is loaded but show this message: efibootmgr Fatal: Couldn''t open either sysfs or procfs directories for accessing EFI variables. Try ''modprobe

Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- tools/firmware/ovmf-makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/firmware/ovmf-makefile b/tools/firmware/ovmf-makefile index c3cd466..073ed44 100644 --- a/tools/firmware/ovmf-makefile +++ b/tools/firmware/ovmf-makefile @@ -10,7 +10,7

- Enable vdagent on upstream qemu if spice is used. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- tools/libxl/libxl_dm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index a8a36d7..110f1dc 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -427,6 +427,10 @@ static char **

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

From: Fabio Fantoni <fabio.fantoni@heliman.it> Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> --- tools/libxl/libxl_dm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 51f9914..c265618 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -406,6 +406,9 @@ static char **

Package: xen-system-amd64 Version: 4.3.0-3+b1 Severity: wishlist --- Please enter the report below this line. --- Please package Xen 4.4: http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/ It has experimental support for PVH mode among other improvements: http://wiki.xenproject.org/wiki/Xen_4.4_Feature_List#Experimental_Support_for_ParaVirtualization_Hardware_.28PVH.29_Mode_for_Guests

Usage: vga="qxl" Reposted for xen 4.4, require SSE support on hvm domU otherwise it works only as a standard vga. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Zhou Peng <zpengxen@gmail.com> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> --- docs/man/xl.cfg.pod.5 |

I have a IBM System x3600 series server with UEFI. I managed to compile the xen EFI (xen-4.2-unstable.efi). The machine is currently running Ubuntu with grub2. I can see a grubx64.efi in /boot/efi/EFI/ubuntu/grubx64.efi Where should I put the xen efi ? I tried creating a efi/EFI/xen/xen-4.2-unstable.efi and added it as a boot option using efibootmgr. All I get in that case is a blank screen. I

tools/libxl: Disable useless empty floppy drive with qemu-xen Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> --- tools/libxl/libxl_dm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 51f9914..c265618 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -406,6 +406,9 @@ static char **

Hey, There has been some discussion about EFI and SecureBoot and such. Most of the time I get questions in the form of "How do I get Fedora 17 with Xen to do EFI", I am going to concentrate on Fedora, but I think this applies to other distros too. From my reading (I hadn't actually tried EFI yet), there are two ways to bootup a system: - Using grub2.efi. Grub2 does the EFI API

The user has the option of disabling the platform driver: 00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01) which is used to unplug the emulated drivers (IDE, Realtek 8169, etc) and allow the PV drivers to take over. If the user wishes to disable that they can set: xen_platform_pci=0 (in the guest config file) or xen_emul_unplug=never (on the Linux command

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- tools/firmware/ovmf-makefile | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/tools/firmware/ovmf-makefile b/tools/firmware/ovmf-makefile index 073ed44..efb4fb1 100644 --- a/tools/firmware/ovmf-makefile +++ b/tools/firmware/ovmf-makefile @@ -1,3 +1,6 @@ +XEN_ROOT = $(CURDIR)/../../.. +include

This small series reintroduces OVMF support in Xen You can fetch working OVMF tree on: git://xenbits.xen.org/people/liuw/ovmf.git master Working changeset that can be sticked in Config.mk is: 8833370303d3bf3153760ee42760ef1b9b5c562 Note that VNC doesn''t work properly when using OVMF, but that''s not OVMF''s problem. This issue should be addressed in Xen and I''m

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream will be used in Xen

----- Original Message ----- | On Fri, Aug 19, 2016 at 4:59 PM, James A. Peltier <jpeltier at sfu.ca> wrote: | > | > | > ----- Original Message ----- | > | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> | > | wrote: | > | > Hi All, | > | > | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | > | | > | |

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

----- Original Message ----- | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> wrote: | > Hi All, | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | | | This is hardware RAID 5? Because it's pretty screwy how this ends up | working when using software RAID and might take additional | troubleshooting. Yes, it's a Dell R710XD |