-accelerated-execution-manager/
Best regards
Holger
Am 21.03.20 um 06:17 schrieb Holger Schranz:
Hi Jerry,
have you read the instructtions on Intel:
https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows
May be this helps you
Best regards
Holger
Am 20.03.20 um 21:22 schrieb Jerry
Hi Jerry,
have you read the instructtions on Intel:
https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows
May be this helps you
Best regards
Holger
Am 20.03.20 um 21:22 schrieb Jerry Geis:
So I tried --enable-whpx and I get Invalid option. Im on Windows 10
and QEMU 4.2.0
22/12/2016 13:33, Holger Schranz wrote:
I have installed an RH 7.7 based on kernel 3.10 and a SuSE LEAP 42.2 which
is based on kernel 4.4. Both system see the tape devices and can work.
Than I restart in the same session the VM with SLES11 SP4 (kernel 3.0.101)
and an older RH based on kernel 2.6.
can't see the tape
drives.
But all 5 VM guest systems are registered in iscsi and show the UUID of the
guest system.
Please, what should I do as a next step please?
Best regards
Holger
Am 22.12.2016 um 07:22 schrieb Fam Zheng:
On Wed, 12/21 05:44, Holger Schranz wrote:
Hi Fam,
meanwh
Hi,
sorry for an additional mail.
Attached is the iscsiadm information which Fam requested.
Best regards
Holger
Am 21.12.2016 um 12:51 schrieb Holger Schranz:
Hi Fam, John,
meanwhile i have installed the 2.8.0 from the official wiki.qemu.org
(tarball says rc4 ??).
About dmesg, I have
Hi Michael,
could it be, that the link to qemu-2.8.0.tar.bz2 is linked to the
qemu-2.8.0-rc4.tar.bz2? The link for signature seems it is correct.
Best regards
Holger
Am 20.12.2016 um 22:00 schrieb Michael Roth:
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of
the Q
Hi Fam,
meanwhile I have sent the requested QEMU CLI direct to John. Your request
I will try after the reinstall with the released version.So please wait
for a while.
Best regards
Holger
Am 21.12.2016 um 00:47 schrieb Fam Zheng:
On Tue, 12/20 17:53, Holger Schranz wrote:
Hi John,
sorry or
s
(I can't find the issue number).
Best regards
Holger
Am 19.12.2016 um 18:30 schrieb John Snow:
On 12/19/2016 04:05 AM, Holger Schranz wrote:
# Strange/wrong behavior in QEMU 2.8.0-rc4
After update from QEMU 2.6.2 to 2.8.0-rc4 the tape devices
and the corresponding medium changer are
# Strange/wrong behavior in QEMU 2.8.0-rc4
After update from QEMU 2.6.2 to 2.8.0-rc4 the tape devices
and the corresponding medium changer are no longer available
in the VM quest system.
The tape devices and the media changer are declared in the
xml-file for libvirt. Both, tape drives and medium
Hello Eric, Kevin, Paolo,
Thank you very much for the very fast help.
All works fine now!!!
Best regards and have nice weekend
Holger
Am 08.09.2016 um 19:34 schrieb Holger Schranz:
Hi Eric,
Am 08.09.2016 um 17:25 schrieb Eric Blake:
On 09/08/2016 09:27 AM, Holger Schranz wrote:
Hi Eric
Hi Eric,
Am 08.09.2016 um 17:25 schrieb Eric Blake:
On 09/08/2016 09:27 AM, Holger Schranz wrote:
Hi Eric,
Thanks a lot, it seems the patch works. The VM starting.
Should I take that as a Tested-by: line?
The test was:
1) login as root
2) cd to workdir
3) start virt-viewer: "virt-v
But this patch takes a slightly
more conservative approach, and merely guarantees that scaling
will succeed, while still using multiples of the original size
where possible. Resulting limits may still be zero in SG mode
(that is, we mostly only fix block_size used as a denominator
or which affect
as a denominator, not
all uses).
Reported-by: Holger Schranz
Signed-off-by: Eric Blake
CC: qemu-sta...@nongnu.org
---
I would really appreciate Holger testing this patch. We could
also go with the much shorter patch that just does
if (bs->sg) { return; }
at the top of iscsi_refresh_limits(),
esulting limits may still be zero in SG
mode (that is, we only fix block_size used as a denominator, not
all uses).
Reported-by: Holger Schranz
Signed-off-by: Eric Blake
CC: qemu-sta...@nongnu.org
---
I would really appreciate Holger testing this patch. We could
also go with the much shorter pa
Hello,
we need help for an issue we have sice QEMU 2.7.
May be we use the wrong mailing list. If so please let me know which
mail list we have to use to report problems in QEMU.
Best regards
Holger
===
We use the
Hello,
at our test (upgrade from qemu 2.6 -> 2.7[rc2/3/4]) the following
problem occur:
2016-08-25T09:42:32.066972+02:00 etcsvms3 systemd[1]: Starting Virtual
Machine qemu-8-VTC61CST.
2016-08-25T09:42:32.067331+02:00 etcsvms3 systemd-machined[16661]: New
machine qemu-8-VTC61CST.
2016-08-25T09:42
16 matches
Mail list logo
