similar to: xen and libvirt

Hi Does someone know how it is possible these parameters: e820_host max_grant_frames to set with libvirt xml config? I use them with xl config but I want to change to libvirt config/tools. (with libvirt 4.10 it is possible to start pvh domains) -- ------ Greetz

Hi I need the e820_host option for a passthrough of an digitaldevices dvb-s2 card. Without this I'cant initialize the card in the domU. On an all my domU's with high IO load like an file server I need to set max_grant_frames = 64 or higher. Without this I get a lot of messages on dom0/domU and kernel exceptions. I've read it should be ok to set it = 256 on all domU's

On 1/4/19 9:14 AM, Christoph wrote: > Hi > > Does someone know how it is possible these parameters: > > e820_host > max_grant_frames > > to set with libvirt xml config? Currently, those settings are not supported by libvirt. Do you need to adjust them for PCI passthrough to PV domains? I took a quick peek at xl.cfg(5) and based on the description of those settings

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2

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

Hi, On 10/23/18 7:34 PM, Ian Jackson wrote: > Control: retitle -1 max grant frames problem (domu freeze with linux-image-4.9.0-4-amd64) > Control: severity -1 important > Control: reassign -1 src:xen 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 my last comment in this bts bug was about:

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

Hi all, I 've such a config on xen (4.14): name = "marax.chao5.int" uuid = "e0de3cb7-3937-417d-8d63-b0993b377b6a" maxmem = 16384 memory = 16384 kernel = '/usr/lib64/xen/boot/hvmloader' vcpus = 16 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vif = [

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

It seems to be a problem with kernel... I use the kernel-ml there (5.5.6)... with kernel from centos-virt repo (4.9.*) it works without this problem... --- ------ Greetz Am 27.02.2020 07:50, schrieb Christoph: > Hi > > I cant start a hvm domU with more than 3 nic's configured... why? it is > a bug? > With previous versions it was possible... > > here the config - it is

Hello @ all, i wonder if there is any support for Xen PVH (https://wiki.xen.org/wiki/Xen_Project_Software_Overview) within libvirt. If i parse a xen native domU config file with 'virsh domxml-from-native' in which i set type='pvh' it changes it in the libvirt xml output to normal pv. Also the docs of libvirt do not state something like pvh. I am currently running Xen 4.10.0 with

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2

Hi it is possible to use xen and spice already? If yes is there any howto or doc how? If I turn on spice in cfg of a hvm domU, I get this error: Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail:

On Thu, Mar 7, 2019 at 1:42 PM Sarah Newman <srn at prgmr.com> wrote: > On 3/7/19 10:30 AM, Akemi Yagi wrote: > > On Thu, Mar 7, 2019 at 9:42 AM George Dunlap <dunlapg at umich.edu> wrote: > >> > >> Hey all, > >> > >> We've been on 4.9 for some time now, and while it's still supported, I > >> think it's time to start

http://107.185.144.55/xen/cent7/dom0/RPMS/stable-4.6/mock/ above is a build of upstream xen with this `configure` including spice support:./configure --enable-systemd --prefix=/usr --enable-xsmpolicy --enable-ocamltools \ ? --libdir=%{_libdir} --enable-efi \ ? --with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir" there is no associated libvirt buildIncluded are patches up

On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: > In normal cases PCI passthrough in PV guests requires to start the guest > with e820_host=1. So it should be rather easy to limit allocating the > 64MB in PV guests to the cases where the memory map has non-RAM regions > especially in the first 1MB of the memory. > > This will cover even hotplug cases. The only case

On 07.06.23 15:12, Christoph Hellwig wrote: > On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: >> In normal cases PCI passthrough in PV guests requires to start the guest >> with e820_host=1. So it should be rather easy to limit allocating the >> 64MB in PV guests to the cases where the memory map has non-RAM regions >> especially in the first 1MB of the

Hey all, We've been on 4.9 for some time now, and while it's still supported, I think it's time to start thinking about upgrading, and I'd like input from the community about which version to move up to. 4.19 has been out for almost 5 months now. It will include PVH domU support, and PVH dom0 support in what _is believed_ to be the final form; so when the Virt SIG moves to a

On Thu, Mar 7, 2019 at 9:42 AM George Dunlap <dunlapg at umich.edu> wrote: > > Hey all, > > We've been on 4.9 for some time now, and while it's still supported, I > think it's time to start thinking about upgrading, and I'd like input > from the community about which version to move up to. > > 4.19 has been out for almost 5 months now. It will include

On 3/7/19 10:30 AM, Akemi Yagi wrote: > On Thu, Mar 7, 2019 at 9:42 AM George Dunlap <dunlapg at umich.edu> wrote: >> >> Hey all, >> >> We've been on 4.9 for some time now, and while it's still supported, I >> think it's time to start thinking about upgrading, and I'd like input >> from the community about which version to move up to.