Re: [Qemu-devel] pci-assign fails with read error on config-space file

2016-11-02 Thread Henning Schild
Am Wed, 2 Nov 2016 09:54:16 + schrieb "Daniel P. Berrange" : > On Fri, Oct 28, 2016 at 01:28:19PM +0200, Henning Schild wrote: > > Hey, > > > > i am running an unusual setup where i assign pci devices behind the > > back of libvirt. I have two options to

Re: [Qemu-devel] [libvirt-users] pci-assign fails with read error on config-space file

2016-11-02 Thread Henning Schild
Am Fri, 28 Oct 2016 11:25:55 -0400 schrieb Laine Stump : > On 10/28/2016 07:28 AM, Henning Schild wrote: > > Hey, > > > > i am running an unusual setup where i assign pci devices behind the > > back of libvirt. I have two options to do that: > > 1. a wrapper s

Re: [Qemu-devel] pci-assign fails with read error on config-space file

2016-11-02 Thread Henning Schild
Am Fri, 28 Oct 2016 17:22:41 +0200 schrieb Laszlo Ersek : > On 10/28/16 13:28, Henning Schild wrote: > > Hey, > > > > i am running an unusual setup where i assign pci devices behind the > > back of libvirt. I have two options to do that: > > 1. a wrapper script

[Qemu-devel] pci-assign fails with read error on config-space file

2016-10-28 Thread Henning Schild
Hey, i am running an unusual setup where i assign pci devices behind the back of libvirt. I have two options to do that: 1. a wrapper script for qemu that takes care of suid-root and appends arguments for pci-assign 2. virsh qemu-monitor-command ... 'device_add pci-assign...' I know i should prob

Re: [Qemu-devel] Using virtio for inter-VM communication

2014-06-12 Thread Henning Schild
On Thu, 12 Jun 2014 08:48:04 +0200 Markus Armbruster wrote: > Vincent JARDIN writes: > > > On 10/06/2014 18:48, Henning Schild wrote:> Hi, > >> In a first prototype i implemented a ivshmem[2] device for the > >> hypervisor. That way we can share memory between

[Qemu-devel] Using virtio for inter-VM communication

2014-06-10 Thread Henning Schild
Hi, i am working on the jailhouse[1] project and am currently looking at inter-VM communication. We want to connect guests directly with virtual consoles based on shared memory. The code complexity in the hypervisor should be minimal, it should just make the shared memory discoverable and provide

Re: [Qemu-devel] [PATCH] fix entry pointer for ELF kernels loaded with -kernel option

2012-09-05 Thread Henning Schild
Find a hopefully proper patch attached. Take it or leave it. Signed-off-by: Henning Schild --- hw/elf_ops.h | 11 +++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/hw/elf_ops.h b/hw/elf_ops.h index fa65ce2..731a983 100644 --- a/hw/elf_ops.h +++ b/hw/elf_ops.h

[Qemu-devel] [PATCH] fix entry pointer for ELF kernels loaded with -kernel option

2012-09-05 Thread Henning Schild
This patch fixes a bug in qemu which prevents Multiboot ELF kernels from being loaded with the -kernel option. Find a full description of the problem here https://bugs.launchpad.net/qemu/+bug/1044727 . --- hw/elf_ops.h | 10 ++ 1 files changed, 10 insertions(+), 0 deletions(-) diff

[Qemu-devel] [Bug 1044727] [NEW] -kernel does not work for multiboot ELF kernels

2012-09-01 Thread Henning Schild
Public bug reported: The multiboot header of a kernel image can contain the entry point and memory segment information. If it does not the kernel should have an ELF header that describes the memory segments and contains the entry point. http://www.gnu.org/software/grub/manual/multiboot/multiboot.

[Qemu-devel] [Bug 1030807] Re: PCI host bridge should ignore 1- and 2-byte I/O accesses

2012-07-30 Thread Henning Schild
I tried the following quick fix but the BIOS does not seem to like that. ** Attachment added: "pci" https://bugs.launchpad.net/qemu/+bug/1030807/+attachment/3242137/+files/pci -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https

[Qemu-devel] [Bug 1030807] [NEW] PCI host bridge should ignore 1- and 2-byte I/O accesses

2012-07-30 Thread Henning Schild
Public bug reported: In PCI there are two IO modes. Deprecated Mode2 that uses single byte IO and Mode1 that uses 4byte IO. According to the spec a host bridge that supports Mode1 should ignore all IO that is not 4bytes. > Anytime a host bridge sees a full DWORD I/O write from the host to > CON