similar to: Problems moving qemu machine to libvirt

From: "Anthony G. Basile" <basile at opensource.dyc.edu> The current configure.in file does not correctly make use of these macros. The resulting configure file will therefore enable an item even if --disable-FEATURE is given. This patch restores the intended behavior. --- configure.in | 50 +++++++++++++++++++++++++++++++++----------------- 1 files changed, 33 insertions(+),

Hi guys and gals, I just wanted to compile tinc with vde interface, but found src/vde is missing in tar balls of tinc-1.0.16 and tinc-1.0.14. I remember once I have compiled vde on tinc-1.0.14. Is it removed intentionally? I couldn't find an update in ChangeLog. Besides, the newest code in git fails to compile, because of a redefined extern static variable in src/vde/device.c. I need to

--- In english --- Hello! I am to implement a new architecture of the network in my company but I do not know right where to start ... need help! Currently 90% of my servers are virtual machines under Xen. I have many valid IP networks and all Hypervisors are configured in bridge mode, to simplify. We have 3 VMWare ESX Hypervisor also in bridge mode. Some networks are exclusive to certain

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

Hi, Can any one explain what the following can be used for ? I want to know , so that i can use it in the future :-) > Add support for VDE through libvdeplug. > > When compiled with vde/device.c, tinc will connect to a vde_switch instance > instead of using a tun/tap device. Perry

Hi, I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. I am not interested in connecting the VDE to the outside world. I have created a FW machine using macvtap. To this machine I would like to attach machines from different zones (dmz, prod, cust). I was thinking on using VDE and vlans (FW would

Hi! Just in case somebody else needs this. Below is a patch which allows building qemu-kvm-0.15 unter CentOS 5.6 with vanilla kernel 2.6.35.14 and (optionally) vde2 [1]. FYI: qemu-kvm-0.15 compiles fine on CentOS 6 with distro-kernel, no patches needed. For CentOS 5.6, unpack 0.15 qemu-kvm tarball [2], apply the path below, configure and compile. Make sure to export the kernel include path

Hi Erik, thanks for the solution provided. I tried that but unfortunately it spits out this error message: > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain > vm.startup() > File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup > self._backend.create() >

From: Marc Carino <marc.ceeeee@gmail.com> Let Xen recognize the Broadcom Brahma-B15 CPU by adding the appropriate MIDR mask to the initialization phase. Further, ensure that the console output properly reports the CPU manufacturer as "Broadcom Corporation". Signed-off-by: Marc Carino <marc.ceeeee@gmail.com> --- xen/arch/arm/arm32/proc-v7.S | 8 ++++++++

With all the talk about using lld on the list, I thought it would be interesting to try using it in my clang based ELLCC cross compilation tool chain. http://ellcc.org The change was simple, since I use configuration files to tell clang how to compile, where to find libraries, etc. I described the config files here: http://ellcc.org/blog/?p=13246 All I had to do was change the linker

On Fri, Oct 28, 2016 at 2:56 PM, Richard Pennington via cfe-dev < cfe-dev at lists.llvm.org> wrote: > With all the talk about using lld on the list, I thought it would be > interesting to try using it in my clang based ELLCC cross compilation tool > chain. http://ellcc.org > > The change was simple, since I use configuration files to tell clang how > to compile, where to

These series patch enable Allwinner A31(code name sun6i) support in assemble. with these patches, the cpu 0 of sun6i SOC could successful boot into the c environment. Bamvor Jian Zhang (4): xen/arm: introduce Cortex-A7 support xen/arm: introduce Allwinner sun6i SOC basic support xen/arm: enable early printk for sun6i xen/arm: enable switch to hyper mode for sun6i xen/arch/arm/Rules.mk

Hi, I would like to use SafeStack sanitize option on ARM platform. Since Linux libc does not implement such functionality (in opposite to FreeBSD or Android), I need to use SafeStack compiler RT library. Unfortunately I've noticed that libclang_rt.safestack is not compiled/built for ARM platform. Looking into cmake file: "set(ALL_SAFESTACK_SUPPORTED_ARCH ${X86} ${X86_64} ${ARM64}

Hello, This is the second version of this patch series. I only implement the VPF context switch support for arm32 and add dummy function to avoid compilation on arm64. I have switched the order of the patch because the old second one can be applied alone and the patch are cleaner :). For all the changes see each patch. Cheers, Julien Grall (2): xen/arm: don''t enable VFP on XEN

Hi Ian, I am trying to add supporting dumping 32-bit guest on arm32 to see what happened in my dom0 kernel when booting. It seems gvirt_to_maddr() is not workable under arm32. But why has it been implemented both in include/asm-arm/arm{32,64}/page.h? Thanks. Baozi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

hello, in my windows vm i installed qemu-guest-agent and rebootet the vm. In the settings for the vm i set via virt-manager a new channel "unix socket" "org.qemu.guest_agent.0" "virtio". when i try to do a snapshot via shell i get: virsh snapshot-create-as --domain win7new win7new-snap1 --disk-only --atomic --quiesce error: Guest agent is not responding:

Hi, This is the fifth version of this patch series. With the Versatile Express TC2, it''s possible to boot only with A7 or A15. If the user choose to boot with only A7, the CPU ID will start at 0x100. As Xen relies on it to set the logical ID and the GIC, it won''t be possible to use Xen with this use case. This patch series is divided in 3 parts: - Patch 1: prepare Xen

On 28 October 2016 at 23:02, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Awesome results! I'm surprised! LLD is barely working on ARM at the moment. :) > I wonder if ARM32 BE is a real thing. I know that the processor is > bi-endian, but is there any system that uses ARM32 in big-endian mode? Yes... it is "a thing". :) ARM has two modes: BE32 and

On Fri, 14 Sep 2018, Arnd Bergmann wrote: > On Fri, Sep 14, 2018 at 2:52 PM Thomas Gleixner <tglx at linutronix.de> wrote: > A couple of architectures (s390, ia64, riscv, powerpc, arm64) > implement the vdso as assembler code at the moment, so they > won't be as easy to consolidate (other than outright replacing all > the code). > > The other five: >

Hi all, I'm working on the CoreCLR project, coordinating a community effort to produce an Android port of Microsoft's open-source version of the CLR.  A major part of that is getting everything to run on the ARM32 architecture, which is by far the most common CPU for Android devices. A couple weeks ago, Ben Pye, a developer working on the ARM32 stuff, found and reported a bug related to