I'm getting a 15 second delay on every VM boot when using the
ArchLinux kernel and using the virtio-scsi-pci system.
QEMU emulator version 2.12.0 running on Arch Linux (4.17.4 kernel),
booting the same.
I run qemu like so:
qemu-system-x86_64 \
-nodefaults \
-machine type=pc,accel=kvm -smp
m the mainline ppa on
Ubuntu 18.04 and now there is a delay. It's only 7.5 seconds but still
noticeable. There was previously no delay with the 4.15 kernel.
Definitely seems like it could be something introduced in kernel 4.16.
Chris
tend this limit, or where I find the
limitation in the code? Mybe this limit is not directly found in qemu.
But if I start a regular vncserver, I don't have any limit.
Thanks very much in advance for any help on this problem.
Best regards, -chris-
.18 Mbit/sec <<< wguest to host, e1000, Jumbo-4088
1.25 GBit/sec <<< host to wguest, e1000, Jumbo-4088
3.60 Mbit/sec <<< wguest to host, virtio, Jumbo-4088
1.43 GBit/sec <<< host to wguest, virtio, Jumbo-4088
The transfer rates are measured using basic iperf:
server# iperf -s
client# iperf -c ${server} -i 5 -t 60
Cheers,
Chris
Hi,
I'm using a system where I need to be able to netboot via eth1.
Under virtualbox I can use the "VBoxManage modifyvm --nicbootprio2 1"
command to make it attempt to netboot over eth1 before any of the other
nics.
Is there a way to do anything similar with qemu?
Thanks,
Chris
get it
to use my back-end driver, but if this is the correct approach, I don't
understand what I need to edit when I rebuild.
A couple questions:
1. Is my current approach correct?
2. What do I need to do to get my front-end and back-end drivers
communicating with each other?
Regards,
Chris
roblem.
What should I be looking at to find out what's actually going wrong?
Cheers,
Chris
o the list.)
Thanks,
Chris
bvirt support it yet?
Any information would be helpful.
Thanks,
Chris
this.
Thank you for your time; I appreciate any feedback.
Chris
=n1,br=br0 -device virtio-net-pci,netdev=n1
in my qemu-system-x86_64 command (which I run as root).
But this doesn't set up networking correctly in the guest machine. I get
message
W: /etc/qemu-ifup: no bridge for guest interface found
Can anyone help me get my configuration working ?
T J (C
different Host OS?
Thanks in advance for your help,
Chris
at startup and it doesn't seem that
they have been made available?
$ qemu-system-x86_64 -enable-kvm -cpu "host,+ssse3,+sse4.1" -m 256M -smp 1
-boot d -cdrom /home/chris/vmware/iso/TinyCorePure64-15.0.iso -vga qxl
-device AC97
qemu-system-x86_64: warning: host doesn't support req
the coming years as applications and operating systems
continue to disregard old hardware and begin to use newer processor
features.
CP
On Mon, Aug 12, 2024 at 1:01 PM Peter Maydell
wrote:
> On Mon, 12 Aug 2024 at 14:19, Peter Maydell
> wrote:
> >
> > On Mon, 12 Aug 2024 at 1
and system dependencies would neee to be stored under a sort of
ARM chroot pointed to by the -L argument?
Much appreciation for all your help and comments!
CP
On Tue, Aug 13, 2024, 5:53 AM Peter Maydell
wrote:
> On Mon, 12 Aug 2024 at 18:47, Chris Parker
> wrote:
> > FYI - I have
Hi all,
is it possible to turn off the built-in DHCP server for usermode networking?
Background is I'm writing some tests for a DHCP client, and am looking to
test quite a few more options than I can set in QEMU's DHCP server, as well
as malformed responses, etc.
Thanks,
Chris
16 matches
Mail list logo
