search for: xen_dom0

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the o...

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the o...

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the o...

...ael Opdenacker <michael.opdenacker at free-electrons.com> --- arch/x86/xen/Kconfig | 5 ----- 1 file changed, 5 deletions(-) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index 1a3c765..b6401dc 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -19,11 +19,6 @@ config XEN_DOM0 depends on XEN && PCI_XEN && SWIOTLB_XEN depends on X86_LOCAL_APIC && X86_IO_APIC && ACPI && PCI -# Dummy symbol since people have come to rely on the PRIVILEGED_GUEST -# name in tools. -config XEN_PRIVILEGED_GUEST - def_bool XEN_DOM0 - config XEN_PVHV...

...ael Opdenacker <michael.opdenacker at free-electrons.com> --- arch/x86/xen/Kconfig | 5 ----- 1 file changed, 5 deletions(-) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index 1a3c765..b6401dc 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -19,11 +19,6 @@ config XEN_DOM0 depends on XEN && PCI_XEN && SWIOTLB_XEN depends on X86_LOCAL_APIC && X86_IO_APIC && ACPI && PCI -# Dummy symbol since people have come to rely on the PRIVILEGED_GUEST -# name in tools. -config XEN_PRIVILEGED_GUEST - def_bool XEN_DOM0 - config XEN_PVHV...

...ael Opdenacker <michael.opdenacker at free-electrons.com> --- arch/x86/xen/Kconfig | 5 ----- 1 file changed, 5 deletions(-) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index 1a3c765..b6401dc 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -19,11 +19,6 @@ config XEN_DOM0 depends on XEN && PCI_XEN && SWIOTLB_XEN depends on X86_LOCAL_APIC && X86_IO_APIC && ACPI && PCI -# Dummy symbol since people have come to rely on the PRIVILEGED_GUEST -# name in tools. -config XEN_PRIVILEGED_GUEST - def_bool XEN_DOM0 - config XEN_PVHV...

...ood. Hardware: Motherboard: S1200BTLR Onboard video: ServerEngines LLC Pilot III (as written in manual) CPU: Intel Xeon E3-1270v2 Software: OS: Centos 6.3 64-bit Xen: 4.2.1 Kernels tested (all with Xen Hypervisor Loaded - except 2.6.32): Kernel 2.6.32-279 (shipped with CentOS - does not support XEN_DOM0): - Screen is fast, but with 640x480 resolution. - Xorg starts with mga driver Kernel 3.0.57-1.el6.elrepo.x86_64 (from elrepo.org - with XEN_DOM0 support) - "CONFIG_DRM_MGAG200" does not exist. - Xorg starts with mga driver Kernel 3.7.1-3.el6xen.x86_64 (from here: https://www.crc.id.au/...

Hi all, this patch series introduces stolen ticks accounting for Xen on ARM. Stolen ticks are clocksource ticks that have been "stolen" from the cpu, typically because Linux is running in a virtual machine and the vcpu has been descheduled. To account for these ticks we introduce CONFIG_PARAVIRT and pv_time_ops so that we can make use of:

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Hi all, This series adds a new microcode driver for Xen. The Xen hypervisor can deal with all the low-level details of doing a microcode update (Intel vs AMD, doing all the physical CPUs present on the system, current and future, etc), so all the driver has to do is make a hypercall to upload the microcode into Xen. This only

Hi, Jeremy Since now the pv_ops domain0 is approaching, we are considering to port the dom0 power management related code, or more specifically, the Cx/Px ACPI info parsing code, to pv_ops domain0 tree, so that people can utilize Xen power management capability (Cx/PX) under pv_ops domain0. This RFC is a draft version for comments. === Overview === Requirement: Xen hypervisor need Cx/Px ACPI

Hi all, this patch series enables xen-swiotlb on arm and arm64. It has been heavily reworked compared to the previous versions in order to achieve better performances and to address review comments. We are not using dma_mark_clean to ensure coherency anymore. We call the platform implementation of map_page and unmap_page. We assume that dom0 has been mapped 1:1 (physical address == machine

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that

...the Xen + Create entries under /sys/hypervisor describing the Xen hypervisor environment. When running native or in another virtual environment, /sys/hypervisor will still be present, but will have no xen contents. @@ -270,7 +270,7 @@ config XEN_ACPI_PROCESSOR depends on XEN && XEN_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ default m help - This ACPI processor uploads Power Management information to the Xen + This ACPI processor uploads Power Management information to the Xen hypervisor. To do that the driver parses the Power Managem...

...the Xen + Create entries under /sys/hypervisor describing the Xen hypervisor environment. When running native or in another virtual environment, /sys/hypervisor will still be present, but will have no xen contents. @@ -270,7 +270,7 @@ config XEN_ACPI_PROCESSOR depends on XEN && XEN_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ default m help - This ACPI processor uploads Power Management information to the Xen + This ACPI processor uploads Power Management information to the Xen hypervisor. To do that the driver parses the Power Managem...

This time make world on Ubuntu 10.04 gives following error gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .fsimage.so.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -I../../../tools/libfsimage/common/

...>From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on: http://wiki.xensource.com/xenwiki/XenParavirtOps Then I did make menuconfig and added: XEN_DOM0 XEN_BLKDEV_BACKEND here are the two grub entries I tried title Xen 3.4-unstable / Ubuntu 8.10, kernel 2.6.28-rc6-tip root (hd0,0) kernel /boot/xen-3.4-unstable.gz loglvl=all guest_loglvl=all dom0_max_vcpus=1 com1=115200,8n1 console=com1 noreboot dom0_mem=512M module /boot/vmlinuz-2.6.28-rc6-...