search for: c180

...onnections succesfully, but I experienced performance problem during the connection phase. It seems, that the client needs quite some computer time just after debug: Got SSH2_MSG_KEX_DH_GEX_GROUP. By inserting test-printouts, I verifyed that the dh_gen_key(dh); call seems to take that long. On a HP C180 it takes around 8 seconds. OpenSSH is built without optimization but as far as I could see, the time is spent in the OpenSSL library (built with maximum optimization). There are other places in which 3-4 seconds are spent each. Can somebody verify these observations? Setup is the default setting....

...mory at febf5000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] MSI-X: Enable+ Count=2 Masked- Kernel driver in use: virtio-pci 00:09.0 SCSI storage controller: Red Hat, Inc Device 1004 Subsystem: Red Hat, Inc Device 0008 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at c180 [size=64] Memory at febf6000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] MSI-X: Enable+ Count=2 Masked- Kernel driver in use: virtio-pci 00:0a.0 SCSI storage controller: Red Hat, Inc Device 1004 Subsystem: Red Hat, Inc Device 0008 Flags: bus master, fast devsel, latency 0, IRQ 10...

...mory at febf5000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] MSI-X: Enable+ Count=2 Masked- Kernel driver in use: virtio-pci 00:09.0 SCSI storage controller: Red Hat, Inc Device 1004 Subsystem: Red Hat, Inc Device 0008 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at c180 [size=64] Memory at febf6000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] MSI-X: Enable+ Count=2 Masked- Kernel driver in use: virtio-pci 00:0a.0 SCSI storage controller: Red Hat, Inc Device 1004 Subsystem: Red Hat, Inc Device 0008 Flags: bus master, fast devsel, latency 0, IRQ 10...

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB