On Tue, 8 Nov 2011 16:23:50 +0200, Avi Kivity wrote:
> Modern distributions place xattr.h in /usr/include/sys, and fold
> libattr.so into libc. They also don't have an ENOATTR.
>
> Make configure detect this, and add a qemu-xattr.h file that
> directs the #include to the right place.
>
> Signe
Tested linux-image-3.0.0-13-server 3.0.0-13.22 from oneiric-proposed --
same failure.
Tested linux-image-2.6.38-12-server 2.6.38-12.51 from natty-updates --
works fine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Currently, we just print the numerical value of 9p operation identifier in
case of RERROR which is less meaningful for readability. Mapping 9p
operation ids to symbolic names provides a better tracelog:
RERROR (tag = 1 , id = TWALK , err = 2 )
RERROR (tag = 1 , id = TUNLINKAT , err
On Tue, 8 Nov 2011, Arnaldo Carvalho de Melo wrote:
> Em Tue, Nov 08, 2011 at 01:07:55PM +0100, Ingo Molnar escreveu:
> > * Vince Weaver wrote:
> > > as mentioned before I have my own perf_event test suite with 20+ tests.
> > > http://web.eecs.utk.edu/~vweaver1/projects/perf-events/validation.h
Am 09.11.2011 02:38, schrieb Alexander Graf:
Commit 79627472db3 introduced breakage in compiling the s390x-softmmu
target. Instead of compiling, it just throws a lot of errors:
In file included from /dev/shm/qemu/hw/pci-stub.c:24:
./qmp-commands.h:3: error: expected identifier or ‘(’ before ‘{’
Anthony wrote this quickly to aid in testing. It's similar to qmp-shell with
a few important differences:
1) It is not interactive. That makes it useful for scripting.
2) qmp-shell:
(QEMU) set_password protocol=vnc password=foo
3) qmp:
$ qmp set_password --protocol=vnc --password=foo
4) Ext
> I apologize for asking this question on the developers group, but the
> users group is dead.
https://lists.nongnu.org/mailman/listinfo/qemu-discuss
http://tech.groups.yahoo.com/group/qemu-users/
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
On 11/09/11 15:26, Benjamin wrote:
Oh, I forgot to remove a line from the old patch, when I wanted to
introduce -netdev udp. Now it's just -net[dev] socket.
Here's the updated patch, my apologies.
It didn't break anything, it's just useless, use this instead.
I sent the old one again...
This
I apologize for asking this question on the developers group, but the
users group is dead.
I installed qemu on an IBM 366 Dual processor Rack server.
Qemu is very slow on this machine (Running Debian 6)
I used to use kqemu which made everything faster, but I see that kqemu
is not supported an
Public bug reported:
Coverity scan detected some issues such as RESOURCE_LEAK and
REVERSE_INULL etc on qemu-1.0rc1:
Analysis summary report:
Files analyzed : 830
Total LoC input to cov-analyze : 576549
Functions analyzed : 20721
Paths analyzed
** Attachment added: "qemu-1.0rc1.err"
https://bugs.launchpad.net/bugs/887883/+attachment/2590257/+files/qemu-1.0rc1.err
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/887883
Title:
Coverity sca
On 11/08/11 11:52, Jan Kiszka wrote:
On 2011-11-07 23:03, Benjamin wrote:
On 11/07/11 12:23, Jan Kiszka wrote:
On 2011-11-07 15:01, Benjamin wrote:
Here is the updated patch, using only localaddr. mcast expects it to be
addr whereas udp expects addr:port. It's documented in the help output.
I
Hi,
I get the following error when i created a account on wiki.qemu.org
My email id is correctly mentioned, but it still says unable to send mail
for confirmation to my given email ID.
"QEMU could not send your confirmation mail. Please check your e-mail
address for invalid characters.
Mailer r
On Tue, 2011-11-08 at 20:17 -0800, Aaron Fabbri wrote:
> I'm going to send out chunks of comments as I go over this stuff. Below
> I've covered the documentation file and vfio_iommu.c. More comments coming
> soon...
>
> On 11/3/11 1:12 PM, "Alex Williamson" wrote:
>
> > VFIO provides a secure,
I'm going to send out chunks of comments as I go over this stuff. Below
I've covered the documentation file and vfio_iommu.c. More comments coming
soon...
On 11/3/11 1:12 PM, "Alex Williamson" wrote:
> VFIO provides a secure, IOMMU based interface for user space
> drivers, including device ass
> I am wondering when using -smp 16 and --enable-kvm at the same time
> (while the host has 4 cores), what will happen?
"-smp 16" will lauch 16 virtual cpu threads, and "--enable-kvm" means
you run those threads on physical cpus *at the same time*. How 16 virtual
cpu threads are scheduled on 4 p
I am wondering when using -smp 16 and --enable-kvm at the same time
(while the host has 4 cores), what will happen?
在 2011年11月8日 下午9:08，陳韋任 写道：
>> so qemu exposes multiple processors to the guest os by having multiple
>> vCPUs. and it realizes the multiple vCPUs by either using RR on a
>> single
On 09.11.2011, at 02:52, Andreas Färber wrote:
> Am 09.11.2011 02:41, schrieb David Gibson:
>> On Tue, Nov 08, 2011 at 11:40:20AM +0100, Andreas Färber wrote:
>>> Hello,
>>>
>>> On openSUSE 12.1 RC2 x86_64 host
>>>
>>> $ ppc64-softmmu/qemu-system-ppc64 -M pseries -L .../pc-bios
>>>
>>> segfaul
> > $(filter %-softmmu,$(SUBDIR_RULES)): $(trace-obj-y) $(common-obj-y)
> > subdir-libdis
> >
> > I guess you ran into trouble while building *-softmmu? I think we can
> > just remove "libqemu_common.a:" from the comment of common-obj-y and
> > leave the rest part alone.
>
> Yes, please. I bel
Am 09.11.2011 02:41, schrieb David Gibson:
> On Tue, Nov 08, 2011 at 11:40:20AM +0100, Andreas Färber wrote:
>> Hello,
>>
>> On openSUSE 12.1 RC2 x86_64 host
>>
>> $ ppc64-softmmu/qemu-system-ppc64 -M pseries -L .../pc-bios
>>
>> segfaults. Backtrace:
>>
>> Program received signal SIGSEGV, Segmenta
Please use reply-all, then others could contribute.:)
于 2011年11月08日 15:45, Jun Koi 写道:
On Tue, Nov 8, 2011 at 3:43 PM, Jun Koi wrote:
On Tue, Nov 8, 2011 at 3:20 PM, Dong Xu Wang wrote:
You can try like this:
(qemu) info snapshots
IDTAG VM SIZEDATE
On 09.11.2011, at 02:41, David Gibson wrote:
> On Tue, Nov 08, 2011 at 11:40:20AM +0100, Andreas Färber wrote:
>> Hello,
>>
>> On openSUSE 12.1 RC2 x86_64 host
>>
>> $ ppc64-softmmu/qemu-system-ppc64 -M pseries -L .../pc-bios
>>
>> segfaults. Backtrace:
>>
>> Program received signal SIGSEGV,
On Tue, Nov 08, 2011 at 11:40:20AM +0100, Andreas Färber wrote:
> Hello,
>
> On openSUSE 12.1 RC2 x86_64 host
>
> $ ppc64-softmmu/qemu-system-ppc64 -M pseries -L .../pc-bios
>
> segfaults. Backtrace:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00578a7e in spapr_create_p
Am 08.11.2011 11:40, schrieb Andreas Färber:
> $ ppc64-softmmu/qemu-system-ppc64 -M pseries -L .../pc-bios
>
> segfaults. Backtrace:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00578a7e in spapr_create_phb (spapr=0x1247f80, busname=
> 0x77f1b2 "pci", buid=, mem_win_ad
While we're waiting for a proper fix to the compilation issue with
TCGRegs on s390x targets, I would like to have a quick fix in the
tree that allows us to build at all. I'd happily remove it again
later when we have a real fix.
This patch just #defines TCGReg to int, rendering the target API
comp
Commit 79627472db3 introduced breakage in compiling the s390x-softmmu
target. Instead of compiling, it just throws a lot of errors:
In file included from /dev/shm/qemu/hw/pci-stub.c:24:
./qmp-commands.h:3: error: expected identifier or ‘(’ before ‘{’ token
[...]
This is because we have two files
hpet_timer timer callback rearms itself based on difference between
current HPET tick counter and comparator value. Difference calculated by
the hpet_calculate_diff function is limited to non-negative values.
cur_tick is calculated via hpet_get_ticks that uses qemu_get_clock_ns(vm_clock).
With -i
Those of us who have vmdk images bestowed upon us and would prefer to
run them under qemu would very like to have a way to convert the images
in both directions.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
On Tue, Nov 08, 2011 at 10:32:25AM +0100, Ingo Molnar wrote:
>
> None of the perf developers with whom i'm working complained about
> the shared repo so far - publicly or privately. By all means they are
> enjoying it and if you look at the stats and results you'll agree
> that they are highly
On 8 November 2011 22:28, Ben Taylor wrote:
> I picked up a omap2430 prototype board, and am looking to start
> working with this. Since this is a foray back into development for
> me, I'm a little overwhelmed by the amount of information I'm trying
> to digest in starting this project (and the u
I picked up a omap2430 prototype board, and am looking to start
working with this. Since this is a foray back into development for
me, I'm a little overwhelmed by the amount of information I'm trying
to digest in starting this project (and the user forum at qemu-forum.ipi.fi
being down is a bit de
On 09.11.2011 00:32, Jernej Simončič wrote:
> On Tuesday, November 8, 2011, 21:02:52, Michael Tokarev wrote:
>
>> FWIW, WinXP drivers from the latest .iso there can't be installed
>> (it fails during driver install phase, saying "No driver for this
>> hardware found at given location"), while prev
Am 08.11.2011 18:08, schrieb 陳韋任:
>> Have you build this? without this files qemu is not going to work.
>> Perhaps the naming is wrong, and we should change common-obj to
>> something else, but it is still needed to get things working as
>> expected.
>
> I found the line below in Makefile,
>
>
陳韋任 wrote:
>> Have you build this? without this files qemu is not going to work.
>> Perhaps the naming is wrong, and we should change common-obj to
>> something else, but it is still needed to get things working as
>> expected.
>
> I found the line below in Makefile,
>
> $(filter %-softmmu,$(SU
On Tue, 8 Nov 2011, Ted Ts'o wrote:
> On Tue, Nov 08, 2011 at 01:55:09PM +0100, Ingo Molnar wrote:
> > I guess you can do well with a split project as well - my main claim
> > is that good compatibility comes *naturally* with integration.
>
> Here I have to disagree; my main worry is that inte
On Mon, Nov 07, 2011 at 03:25:45PM -0800, Michael Eager wrote:
> Works for me.
Thanks, I've applied the fix.
Cheers
On Thu, Oct 27, 2011 at 07:25:58PM +0200, Jan Kiszka wrote:
> Keep a per-VCPU xsave buffer for kvm_put/get_xsave instead of
> continuously allocating and freeing it on state sync.
>
> Signed-off-by: Jan Kiszka
> ---
> target-i386/cpu.h |3 ++-
> target-i386/kvm.c | 15 +++
> 2
On Tuesday, November 8, 2011, 21:02:52, Michael Tokarev wrote:
> FWIW, WinXP drivers from the latest .iso there can't be installed
> (it fails during driver install phase, saying "No driver for this
> hardware found at given location"), while previous version works
> just fine, and the driver itse
On 11/08/2011 02:02 PM, Michael Tokarev wrote:
On 08.11.2011 23:19, Anthony Liguori wrote:
[]
Windows virtio drivers are available in binary form from Fedora Hosted. See
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
FWIW, WinXP drivers from the latest .iso there can't be ins
Am 08.11.2011 20:25, schrieb Charles Arnold:
> The Data Offset field in the Dynamic Disk Header is an 8 byte field.
> Although the specification (2006-10-11) gives an example of initializing
> only the first 4 bytes, images generated by Microsoft on Windows initialize
> all 8 bytes.
>
> Failure t
On 08.11.2011 23:19, Anthony Liguori wrote:
[]
> Windows virtio drivers are available in binary form from Fedora Hosted. See
> http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/
FWIW, WinXP drivers from the latest .iso there can't be installed
(it fails during driver install phase, s
On Mon, Nov 7, 2011 at 12:03 PM, Anthony Liguori wrote:
> On 11/07/2011 11:52 AM, Sasha Levin wrote:
>>
>> Hi Anthony,
>>
>> Thank you for your comments!
>>
>> On Mon, 2011-11-07 at 11:37 -0600, Anthony Liguori wrote:
>>>
>>> On 11/06/2011 02:40 PM, Sasha Levin wrote:
Hi all,
I
The Data Offset field in the Dynamic Disk Header is an 8 byte field.
Although the specification (2006-10-11) gives an example of initializing
only the first 4 bytes, images generated by Microsoft on Windows initialize
all 8 bytes.
Failure to initialize all 8 bytes results in errors from utilities
On Tue, Nov 08, 2011 at 07:14:57PM +0200, Anca Emanuel wrote:
> @Ten Ts'o: you are sponsored by something like microsoft (joking) ?
> Stop trolling. If you are not familiar with perf, or other tools, save
> your time and do some useful things.
I am quite familiar with perf. A disagreement with ho
On 11/08/2011 01:03 PM, Rick Vernam wrote:
On Tuesday 08 November 2011 12:50:47 Stefan Weil wrote:
Am 08.11.2011 18:42, schrieb Rick Vernam:
Are there supporting windows binaries (ie, various virtio drivers and
vdagent)?
Also, I've seen instructions to build the various windows binaries from
s
Hi,
i am now testing a hack that adds O_EXCL to the call of qemu_open()
in block/raw-posix.c. Just as proof-of-concept.
This is Linux-host-specific, of course.
---
As first i learned to distinguish between octal and hex. :))
So
On Tuesday 08 November 2011 12:50:47 Stefan Weil wrote:
> Am 08.11.2011 18:42, schrieb Rick Vernam:
> > Are there supporting windows binaries (ie, various virtio drivers and
> > vdagent)?
> >
> > Also, I've seen instructions to build the various windows binaries from
> > source in a number of diff
Am 08.11.2011 18:42, schrieb Rick Vernam:
Are there supporting windows binaries (ie, various virtio drivers and
vdagent)?
Also, I've seen instructions to build the various windows binaries from source
in a number of different places. Is there an "official" site describing the
method?
Thanks,
-
On Monday 07 November 2011 15:58:24 Anthony Liguori wrote:
> Hi,
>
> On behalf of the QEMU Team, I'd like to announce the availability of QEMU
> 1.0, release candidate 1. This is the first release candidate for the 1.0
> release. This is not intended for production use but rather for testing.
>
On 11/08/2011 07:34 PM, Alexander Graf wrote:
>>
>>> It could work with a btrfs snapshot, but not everyone uses that.
>> Or LVM snapshot. Either way, just reusing the root fs without care
>> is a dumb idea, and I really don't want any tool or script that
>> encurages such braindead behaviour in th
This is something were we need a consensus of all maintainers of tcg
targets,
therefore I extended the cc list to get them informed.
Am 08.11.2011 11:03, schrieb Andreas Färber:
Hi everyone,
Got this with v1.0-rc1 tarball:
CC i386-softmmu/tcg/tcg.o
In file included from /suse/afaerber/QEMU/qe
* Alexander Graf (ag...@suse.de) wrote:
> On 29.10.2011, at 20:45, Bharata B Rao wrote:
> > As guests become NUMA aware, it becomes important for the guests to
> > have correct NUMA policies when they run on NUMA aware hosts.
> > Currently limited support for NUMA binding is available via libvirt
>
On 11/07/2011 09:33 AM, Gerd Hoffmann wrote:
This patch adds a pc-1.0 machine type.
Signed-off-by: Gerd Hoffmann
Applied both. Thanks.
Regards,
Anthony Liguori
---
hw/pc_piix.c | 14 +++---
1 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_p
On 11/03/2011 09:45 PM, Wen Congyang wrote:
We disable vm_clock when pausing all vcpus, but we forget to
reenable it when resuming all vcpus. It will cause that the
guest can not be rebooted.
Signed-off-by: Wen Congyang
Applied. Thanks.
Regards,
Anthony Liguori
---
cpus.c |1 +
1
On 11/03/2011 12:21 PM, Gerd Hoffmann wrote:
Commit 0a039dc70096b768d3810afa50ba1d214768aaf4 broke vga modes for
qxl-vga by loosing vga_ioport_read windup. qxl needs to hook into
vga port writes only and used to realize that by letting vga_init() do
the work for both reads and writes, then overw
On 11/06/2011 10:00 AM, Gleb Natapov wrote:
The caller of qemu_timedate_diff() does not expect that tm it passes to
the function will be modified, but mktime() is destructive and modifies
its argument. Pass a copy of tm to it and set tm_isdst so that mktime()
will not rely on it since its value m
On 11/04/2011 04:38 AM, Markus Armbruster wrote:
vga_putcharxy()'s underline code sets font_data to 0x instead of
0xff. vga_putcharxy() then reads dmask16[0x>> 4] and
dmask4[0x>> 6]. In practice, these out-of-bounds subscripts
"only" put a few crap bits into the display surface.
On 11/03/2011 09:14 AM, Paolo Bonzini wrote:
The rom was not added together with the sgabios device and is
not installed.
Signed-off-by: Paolo Bonzini
Applied. Thanks.
Regards,
Anthony Liguori
---
The sgabios.git mirror repository can be fetched from
http://people.redhat.c
On 11/03/2011 10:00 AM, Paolo Bonzini wrote:
sgabios hasn't gotten a lot of coverage since it was not shipped. For 1.0,
let's disable the automatic loading of the option ROM in -nographic
mode. We can put it back for 1.1.
Signed-off-by: Paolo Bonzini
Applied. Thanks.
Regards,
Anthony Ligu
On 11/08/2011 03:59 PM, Christoph Hellwig wrote:
On Tue, Nov 08, 2011 at 04:57:04PM +0200, Avi Kivity wrote:
Running qemu -snapshot on the actual root block device is the only
safe way to reuse the host installation, although it gets a bit
complicated if people have multiple devices mounted into
On 11/08/2011 05:32 PM, Anthony Liguori wrote:
>
>>>
>>> If the question is, how do we restore the immutable state, that should
>>> be happening as part of device creation, no?
>>>
The way I see it, we create a link between some device state (a
register) and a memory API field (like the o
@Ten Ts'o: you are sponsored by something like microsoft (joking) ?
Stop trolling. If you are not familiar with perf, or other tools, save
your time and do some useful things.
> Have you build this? without this files qemu is not going to work.
> Perhaps the naming is wrong, and we should change common-obj to
> something else, but it is still needed to get things working as
> expected.
I found the line below in Makefile,
$(filter %-softmmu,$(SUBDIR_RULES)): $(trace-
> Have you build this? without this files qemu is not going to work.
> Perhaps the naming is wrong, and we should change common-obj to
> something else, but it is still needed to get things working as
> expected.
Sorry, I have only tested i386-linux-user when I sent the patch.
And i386-softmmu
Hi,
the test results on CD-RW, DVD-RW, DVD+RW, BD-RE are flawless with
Paolo Bonzini's most recent proposal
-drive file=/dev/sr2,if=none,id=scsicd
-device
virtio-blk,drive=scsicd,logical_block_size=2048,physical_block_size=2048
libburn works fine via SG_IO. dd and other unaware readers work fi
"Chen Wei-Ren (陳韋任)" wrote:
> From: Chen Wen-Ren
>
> Remove libqemu_common.a target from Makefile.objs.
Have you build this? without this files qemu is not going to work.
Perhaps the naming is wrong, and we should change common-obj to
something else, but it is still needed to get things worki
On Tue, Nov 08, 2011 at 01:55:09PM +0100, Ingo Molnar wrote:
> I guess you can do well with a split project as well - my main claim
> is that good compatibility comes *naturally* with integration.
Here I have to disagree; my main worry is that integration makes it
*naturally* easy for people to s
On 11/08/2011 04:39 PM, Peter Maydell wrote:
>> + * This work is licensed under the terms of the GNU GPL, version 2. See
>> + * the COPYING file in the top-level directory.
>
> ... or later please.
Need to be careful here. Marking something previously unmarked as
GPLv2 is pretty clearly OK
Thanks, Markus and Peter.
> Max already explaind chainreplyto. I agree with him that chainreplyto
> off is preferable.
>
> But what you're after is --thread / sendemail.thread. See man
> git-send-email for details. The default is --thread, which does the
> threading, provided you send all pa
Em Tue, Nov 08, 2011 at 04:38:48PM +0100, Gerd Hoffmann escreveu:
> Seems to have no effect, guess the distro perf is too old (RHEL-6).
> > [tui]
> > report = off
> That works. I don't want turn off the tui altogether though, I actually
> like the interactive expanding+collapsing of the call
On Tue, Nov 08, 2011 at 04:41:40PM +0200, Avi Kivity wrote:
> On 11/06/2011 03:35 AM, Alexander Graf wrote:
> > To quickly get going, just execute the following as user:
> >
> > $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
> >
> > This will drop you into a shell on your rootfs.
> >
>
>
On Tue, Nov 08, 2011 at 04:57:04PM +0200, Avi Kivity wrote:
> > Running qemu -snapshot on the actual root block device is the only
> > safe way to reuse the host installation, although it gets a bit
> > complicated if people have multiple devices mounted into the namespace.
>
> How is -snapshot an
陳韋任 writes:
> On Tue, Nov 08, 2011 at 04:07:12PM +0100, Markus Armbruster wrote:
>> 陳韋任 writes:
>>
>> >> Please thread together your patches so that the parts appear as replies
>> >> to the cover letter. git-send-email should do that by default.
>> >>
>> >> Why? Disconnected parts can easily
> If you enable sendemail.chainreplyto then each letter in a series
> (except the first) will go as a reply to the previous letter.
> If you omit sendemail.chainreplyto then letters following the first
> one will go as replies to that first letter.
>
> Second option is commonly used and IMHO a bit
On 8 November 2011 15:16, 陳韋任 wrote:
> O.K.. Just want to make sure. What you said "thread together your
> patches" has something to do with "sendemail.chainreplyto"? I found
> I sent this series one by one, i.e., `git send-email 000#.patch`.
> I think I should sent them as a whole, i.e., `git se
With kernel command line of 'console=ttyS0 noapic=1 panic=1' patched
qemu boots up successfully with -icount, whereas unpatched qemu loops
infinitely.
Looks like APIC emulation issue to me.
--
Thanks.
-- Max
On 7 November 2011 18:38, Juan Quintela wrote:
> This patch adds copyrights to all the machine description files for
> all architectures supported. (this is done on top of my vmstate-cpus
> series patches) The problem?
>
> - What should we put as "copyirght" owners.
>
> Althought I modified almost
> O.K.. Just want to make sure. What you said "thread together your
> patches" has something to do with "sendemail.chainreplyto"? I found
> I sent this series one by one, i.e., `git send-email 000#.patch`.
> I think I should sent them as a whole, i.e., `git send-email *`. But
> I am not sure "send
On 7 November 2011 17:46, Paolo Bonzini wrote:
> On 11/07/2011 06:38 PM, Juan Quintela wrote:
>>
>> + * This work is licensed under the terms of the GNU GPL, version 2. See
>> + * the COPYING file in the top-level directory.
>
> ... or later please.
Need to be careful here. Marking something pre
Hi,
>> documentation: Where the heck is the perf config file documented, other
>> than source code? Reading the parser to figure how the config file is
>> supposed to look like really isn't fun :(
>
>> I'm looking for a way to disable the colors in the perf report tui. Or
>> configure them
On 11/08/2011 01:46 AM, Zhi Yong Wu wrote:
Why do you not develop one helper to set up bridge env for qemu guests
when the host have no bridge interface?
I'm not sure that I understand your question. I think the actual bridge
setup should be left as an admin task, but the allocation/attach
On 11/08/2011 09:15 AM, Avi Kivity wrote:
On 11/08/2011 05:04 PM, Anthony Liguori wrote:
What state is that? Some devices have fixed size, offset, parent, and
enable/disable state (is there a word for that?), so there is no state
that needs to be transferred. For other devices this is all dyna
On Tue, Nov 08, 2011 at 05:26:03PM +0200, Pekka Enberg wrote:
> On Tue, Nov 8, 2011 at 4:52 PM, Christoph Hellwig wrote:
> > Nevermind that running virtfs as a rootfs is a really dumb idea. ?You
> > do now want to run a VM that has a rootfs that gets changed all the
> > time behind your back.
>
>
On Tue, Nov 8, 2011 at 4:52 PM, Christoph Hellwig wrote:
> Nevermind that running virtfs as a rootfs is a really dumb idea. You
> do now want to run a VM that has a rootfs that gets changed all the
> time behind your back.
It's rootfs binaries that are shared, not configuration. It's
unfortunate
git://git.kernel.org/pub/scm/virt/kvm/kvm.git
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
happy fetching!
--
error compiling committee.c: too many arguments to function
On 8 November 2011 14:45, Jason Wessel wrote:
> On 11/08/2011 08:40 AM, Peter Maydell wrote:
>> On 8 November 2011 14:22, Jason Wessel wrote:
>>> +#define FPU_MIN(size, a, b) float ## size ## _lt(a, b, &env->sse_status) ?
>>> (a) : (b)
>>> +#define FPU_MAX(size, a, b) float ## size ## _lt(b, a,
On Tue, Nov 08, 2011 at 04:07:12PM +0100, Markus Armbruster wrote:
> 陳韋任 writes:
>
> >> Please thread together your patches so that the parts appear as replies
> >> to the cover letter. git-send-email should do that by default.
> >>
> >> Why? Disconnected parts can easily get separated in the
On 11/08/2011 05:04 PM, Anthony Liguori wrote:
>
> There's no code generation in QOM :-)
>
> This just comes down to how we do save/restore. We white list things
> we care about. We should move to a model where we save/restore
> everything (preferably via code generation), and then black
> list/t
陳韋任 writes:
>> Please thread together your patches so that the parts appear as replies
>> to the cover letter. git-send-email should do that by default.
>>
>> Why? Disconnected parts can easily get separated in the list. When
>> that happens, your reviewers need to hunt for parts. They may c
On 2011-11-08 15:52, Christoph Hellwig wrote:
> On Tue, Nov 08, 2011 at 04:41:40PM +0200, Avi Kivity wrote:
>> On 11/06/2011 03:35 AM, Alexander Graf wrote:
>>> To quickly get going, just execute the following as user:
>>>
>>> $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
>>>
>>> This wi
Am 04.11.2011 15:51, schrieb Paolo Bonzini:
> This is another approach to fixing the breakage of "qemu-nbd -c" due
> to mixing fork with threads. It switches operation of qemu-nbd to
> threads completely, with the exception of daemonization which is moved
> as early as possible to avoid conflicts
On 11/08/2011 08:38 AM, Avi Kivity wrote:
On 11/08/2011 03:50 PM, Anthony Liguori wrote:
We agree, the only difference is in what "core" refers to. I don't want
memory.c do become intermingled with everything else. It should be in a
separate layer. Devices would then talk to this layer, and n
On 11/08/2011 04:52 PM, Christoph Hellwig wrote:
> On Tue, Nov 08, 2011 at 04:41:40PM +0200, Avi Kivity wrote:
> > On 11/06/2011 03:35 AM, Alexander Graf wrote:
> > > To quickly get going, just execute the following as user:
> > >
> > > $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
> > >
On Tue, Nov 8, 2011 at 4:52 PM, Christoph Hellwig wrote:
> On Tue, Nov 08, 2011 at 04:41:40PM +0200, Avi Kivity wrote:
>> On 11/06/2011 03:35 AM, Alexander Graf wrote:
>> > To quickly get going, just execute the following as user:
>> >
>> > $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
On 11/07/2011 03:45 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
Null agenda -> null call, hope to get some next week.
Thanks, Juan.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.
On 11/08/2011 08:40 AM, Peter Maydell wrote:
> On 8 November 2011 14:22, Jason Wessel wrote:
>> +#define FPU_MIN(size, a, b) float ## size ## _lt(a, b, &env->sse_status) ?
>> (a) : (b)
>> +#define FPU_MAX(size, a, b) float ## size ## _lt(b, a, &env->sse_status) ?
>> (a) : (b)
> This will give th
> Please thread together your patches so that the parts appear as replies
> to the cover letter. git-send-email should do that by default.
>
> Why? Disconnected parts can easily get separated in the list. When
> that happens, your reviewers need to hunt for parts. They may choose to
> review s
On 11/06/2011 03:35 AM, Alexander Graf wrote:
> To quickly get going, just execute the following as user:
>
> $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
>
> This will drop you into a shell on your rootfs.
>
Doesn't work on Fedora 15. F15's qemu-kvm doesn't have -machine or
-virtfs.
Am 08.11.2011 15:34, schrieb 陳韋任:
>> Stefan Hajnoczi writes:
>>
>>> On Tue, Nov 8, 2011 at 12:45 PM, Markus Armbruster
>>> wrote:
Fixes protocol_client_auth_sasl_mechname() not to crash when malloc()
fails. Spotted by Coverity.
---
ui/vnc-auth-sasl.c | 19 +---
On 8 November 2011 14:22, Jason Wessel wrote:
> +#define FPU_MIN(size, a, b) float ## size ## _lt(a, b, &env->sse_status) ?
> (a) : (b)
> +#define FPU_MAX(size, a, b) float ## size ## _lt(b, a, &env->sse_status) ?
> (a) : (b)
This will give the wrong answers for special cases involving +0, -0
a
1 - 100 of 210 matches
Mail list logo
