similar to: app does not start but "Wine exited with a successful status"

Hello, I still have no clue what to do. jochen@rod:~$ wine .wine/drive_c/Programme/SchILD-NRW/SCHILD2000.exe Invoking /usr/lib/wine/wine.bin .wine/drive_c/Programme/SchILD-NRW/SCHILD2000.exe ... err:ole:CoGetClassObject class {00000507-0000-0010-8000-00aa006d2ea4} not registered err:ole:create_server class {00000507-0000-0010-8000-00aa006d2ea4} not registered err:ole:CoGetClassObject no

Henning Schild <henning.schild at siemens.com> writes: > 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 a

Jan Kiszka <jan.kiszka at siemens.com> writes: > On 2014-06-12 04:27, Rusty Russell wrote: >> Henning Schild <henning.schild at siemens.com> writes: >> It was also never implemented, and remains a thought experiment. >> However, implementing it in lguest should be fairly easy. > > The reason why a trusted helper, i.e. additional logic in the > hypervisor,

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> 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

On 2014-06-12 04:27, Rusty Russell wrote: > Henning Schild <henning.schild at siemens.com> writes: >> 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

I used R on OS X 10.3x quite some time with no serious problems. Sometimes R stopped when I tried to execute a bigger program. After updating to OS X to version 10.4 R worked but I still had the problem with bigger programs. Therefore I re-installed R on top of the existing R version. The installation finished properly but suddenly R did not work. Then I reinstalled OS X 10.4 because I

Vincent JARDIN <vincent.jardin at 6wind.com> 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 virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Vincent JARDIN <vincent.jardin at 6wind.com> 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 virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

On 2014-06-13 02:47, Rusty Russell wrote: > Jan Kiszka <jan.kiszka at siemens.com> writes: >> On 2014-06-12 04:27, Rusty Russell wrote: >>> Henning Schild <henning.schild at siemens.com> writes: >>> It was also never implemented, and remains a thought experiment. >>> However, implementing it in lguest should be fairly easy. >> >> The

On 2014-06-13 02:47, Rusty Russell wrote: > Jan Kiszka <jan.kiszka at siemens.com> writes: >> On 2014-06-12 04:27, Rusty Russell wrote: >>> Henning Schild <henning.schild at siemens.com> writes: >>> It was also never implemented, and remains a thought experiment. >>> However, implementing it in lguest should be fairly easy. >> >> The

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>

Hello, Using cyrus2dovecot (https://github.com/a-schild/cyrus2dovecot) I have migrated some test mailboxes from Cyrus (2.4.17) to Dovecot (2.2.9). The problem I'm having is that the seen status is in cyrus.index files, which cyrus2dovecot doesn't understand. Does anyone use cyrus2dovecot for migrations? If so, how do you deal with seen status when it is stored in the .index files?

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 virtual machines. > Ivshmem is nice and simple but does not seem to be used anymore. > And it > does not define higher level devices, like a console. FYI, ivhsmem is used here:

On Thu, 12 Jun 2014 08:48:04 +0200 Markus Armbruster <armbru at redhat.com> wrote: > Vincent JARDIN <vincent.jardin at 6wind.com> 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 virtual machines. > >> Ivshmem

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

Hi > Using cyrus2dovecot (https://github.com/a-schild/cyrus2dovecot) I have > migrated some test mailboxes from Cyrus (2.4.17) to Dovecot (2.2.9). > > The problem I'm having is that the seen status is in cyrus.index files, > which cyrus2dovecot doesn't understand. > > Does anyone use cyrus2dovecot for migrations? Yes, but this software which is not related to the

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 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 probably

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 script for qemu that takes care of suid-root and appends > arguments for pci-assign > 2. virsh qemu-monitor-command ... 'device_add pci-assign...' With any reasonably modern

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 a signaling mechanism. We would like to reuse virtio so that Linux-guests will eventually just work