similar to: Re: Problem with xen config

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 = [

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1346428441 -3600 # Node ID ddde6c2c45de8e60518aafa077f0f3867ff68e17 # Parent ccbee5bcb31b72706497725381f4e6836b9df657 libxl/xl: implement support for guest iooprt and irq permissions. This is useful for passing legacy ISA devices (e.g. com ports, parallel ports) to guests. Supported syntax is as described in

Add support for mapping hardware io memory into domains via domain config files. The syntax is iomem=[PAGE,NUM_PAGES] Signed off by Matthew Fioravante: matthew.fioravante@jhuapl.edu --- Changes from previous * Rebased onto latest xen-unstable * Rewrote the feature to mimic the style used by iports and irqs in current libxl * Updated xl.cfg manpage * removed the redundant "allow"

Hi everyone, after following in the footsteps of the following discussion (http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00106.html) I had been able to turn my GTX 480 into a Quadro 6000. When I VT-d passthrough it to a Debian jessie VM it shows up fine and CUDA 5.5 seems to function properly up to a point: lspci -v: 00:04.0 VGA compatible controller: NVIDIA Corporation GF100GL

The xen_platform_pci xl configuration parameter currently has no effect on upstream QEMU; creation of the platform device is hardcoded. I have created a patch to QEMU to remove this hardcoded creation. This patch specifies the appropriate -device argument on the QEMU command line (and hence creates the device) only when xen_platform_pci is true. Signed-off-by: Paul Durrant

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

Jim, Thanks a lot for your confirmation. Could you also please explain if the issue can be ever fixed, if it's possible to make some patch to fix it? Is it libvirt-specific bug or Libvirt development team rely on some other developers of libxl code...etc? I'm asking because XL tools works fine and I wonder if XL uses the same libxl libraries , doesn't it? Lastly is the issue is going

Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. Creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. It requires an usb controller and if not defined will automatically adds an usb2 controller. Changes from v2: - updated for usbversion patch v7 - now usbredirection cannot be used with usb and

I know these are mostly gamers but they have a lot of experience doing PCI pass though: https://discord.gg/du9ecG I have found them extremely helpful in the past doing libvirt PCI passthough. *Paul O'Rorke* On 2020-02-05 10:13 a.m., Jim Fehlig wrote: > On 2/4/20 1:04 AM, Christoph wrote: >> this config does not work... why? > > Without more details, I don't know why

Hi everyone, after following in the footsteps of the following discussion (http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00106.html) I had been able to turn my GTX 480 into a Quadro 6000. When I VT-d passthrough it to a Debian jessie VM it shows up fine and CUDA 5.5 seems to function properly up to a point: lspci -v: 00:04.0 VGA compatible controller: NVIDIA Corporation GF100GL

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

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

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, I'm looking for an example configuration for a PVHVM domU that works with 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers causes 3 warnings and some errors: WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware WARNING: ignoring device_model directive. WARNING: Use

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the

On Thu, Feb 20, 2020 at 12:40:35PM +0100, Christoph wrote: >I use centos 7 (7.7.1908). > >these pkgs are installed: > >xen-hypervisor-4.12.2-1.el7.x86_64 >xen-devel-4.12.2-1.el7.x86_64 >qemu-xen-4.12.1-1.el7.x86_64 >xen-runtime-4.12.2-1.el7.x86_64 >xen-licenses-4.12.2-1.el7.x86_64 >xen-4.12.2-1.el7.x86_64 >xen-libs-4.12.2-1.el7.x86_64

[adding Anthony PERARD to cc since his name is next to xen-4.12.2-1.el7's ChangeLog entry] Hi, Anthony! On Thu, Feb 20, 2020 at 07:10:38PM +0100, Christoph wrote: >https://wiki.centos.org/HowTos/Xen/Xen4QuickStart > >configure:53501: checking for LIBXL >configure:53508: $PKG_CONFIG --exists --print-errors "xenlight >= 4.6.0" >Package xenblktapctl was not found in