We've been seeing an issue with FreeBSD 10 x64 guests where they
frequently cause kernel warnings on the host. We're using QEMU 2.0.0,
on a variety of kernels (we've been seeing this on everything from
2.6.32 all the way up to 3.15.5).
We're using a bridged networking setup, and the qemu comm
Failed to start VNC server on `127.0.0.1:4105': Failed to bind socket:
Address already in use
This error message is *highly* confusing. '127.0.0.1:4105' in any other
software would mean it was trying to bind to 127.0.0.1, port 4105. In
qemu's terms, it really means port 10005. Why is this l
On 7/25/2014 1:59 PM, Dale R. Worley wrote:
From: Brian Rak
Failed to start VNC server on `127.0.0.1:4105': Failed to bind socket:
Address already in use
This error message is *highly* confusing. '127.0.0.1:4105' in any other
software would mean it was trying to bind to 127.0
I've been testing 2.1.0, and qemu will no longer start up with our CPU
configuration. I get the error:
qemu-kvm: /root/qemu/src/hw/i386/smbios.c:825: smbios_get_tables:
Assertion `smbios_smp_sockets >= 1' failed.
The relevant parts of my command line:
-smp 4,sockets=2,cores=12,threads=2
Th
On 8/13/2014 7:33 AM, Jakob Bohm wrote:
On 8/12/2014 8:40 PM, Brian Rak wrote:
I've been testing 2.1.0, and qemu will no longer start up with our CPU
configuration. I get the error:
qemu-kvm: /root/qemu/src/hw/i386/smbios.c:825: smbios_get_tables:
Assertion `smbios_smp_sockets >= 1
Why are you using e1000 and not virtio? The virtio drives have
significantly better performance Ubuntu should also have native
support for them.
On 8/17/2014 10:34 PM, JHM wrote:
Salutations to all members, first off. This is my first post in the
discussion group.
I searched for this to
You could look at the KVM perf support, but I'm unsure if that gives you
enough detail: http://www.linux-kvm.org/page/Perf_events
On 8/18/2014 8:26 AM, Mie Ite wrote:
Hi everyone,
I would like to know the following information of the guest application
executed in QEMU:
- the number of gue
Are there any plans to bring trim support to Virtio-blk? We've got a
couple things that would be made nicer by having working trim support.
I see that it's implemented in virtio-scsi, but there's a decent
performance hit for switching over to that.
fferent in SD cards. But
linux call it 'discard', or, to be precise, BLKDISCARD (name of ioctl).
On 10/01/2014 02:21 AM, Brian Rak wrote:
Are there any plans to bring trim support to Virtio-blk? We've got a
couple things that would be made nicer by having working trim support.
I
On 10/1/2014 6:03 PM, Mike Lovell wrote:
On 09/30/2014 05:21 PM, Brian Rak wrote:
Are there any plans to bring trim support to Virtio-blk? We've got a
couple things that would be made nicer by having working trim support.
I see that it's implemented in virtio-scsi, but there&
ic ATA
command.
It done completely different in SCSI and slightly different in SD
cards. But
linux call it 'discard', or, to be precise, BLKDISCARD (name of ioctl).
On 10/01/2014 02:21 AM, Brian Rak wrote:
Are there any plans to bring trim support to Virtio-blk? We've got
So, I'm saying LVM on the host. If you have trim/discard enabled, when
the guest trims a block, LVM marks that space as not used on the host.
It works like this:
* Take a guest running on a LVM LV (so, LVM on the host) with a 50GB
disk. Assume 1GB in use
* Write 30 GB to that disk, and dele
On 8/13/2014 9:55 AM, Jakob Bohm wrote:
On 8/13/2014 3:22 PM, Brian Rak wrote:
On 8/13/2014 7:33 AM, Jakob Bohm wrote:
On 8/12/2014 8:40 PM, Brian Rak wrote:
I've been testing 2.1.0, and qemu will no longer start up with our CPU
configuration. I get the error:
qemu-kvm: /root/qemu/s
In 6.1, a guest with 15 empty pcie-root-port devices will not boot
properly - it just hangs on "Guest has not initialized the display
(yet).". As soon as I remove the last pcie-root-port, the guest begins
starting up normally. My qemu command line:
/usr/libexec/qemu-kvm -name guest=xxx,debug
In 6.1, a guest with 15 empty pcie-root-port devices will not boot
properly - it just hangs on "Guest has not initialized the display
(yet).". As soon as I remove the last pcie-root-port, the guest begins
starting up normally. My qemu command line:
/usr/libexec/qemu-kvm -name guest=xxx,debug
15 matches
Mail list logo
