Re: test Digest, Vol 203, Issue 98
Sam,
Thanks for responding.
There are two reasons: 1) virtual-manager is really slow on my system, PAINFULLY SLOW 2) I
recall reading somewhere (RedHat or qemu.org) that virtual-manager was/is deprecated.
Best regards,
George...
Date: Tue, 26 Jan 2021 16:14:50 -0800
From: Samuel Sieb <samuel(a)sieb.net>
Subject: Re: console for qemu VM running fc34 x86_64 Rawhide
To: test(a)lists.fedoraproject.org
Message-ID: <857fefa8-daa0-2dc3-695c-eb9cf7d7601b(a)sieb.net>
Content-Type: text/plain; charset=utf-8; format=flowed
On 1/26/21 4:03 PM, George R Goffe via test wrote:
I'm having some trouble with qemu and it's console for the
vm. This was working fine and then along came the later versions of the 5.10 kernels. The
"new" behavior makes a console that is about 75% bigger than the physical
monitor. It's effectively unusable.
Here is the script I use to start qemu.
qemu-system-x86_64 \
-name fc34v \
-cdrom /isos/Fedora-Everything-netinst-x86_64-Rawhide-20210122.n.0.iso \
-cpu host \
-enable-kvm \
-m 2g \
-smp 2 \
-drive file=/export/home/var-lib-libvirt-images/fc34-bt.img,format=raw \
-trace file=/root/qemu-trace-events \
-boot menu=on,reboot-timeout=15
Is there a reason you're running qemu directly instead of using
something like virt-manager?