similar to: Xen 4.0 native UEFI support

We are utilizing the xen hypervisor on nexenta with ISCSI as our method of communication with the guests (currently ubuntu but could be moving to centos). Obviously jumbo packet support would be nice to have. The last time I see that on the xen roadmap http://wiki.xensource.com/xenwiki/XenRoadMap . Is there a canonical place that spells out if jumbo frames are now supported or still on the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Hi List, is it possible to limit the (disc) io for a domU? Best regrads, Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi Ola, There was some code done by IBM a few years ago in conjunction with a University that worked and showed the benefits but AFAIK it was never integrated into Xen. The research paper is around on the web. A few of us requested RDMA migration support for version 4.0 and it is at the top of the request list, I suspect it is probably a case of enough people asking and Citrix approving.

Hi, I''ve collected together a bunch of XCP-related project suggestions and stuck them on the xen wiki: http://wiki.xensource.com/xenwiki/XAPI_project_suggestions The main idea is that new people who want to work on XCP can use this list for inspiration... each idea has a rough guesstimate of size/ knowledge required/ impact and an initial first contact (who either suggested the idea

Highlights for April 18 - April 24, 2009: * Xen.org Summer Internship Available - http://blog.xen.org/index.php/2009/04/21/xenorg-internship-available/ * VM Snapshots Code Released - http://blog.xen.org/index.php/2009/04/21/vm-snapshots-code-released/ * Xen 4.0 Feature Requests List - http://wiki.xensource.com/xenwiki/XenRoadMap * Lots of Patches and Answers to

Highlights for April 18 - April 24, 2009: * Xen.org Summer Internship Available - http://blog.xen.org/index.php/2009/04/21/xenorg-internship-available/ * VM Snapshots Code Released - http://blog.xen.org/index.php/2009/04/21/vm-snapshots-code-released/ * Xen 4.0 Feature Requests List - http://wiki.xensource.com/xenwiki/XenRoadMap * Lots of Patches and Answers to

As promised, in preparation for next week's SIG meeting, here's a kick-off discussion about the Virtualization SIG roadmap. I'm mainly tossing out ideas here -- see this is an invitation to discussion. Key things I think should be on the roadmap: * Release process - General cadence - Estimate of the next release (if any) * Specification of targets - Right now, mainly xen4centos

Hi, What text should be in monthly posting to this mailingist, the Syslinux mailinglist? Things I have in mind: * That gettng a wiki account is in two phase, first create a wiki account, then tell the accountname so it gets write permission * our Roadmap (currently: BIOS works, UEFI is work in progress ) * Download locations and git repositories. * Answers to Frequently Asked Questions.

Is there a native linker in the roadmap so that there isn't a dependency on binutils? Is it considered out of scope? It seems to me that I saw mention of someone starting such a project a while ago. Did it ever get anywhere? Was there a particular reason why it wasn't folded into llvm as an official project? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Commit 889386f8c6088e57fd68f2bb6bf85f69ecfc6f6c removed most of them already, so remove the last ones, and the supporting code. --- generator/UEFI.ml | 6 ------ v2v/utils.ml | 1 - 2 files changed, 7 deletions(-) diff --git a/generator/UEFI.ml b/generator/UEFI.ml index 5161e28ee..1ff3f84d2 100644 --- a/generator/UEFI.ml +++ b/generator/UEFI.ml @@ -30,12 +30,6 @@ open Docstrings (* Order

I checked and secure boot is turned off. Jonathan brings it exactly to the point: we have to face UEFI because legacy mode is fading out, if I enable legacy mode I can't even boot anymore through the network (PXE) as these newer network cards can only boot PXE with UEFI. In the mean time I have installed Ubuntu 17.10 with Xen and I was lucky to see that this combination works with UEFI even

All, I realize this is not strictly a PXELINUX question. So I hope you'll indulge me; hopefully some of these PXELINUX experts have seen this before. And can tell me what I'm doing wrong. Or confirm my suspicions. I have a test lab server at work. Split config. The network team manages the DHCP servers, points to our TFTP server. Test subnet has 3 DHCP pools. BIOS PXE, UEFI PXE and

Ady, There are at least 3 ways to set up your DHCP server to differentiate between std DHCP, BIOS PXE and UEFI PXE. Option 93 (arch) is one way. In ISC syntax, here's 3 ways: 1. Match on VCI class "pxe-clients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; set vendor-string = substring ( option vendor-class-identifier, 0, 9);

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

Add new paths for the Secure Boot variant of OVMF as found in Fedora. --- generator/UEFI.ml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/generator/UEFI.ml b/generator/UEFI.ml index 1ff3f84d2..bca3fa1ae 100644 --- a/generator/UEFI.ml +++ b/generator/UEFI.ml @@ -52,6 +52,12 @@ let firmware = [ "/usr/share/edk2/ovmf/OVMF_VARS.fd", []; + "x86_64", +

We currently are running legacy pxe, in Centos 5.8 I am trying to develop a Dual mode (Legacy and uEFI) with Centos 6.7. I have be able to successfully PXE boot the legacy pxelinux and am having some Progress on the uEFI. Where I need help is the layout of the uEFI default file and proper use of the chain.c32. Been doing quite a bit of googling, but the uEFI pxe stuff is sparse. Any references

Hi, I need two questions answered: 1) When will PXELINUX have uEFI support? 2) With uEFI support comes IPv6 PXE support. Our latest IBM System X boxes all have IPv6 EFI-based PXE code ready to go, however the syslinux community seems to be very behind on uEFI and IPv6 integration for PXELINUX. Will PXELINUX ever support IPv6 from a uEFI network boot? I guess a 3rd question arises too: If

Hi! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram