Writing a snapshot can be done by typing 'C-a s'. Where do you type this
and are these normal uppercase and lowercase letters? Are the hyphen and
space an integral part of the command?
Frans.
working either in the graphical session.
Any more suggestions?
Frans.
On 06/13/2014 04:45 PM, Darac Marjal wrote:
On Fri, Jun 13, 2014 at 03:39:28PM +0200, Frans de Boer wrote:
Writing a snapshot can be done by typing 'C-a s'. Where do you type this and
are these normal uppercase and
Ctrl-a s is not working either in the graphical session.
Any more suggestions?
Frans.
On 06/13/2014 04:45 PM, Darac Marjal wrote:
On Fri, Jun 13, 2014 at 03:39:28PM +0200, Frans de Boer wrote:
Writing a snapshot can be done by typing 'C-a s'. Where do you type
this and
are t
After having run qemu with the -snapshot option, I tried to run another
time without the -snapshot option, only to see that qemu reported that
the device is empty.
Each time running again with that option, brings back a working system,
but never again without that option.
I like to know what
I do not understand: with the -snapshot option it is reading the image
correctly, but without it it is corrupted?
The image worked for years, once I started using the -snapshot option it
can no longer be used without it.
Frans.
On 06/17/2014 04:17 PM, Dale R. Worley wrote:
From: Frans de
. Morley wrote:
From: Frans de Boer
After having run qemu with the -snapshot option, I tried to run another
time without the -snapshot option, only to see that qemu reported that
the device is empty.
Each time running again with that option, brings back a working system,
but never again without that
Dear reader,
I am using the GTK3 UI now some time. However, when I go to fullscreen
mode, my cursor gets locked inside the QEMU window and can get out
except by aborting QEMU. This behavior is with 2.4.0.1 and 2.4.1. I
tried the master too (before the 2.4.1 release), where there is no
problem
On 11/05/2015 09:06 AM, Narcis Garcia wrote:
I suppose you are using SDL display.
Have you tried to press Ctrl+Alt to release mouse grab?
El 04/11/15 a les 21:08, Frans de Boer ha escrit:
Dear reader,
I am using the GTK3 UI now some time. However, when I go to fullscreen
mode, my cursor gets
LS,
I am having stability issues with KVM+QEMU+Win10 and Citrix Receiver.
Native Win10 and Citrix Rec. is working just fine. However, generating
fast interrupts by using the mouse or keyboard freezes the Citrix Engine.
I am looking where in the Qemu source I can set a variable to increase
th
...@nongnu.org] Namens Frans de
Boer
Verzonden: maandag 4 juli 2016 16:55
Aan: qemu-discuss@nongnu.org
Onderwerp: [Qemu-discuss] Stack size
LS,
I am having stability issues with KVM+QEMU+Win10 and Citrix Receiver.
Native Win10 and Citrix Rec. is working just fine. However, generating fast
interrupts
Ever since the release of qemu 3.0, the booting of win10 under qemu 3.0
freezes in it's initial stage. The Window is showed but there is no
indication of any progress or error report.
Below is the same qemu command is used as under qemu 2.12.1, which
functions properly there.
qemu-system-x86
On 9/14/18 1:17 PM, Nerijus Baliunas wrote:
On Fri, 14 Sep 2018 13:02:07 +0200 Frans de Boer wrote:
Ever since the release of qemu 3.0, the booting of win10 under qemu 3.0
freezes in it's initial stage. The Window is showed but there is no
indication of any progress or error report.
Bel
On 9/14/18 1:31 PM, Frans de Boer wrote:
On 9/14/18 1:17 PM, Nerijus Baliunas wrote:
On Fri, 14 Sep 2018 13:02:07 +0200 Frans de Boer
wrote:
Ever since the release of qemu 3.0, the booting of win10 under qemu 3.0
freezes in it's initial stage. The Window is showed but there is no
indic
LS,
I have mentioned this in another thread, but would like to draw
attention to next issue separately:
Using '-cpu host' on a system with a AMD Phenom II causes the quest
system to freeze during the boot phase.
Removing this argument from the command line resolves this because the
quest now
On 9/29/18 9:20 AM, Frans de Boer wrote:
LS,
I have mentioned this in another thread, but would like to draw
attention to next issue separately:
Using '-cpu host' on a system with a AMD Phenom II causes the quest
system to freeze during the boot phase.
Removing this argumen
LS,
When using spice in a dual monitor environment (under Linux), the VM
starts two windows using remote-viewer. However, it would be nice if the
second window is automatically placed on the second monitor.
I did not find any switch to accommodate this, but maybe I am
overlooking something?
LS,
Another observation:
Using "qemu -display gtk -daemonize -spice ..." results in the
display of three windows: the original QEMU window and two remote-viewer
windows in a dual monitor setting.
Leaving out the "-display gtk" portion, results in only two
remote-viewer windows.
It look
I use QEMU already some years for my VM's running servers and sometimes
even Windows XP. The later is not a real pleasure but required because
most video's are flash based and are not well handled under Linux. Then
again I switch back to Linux/Lightspark because streaming video and
sound is rea
LS,
After some months I needed Qemu with two displays again. The last time I
used it was with the latest 3.x version, without problem.
You guessed already that it did not work anymore. So, I started to add
the "-display spice-app", changed to sockets after finding out that
communication via
On 10-09-19 08:05, Brad Campbell wrote:
On 9/9/19 4:54 pm, Frans de Boer wrote:
LS,
After some months I needed Qemu with two displays again. The last
time I used it was with the latest 3.x version, without problem.
You guessed already that it did not work anymore. So, I started to
add the
On 10-09-19 10:49, Actiu informatica wrote:
Does anybody know how to make M.Thunderbird to use "List-Id" header to
label any mailing list (without having to setup for each mailing list).
El 10/9/19 a les 10:38, Peter Maydell ha escrit:
Hi; this is an announcement to let you know that in future
On 10-09-19 14:48, Narcis Garcia wrote:
El 10/9/19 a les 12:49, Frans de Boer ha escrit:
On 10-09-19 10:49, Actiu informatica wrote:
Does anybody know how to make M.Thunderbird to use "List-Id" header to
label any mailing list (without having to setup for each mailing list).
El 10/
On 10-09-19 16:02, Narcis Garcia wrote:
El 10/9/19 a les 15:44, Frans de Boer ha escrit:
On 10-09-19 14:48, Narcis Garcia wrote:
El 10/9/19 a les 12:49, Frans de Boer ha escrit:
On 10-09-19 10:49, Actiu informatica wrote:
Does anybody know how to make M.Thunderbird to use "List-Id"
On 10-09-19 09:53, Frans de Boer wrote:
On 10-09-19 08:05, Brad Campbell wrote:
On 9/9/19 4:54 pm, Frans de Boer wrote:
LS,
After some months I needed Qemu with two displays again. The last
time I used it was with the latest 3.x version, without problem.
You guessed already that it did not
LS,
I was trying to use qemu 4.1. under opensuse tumbleweed, had compiled it
myself for opensuse 15.1, but none is able to get a network connection.
When I switched back to qemu 3.1.1, there is no problem.
I tried various settings like '-net nic.', '-nic tap' and even
'-netdev ..', t
On 18-10-2019 20:37, Frans de Boer wrote:
LS,
I was trying to use qemu 4.1. under opensuse tumbleweed, had compiled
it myself for opensuse 15.1, but none is able to get a network
connection.
When I switched back to qemu 3.1.1, there is no problem.
I tried various settings like '-ne
LS,
I get the following error during tests:
GLib-GIO:ERROR:../gio/gtestdbus.c:619:start_daemon: assertion failed
(error == NULL): Failed to execute child process
?/mnt/rhome/frans-tw/data/projects/1/kernel/qemu/git-qemu/tests/dbus-vmstate-daemon.sh?
(No such file or directory) (g-exec-error-q
LS,
I get the following error during tests:
GLib-GIO:ERROR:../gio/gtestdbus.c:619:start_daemon: assertion failed
(error == NULL): Failed to execute child process
?/mnt/rhome/frans-tw/data/projects/1/kernel/qemu/git-qemu/tests/dbus-vmstate-daemon.sh?
(No such file or directory) (g-exec-error-q
LS,
The latest version of Qemu I can use is 4.1.1. I tried 4.2.0 from the
vendor (openSUSE TW), compiled it myself, but I can't get a network up
and running.
This is the response I get:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp
cores=2,threads=1,sockets=1 -enable-kvm -m
LS,
I have a puzzle for which I seek some assistance for the following case:
I have build a cross-compiler for - say - the i586 architecture,
including glibc and some others. The next step would be to transfer this
together with other sources to the target machine and finish the
building of a
On 8/11/21 6:26 PM, Philippe Mathieu-Daudé wrote:
On 8/11/21 1:15 PM, Frans de Boer wrote:
LS,
I have a puzzle for which I seek some assistance for the following case:
I have build a cross-compiler for - say - the i586 architecture,
including glibc and some others. The next step would be to
On 8/11/21 6:11 PM, Peter Maydell wrote:
On Wed, 11 Aug 2021 at 12:20, Frans de Boer wrote:
However when I start:
qemu-i386 /path to i386 sbin/chroot " /usr/bin/env
-i ... /usr/bin/bash --login
I end up that the chroot program complains that it can't find
/lib/libc.s
LS,
Suppose I want to simulate, using qemu, a Ryzen znver3 processor, what
-cpu flag do I set?
The current list for qemu does not include any Ryzen/Threadripper cpu.
So, I can optimize code using -mtune of -march for gcc, but these flags
do not correspond with qemu's processor list.
Regards,
On 8/14/21 12:19 PM, Frans de Boer wrote:
LS,
Suppose I want to simulate, using qemu, a Ryzen znver3 processor, what
-cpu flag do I set?
The current list for qemu does not include any Ryzen/Threadripper cpu.
So, I can optimize code using -mtune of -march for gcc, but these
flags do not
LS,
I try to build qemu-aarch64-static, but all I get are errors;
6.1.0 "big/little test failed"
6.0.0 "ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
You probably need to set PKG_CONFIG_LIBDIR
to point to the right pkg-config files for your
build target"
/Settin
On 8/27/21 12:22, Peter Maydell wrote:
On Fri, 27 Aug 2021 at 10:34, Frans de Boer wrote:
I try to build qemu-aarch64-static, but all I get are errors;
6.1.0"big/little test failed"
6.0.0 "ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.
You
On 8/28/21 12:47, Peter Maydell wrote:
On Fri, 27 Aug 2021 at 19:49, Frans de Boer wrote:
Following your pointers, I noticed that it was all about missing static
libraries/header files. The error messages where not helpful at all. config.log
provided some pointers.
Yeah. We tend to assume
LS,
When I use qemu-aarch64to start a chroot jail and within the jail use
qemu-aarch64-binfmt to cope with the different binary file headers, I
can't use bash properly.
That is, the -r and -x flags do not give the normal response. I tested
also with -a, -d, -f, -e and -s, and they worked as
On 9/4/21 10:31, Frans de Boer wrote:
LS,
When I use qemu-aarch64to start a chroot jail and within the jail use
qemu-aarch64-binfmt to cope with the different binary file headers, I
can't use bash properly.
That is, the -r and -x flags do not give the normal response. I tested
also wi
On 9/5/21 21:18, Ken Moffat wrote:
On Sun, Sep 05, 2021 at 08:24:08PM +0200, Frans de Boer wrote:
On 9/4/21 10:31, Frans de Boer wrote:
LS,
When I use qemu-aarch64to start a chroot jail and within the jail use
qemu-aarch64-binfmt to cope with the different binary file headers, I
can'
LS,
OK, 32-bit systems can't handle more than 4GB memory. So, I specify '-m
4096' and still get only 2GB. Is this (very) old bug still not resolved
or is it a feature now?
Regards, Frans.
--
A: Yes, just like thatA: Ja, net zo
Q: Oh, Just like reading a book backw
On 23/11/2021 09:27, Narcis Garcia wrote:
Some 32-bit system can't handle more than 512 MiB of RAM, and some
32-bit systems can handle up to 64 GiB.
This is not related to memory assigned by Qemu to VE.
Narcis Garcia
El 22/11/21 a les 18:38, Frans de Boer ha escrit:
LS,
OK, 32-bit sy
On 23/11/2021 11:44, Narcis Garcia wrote:
El 23/11/21 a les 10:03, Frans de Boer ha escrit:
On 23/11/2021 09:27, Narcis Garcia wrote:
Some 32-bit system can't handle more than 512 MiB of RAM, and some
32-bit systems can handle up to 64 GiB.
This is not related to memory assigned by Qe
On 24/11/2021 09:42, Narcis Garcia wrote:
El 23/11/21 a les 14:33, Frans de Boer ha escrit:
On 23/11/2021 11:44, Narcis Garcia wrote:
El 23/11/21 a les 10:03, Frans de Boer ha escrit:
On 23/11/2021 09:27, Narcis Garcia wrote:
Some 32-bit system can't handle more than 512 MiB of RAM, and
On 29/11/2021 08:46, Narcis Garcia wrote:
El 28/11/21 a les 19:42, Frans de Boer ha escrit:
On 24/11/2021 09:42, Narcis Garcia wrote:
El 23/11/21 a les 14:33, Frans de Boer ha escrit:
On 23/11/2021 11:44, Narcis Garcia wrote:
El 23/11/21 a les 10:03, Frans de Boer ha escrit:
On 23/11/2021
On 29/11/2021 09:36, Narcis Garcia wrote:
El 29/11/21 a les 9:33, Frans de Boer ha escrit:
On 29/11/2021 08:46, Narcis Garcia wrote:
El 28/11/21 a les 19:42, Frans de Boer ha escrit:
On 24/11/2021 09:42, Narcis Garcia wrote:
El 23/11/21 a les 14:33, Frans de Boer ha escrit:
On 23/11/2021 11
On 29/11/2021 10:13, Frans de Boer wrote:
On 29/11/2021 09:36, Narcis Garcia wrote:
El 29/11/21 a les 9:33, Frans de Boer ha escrit:
On 29/11/2021 08:46, Narcis Garcia wrote:
El 28/11/21 a les 19:42, Frans de Boer ha escrit:
On 24/11/2021 09:42, Narcis Garcia wrote:
El 23/11/21 a les 14:33
47 matches
Mail list logo
