On Wed, Mar 06, 2013 at 11:47:58AM +0800, Peter Maydell wrote:
> On 6 March 2013 11:30, 陳韋任 (Wei-Ren Chen) wrote:
> > While searching for QEMU SIMD issues, I found there was a paper presented
> > in 2011 [1], and the source code is also public on [2]. However, it seems
> > this project doesn't mak
Il 06/03/2013 04:47, Peter Maydell ha scritto:
> On 6 March 2013 11:30, 陳韋任 (Wei-Ren Chen) wrote:
>> While searching for QEMU SIMD issues, I found there was a paper presented
>> in 2011 [1], and the source code is also public on [2]. However, it seems
>> this project doesn't make any progress sinc
The FTSPI020 is an integrated SPI Flash controller
which supports up to 4 flash chips.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369.c | 16 +++
hw/arm/ftspi020.c | 340 +
hw/arm/ftspi020.h | 81 +++
Using qemu 1.4.0:
# qemu -hda test.raw -m 512 -cdrom
pfSense-LiveCD-2.0.2-RELEASE-amd64-20121207-2239.iso
Results in:
trap 12: page fault while in kernel mode
...
stopped at x86bios_emu_rdw+0x2f: movzwl (%rbx),%eax
Any ideas? Can somebody reproduce that?
To get the FreeBSD VM boot use the con
Il 06/03/2013 08:27, Kuo-Jung Su ha scritto:
> The FTWDT010 is used to prevent system from infinite loop
> while software gets trapped in the deadlock.
>
> Under the normal operation, users should restart FTWDT010
> at the regular intervals before counter counts down to 0.
>
> If the counter does
Il 06/03/2013 08:27, Kuo-Jung Su ha scritto:
> It provides separate second, minute, hour, and day counters. The second
> counter is toggled each second, the minute counter is toggled each minute,
> the hour counter is toggled each hour, and the day counter is toggled each
> day.
>
> The FTRTC011
Il 06/03/2013 08:27, Kuo-Jung Su ha scritto:
> Signed-off-by: Kuo-Jung Su
> ---
> include/qemu/bitops.h | 63
> -
> 1 file changed, 62 insertions(+), 1 deletion(-)
>
> diff --git a/include/qemu/bitops.h b/include/qemu/bitops.h
> index affcc96..9
Wolfson WM8731 is a simple audio codec for embedded systems.
It has 2 input and 1 output ports:
** Input **
1. Linue-In
2. Microphone
** Output **
1. Headphone out
BTW it's based on hw/wm8750.c with 16-bit I2S support by default.
Signed-off-by: Kuo-Jung Su
---
default-configs/arm-
On 6 March 2013 16:18, Paolo Bonzini wrote:
> Il 06/03/2013 04:47, Peter Maydell ha scritto:
>> I think my opinions are still the same -- interesting idea, but getting
>> it to work with a set of IR ops which aren't target or host specific
>> and getting it to give correct bit-for-bit results, rou
On Tue, 2013-03-05 at 20:45 -0500, Kevin O'Connor wrote:
>
> So, I think the question isn't what does real-hardware do (there's no
> gain to be had in emulating all of this). Instead, I think the
> question is - what makes the most sense.
Well,... what we implement for the 'native SeaBIOS on q
Il 06/03/2013 03:02, li guang ha scritto:
> 在 2013-03-05二的 20:00 +0100，Paolo Bonzini写道：
>> Do not do a hard reset for port 92h, keyboard controller, or cf9h soft reset.
>> These only reset the CPU.
>>
>> Reviewed-by: Anthony Liguori
>> Signed-off-by: Paolo Bonzini
>> ---
>> hw/lpc_ich9.c | 7 +++
The FTTMR010 provides three independent sets of sub-timers.
Two match registers are provided for each sub-timer, whenever
the value of the match registers equals any one value of the
sub-timers, the timer interrupt will be immediately triggered.
And it would also issue an interrupt when an overflow
On Sun, Mar 03, 2013 at 11:17:38AM +0200, Gleb Natapov wrote:
> On Thu, Feb 28, 2013 at 08:13:10PM +0800, Hu Tao wrote:
> > This series implements a new interface, kvm pv event, to notify host when
> > some events happen in guest. Right now there is one supported event: guest
> > panic.
> >
> What
Il 06/03/2013 00:23, Peter Maydell ha scritto:
> On 6 March 2013 03:00, Paolo Bonzini wrote:
>> On the x86, some devices need access to the CPU reset pin (INIT#).
>> Provide a generic service to do this, using one of the internal
>> cpu_interrupt targets. Generalize the PPC-specific code for
>> C
Hi,
On Mon, Mar 04, 2013 at 11:05:37AM +0100, Paolo Bonzini wrote:
> Il 03/03/2013 10:17, Gleb Natapov ha scritto:
> > On Thu, Feb 28, 2013 at 08:13:10PM +0800, Hu Tao wrote:
> >> This series implements a new interface, kvm pv event, to notify host when
> >> some events happen in guest. Right now
2013/3/6 Paolo Bonzini :
> Il 06/03/2013 08:27, Kuo-Jung Su ha scritto:
>> The FTWDT010 is used to prevent system from infinite loop
>> while software gets trapped in the deadlock.
>>
>> Under the normal operation, users should restart FTWDT010
>> at the regular intervals before counter counts down
Lei Li writes:
> Pass the right type for setsockopt(), and this will also
> fix the compiler warning when cross build for qemu-ga.exe:
>
> util/osdep.c: In function 'socket_set_nodelay':
> util/osdep.c:69:5: warning: passing argument 4 of 'setsockopt' from
>incompatible pointe
On Tue, Mar 05, 2013 at 09:26:18AM +0100, Paolo Bonzini wrote:
> Il 05/03/2013 04:17, Hu Tao ha scritto:
> > Will
> >
> > if (runstate_check(RUN_STATE_INTERNAL_ERROR) ||
> > runstate_check(RUN_STATE_SHUTDOWN) ||
> > runstate_check(RUN_STATE_GUEST_PANICKED)) {
>
在 2013-03-06三的 09:36 +0100，Paolo Bonzini写道：
> Il 06/03/2013 03:02, li guang ha scritto:
> > 在 2013-03-05二的 20:00 +0100，Paolo Bonzini写道：
> >> Do not do a hard reset for port 92h, keyboard controller, or cf9h soft
> >> reset.
> >> These only reset the CPU.
> >>
> >> Reviewed-by: Anthony Liguori
> >
Il 06/03/2013 09:56, Hu Tao ha scritto:
>> >
>> > Something like this should work (in SeaBIOS's src/acpi-dsdt-isa.dsl):
>> >
>> > Device(PEVT) {
>> > Name(_HID, EisaId("QEMU0001"))
>> > OperationRegion(PEOR, SystemIO, 0x505, 0x01)
>> > Field(PEOR, ByteAcc, NoLock, Pres
Il 06/03/2013 03:02, Peter Crosthwaite ha scritto:
> If you truly have connectivity from device land to the CPU cluster
> should that be reflected by some sort of QOM linkage?
I think in real hardware what happens is that a single "wire" is
distributed to all CPUs. Devices do not have direct link
Il 06/03/2013 10:06, li guang ha scritto:
> 在 2013-03-06三的 09:36 +0100，Paolo Bonzini写道：
>> > Il 06/03/2013 03:02, li guang ha scritto:
>>> > > 在 2013-03-05二的 20:00 +0100，Paolo Bonzini写道：
> >> Do not do a hard reset for port 92h, keyboard controller, or cf9h
> >> soft reset.
> >> The
Aurelien Jarno writes:
> On Tue, Mar 05, 2013 at 08:22:57AM +0800, Peter Maydell wrote:
>> On 5 March 2013 08:19, Aurelien Jarno wrote:
>> > The versatile express has no SCSI card, but instead boot on an SD card.
>> > Change block_default_type accordingly.
>>
>> I notice that no other board has
On Wed, Mar 06, 2013 at 09:24:35AM +0200, Dmitry Fleytman wrote:
> I've sent V13 of patches with license changed.
Thanks for resending. I'm happy to do trivial fixups while merging but
I don't do that in the case of license changes. The reason is that
there must be a clear record of you choosing
Peter Maydell writes:
> On 5 March 2013 13:26, Michael Tokarev wrote:
>> For many years, qemu defaults to 128Mb of guest RAM size.
>> Today, this is just too small, and many OSes fails to boot
>> with this size, more, they fail to produce any reasonable
>> messages either (eg, windows7 just cras
在 2013-03-06三的 10:07 +0100，Paolo Bonzini写道：
> Il 06/03/2013 09:56, Hu Tao ha scritto:
> >> >
> >> > Something like this should work (in SeaBIOS's src/acpi-dsdt-isa.dsl):
> >> >
> >> > Device(PEVT) {
> >> > Name(_HID, EisaId("QEMU0001"))
> >> > OperationRegion(PEOR, SystemIO, 0
Am 06.03.2013 um 08:11 schrieb Laurent Desnogues :
> On Wed, Mar 6, 2013 at 3:01 AM, Alexander Graf wrote:
>> This patch adds all the prerequisites for AArch64 support that didn't
>> fit into split up patches. It extends important bits in the core cpu
>> headers to also take AArch64 mode into a
On Wed, Mar 06, 2013 at 04:46:58PM +0800, Hu Tao wrote:
> On Sun, Mar 03, 2013 at 11:17:38AM +0200, Gleb Natapov wrote:
> > On Thu, Feb 28, 2013 at 08:13:10PM +0800, Hu Tao wrote:
> > > This series implements a new interface, kvm pv event, to notify host when
> > > some events happen in guest. Righ
On Wed, Mar 06, 2013 at 10:07:31AM +0100, Paolo Bonzini wrote:
> Il 06/03/2013 09:56, Hu Tao ha scritto:
> >> >
> >> > Something like this should work (in SeaBIOS's src/acpi-dsdt-isa.dsl):
> >> >
> >> > Device(PEVT) {
> >> > Name(_HID, EisaId("QEMU0001"))
> >> > OperationRegio
On Wed, Mar 6, 2013 at 10:36 AM, Alexander Graf wrote:
>
>
> Am 06.03.2013 um 08:11 schrieb Laurent Desnogues
> :
>
>> On Wed, Mar 6, 2013 at 3:01 AM, Alexander Graf wrote:
>>> This patch adds all the prerequisites for AArch64 support that didn't
>>> fit into split up patches. It extends importa
> On Wed, Mar 06, 2013 at 10:07:31AM +0100, Paolo Bonzini wrote:
> > Il 06/03/2013 09:56, Hu Tao ha scritto:
> > >> >
> > >> > Something like this should work (in SeaBIOS's
> > >> > src/acpi-dsdt-isa.dsl):
> > >> >
> > >> > Device(PEVT) {
> > >> > Name(_HID, EisaId("QEMU0001"))
> > >
On Tue, Mar 05, 2013 at 01:21:18PM -0300, Lucas Meneghel Rodrigues wrote:
> On 03/05/2013 01:14 PM, Gerd Hoffmann wrote:
> > Hi,
> >
> >>>I don't think we have *any* regular autotest coverage for master, have
> >>>we?
> >>
> >>^ Yes, there is coverage. There's a daily job called sanity that takes
On Tue, Mar 05, 2013 at 05:51:21PM +0800, Lei Li wrote:
> Pass the right type for setsockopt(), and this will also
> fix the compiler warning when cross build for qemu-ga.exe:
>
> util/osdep.c: In function 'socket_set_nodelay':
> util/osdep.c:69:5: warning: passing argument 4 of 'setsockopt' from
> On 03/06/13 00:37, Eric Blake wrote:
>
> > I guess I had in my mind %c instead of %u; still, I can't help but
> > wonder if fprintf() and buffering is overkill, compared to just
> > doing
> > something like this:
> > write(fd, &"01"[vcpu->online], 1);
> >
> > (okay, I hope you would favor read
On Wed, Mar 06, 2013 at 04:48:17AM -0500, Paolo Bonzini wrote:
>
> > On Wed, Mar 06, 2013 at 10:07:31AM +0100, Paolo Bonzini wrote:
> > > Il 06/03/2013 09:56, Hu Tao ha scritto:
> > > >> >
> > > >> > Something like this should work (in SeaBIOS's
> > > >> > src/acpi-dsdt-isa.dsl):
> > > >> >
> >
> diff --git a/tcg/arm/tcg-target.h b/tcg/arm/tcg-target.h
> index b6eed1f..cb89419 100644
> --- a/tcg/arm/tcg-target.h
> +++ b/tcg/arm/tcg-target.h
> @@ -73,10 +73,13 @@ typedef enum {
> #define TCG_TARGET_HAS_eqv_i32 0
> #define TCG_TARGET_HAS_nand_i32 0
> #define TCG_TARGET_H
On Tue, Mar 05, 2013 at 09:46:30PM +0100, Benoît Canet wrote:
> > You need to set a more specific goal. Some questions to get started:
> > * Which workloads do you care about and what are their
> > characteristics (sequential or random I/O, queue depth)?
> > * Do you care about 1 vcpu guests or
> On Tue, Feb 19, 2013 at 09:42:45AM +0100, Paolo Bonzini wrote:
> > Il 19/02/2013 07:00, Michael R. Hines ha scritto:
> > > Yes, this is done at migration time (see functions
> > > "rdma_client_init"
> > > and "rdma_server_prepare()")
> > >
> > > To explain the host and port:
> > >
> > > The se
On Wed, Mar 06, 2013 at 09:57:40AM +1100, Alexey Kardashevskiy wrote:
> On 06/03/13 01:23, Michael S. Tsirkin wrote:
> >On Wed, Mar 06, 2013 at 12:21:47AM +1100, Alexey Kardashevskiy wrote:
> >>On 05/03/13 23:56, Michael S. Tsirkin wrote:
> The patch f56a12475ff1b8aa61210d08522c3c8aaf0e2648 "vh
> > > It doesn't work while running under ROM mode. ( no -kernel )
> > > Because Faraday SoC Platform usually designed to boot from ROM and
> > > followed by an AHB remapping process (i.e. remap ROM/RAM address).
> >
> > What doesn't work exactly? Why aren't these called? Or are
> > you forcing a
inet_connect_opts() tries all possible addrinfos returned by
getaddrinfo(). If one fails with an error, the next one is tried. In
this case, the Error should be discarded because the whole operation is
successful if another addrinfo from the list succeeds; and if it
doesn't, setting an already set
Il 06/03/2013 11:48, Kevin Wolf ha scritto:
> inet_connect_opts() tries all possible addrinfos returned by
> getaddrinfo(). If one fails with an error, the next one is tried. In
> this case, the Error should be discarded because the whole operation is
> successful if another addrinfo from the list
Am 06.03.2013 um 12:04 hat Paolo Bonzini geschrieben:
> Il 06/03/2013 11:48, Kevin Wolf ha scritto:
> > inet_connect_opts() tries all possible addrinfos returned by
> > getaddrinfo(). If one fails with an error, the next one is tried. In
> > this case, the Error should be discarded because the whol
No problem.
On Wed, Mar 6, 2013 at 11:26 AM, Stefan Hajnoczi wrote:
> On Wed, Mar 06, 2013 at 09:24:35AM +0200, Dmitry Fleytman wrote:
> > I've sent V13 of patches with license changed.
>
> Thanks for resending. I'm happy to do trivial fixups while merging but
> I don't do that in the case of
Am 06.03.2013 10:13, schrieb Paolo Bonzini:
> Il 06/03/2013 03:02, Peter Crosthwaite ha scritto:
>> If you truly have connectivity from device land to the CPU cluster
>> should that be reflected by some sort of QOM linkage?
>
> I think in real hardware what happens is that a single "wire" is
> dis
Stefan Hajnoczi writes:
[...]
> The way that buildbot does this is and I think the same is possible for
> kvm autotest:
> 1. Send failure notifications to qemu-devel.
> 2. Provide a website to check the status
> http://buildbot.b1-systems.de/qemu/.
+1
[...]
On 6 March 2013 17:13, Paolo Bonzini wrote:
> Il 06/03/2013 03:02, Peter Crosthwaite ha scritto:
>> If you truly have connectivity from device land to the CPU cluster
>> should that be reflected by some sort of QOM linkage?
>
> I think in real hardware what happens is that a single "wire" is
> dis
Il 06/03/2013 13:12, Peter Maydell ha scritto:
> On 6 March 2013 17:13, Paolo Bonzini wrote:
>> Il 06/03/2013 03:02, Peter Crosthwaite ha scritto:
>>> If you truly have connectivity from device land to the CPU cluster
>>> should that be reflected by some sort of QOM linkage?
>>
>> I think in real
On Tue, Mar 05, 2013 at 05:35:10PM +0100, Samuel Thibault wrote:
> The reason why IPv6 does not work when using -net socket,mcast=foo is
> that since qemu explicitly sets IP_MULTICAST_LOOP to 1, it receives its
> own frames. When the IPv6 stack performs duplicate addresse detection
> (DAD) through
I can also reproduce it. (Host cpu intel or amd, Guest cpu qemu64/kvm64/host).
They are also a bugreport on the freebsd mailing here:
http://lists.freebsd.org/pipermail/freebsd-amd64/2013-January/015092.html
- Mail original -
De: "Dietmar Maurer"
À: qemu-devel@nongnu.org
Envoyé: Merc
On Mon, Mar 04, 2013 at 02:33:16PM +, Dietmar Maurer wrote:
> > > > Is it using 64 KB writes and have you tried 256 KB writes?
> > >
> > > I use a modified 'qemu-img convert' at 64KB block size (I need 64KB for
> > backup).
> >
> > Maybe you'd better use a different output format that doesn't
This patch series attempts to add Windows implementation
for qemu-ga commands guest-get-time and guest-set-time.
The previous thread about the interfaces introduced and
the POSIX-specific command implementation has already
been accepted, the reference link:
http://article.gmane.org/gmane.comp.em
Signed-off-by: Lei Li
---
qga/commands-win32.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 7e8ecb3..4febec7 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -22,6 +22,8 @@
#d
Signed-off-by: Lei Li
---
qga/commands-win32.c | 35 +++
1 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 4febec7..1a90aa7 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -136,6 +136
On Mon, Feb 25, 2013 at 04:35:09PM +, Dietmar Maurer wrote:
> > >>> If we use nbd, how can we pass additional information to the other
> > >>> side, for example information about unallocated regions?
> > >>>
> > >>
> > >> You can either send trim commands, or just skip those regions and let
> >
On 03/06/2013 05:56 PM, Stefan Hajnoczi wrote:
On Tue, Mar 05, 2013 at 05:51:21PM +0800, Lei Li wrote:
Pass the right type for setsockopt(), and this will also
fix the compiler warning when cross build for qemu-ga.exe:
util/osdep.c: In function 'socket_set_nodelay':
util/osdep.c:69:5: warning:
On 03/06/2013 04:59 PM, Markus Armbruster wrote:
Lei Li writes:
Pass the right type for setsockopt(), and this will also
fix the compiler warning when cross build for qemu-ga.exe:
util/osdep.c: In function 'socket_set_nodelay':
util/osdep.c:69:5: warning: passing argument 4 of 'setsockopt' fr
libvirt has a long-standing bug: when removing the device,
it can request removal but does not know when does the
removal complete. Add an event so we can fix this in a robust way.
Signed-off-by: Michael S. Tsirkin
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index b2698e4..ec5b810 10064
Stefan Hajnoczi, le Wed 06 Mar 2013 13:29:37 +0100, a écrit :
> On Tue, Mar 05, 2013 at 05:35:10PM +0100, Samuel Thibault wrote:
> > The reason why IPv6 does not work when using -net socket,mcast=foo is
> > that since qemu explicitly sets IP_MULTICAST_LOOP to 1, it receives its
> > own frames. Whe
On Wed, Mar 06, 2013 at 09:07:25PM +0800, Lei Li wrote:
> On 03/06/2013 05:56 PM, Stefan Hajnoczi wrote:
> >On Tue, Mar 05, 2013 at 05:51:21PM +0800, Lei Li wrote:
> >>Pass the right type for setsockopt(), and this will also
> >>fix the compiler warning when cross build for qemu-ga.exe:
> >>
> >>ut
On 03/06/2013 09:16 PM, Stefan Hajnoczi wrote:
On Wed, Mar 06, 2013 at 09:07:25PM +0800, Lei Li wrote:
On 03/06/2013 05:56 PM, Stefan Hajnoczi wrote:
On Tue, Mar 05, 2013 at 05:51:21PM +0800, Lei Li wrote:
Pass the right type for setsockopt(), and this will also
fix the compiler warning when c
With passthrough security model creation files in guest still doesn't
work in Raring.
QEMU version is 1.4.0,
AppArmor folder rules added to libvirt profile of tested VM,
Permissions on testing folder is 777.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Ops, wrong patch set... will resend it. Sorry for the missending. :-(
On 03/06/2013 08:57 PM, Lei Li wrote:
Signed-off-by: Lei Li
---
qga/commands-win32.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands
This patch series attempts to add Windows implementation
for qemu-ga commands guest-get-time and guest-set-time.
The previous thread about the interfaces introduced and
the POSIX-specific command implementation has already
been accepted, the reference link:
http://article.gmane.org/gmane.comp.em
Signed-off-by: Lei Li
---
qga/commands-win32.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 7e8ecb3..4febec7 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -22,6 +22,8 @@
#d
Signed-off-by: Lei Li
---
qga/commands-win32.c | 35 +++
1 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index 4febec7..1a90aa7 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -136,6 +136
On 03/05/2013 05:44 PM, Laszlo Ersek wrote:
>
> Anyway I'd prefer to avoid direct write()s with nbyte > 1 as I'd have to
> handle partial transfers, if for nothing else than principle. (IIRC
> avoiding that loop was my main motivation for stdio.)
Fair enough - this code is not a hotspot, so stdio
On 03/05/2013 04:05 PM, Laszlo Ersek wrote:
>>> +# If part or whole of the requested operation can't be carried out, the
>>> guest
>>> +# VCPU state will be unspecified.
>>
>> Completely unspecified?
>
> Yes. "Unspecified" means "valid" (ie. at least one VCPU will be online,
> the guest won't be
Am 06.03.2013 14:00, schrieb Michael S. Tsirkin:
> libvirt has a long-standing bug: when removing the device,
> it can request removal but does not know when does the
> removal complete. Add an event so we can fix this in a robust way.
>
> Signed-off-by: Michael S. Tsirkin
Sounds like a good ide
On Wed, Mar 06, 2013 at 02:57:22PM +0100, Andreas Färber wrote:
> Am 06.03.2013 14:00, schrieb Michael S. Tsirkin:
> > libvirt has a long-standing bug: when removing the device,
> > it can request removal but does not know when does the
> > removal complete. Add an event so we can fix this in a rob
Fix the compiler warning when cross build qemu-ga
for windows by using qemu_setsockopt() instead of
setsockopt().
util/osdep.c: In function 'socket_set_nodelay':
util/osdep.c:69:5: warning: passing argument 4 of 'setsockopt' from
incompatible pointer type [enabled by default]
In
Please file a new bug using 'ubuntu-bug libvirt-bin', providing details
on the setup and how it is failing.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1018530
Title:
No write access in a 9p/virt
I already sent a mail to the qemu-devel list - no answer so far.
> -Original Message-
> From: Alexandre DERUMIER [mailto:aderum...@odiso.com]
> Sent: Mittwoch, 06. März 2013 13:42
> To: Dietmar Maurer
> Cc: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] problems with freeBSD
>
> I can
> > > Maybe you'd better use a different output format that doesn't
> > > restrict you to 64k writes.
> >
> > The output format is not really the restriction. The problem is that
> > an additional IPC layer add overhead, an d I do not want that (because it is
> totally unnecessary).
>
> I missed t
On 03/06/2013 06:00 AM, Michael S. Tsirkin wrote:
> libvirt has a long-standing bug: when removing the device,
> it can request removal but does not know when does the
> removal complete. Add an event so we can fix this in a robust way.
s/complete/completes/
>
> Signed-off-by: Michael S. Tsirkin
On 03/06/13 12:11, Kevin Wolf wrote:
> Am 06.03.2013 um 12:04 hat Paolo Bonzini geschrieben:
>> Il 06/03/2013 11:48, Kevin Wolf ha scritto:
>>> inet_connect_opts() tries all possible addrinfos returned by
>>> getaddrinfo(). If one fails with an error, the next one is tried. In
>>> this case, the Er
Note: Patch 1/7 is a bug fix for QCOW, that is also needed for VHDX
This adds the initial support for VHDX image files. It supports both
read and write operations, across fixed and dynamic files.
Notably, the following is not yet supported:
* Differencing files
* Log replay (so we will r
Commit 9a665b2b made bdrv_truncate() call bdrv_drain_all(), but this breaks
QCOW images, as well other future image formats (such as VHDX) that may call
bdrv_truncate(bs->file) from within a read/write operation. For example, QCOW
will cause an assert, due to tracked_requests not being empty (sinc
> > > > Or can we simply add a header to each write with additional information?
> > >
> > > Let's discuss it once we have a clearer picture of what that
> > > additional info would be.
> >
> > OK, just discovered such case.
> >
> > For example it would be nice to pass the size of the devices someh
This adds the Castagnoli CRC32C algorithm, using the 0x11EDC6F41
polynomial.
This is extracted from the linux kernel cryptographic crc32.c module.
The algorithm is based on:
Castagnoli93: Guy Castagnoli and Stefan Braeuer and Martin Herrman
"Optimization of Cyclic Redundancy-Check C
This is the initial block driver framework for VHDX image support
(i.e. Hyper-V image file formats), that supports opening VHDX files, and
parsing the headers.
This commit does not yet enable:
- reading
- writing
- updating the header
- differencing files (images with parents)
This adds in write support for VHDX images. This supports writing to
both dynamic and fixed VHDX images. Differencing images are still
unsupported.
Signed-off-by: Jeff Cody
---
block/vhdx.c | 144 ++-
1 file changed, 142 insertions(+), 2
This is based on Microsoft's VHDX specification:
"VHDX Format Specification v0.95", published 4/12/2012
https://www.microsoft.com/en-us/download/details.aspx?id=29681
These structures define the various header, metadata, and other
block structures defined in the VHDX specification.
Signed
This adds in read-only support to the VHDX image format. This supports
reads for fixed-size, and dynamic sized VHDX images.
Differencing files are still unsupported.
The image must be opened without BDRV_O_RDWR set, because we do not
yet update the headers. I.e., pass 'readonly=on' in the drive
This adds the ability to update the headers in a VHDX image, including
generating a new MS-compatible GUID, and checksum.
Signed-off-by: Jeff Cody
---
block/vhdx.c | 165 ++-
1 file changed, 163 insertions(+), 2 deletions(-)
diff --git a/b
On Wed, Mar 06, 2013 at 07:44:32AM -0700, Eric Blake wrote:
> On 03/06/2013 06:00 AM, Michael S. Tsirkin wrote:
> > libvirt has a long-standing bug: when removing the device,
> > it can request removal but does not know when does the
> > removal complete. Add an event so we can fix this in a robust
Il 06/03/2013 15:44, Eric Blake ha scritto:
> Question - if libvirt misses the event (for example, if libvirtd
> requests a remove, but then gets restarted, and the event arrives before
> libvirtd is back up), is there a way to poll whether the the removal has
> completed? The event is great to mi
CoQueue uses a BH to awake coroutines that were made ready to run again
using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
currently runs in the iothread AioContext and would break coroutines
that run in a different AioContext.
This is a slightly tricky problem because the lifetime
Il 06/03/2013 15:53, Stefan Hajnoczi ha scritto:
> CoQueue uses a BH to awake coroutines that were made ready to run again
> using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
> currently runs in the iothread AioContext and would break coroutines
> that run in a different AioContext
Il 06/03/2013 15:46, Laszlo Ersek ha scritto:
>> > We could assert(!error_is_set(errp)) if we wanted. As soon as you've got
>> > an Error, you must return instead of calling more functions with the
>> > same error pointer.
> I think Luiz would suggest (*) to receive any error into a
> NULL-initiali
[Note cc: Luiz]
Kevin Wolf writes:
> inet_connect_opts() tries all possible addrinfos returned by
> getaddrinfo(). If one fails with an error, the next one is tried. In
> this case, the Error should be discarded because the whole operation is
> successful if another addrinfo from the list succee
Kevin Wolf writes:
> Am 06.03.2013 um 12:04 hat Paolo Bonzini geschrieben:
>> Il 06/03/2013 11:48, Kevin Wolf ha scritto:
>> > inet_connect_opts() tries all possible addrinfos returned by
>> > getaddrinfo(). If one fails with an error, the next one is tried. In
>> > this case, the Error should be
On 03/06/2013 06:45 AM, Lei Li wrote:
> Signed-off-by: Lei Li
> ---
> qga/commands-win32.c | 35 +++
> 1 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/qga/commands-win32.c b/qga/commands-win32.c
> index 4febec7..1a90aa7 100644
> --- a/qga/comm
Am 06.03.2013 um 16:04 hat Paolo Bonzini geschrieben:
> Il 06/03/2013 15:46, Laszlo Ersek ha scritto:
> >> > We could assert(!error_is_set(errp)) if we wanted. As soon as you've got
> >> > an Error, you must return instead of calling more functions with the
> >> > same error pointer.
> > I think Lu
Am 06.03.2013 um 15:42 hat Dietmar Maurer geschrieben:
> > > > Maybe you'd better use a different output format that doesn't
> > > > restrict you to 64k writes.
> > >
> > > The output format is not really the restriction. The problem is that
> > > an additional IPC layer add overhead, an d I do not
On 03/06/2013 06:45 AM, Lei Li wrote:
> Signed-off-by: Lei Li
> ---
> qga/commands-win32.c | 28
> 1 files changed, 28 insertions(+), 0 deletions(-)
>
> diff --git a/qga/commands-win32.c b/qga/commands-win32.c
> index 7e8ecb3..4febec7 100644
> --- a/qga/commands-wi
> > When we run backup, we need to read such block on every write from the
> guest.
> > So if we increase block size we get additional delays.
>
> How about variable block sizes? I mean this is a stream format that has a
> header
> for each block anyway. Include a size there and be done.
You can
On 03/06/13 16:19, Kevin Wolf wrote:
> Am 06.03.2013 um 16:04 hat Paolo Bonzini geschrieben:
>> Il 06/03/2013 15:46, Laszlo Ersek ha scritto:
> We could assert(!error_is_set(errp)) if we wanted. As soon as you've got
> an Error, you must return instead of calling more functions with the
>>>
Am 06.03.2013 um 15:53 hat Stefan Hajnoczi geschrieben:
> CoQueue uses a BH to awake coroutines that were made ready to run again
> using qemu_co_queue_next() or qemu_co_queue_restart_all(). The BH
> currently runs in the iothread AioContext and would break coroutines
> that run in a different Aio
[adding libvirt]
On 03/06/2013 07:52 AM, Paolo Bonzini wrote:
> Il 06/03/2013 15:44, Eric Blake ha scritto:
>> Question - if libvirt misses the event (for example, if libvirtd
>> requests a remove, but then gets restarted, and the event arrives before
>> libvirtd is back up), is there a way to pol
1 - 100 of 247 matches
Mail list logo
