When the guest is panicked, it will write 0x1 to the port KVM_PV_PORT.
So if qemu reads 0x1 from this port, we can do the folloing three
things according to the parameter -onpanic:
1. emit QEVENT_GUEST_PANICKED only
2. emit QEVENT_GUEST_PANICKED and pause the guest
3. emit QEVENT_GUEST_PANICKED and
Add a new qevent QEVENT_GUEST_PANICKED. QEMU will emit this
event if the guest is panicked.
Signed-off-by: Wen Congyang
---
monitor.c |1 +
monitor.h |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index f6107ba..28f7482 100644
--- a/monitor.c
+
Add a new runstate RUN_STATE_GUEST_PANICKED. The guest can be in this
state if it is paused due to panicked event.
Signed-off-by: Wen Congyang
---
qapi-schema.json |6 +-
qmp.c|3 ++-
vl.c |7 ++-
3 files changed, 13 insertions(+), 3 deletions(-)
diff
Signed-off-by: Wen Congyang
---
linux-headers/asm-x86/kvm_para.h |2 ++
linux-headers/linux/kvm_para.h |6 ++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/linux-headers/asm-x86/kvm_para.h b/linux-headers/asm-x86/kvm_para.h
index f2ac46a..f9d858f 100644
--- a/linux-
The guest should run after reseting it, but it does not
run if its old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
Signed-off-by: Wen Congyang
---
block.h |2 ++
qmp.c |2 +-
vl.c|3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/block.h b/block.h
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
> Thanks for heading up. i am not sure this software is related to QEMU, but it
> seems that BlueStacks is a system-emulator.
> I would like to learn your experiences of qemu-user.
If you read carefully the thread mentioned in the link I gave you,
https://groups.google.com/forum/?fromgroups#
On 27.06.2012 10:06, Oleg Ogurtsov wrote:
Oleg Ogurtsov (1):
Exynos4: add RTC device
hw/arm/Makefile.objs |1 +
hw/exynos4210.c |8 +
hw/exynos4210_rtc.c | 595 ++
3 files changed, 604 insertions(+), 0 deletions(-)
create m
Oleg Ogurtsov (1):
Exynos4: add RTC device
hw/arm/Makefile.objs |1 +
hw/exynos4210.c |8 +
hw/exynos4210_rtc.c | 595 ++
3 files changed, 604 insertions(+), 0 deletions(-)
create mode 100644 hw/exynos4210_rtc.c
--
1.7.5.4
Signed-off-by: Oleg Ogurtsov
---
hw/arm/Makefile.objs |1 +
hw/exynos4210.c |8 +
hw/exynos4210_rtc.c | 595 ++
3 files changed, 604 insertions(+), 0 deletions(-)
create mode 100644 hw/exynos4210_rtc.c
diff --git a/hw/arm/Makefile.
Blue Swirl writes:
> On Tue, Jun 26, 2012 at 6:41 PM, Peter Maydell
> wrote:
>> On 26 June 2012 19:25, Blue Swirl wrote:
>>> On Tue, Jun 26, 2012 at 6:11 PM, Peter Maydell
>>> wrote:
On 26 June 2012 18:58, Blue Swirl wrote:
> On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell
> w
From: David Gibson
The AHCI device can provide both PCI and SysBus AHCI device
emulations. For this reason, it wasn't previously converted to use
the pci_dma_*() helper functions. Now that we have universal DMA
helper functions, this converts AHCI to use them.
The DMAContext is obtained from p
From: David Gibson
Not that long ago, every device implementation using DMA directly
accessed guest memory using cpu_physical_memory_*(). This meant that
adding support for a guest visible IOMMU would require changing every
one of these devices to go through IOMMU translation.
Shortly before qe
From: David Gibson
This patch adds some hooks to let PCI devices and busses use the new IOMMU
infrastructure. When IOMMU support is enabled, each PCI device now
contains a DMAContext * which is used by the pci_dma_*() wrapper functions.
By default, the contexts are initialized to NULL, assuming
From: David Gibson
Currently the pseries machine emulation does not support DMA for emulated
PCI devices, because the PAPR spec always requires a (guest visible,
paravirtualized) IOMMU which was not implemented. Now that we have
infrastructure for IOMMU emulation, we can correct this and allow P
The emulated devices can run simultaneously with the guest, so
we need to be careful with ordering of load and stores done by
them to the guest system memory, which need to be observed in
the right order by the guest operating system.
This adds a barrier call to the basic DMA read/write ops which
From: David Gibson
dma-helpers.c contains a number of helper functions for doing
scatter/gather DMA, and various block device related DMA. Currently,
these directly access guest memory using cpu_physical_memory_*(),
assuming no IOMMU translation.
This patch updates this code to use the new univ
On (Tue) 26 Jun 2012 [08:01:20], Anthony Liguori wrote:
> >>>+/* Send data from a char device over to the guest */
> >>>+static void chr_read(void *opaque, const void *buf, size_t size)
> >>>+{
> >>>+VirtIORNG *vrng = opaque;
> >>>+size_t len;
> >>>+int offset;
> >>>+
> >>>+if (!is
-- Forwarded message --
From: Liu Xin
Date: Wed, Jun 27, 2012 at 1:19 PM
Subject: Re: [Qemu-devel] qemu as dynamic binary translation infrastructure
To: "陳韋任 (Wei-Ren Chen)"
Weiren,
Thanks for heading up. i am not sure this software is related to QEMU, but
it seems that BlueSta
From: David Gibson
The pseries platform already contains an IOMMU implementation, since it is
essential for the platform's paravirtualized VIO devices. This IOMMU
support is currently built into the implementation of the VIO "bus" and
the various VIO devices.
This patch converts this code to ma
From: David Gibson
This patch adds the basic infrastructure necessary to emulate an IOMMU
visible to the guest. The DMAContext structure is extended with
information and a callback describing the translation, and the various
DMA functions used by devices will now perform IOMMU translation using
From: David Gibson
The USB UHCI and EHCI drivers were converted some time ago to use the
pci_dma_*() helper functions. However, this conversion was not complete
because in some places both these drivers do DMA via the usb_packet_map()
function in usb-libhw.c. That function directly used
cpu_phy
From: David Gibson
The OHCI device emulation can provide both PCI and SysBus OHCI
implementations. Because of this, it was not previously converted to
use the PCI DMA helper functions.
This patch converts it to use the new universal DMA helper functions.
In the PCI case, it obtains its DMAConte
From: David Gibson
A while back, we introduced the dma_addr_t type, which is supposed to
be used for bus visible memory addresses. At present, this is an
alias for target_phys_addr_t, but this will change when we eventually
add support for guest visible IOMMUs.
There are some instances of targe
Only difference (appart from being rebased) is the memory
barrier patch getting a couple of curly braces where they
were missing.
Cheers,
Ben.
Ping!
Whats the action item here? Put out an RFC about unifying bootloaders
or some such?
Regards,
Peter
On Mon, Jun 25, 2012 at 7:19 PM, Peter Crosthwaite
wrote:
> On Mon, Jun 25, 2012 at 7:03 PM, Peter Maydell
> wrote:
>> On 25 June 2012 09:55, Peter Crosthwaite
>> wrote:
>>> As for archit
From: Stanislav Vorobiov
After some long period of time Linux kernel hanged due to
ptimer_get_count may return 0 before timer interrupt occurs,
thus, causing FRC to jump back in time
Signed-off-by: Evgeny Voevodin
---
hw/exynos4210_mct.c |4
1 file changed, 4 deletions(-)
diff --git
We want to mirror whole IROM and should pass zero instead of
EXYNOS4210_IROM_BASE_ADDR (though it equals to zero too) since
memory_region_init_alias takes an offset within an original
region as an argument.
Signed-off-by: Evgeny Voevodin
---
hw/exynos4210.c |2 +-
1 file changed, 1 insertion
First patch is on the list:
http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg03717.html
It fixes a critical bug in MCT that leads to hanged linux kernel v3.0. I
preferred to pick this
patch into this patch set.
Second patch fixes STOP status bit setting in PWM
(not critical only since lat
START/STOP bit was not cleaned correctly.
Signed-off-by: Evgeny Voevodin
---
hw/exynos4210_pwm.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/exynos4210_pwm.c b/hw/exynos4210_pwm.c
index 6243e59..0c22828 100644
--- a/hw/exynos4210_pwm.c
+++ b/hw/exynos4210_pwm.c
@@ -
Ping!
Any Further thoughts Kevin?
This thread flew off on a tangent over whether or not coroutines
should be depracated. Seems to be the answer there was no on that
front - coroutines are here to stay.
I still think this thread points out a major flaw in block+coroutines,
regardless of the fact
Hi Liu,
You might find this thread interesting,
http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg04351.html
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people
The Buildbot has detected a new failure on builder block_openbsd_current while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_openbsd_current/builds/262
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: brad_openbsd_cur
The Buildbot has detected a new failure on builder block_openbsd_4.9 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_openbsd_4.9/builds/249
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_openbsd49
Build
Hi Alex,
On Mon, 25 Jun 2012 22:55:52 -0600 Alex Williamson
wrote:
>
> VFIO has been kicking around for well over a year now and has been
> posted numerous times for review. The pre-requirements are finally
> available in linux-next (or will be in the 20120626 build) so I'd li
I read a thread "ARM binary code translator" on android-x86 Google Group (
https://groups.google.com/forum/?fromgroups#!topic/android-x86/_3HoNJTi_Y0).
It is mentioned that Bluestacks (www.bluestacks.com) uses qemu for an arm
binary translator in its software that runs Android apps. I downloaded th
Currently, no one reenters the yielded coroutine. This fixes it.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index afd06aa..0b49c6d 100644
--- a/block/sheepdog.c
++
outstanding_list_head is used for both pending and inflight requests.
This patch splits it and improves readability.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c | 49 -
1 files changed, 24 insertions(+), 25 deletions(-)
diff --git a/bloc
This patch increments the pending counter before sending requests, and
make sures that aiocb is not freed while sending them.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c | 29 -
1 files changed, 16 insertions(+), 13 deletions(-)
diff --git a/block/sheepdog.
This fixes warnings about dprintf format in debug mode.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index 8877f45..afd06aa 100644
--- a/block/sheepdog.c
+++ b/block/sheepdo
On 06/26/2012 04:28 PM, Corey Bryant wrote:
With this proposed series, we have usage akin to:
1. pass_fd FDSET={M} -> returns a string "/dev/fd/N" showing QEMU's
view of the FD
2. drive_add file=/dev/fd/N
3. if failure:
close_fd "/dev/fd/N"
On 06/26/2012 04:42 PM, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 02:40:03PM -0400, Corey Bryant wrote:
On 06/26/2012 11:37 AM, Corey Bryant wrote:
On 06/26/2012 11:03 AM, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 03:11:40PM +0100, Daniel P. Berrange wrote:
On Tue, Jun 2
See individual patches for details.
MORITA Kazutaka (6):
sheepdog: fix dprintf format strings
sheepdog: restart I/O when socket becomes ready in do_co_req()
sheepdog: use coroutine based socket functions in coroutine context
sheepdog: make sure we don't free aiocb before sending all reques
This removes blocking network I/Os in coroutine context.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index 0b49c6d..5dc1d7a 100644
--- a/block/sheepdog.c
+++ b/block/shee
On 06/22/2012 04:39 AM, Stefan Hajnoczi wrote:
The following changes since commit 47ecbdf07ed2c37bdfd2d77137d01bb319ce13da:
libcacard: build fixes (2012-06-21 20:04:24 +)
are available in the git repository at:
git://github.com/stefanha/qemu.git trivial-patches
for you to fetch chan
On 06/22/2012 04:25 AM, Gerd Hoffmann wrote:
Hi,
The spice patch queue carries a few vga bits this time,
specifically it makes the vga ram size configurable.
There are also a few qxl bugfixes and cleanups.
Pulled. Thanks.
Regards,
Anthony Liguori
please pull,
Gerd
Alon Levy (6):
On 06/21/2012 06:04 PM, Michael Roth wrote:
The following changes since commit 47ecbdf07ed2c37bdfd2d77137d01bb319ce13da:
libcacard: build fixes (2012-06-21 20:04:24 +)
are available in the git repository at:
git://github.com/mdroth/qemu.git qga-pull-6-21-12
Pulled. Thanks.
Regards
On 06/21/2012 11:17 AM, Stefano Stabellini wrote:
Anthony,
please pull a couple of small Xen compile fixes to compile against
xen-unstable:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git compile-xs
Pulled. Thanks.
Regards,
Anthony Liguori
Anthony PERARD (2):
xen: Reorganize
On 06/21/2012 11:13 AM, Stefano Stabellini wrote:
Anthony,
please pull Anthony Perard's Xen PCI Passthrough series from:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git xen-pt
All the generic patches have been acked by Michael, the Xen patches have
been reviewed by Konrad and me.
Pulled.
On 06/20/2012 09:05 AM, Gerd Hoffmann wrote:
Hi,
This is the usb patch queue, featuring live migration support for
ehci and usb-host. Also as usual some small bugfixes.
pleae pull,
Gerd
Pulled. Thanks.
Regards,
Anthony Liguori
The following changes since commit 93bfef4c6e4b23caea
The pending list can be modified in other coroutine context
sd_co_rw_vector, so we need to traverse the list from the first again
after we send the pending request.
Signed-off-by: MORITA Kazutaka
---
block/sheepdog.c | 22 --
1 files changed, 16 insertions(+), 6 deletions(-
On 06/26/2012 04:50 PM, Luiz Capitulino wrote:
On Tue, 26 Jun 2012 13:45:52 +0200
Kevin Wolf wrote:
Am 26.06.2012 11:10, schrieb Daniel P. Berrange:
I was thinking about some of the sources complexity when using
FD passing from libvirt and wanted to raise one idea for discussion
before we c
On 06/26/2012 05:28 PM, Luiz Capitulino wrote:
On Tue, 26 Jun 2012 17:15:05 -0400
Corey Bryant wrote:
On 06/26/2012 04:44 PM, Luiz Capitulino wrote:
On Fri, 22 Jun 2012 14:36:09 -0400
Corey Bryant wrote:
Signed-off-by: Corey Bryant
If this patch doesn't change anymore you can add:
On 06/26/2012 05:28 PM, Luiz Capitulino wrote:
On Tue, 26 Jun 2012 17:16:28 -0400
Corey Bryant wrote:
On 06/26/2012 04:45 PM, Luiz Capitulino wrote:
On Fri, 22 Jun 2012 14:36:11 -0400
Corey Bryant wrote:
Signed-off-by: Corey Bryant
---
v4:
-This patch is new in v4.
Can you explai
On Tue, 26 Jun 2012 17:16:28 -0400
Corey Bryant wrote:
>
>
> On 06/26/2012 04:45 PM, Luiz Capitulino wrote:
> > On Fri, 22 Jun 2012 14:36:11 -0400
> > Corey Bryant wrote:
> >
> >> Signed-off-by: Corey Bryant
> >> ---
> >> v4:
> >> -This patch is new in v4.
> >
> > Can you explain why it's n
On Tue, 26 Jun 2012 17:15:05 -0400
Corey Bryant wrote:
>
>
> On 06/26/2012 04:44 PM, Luiz Capitulino wrote:
> > On Fri, 22 Jun 2012 14:36:09 -0400
> > Corey Bryant wrote:
> >
> >> Signed-off-by: Corey Bryant
> >
> > If this patch doesn't change anymore you can add:
> >
> > Reviewed-by: Luiz
On 06/26/2012 04:45 PM, Luiz Capitulino wrote:
On Fri, 22 Jun 2012 14:36:11 -0400
Corey Bryant wrote:
Signed-off-by: Corey Bryant
---
v4:
-This patch is new in v4.
Can you explain why it's needed?
This just made patch 3/7 easier to review.
monitor.c | 40 --
On Mon, 2012-06-25 at 22:55 -0600, Alex Williamson wrote:
> Hi,
>
> VFIO has been kicking around for well over a year now and has been
> posted numerous times for review. The pre-requirements are finally
> available in linux-next (or will be in the 20120626 build) so I'd lik
On Tue, 26 Jun 2012 13:45:52 +0200
Kevin Wolf wrote:
> Am 26.06.2012 11:10, schrieb Daniel P. Berrange:
> > I was thinking about some of the sources complexity when using
> > FD passing from libvirt and wanted to raise one idea for discussion
> > before we continue.
> >
> > With this proposed se
On 06/26/2012 04:44 PM, Luiz Capitulino wrote:
On Fri, 22 Jun 2012 14:36:09 -0400
Corey Bryant wrote:
Signed-off-by: Corey Bryant
If this patch doesn't change anymore you can add:
Reviewed-by: Luiz Capitulino
Thanks! I'll do that. I'll assume we still want this patch even if
pas
Signed-off-by: Eduardo Habkost
---
exec.c | 35 +--
1 file changed, 25 insertions(+), 10 deletions(-)
diff --git a/exec.c b/exec.c
index 5f3b265..dcbe4e1 100644
--- a/exec.c
+++ b/exec.c
@@ -2353,11 +2353,34 @@ static long gethugepagesize(const char *path)
I was investigating if there are any mechanisms that allow manually pinning of
guest RAM to specific host NUMA nodes, in the case of multi-node KVM guests, and
noticed that -mem-path could be used for that, except that it currently removes
any files it creates (using mkstemp()) immediately, not all
This make QEMU create files inside the -mem-path directory using
more predictable names, and not remove them afterwards.
This allow (for example) users or management layers to use numactl
later, to set NUMA policy for the guest RAM.
Signed-off-by: Eduardo Habkost
---
cpu-all.h |1 +
e
Signed-off-by: Eduardo Habkost
---
cpu-all.h |2 +-
vl.c |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/cpu-all.h b/cpu-all.h
index 9dc249a..2beed5a 100644
--- a/cpu-all.h
+++ b/cpu-all.h
@@ -490,7 +490,7 @@ typedef struct RAMList {
extern RAMList ram_list;
While we are at it, rename it to "length", as "memory" doesn't mean
anything.
Signed-off-by: Eduardo Habkost
---
exec.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/exec.c b/exec.c
index 8244d54..5f3b265 100644
--- a/exec.c
+++ b/exec.c
@@ -2354,7 +2354,7 @@
On Fri, 22 Jun 2012 14:36:11 -0400
Corey Bryant wrote:
> Signed-off-by: Corey Bryant
> ---
> v4:
> -This patch is new in v4.
Can you explain why it's needed?
>
> monitor.c | 40
> 1 file changed, 20 insertions(+), 20 deletions(-)
>
> diff --git a/
On Fri, 22 Jun 2012 14:36:09 -0400
Corey Bryant wrote:
> Signed-off-by: Corey Bryant
If this patch doesn't change anymore you can add:
Reviewed-by: Luiz Capitulino
> ---
> v2:
> -Convert getfd and closefd to QAPI (lcapitul...@redhat.com)
> -Remove changes that returned fd from getfd (lcap
On Tue, Jun 26, 2012 at 02:40:03PM -0400, Corey Bryant wrote:
>
>
> On 06/26/2012 11:37 AM, Corey Bryant wrote:
> >
> >
> >On 06/26/2012 11:03 AM, Daniel P. Berrange wrote:
> >>On Tue, Jun 26, 2012 at 03:11:40PM +0100, Daniel P. Berrange wrote:
> >>>On Tue, Jun 26, 2012 at 09:52:51AM -0400, Corey
On Wed, 20 Jun 2012 22:58:20 +0530
Rabin Vincent wrote:
> Make dump-guest-memory not create read-only files, so that it can
> overwrite a file created by a previous invocation without having it to
> be removed externally.
I think we need a force parameter to do this, the command shouldn't overwr
On Wed, 20 Jun 2012 06:53:40 -0600
Eric Blake wrote:
> On 06/19/2012 10:47 PM, Amos Kong wrote:
> > Convert 'sendkey' to use QAPI. do_sendkey() depends on some
> > variables/functions in monitor.c, so reserve qmp_sendkey()
> > to monitor.c
> >
> > key_defs[] in monitor.c is the mapping of key na
On Wed, 20 Jun 2012 12:47:40 +0800
Amos Kong wrote:
> Convert 'sendkey' to use QAPI. do_sendkey() depends on some
> variables/functions in monitor.c, so reserve qmp_sendkey()
> to monitor.c
>
> key_defs[] in monitor.c is the mapping of key name to keycode,
> Keys' order in the enmu and key_defs[
On Sat, Jun 23, 2012 at 12:55:49AM +0200, Jan Kiszka wrote:
> Should have declared this [RFC] in the subject and CC'ed kvm...
>
> On 2012-06-23 00:45, Jan Kiszka wrote:
> > This sketches a possible path to get rid of the iothread lock on vmexits
> > in KVM mode. On x86, the the in-kernel irqchips
On Tue, Jun 26, 2012 at 6:41 PM, Peter Maydell wrote:
> On 26 June 2012 19:25, Blue Swirl wrote:
>> On Tue, Jun 26, 2012 at 6:11 PM, Peter Maydell
>> wrote:
>>> On 26 June 2012 18:58, Blue Swirl wrote:
On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell
wrote:
> +static inline uint6
Anthony Liguori writes:
> On 06/26/2012 03:42 AM, Markus Armbruster wrote:
>> Anthony Liguori writes:
>>
>>> This will create a new QOM object in the '/objects' path. Note that
>>> properties
>>
>> Long line, will look fugly in git-log. Please wrap at column 70-75.
>
> Okay, let me turn this
Hi
This are the minutes for Today call
- q35 integration
why not ICH10? ICH9 is already obsolete.
what are the differences?
We need to check guests from Windows XP and some *BSD.
Having it default for 1.2? Anthony.
Having is as an option in 1.2 and make it defalut in 1.3. Alex?
Anthon
On 06/26/2012 11:37 AM, Corey Bryant wrote:
On 06/26/2012 11:03 AM, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 03:11:40PM +0100, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 09:52:51AM -0400, Corey Bryant wrote:
So now from a client's POV you'd have a flow like
* drive_add
On 26 June 2012 19:25, Blue Swirl wrote:
> On Tue, Jun 26, 2012 at 6:11 PM, Peter Maydell
> wrote:
>> On 26 June 2012 18:58, Blue Swirl wrote:
>>> On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell
>>> wrote:
+static inline uint64_t field64(uint64_t value, int start, int length)
>>>
>>> star
On Tue, Jun 26, 2012 at 6:11 PM, Peter Maydell wrote:
> On 26 June 2012 18:58, Blue Swirl wrote:
>> On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell
>> wrote:
>>> +static inline uint64_t field64(uint64_t value, int start, int length)
>>
>> start and length could be unsigned.
>
> They could be, bu
On 26 June 2012 14:35, Anthony Liguori wrote:
> On 06/26/2012 03:42 AM, Markus Armbruster wrote:
>> Long line, will look fugly in git-log. Please wrap at column 70-75.
> How do people normally limit this beyond just eye-balling?
Same way I avoid overly long lines in usenet posts and email:
my e
On Tue, Jun 26, 2012 at 3:49 PM, Igor Mammedov wrote:
> Hello Blue,
>
> I've tried to test if *-bsd-user target works but so far wasn't successful
> so far.
> I've tried qemu-1.x ports on the latest freebsd/openbsd and a freshly
> checked out qemu.
>
> If it works for you, could you tell:
> 1. wh
On 26 June 2012 18:58, Blue Swirl wrote:
> On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell
> wrote:
>> +static inline uint64_t field64(uint64_t value, int start, int length)
>
> start and length could be unsigned.
They could be, but is there any reason why they should be?
set_bit(), clear_bit()
On Mon, Jun 25, 2012 at 10:43 PM, Anthony Liguori wrote:
> This will create a new QOM object in the '/objects' path. Note that
> properties
> are set in order which allows for simple objects to be initialized entirely
> with this option and then realized.
>
> This option is roughly equivalent to
On Mon, Jun 25, 2012 at 7:38 PM, Peter Maydell wrote:
> Add field32() and field64() functions which extract a particular
> bit field from a word and return it. Based on an idea by Jia Liu.
>
> Suggested-by: Jia Liu
> Signed-off-by: Peter Maydell
> ---
> Jia Liu had a function like this in the Op
If a GlobalProperty has already been registered, it won't have its
value overwritten.
Signed-off-by: Crístian Viana
---
Changes since v4:
- Only register a GlobalProperty if it hasn't already been registered. That
avoids the property values to be overwritten (fix previous known bug).
hw/qde
The current value for the -rtc driftfix option is 'none'. This patch
makes sure that the old machines configuration will work the same way
even after that option changes its default value.
Signed-off-by: Crístian Viana
---
hw/pc_piix.c |4
1 file changed, 4 insertions(+)
diff --git a/h
Windows 2008+ is very sensitive to missed ticks. The RTC is used by default as
the time source. If driftfix is not enabled, Windows is prone to
blue screening.
Signed-off-by: Crístian Viana
---
hw/mc146818rtc.c |2 +-
vl.c | 11 ++-
2 files changed, 11 insertions(+), 2
On 06/26/2012 02:29 AM, Stefan Hajnoczi wrote:
On Mon, Jun 25, 2012 at 5:32 PM, Mike Lovell wrote:
Oh. I forgot another reason why I decided to do this over using VDE. I'll do
this one with an example. Say you have 3 virtual machines on 3 different
hosts. Each host has a vde_switch process run
On 13.03.2012 16:06, Alexander Graf wrote:
On 13.03.2012, at 16:05, Corentin Chary wrote:
On Tue, Mar 13, 2012 at 12:29 PM, Peter Lieven wrote:
On 11.02.2012 09:55, Corentin Chary wrote:
On Thu, Feb 9, 2012 at 7:08 PM, Peter Lieven wrote:
Hi,
is anyone aware if there are still problems w
Hi, community,
our company uses QEMU as system emulator, to emulate our private-ISA
processor and SoC. recently, we came up an idea to build a dynamic binary
translator on top of current QEMU technology. please you guys in this
community are experienced and your aforementioned advices are really
p
Public bug reported:
Is it possible to add S3 Trio emulation to QEMU at all? Since 0.12.3 the
Cirrus Logic seems no longer working properly (bad font render/corrupted
video). Also, S3 is a widely supported device on many OSes and
architectures, which will give more compatibility for QEMU.
Thanks!
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means "the maximum TCG can emulate".
That's a really good default when using TCG, but when running with KVM
we much rather want a default saying "the max
During discussions on whether to make -cpu host the default in SLE, I found
myself disagreeing to the thought, because it potentially opens a big can
of worms for potential bugs. But if I already am so opposed to it for SLE, how
can it possibly be reasonable to default to -cpu host in upstream QEMU
The kvm_enabled() helper doesn't work in a function as early as -cpu ?
yet. It also doesn't make sense to list the -cpu ? output conditional on
the -enable-kvm parameter. So let's always mention -cpu host in the
CPU list when KVM is supported on that configuration.
In addition, this patch also add
On 06/26/2012 06:21 AM, Markus Armbruster wrote:
"Daniel P. Berrange" writes:
On Tue, Jun 26, 2012 at 09:54:21AM +0200, Markus Armbruster wrote:
Luiz Capitulino writes:
On Thu, 21 Jun 2012 13:42:19 +0100
"Daniel P. Berrange" wrote:
[...]
In libvirt we have always reserved the right to c
On 06/26/2012 11:03 AM, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 03:11:40PM +0100, Daniel P. Berrange wrote:
On Tue, Jun 26, 2012 at 09:52:51AM -0400, Corey Bryant wrote:
So now from a client's POV you'd have a flow like
* drive_add "file=/dev/fd/N" FDSET={N}
IIUC then drive_
On 06/26/2012 05:56 PM, Andreas Färber wrote:
Am 26.06.2012 17:49, schrieb Igor Mammedov:
Example of what I've did on FreeBSD, qemu with your recent patches and
ld patch form qemu-devel port:
# ./configure --enable-debug --disable-werror --target-list=i386-bsd-user
# ./i386-bsd-user/qemu-i38
Am 26.06.2012 17:49, schrieb Igor Mammedov:
> Example of what I've did on FreeBSD, qemu with your recent patches and
> ld patch form qemu-devel port:
>
> # ./configure --enable-debug --disable-werror --target-list=i386-bsd-user
>
> # ./i386-bsd-user/qemu-i386 -strace -bsd FreeBSD -L / /bin/ls
>
Hello Blue,
I've tried to test if *-bsd-user target works but so far wasn't successful so
far.
I've tried qemu-1.x ports on the latest freebsd/openbsd and a freshly checked
out qemu.
If it works for you, could you tell:
1. what flavor of bsd you use for testing
2. what configure options ar
On Tue, Jun 26, 2012 at 03:11:40PM +0100, Daniel P. Berrange wrote:
> On Tue, Jun 26, 2012 at 09:52:51AM -0400, Corey Bryant wrote:
> > >So now from a client's POV you'd have a flow like
> > >
> > >* drive_add "file=/dev/fd/N" FDSET={N}
> >
> > IIUC then drive_add would loop and pass each fd
On Tue, Jun 26, 2012 at 09:52:51AM -0400, Corey Bryant wrote:
> >So now from a client's POV you'd have a flow like
> >
> >* drive_add "file=/dev/fd/N" FDSET={N}
>
> IIUC then drive_add would loop and pass each fd in the set via SCM_RIGHTS?
Yes, you'd probably use the JSON to tell QEMU exactl
1 - 100 of 130 matches
Mail list logo
