In case no listening address was specified, "info spice" reports
"0.0.0.0" as address. Which is incorrect in case spice is listening
on ipv6. Replace it by a wildcard "*" to indicate it is not limited
to a specific address.
Note: Being more specific is not possible without extending the
spice-s
Hi All,
Greetings!!!
We are using KVM hypervisor driver for running OpenStack IaaS. Couple of months
back we have reported one security issue [1] in OS.
Basically we want to limit on the number of vnc client connections that can be
opened by users for a given VM.
>From libvirt 1.0.6 version onw
Hi,
> But while testing I am not able to get expected results for
> allow-exclusive and ignore sharePolicy.
> For allow-exclusive sharePolicy previous connections are not getting
> dropped and console contents are getting shared among all open
> consoles.
The vnc protocol has an option to speci
* Marcus (shadow...@gmail.com) wrote:
> Dang, I was hoping some ground was being made on this.
Can you answer the same questions I asked Marcin?
What's the latest version of QEMU you've seen this on, what CPU are you
using, what guest OS and what's your QEMU command line?
Dave
>
> On Wed, Apr 2
* Shehbaz Jaffer (shehbazjaffer...@gmail.com) wrote:
> Hi,
>
> I am running a Ubuntu 12.04 guest VM that I created using vm-builder on a
> Ubuntu 12.04 Operating System. I am using qemu-2.0.0-rc0 version. I want to
> boot from a saved snapshot instance of the guest VM, so I created a
> snapshot us
On Mo, 2014-04-14 at 16:54 -0400, Gabriel L. Somlo wrote:
> New in version 6 of the patch set:
>
> - down to 17 patches (squashed adding spec v2.4 fields
> in together with adding v2.8 fields further down).
>
> - switching to monolithic aggregate tables plus entry point
> in patch 11/
The current behaviour of tap_open for BSD systems differ greatly from
it's Linux counterpart. Since FreeBSD supports interface renaming and
tap device cloning by opening /dev/tap, implement a FreeBSD specific
version of tap_open that behaves like it's Linux counterpart.
This is specially important
This two patches allow FreeBSD Xen Dom0 to use Qemu (i.e., launch HVM
guests).
First patch fixes the usage of ENODATA, which doesn't exist on FreeBSD
and is replaced with ENOENT instead.
The second patch is more controversial probably, since it introduces a
FreeBSD specific version of tap_open wh
ENODATA doesn't exist on FreeBSD, so ENODATA errors returned by the
hypervisor are translated to ENOENT.
Also, the error code is returned in errno if the call returns -1, so
compare the error code with the value in errno instead of the value
returned by the function.
Signed-off-by: Roger Pau Monn
"Gabriel L. Somlo" writes:
> Check fw_cfg for the presence of a complete set of smbios
> tables (etc/smbios/smbios-tables) and an entry point structure
> (etc/smbios/smbios-anchor), and, if found, use them instead of
> generating our own copies locally.
>
> We ensure the presence of a type 0 (bio
On Mon, 14 Apr 2014 15:08:23 +0200
Alexander Graf wrote:
>
> On 14.04.14 14:55, Michael S. Tsirkin wrote:
> > On Mon, Apr 14, 2014 at 02:40:04PM +0200, Alexander Graf wrote:
> >> On 14.04.14 14:37, Michael S. Tsirkin wrote:
> >>> On Mon, Apr 14, 2014 at 02:29:20PM +0200, Alexander Graf wrote:
>
From: Sangho Park
g_poll has a problem on windows when using
timeouts < 10ms, in glib/gpoll.c:
/* If not, and we have a significant timeout, poll again with
* timeout then. Note that this will return indication for only
* one event, or only for messages. We ignore timeouts less than
* ten mil
> If I read your discussion correctly, you're proposing to change "from
> SeaBIOS defaults" to "from QEMU defaults". Correct?
That is correct, where "qemu defaults" will be "seabios defaults of the
current stable release aka 1.7.4".
cheers,
Gerd
Peter Crosthwaite writes:
> On Tue, Apr 8, 2014 at 10:02 PM, Chen Gang wrote:
>> In function, if no additional resources to free before quit, commonly,
>> need not use additional local variable 'res' to notice about it. So
>> remove it to simplify code.
>>
>
> Styling wise, there is a school of
On Mo, 2014-04-14 at 15:30 -0400, Gabriel L. Somlo wrote:
> If QEMU adds its (still optional) type 0 structure, SeaBIOS just uses
> everything as-is. If no type 0 structure is found, we generate and
> prepend our own, and update the entry point fields accordingly.
>
> I expect the latter to be the
Am 15.04.2014 um 05:18 hat xuanmao_001 geschrieben:
> Hi, there:
>
> I found an issue that cdrom device hotplug iso image.
> 1. if I startup qemu with an iso image, then iso can easily be replaced and it
> worked.
> 2. but if I startup qemu with null image, when I change iso image use qemu
> moni
Chen Gang writes:
> In "vl.c", at least, we can simplify the code below, so can let readers
> read professional C code (especially for new readers, which often start
> reading code at main function).
>
> - remove useless 'continue' in main().
>
> - remove redundant local variable 'res' in get_b
Chen Gang writes:
> Normal "if (...) {...} else {...}" is enough in "while(...) {...}", not
> need additional useless 'continue'.
>
> Signed-off-by: Chen Gang
> ---
> vl.c |1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/vl.c b/vl.c
> index 9975e5a..7505002 100644
> --- a/vl.c
> +++ b
Chen Gang writes:
> For C code, it does not recommend to define a local variable in the
> middle of code block without "{...}". The original author may want to
> zero members not mentioned in structure assignment.
>
> So recommend to use structure initializing block "{...}" for structure
> assign
I think this has been fixed by commit 68dc0364, which was included in
qemu 1.7.0 and also backported to 1.6.1. Can you please try upgrading and
confirm whether it fixes the problem?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
http
On 04/15/14 01:55, Michael R. Hines wrote:
> On 04/14/2014 05:19 PM, Laszlo Ersek wrote:
>> On 04/14/14 04:27, Amos Kong wrote:
>>> We already have a function buffer_is_zero() in util/cutils.c
>>>
>>> Signed-off-by: Amos Kong
>>> ---
>>> arch_init.c | 9 ++---
>>> 1 file changed, 2 insertio
Am 12.04.2014 um 17:01 hat Alexandre DERUMIER geschrieben:
> Hello,
>
> I known that qemu live migration with disk with cache=writeback are not safe
> with storage like nfs,iscsi...
>
> Is it also true with rbd ?
First of all, in order to avoid misunderstandings, let's be clear that
there are t
Am 11.04.2014 um 15:11 hat Eric Blake geschrieben:
> On 04/11/2014 01:27 AM, Peter Maydell wrote:
> > On 11 April 2014 02:40, Eric Blake wrote:
> >> We uncovered a real bug that would be fixed by this patch:
> >> https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg01745.html
> >
> > No, that
Hi,
I was wondering if a document describing how the differents parts of Qemu
worked together existed and if someone could pinpoint it to me. (or explain
it to me ;) )
This project is so big that I don't know where to begin.
thanks in advance !
Am 15.04.2014 um 11:21 hat xuanmao_001 geschrieben:
> Hi, Kevin:
> The lastest version of qemu is ok.
> But I want to know what is going wrong with qemu-kvm-1.0.1.
There have been a lot of changes between 1.0.1 and now. To be honest,
as long as it works now, I don't feel like investing a lot of ti
* Kevin Grandemange (grandemange.ke...@gmail.com) wrote:
> Hi,
>
> I was wondering if a document describing how the differents parts of Qemu
> worked together existed and if someone could pinpoint it to me. (or explain
> it to me ;) )
> This project is so big that I don't know where to begin.
Yes
On 04/15/14 11:58, Dr. David Alan Gilbert wrote:
> * Kevin Grandemange (grandemange.ke...@gmail.com) wrote:
>> Hi,
>>
>> I was wondering if a document describing how the differents parts of Qemu
>> worked together existed and if someone could pinpoint it to me. (or explain
>> it to me ;) )
>> This
On Tue, Apr 15, 2014 at 1:38 AM, Andreas Färber wrote:
> Am 14.04.2014 09:13, schrieb Markus Armbruster:
>> Alistair Francis writes:
>>
>>> On Wed, Apr 9, 2014 at 9:58 PM, Peter Crosthwaite
>>> wrote:
On Wed, Apr 9, 2014 at 7:56 PM, Markus Armbruster
wrote:
> We have a number of
Originally I reported this issue to ubuntu folks, and it is documented on
the launchpad[1] but would like to bring this into attention also on this list.
Basically seems that on some occasions clock interrupts are not happening for
longer periods of time causing that some VMs are crashing (i.e
On 04/15/2014 04:43 PM, Markus Armbruster wrote:
> Peter Crosthwaite writes:
>
>> On Tue, Apr 8, 2014 at 10:02 PM, Chen Gang wrote:
>>> In function, if no additional resources to free before quit, commonly,
>>> need not use additional local variable 'res' to notice about it. So
>>> remove it to
On 04/15/2014 04:50 PM, Markus Armbruster wrote:
> Chen Gang writes:
>
>> Normal "if (...) {...} else {...}" is enough in "while(...) {...}", not
>> need additional useless 'continue'.
>>
>> Signed-off-by: Chen Gang
>> ---
>> vl.c |1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/
On 04/15/2014 04:56 PM, Markus Armbruster wrote:
> Chen Gang writes:
>
>> For C code, it does not recommend to define a local variable in the
>> middle of code block without "{...}". The original author may want to
>> zero members not mentioned in structure assignment.
>>
>> So recommend to use
On 15 April 2014 02:33, zhuxiaodong wrote:
> I am a user of qemu. I found that in qemu2.0.0-rc0 the gic model was
> updated. However, it seems loss ability to bind irqs to any specified core
> when the board includes multiple cortex-a9 cores. The problematic codes
> maybe locate at hw/intc
On 04/15/2014 10:40 AM, Greg Kurz wrote:
On Mon, 14 Apr 2014 15:08:23 +0200
Alexander Graf wrote:
On 14.04.14 14:55, Michael S. Tsirkin wrote:
On Mon, Apr 14, 2014 at 02:40:04PM +0200, Alexander Graf wrote:
On 14.04.14 14:37, Michael S. Tsirkin wrote:
On Mon, Apr 14, 2014 at 02:29:20PM +020
Thanks a lot, that's exactly what I was searching for.
2014-04-15 12:26 GMT+02:00 Laszlo Ersek :
> On 04/15/14 11:58, Dr. David Alan Gilbert wrote:
> > * Kevin Grandemange (grandemange.ke...@gmail.com) wrote:
> >> Hi,
> >>
> >> I was wondering if a document describing how the differents parts of
The (re)implementation of this instruction for mainline never had this
bug.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1263747
Title:
Ar
On Tue, Apr 8, 2014 at 10:05 PM, Chen Gang wrote:
> For C code, it does not recommend to define a local variable in the
> middle of code block without "{...}". The original author may want to
> zero members not mentioned in structure assignment.
>
> So recommend to use structure initializing block
On 04/15/2014 08:29 PM, Peter Crosthwaite wrote:
> On Tue, Apr 8, 2014 at 10:05 PM, Chen Gang wrote:
>> For C code, it does not recommend to define a local variable in the
>> middle of code block without "{...}". The original author may want to
>> zero members not mentioned in structure assignment
Fix will be in 2.0.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1287195
Title:
validate_guest_space incorrectly enabled on AArch6
On 04/14/2014 07:37 PM, Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
As mentioned in the last email I still have the sysbus -device topic on
the list. If Alexey shows up I would also like to discuss the IOMMU bus
patch and why we need a bus solely for l
Am 10.04.2014 17:52, schrieb Peter Maydell:
> On 10 April 2014 16:49, Alexander Graf wrote:
>> For the next call, I would propose to revive the "platform bus"
>> (aka: how to create non-PCI devices with -device) discussions
>> to make sure we're all on the same page.
>
> I rather suspect we are n
Hi all,
I try to replace the display content of a paused VM (to show the operator that
it is actually paused and not usable), but it causes only a short flicker on the
display instead of staying permanent.
By routing an HMP based command to console.c I want to replace the display
contents. I star
On Tue, 15 Apr 2014 13:35:03 +0200
Alexander Graf wrote:
> On 04/15/2014 10:40 AM, Greg Kurz wrote:
> > On Mon, 14 Apr 2014 15:08:23 +0200
> > Alexander Graf wrote:
> >
> >> On 14.04.14 14:55, Michael S. Tsirkin wrote:
> >>> On Mon, Apr 14, 2014 at 02:40:04PM +0200, Alexander Graf wrote:
>
Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
As there are no topics, no call.
Some block drivers have multiple BlockDriver instances with identical
format_name fields (e.g. gluster, nbd). In those cases, the
protocol_name is usually the more unique identifier (e.g. gluster+tcp).
Both qemu-img and qemu will use bdrv_iterate_format() to list the
supported formats when a help
Sorry - ignore that. However, problem persists on a separate fully-
updated amd64 trusty system running kvm version 2.0.0~rc1+dfsg-0ubuntu3.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1257352
Titl
QEMU 1.7 was released, Quantal has 10ish days left of support, and
Raring is EOL
** Changed in: qemu
Status: Fix Committed => Fix Released
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: Triaged => Invalid
** Changed in: qemu-kvm (Ubuntu Raring)
Status: Triaged => Invalid
On 15.04.14 10:33, Roger Pau Monne wrote:
> ENODATA doesn't exist on FreeBSD, so ENODATA errors returned by the
> hypervisor are translated to ENOENT.
>
> Also, the error code is returned in errno if the call returns -1, so
> compare the error code with the value in errno instead of the value
> re
On Tue, Apr 15, 2014 at 10:29:26AM +0200, Gerd Hoffmann wrote:
> So, how about this plan:
>
> Leave the old interface code basically as-is. type0 and type1
> individual fields are passed like they are passed today. We don't
> change to to pass full tables, and we don't extend that to new table
>
I have been trying out the 2.0 RCs, and I've noticed that when I use spice
qemu aborts when I reboot the VM. This occurs on Win XP guest, Win 7 (64-bit)
guest and Win 8 (64-bit) guest.
Is this something that anybody else experiences?
I don't care to divert anybody's energy if this a spice thing
On 04/15/2014 04:49 PM, Markus Armbruster wrote:
> Chen Gang writes:
>
>> In "vl.c", at least, we can simplify the code below, so can let readers
>> read professional C code (especially for new readers, which often start
>> reading code at main function).
>>
>> - remove useless 'continue' in mai
On 15.04.2014 15:28, Jeff Cody wrote:
Some block drivers have multiple BlockDriver instances with identical
format_name fields (e.g. gluster, nbd). In those cases, the
protocol_name is usually the more unique identifier (e.g. gluster+tcp).
Both qemu-img and qemu will use bdrv_iterate_format() t
Am 15.04.2014 um 15:28 hat Jeff Cody geschrieben:
> Some block drivers have multiple BlockDriver instances with identical
> format_name fields (e.g. gluster, nbd). In those cases, the
> protocol_name is usually the more unique identifier (e.g. gluster+tcp).
>
> Both qemu-img and qemu will use bdr
On 15.04.2014 05:15, Fam Zheng wrote:
bdrv_getlength could fail, check the return value before using it.
Signed-off-by: Fam Zheng
---
v2: Make use of error_setg_errno and -errno. (Kevin)
Signed-off-by: Fam Zheng
---
block-migration.c | 28
block.c
* Rick Vernam (rtver...@hobi.com) wrote:
> I have been trying out the 2.0 RCs, and I've noticed that when I use spice
> qemu aborts when I reboot the VM. This occurs on Win XP guest, Win 7
> (64-bit)
> guest and Win 8 (64-bit) guest.
> Is this something that anybody else experiences?
> I don't
Juan Quintela writes:
> Juan Quintela wrote:
>> Hi
>>
>> Please, send any topic that you are interested in covering.
>>
>> Thanks, Juan.
>
> As there are no topics, no call.
Did we have a call anyway? IRC log looks like we did...
On 15 April 2014 14:22, Greg Kurz wrote:
> On Tue, 15 Apr 2014 13:35:03 +0200
> Alexander Graf wrote:
>> That would defeat the purpose - the reason to have the helper inlined is
>> to remove the conditional branch for x86.
>>
>
> Sure but on the other hand, Peter does not like the idea of moving
Chen Gang writes:
> On 04/15/2014 04:49 PM, Markus Armbruster wrote:
>> In future submissions, please send the patches in-reply-to the cover
>> letter, not chained together in-reply-to the previous part. Check out
>> git-send-email --no-chain-reply-to.
>>
>
> OK, thanks. But excuse me, I use th
Thankyou for your reply. I do not face the error using qemu.1.7.1 version.
1 quick question:
I want to create a qcow2 image file after my VM has completed booting;
i.e., when I boot from this new snapshot, I should directly get to my VMs
login prompt. How can i create such a qcow2 snapshot?
I tr
On 04/15/2014 04:00 PM, Markus Armbruster wrote:
Juan Quintela writes:
Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
As there are no topics, no call.
Did we have a call anyway? IRC log looks like we did...
Yes, we did. Whoever attend
Hi,
Am 26.03.2014 01:47, schrieb Alistair Francis:
> This patch introduces a new command line argument that allows
> sysbus devices to be attached via the command line.
>
> This allows devices to be added after the machine init but
> before anything is booted
>
> The new argument is -sysbusdev
>
I am not very sure about the place(s) we would need this. But I think
this is required. Please advise.
When having SVM enabled, the do_interrupt64 shouldn't be
called unless GIF is set otherwise this causes random behaviour
especially bad TR in case guest is running.
Signed-off-by: Himanshu Chauh
On 4 April 2014 03:19, Peter Crosthwaite wrote:
> The smlald (and probably smlsld) instruction was doing incorrect sign
> extensions of the operands amongst 64bit result calculation. The
> instruction psuedo-code is:
>
> operand2 = if m_swap then ROR(R[m],16) else R[m];
> product1 = SInt(R[n]<15
On 04/15/2014 04:55 PM, Alexander Graf wrote:
> On 04/15/2014 04:00 PM, Markus Armbruster wrote:
>> Juan Quintela writes:
>>
>>> Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
>>> As there are no topics, no call.
>> Did w
On 28 March 2014 17:57, Grant Likely wrote:
> Right now to run firmware inside the QEMU VExpress model requires
> padding out the firmware image to the size of the virtual flash and
> passing it in via the -pflash argument. If the firmware image is passed
> without padding, then QEMU will fail. Al
On 28 March 2014 17:57, Grant Likely wrote:
> Right now to run firmware inside the QEMU VExpress model requires
> padding out the firmware image to the size of the virtual flash and
> passing it in via the -pflash argument. If the firmware image is passed
> without padding, then QEMU will fail.
A
On Tue, 15 Apr 2014 14:37:01 +0800
Hu Tao wrote:
> On Mon, Apr 14, 2014 at 06:44:42PM +0200, Igor Mammedov wrote:
> > On Mon, 14 Apr 2014 15:25:01 +0800
> > Hu Tao wrote:
> >
> > > On Fri, Apr 04, 2014 at 03:36:58PM +0200, Igor Mammedov wrote:
> > > > Needed for Windows to use hotplugged memory
> On 04/15/14 01:55, Michael R. Hines wrote:
>> On 04/14/2014 05:19 PM, Laszlo Ersek wrote:
>>> On 04/14/14 04:27, Amos Kong wrote:
We already have a function buffer_is_zero() in util/cutils.c
Signed-off-by: Amos Kong
---
arch_init.c | 9 ++---
1 file changed,
Hi
Do we have any plan to support migration by multi net card?
Thanks
ChenLiang
>
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
>
> Call details:
>
> 15:00 CEST
> 13:00 UTC
> 09:00 EDT
>
> Every two weeks
>
> If you need phone number details, conta
On 04/15/2014 02:04 AM, Andreas Färber wrote:
Am 13.04.2014 15:24, schrieb Jun Li:
Add remove_boot_device_path() function to remove bootindex when hot-unplug
a device. This patch fixed virtio-blk/virtio-net/scsi-disk/scsi-generic device.
So it has fixed bug1086603, ref:
https://bugzilla.redhat.
On 04/15/2014 12:18 AM, Markus Armbruster wrote:
lijun writes:
Hi Markus,
Really appreciate your review first. I almost a new participant. And
I read other's patches very little. So maybe this patch is duplicate
to one of Marcel's patch. But I really do not know. And I really don't
copying
Am 15.04.2014 04:21, schrieb Peter Crosthwaite:
> So clients can set the top level id string.
>
> Signed-off-by: Peter Crosthwaite
Anthony had nack'ed Paolo's attempt to generalize the qdev id to QOM, so
I'm not sure if we should really do this even if just on device level.
The id= is used to co
On Tue, Apr 15, 2014 at 10:33:08AM +0200, Roger Pau Monne wrote:
> ENODATA doesn't exist on FreeBSD, so ENODATA errors returned by the
> hypervisor are translated to ENOENT.
>
> Also, the error code is returned in errno if the call returns -1, so
> compare the error code with the value in errno in
Some fuller comments below on the parts of the call which
I had opinions on.
On 15 April 2014 15:55, Alexander Graf wrote:
>
> 2) -device for non-PCI devices
>
> There are 2 reasons we want to create "platform" devices using -device on
> the command line. One is that Xilinx is trying to create a
On 15/04/14 18:15, Anthony PERARD wrote:
> On Tue, Apr 15, 2014 at 10:33:08AM +0200, Roger Pau Monne wrote:
>> ENODATA doesn't exist on FreeBSD, so ENODATA errors returned by the
>> hypervisor are translated to ENOENT.
>>
>> Also, the error code is returned in errno if the call returns -1, so
>> co
Alexander Graf writes:
> On 04/15/2014 04:00 PM, Markus Armbruster wrote:
>> Juan Quintela writes:
>>
>>> Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
>>> As there are no topics, no call.
>> Did we have a call anyway?
On Mon, Apr 14, 2014 at 08:18:20PM -0700, Peter Crosthwaite wrote:
> Generalise the names of the FIFO API to not include the "8".
>
> The exception is the push/pop functions for which we:
>
> s/fifo8_pop/fifo_pop8
> s/fifo8_push/fifo_push8
>
> This prepares support for generalising FIFO support
I can answer some of the questions. It's been 3 months or so since I
looked into it. I ended up disabling kvmclock from the qemu command
line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 guests.
Sending the guest to the BIOS CLI or PXE would not reproduce the
issue. I didn't attempt an
Use MSR mnemonics from cpu.h instead of magic numbers for the
CPUPPCState.msr_mask
initialization.
There is one bit in the 401x2 (and subsequent) model that I could not find any
documentation for. It is open coded at little endian bit position 20:
pcc->msr_mask = (1ull << 20) |
On Mon, Apr 14, 2014 at 08:18:56PM -0700, Peter Crosthwaite wrote:
> Add support for 16, 32 and 64 bit width FIFOs. The push and pop
> functions are replicated to accept all four different integer types.
> The element width of the FIFO is set at creation time.
>
> The backing storage for all eleme
On Mon, Apr 14, 2014 at 08:19:31PM -0700, Peter Crosthwaite wrote:
> To disentangle it from the monitor.
>
> Signed-off-by: Peter Crosthwaite
> ---
>
> hw/ssi/pl022.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/ssi/pl022.c b/hw/ssi/pl022.c
> index fd479ef..84bf8
On 3 April 2014 06:37, Peter Crosthwaite wrote:
> Hi Peter,
>
> Iv'e finally gotten around to looking at SLCR and its coverity issues.
> Ended up doing a rewrite of the whole thing to action (P1).
>
> Some styling updates to go with it as well (P2-3).
Reviewed-by: Peter Maydell
thanks
-- PMM
On Mon, Apr 14, 2014 at 08:20:06PM -0700, Peter Crosthwaite wrote:
> Use the FIFO API to factor out the ring buffer implementation code.
> Cleans up the somewhat verbose VMS description as well (version bump
> required).
>
> Signed-off-by: Peter Crosthwaite
> ---
>
> hw/ssi/pl022.c | 101
> +++
On 4 April 2014 07:55, Peter Crosthwaite wrote:
> Phys must respond to address 0 by specification. Implement.
>
> Signed-off-by: Nathan Rossi
> Signed-off-by: Peter Crosthwaite
Reviewed-by: Peter Maydell
thanks
-- PMM
* Marcus (shadow...@gmail.com) wrote:
> I can answer some of the questions. It's been 3 months or so since I
> looked into it. I ended up disabling kvmclock from the qemu command
> line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 guests.
> Sending the guest to the BIOS CLI or PXE would
From: Rob Herring
Like was done for AArch32 for WFE, implement both WFE and YIELD as a
yield operation. This speeds up multi-core system emulation.
Signed-off-by: Rob Herring
---
target-arm/translate-a64.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target-arm/translate-a64.c b/t
On 15 April 2014 20:00, Rob Herring wrote:
> From: Rob Herring
>
> Like was done for AArch32 for WFE, implement both WFE and YIELD as a
> yield operation. This speeds up multi-core system emulation.
>
> Signed-off-by: Rob Herring
Reviewed-by: Peter Maydell
thanks
-- PMM
Hi Mateusz,
How are you migrating? If you are using the compress/xbzrle option, try
turning it off and see if that helps, there are some corruption fixes for
xbzrle in 2.0.0.
Dave
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 04/15/2014 02:53 PM, Dr. David Alan Gilbert wrote:
> * Marcus (shadow...@gmail.com) wrote:
>
>> As mentioned by others, the mode of reproduction is to launch the vm,
>> wait about an hour, and then try to migrate it
>>
>> Here's are example qemu command lines (as generated from libvirt with
W dniu 2014-04-15 20:53, Dr. David Alan Gilbert pisze:
* Marcus (shadow...@gmail.com) wrote:
I can answer some of the questions. It's been 3 months or so since I
looked into it. I ended up disabling kvmclock from the qemu command
line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 gues
On Tue, Apr 8, 2014 at 2:28 AM, Alexander Graf wrote:
> On 22.03.14 14:03, Alexey Kardashevskiy wrote:
>>
>> This adds handling of the RESOURCE_ADDR_TRANS_MODE resource from
>> the H_SET_MODE, for POWER8 (PowerISA 2.07) only.
>>
>> Signed-off-by: Alexey Kardashevskiy
>> Reviewed-by: Mike Day
>
>
Currently it is very easy to crash QEMU by issuing an object-add command
using an abstract class or a class that doesn't support
TYPE_USER_CREATABLE as parameter.
Example: with the following QMP command:
(QEMU) object-add qom-type=cpu id=foo
QEMU aborts at:
ERROR:qom/object.c:335:object
Reproduced just as easily with qemu.org git HEAD.
Again, this appears to only be a case when using -smp 4 while locking to
1 cpu with cpuset.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which
On 04/15/2014 04:01 PM, Eduardo Habkost wrote:
> Currently it is very easy to crash QEMU by issuing an object-add command
> using an abstract class or a class that doesn't support
> TYPE_USER_CREATABLE as parameter.
>
> Example: with the following QMP command:
>
> (QEMU) object-add qom-type=c
> Am 15.04.2014 um 18:56 schrieb Markus Armbruster :
>
> Alexander Graf writes:
>
>>> On 04/15/2014 04:00 PM, Markus Armbruster wrote:
>>> Juan Quintela writes:
>>>
Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thank
On Wed, Apr 16, 2014 at 2:16 AM, Andreas Färber wrote:
> Am 15.04.2014 04:21, schrieb Peter Crosthwaite:
>> So clients can set the top level id string.
>>
>> Signed-off-by: Peter Crosthwaite
>
> Anthony had nack'ed Paolo's attempt to generalize the qdev id to QOM, so
> I'm not sure if we should r
Hi,
I keep getting this error: "must include QEMU headers” emitted from
tcg/tcg-op.h. I have no idea how come this is happening.
BTW, the same setup I have (build env + 1.7.1-stable qemu sources) to
successfully build a functional qemu-system-arm for x86-64 host.
Any info/pointers are
On 04/15/2014 10:51 PM, Markus Armbruster wrote:
> Chen Gang writes:
>
>> On 04/15/2014 04:49 PM, Markus Armbruster wrote:
>>> In future submissions, please send the patches in-reply-to the cover
>>> letter, not chained together in-reply-to the previous part. Check out
>>> git-send-email --no-ch
Hi,
I found some more time to work on this. However, I'm not sure I
understand the purpose of compat property:
I noticed that the only place it's set is in PC_COMPAT_1_3 (is this
what you meant by older devices?),
I guess same setting for FS mouse and kbd should be added there as well.
The switch
In "vl.c", at least, we can simplify the code below, so can let readers
read professional C code (especially for new readers, which often start
reading code at main function).
- Remove useless 'continue' in main().
- Eliminate a superfluous local variable in main().
Signed-off-by: Chen Gang
-
1 - 100 of 127 matches
Mail list logo
