Hey,
Just a heads up - on 32 bit hosts where qemu was using preadv and
pwritev, we were seeing data corruption due to file offset being
truncated:
https://bugzilla.redhat.com/533063
https://bugzilla.redhat.com/526549
The glibc headers fix is posted here:
Avi Kivity wrote:
Helpers are really bad. On launch, I find the fragile and hard to do
proper error handling with (but that's probably just me). But the
real problem is at runtime, if you have a 16GB guest then you have to
write-protect 4M ptes and then kvm has to tear down or write protect
Hi,
I found the Linux/Sparc clone operations in copy_thread() from process32.c
(attached)
I tried modifying cpu_clone_regs with the following code per the Sparc/linux
routines, but qemu still stalls on signal suspend.
It seems like it should only need to set the stack pointer and the return
2009/11/4 Blue Swirl blauwir...@gmail.com:
On Wed, Nov 4, 2009 at 1:58 AM, Artyom Tarasenko
atar4q...@googlemail.com wrote:
The page 108 of the SPARC Version 8 Architecture Manual describes
that addcc and addxcc shall compute carry flag the same way.
The page 110 claims the same about subcc
[RFC] virtio: Report new guest memory statistics pertinent to memory
ballooning
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
that will minimize the impact of
Here are the corresponding changes to the Linux virtio driver...
virtio: Add memory statistics reporting to the balloon driver
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
a...@linux.vnet.ibm.com wrote:
[RFC] virtio: Report new guest memory statistics pertinent to memory
ballooning
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage to the host can provide information
that
a...@linux.vnet.ibm.com wrote:
Here are the corresponding changes to the Linux virtio driver...
virtio: Add memory statistics reporting to the balloon driver
When using ballooning to manage overcommitted memory on a host, a system for
guests to communicate their memory usage
Avi Kivity wrote:
On 11/05/2009 07:20 PM, Arnd Bergmann wrote:
On Thursday 05 November 2009, Anthony Liguori wrote:
It'd still install the default helper you've provided and use it by
default, of course.
That's already how it behaves. You can say -net
Hi,
My guest system is 2 cpu smp environment and use icount=0 to measure the total
instructions.I called cpu_get_icount() when the cpu switches in vl.c Sometimes
the return value of cpu_get_icount() increased a lot ( 1 million) but the cpu
actually is in halted state.Normally, the return value
Anthony Liguori wrote:
Avi Kivity wrote:
Helpers are really bad. On launch, I find the fragile and hard to do
proper error handling with (but that's probably just me). But the
real problem is at runtime, if you have a 16GB guest then you have to
write-protect 4M ptes and then kvm has to
Daniel P. Berrange wrote:
On Thu, Nov 05, 2009 at 04:41:45PM +, Jamie Lokier wrote:
Anthony Liguori wrote:
Absolutely. I wanted to not have a hard dependency on PolicyKit to
start out with but that's always been the plan. I'd like to eventually
add an optional PolicyKit
Michael S. Tsirkin wrote:
On Thu, Nov 05, 2009 at 04:12:36AM +, Jamie Lokier wrote:
I notice that if we eventually teach the kernel to have unnamed
bridges (just attach interfaces to each other), only the helper
commands will need changing to use it :-)
What do you mean by attach
Daniel P. Berrange wrote:
On Thu, Nov 05, 2009 at 11:03:48AM -0600, Anthony Liguori wrote:
Daniel P. Berrange wrote:
Indeed the hotplug scenario is a bit of a problem in this model,
since libvirt needs to be able to setup iptables ebtables rules
between creating the device giving it to
Avi Kivity wrote:
On 11/05/2009 05:59 PM, Anthony Liguori wrote:
Avi Kivity wrote:
On 11/05/2009 05:11 PM, Daniel P. Berrange wrote:
The main problem is that we've never really used the 'session'
instances,
since networking configs are rather limited to pretty much just SLIRP
and people
Avi Kivity wrote:
On 11/05/2009 07:16 PM, Scott Tsai wrote:
On Fri, Nov 6, 2009 at 12:50 AM, Anthony Liguorialigu...@us.ibm.com
wrote:
It's just a bit annoying to create an entire new
project for a few hundred line helper.
This new project would also be a better place for
Avi Kivity wrote:
On 11/05/2009 06:50 PM, Anthony Liguori wrote:
I'm worrying that we're transforming one problem into two different
ones. Expanding the scope of qemu, and making it more difficult to
use advanced networking functionality.
Do you object to the idea of having qemu call
Avi Kivity wrote:
I don't see why you consider placing functionality in the
management stack vs qemu user hostile, considering who our users are.
Do you mean that virtually all users use a management stack?
-- Jamie
Anthony Liguori wrote:
Avi Kivity wrote:
+int net_init_bridge(QemuOpts *opts, Monitor *mon, const char *name,
VLANState *vlan);
+
Don't we need to tear the interface down after shutdown?
net_init_bridge calls net_tap_fd_init which registers tap_cleanup. That
closes the fd and
Avi Kivity wrote:
On 11/03/2009 12:09 AM, Alexander Graf wrote:
When we want to create a full VirtIO based machine, we're still missing
graphics output. Fortunately, Linux provides us with most of the frameworks
to render text and everything, we only need to implement a transport.
So this
Jamie Lokier wrote:
Avi Kivity wrote:
On 11/03/2009 12:09 AM, Alexander Graf wrote:
When we want to create a full VirtIO based machine, we're still missing
graphics output. Fortunately, Linux provides us with most of the frameworks
to render text and everything, we only need to
I'm going to add a new mips machine with a mips core. But I can not find a
proper document for me to do so. Can anyone give a link? Or any suggestion
for this?
Thanks in advance.
Michael,
You might want to read these two threads:
RE: [Qemu-devel] Support for new target emulator:
http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg02131.html
[Qemu-devel] [PATCH 00/12] S/390 support
http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg01857.html
On Fri, Nov 6, 2009 at 12:43 PM, Scott Tsai scottt...@gmail.com wrote:
Michael,
You might want to read these two threads:
RE: [Qemu-devel] Support for new target emulator:
http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg02131.html
[Qemu-devel] [PATCH 00/12] S/390 support
On 11/05/2009 09:58 PM, Anthony Liguori wrote:
Avi Kivity wrote:
Helpers are really bad. On launch, I find the fragile and hard to do
proper error handling with (but that's probably just me). But the
real problem is at runtime, if you have a 16GB guest then you have to
write-protect 4M ptes
On 11/06/2009 02:29 AM, Anthony Liguori wrote:
Helpers are really bad. On launch, I find the fragile and hard to do
proper error handling with (but that's probably just me). But the
real problem is at runtime, if you have a 16GB guest then you have to
write-protect 4M ptes and then kvm has
26 matches
Mail list logo
