Am 14.09.2010 17:11, schrieb Anthony Liguori:
> On 09/14/2010 09:47 AM, Chris Wright wrote:
>> 0.13
>> - if all goes well...tomorrow
>>
>
> To tag, it may be thursday for announcement. I need to run a regression
> run tonight.
>
>> qed/qcow2
>> - increase concurrency, performance
>>
>
Public bug reported:
commit 46411f863c26ff85c48b97939502007610c95398
Linux host
Kfreebsd guest
qemu -boot c -hda qemu_kfreebsd_i386.img -enable-kvm
QEMU crashes with free on invalid pointer:
*** glibc detected *** qemu: free(): invalid pointer: 0x0253cf60 ***
=== Backtrace:
Configure command used:
./configure --enable-linux-aio --enable-io-thread --enable-kvm
--
Crashes with kfreebsd guest when using KVM
https://bugs.launchpad.net/bugs/638806
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU:
Hi Rick,
2010/9/15 Corentin Chary :
> On Tue, Sep 14, 2010 at 10:00 PM, Rick Vernam wrote:
>> I don't have nearly enough info to file a proper bug report.
>>
>> I am running qemu-kvm-0.13.0 rc1
>> starting qemu like so:
>> /root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
>> file=/ro
From: Jes Sorensen
This patch introduces cutils.c: strtobytes() and gets rid of the
multiple custom hacks for parsing byte sizes. In addition it add
supports for specifying human style sizes such as 1.5G. Last it
eliminates the horrible abuse of a float to store the byte size for
migrate_set_spee
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
cutils.c | 39 +++
qemu-common.h |1 +
vl.c | 26 +++---
3 files changed, 47 insertions(+), 19 deletions(-)
diff --git a/cutils.c b/cutils.c
index 036ae3c..a3087fe 1
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
cutils.c | 27 ++-
1 files changed, 26 insertions(+), 1 deletions(-)
diff --git a/cutils.c b/cutils.c
index a3087fe..d34ed08 100644
--- a/cutils.c
+++ b/cutils.c
@@ -259,16 +259,38 @@ int fcntl_setfl(int fd, int flag)
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
migration.c |4 ++--
qemu-monitor.hx |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/migration.c b/migration.c
index 468d517..9ee8b17 100644
--- a/migration.c
+++ b/migration.c
@@ -132,10 +132,10 @@ int do_migr
From: Jes Sorensen
'f' double is no longer used, and we should be using floating point
variables to store byte sizes. Remove it.
Signed-off-by: Jes Sorensen
---
monitor.c | 17 +
1 files changed, 1 insertions(+), 16 deletions(-)
diff --git a/monitor.c b/monitor.c
index 36300
From: Jes Sorensen
Octet format relies on strtobytes which supports K/k, M/m, G/g, T/t
suffixes and unit support for humans, like 1.3G
Signed-off-by: Jes Sorensen
---
monitor.c | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monit
Global Innovative Campus Newsletter
We have removed your email address from our list.
We're sorry to see you go.
---
Did you forward your email to a friend, and they accidentally clicked the
unsubscrib
On 09/15/2010 03:30 AM, Kevin Wolf wrote:
Am 14.09.2010 17:11, schrieb Anthony Liguori:
On 09/14/2010 09:47 AM, Chris Wright wrote:
0.13
- if all goes well...tomorrow
To tag, it may be thursday for announcement. I need to run a regression
run tonight.
qed/qcow2
- in
Document the options common to all block devices.
This comes from Kevin.
Signed-off-by: Amit Shah
CC: Kevin Wolf
---
block_int.h | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/block_int.h b/block_int.h
index ce20285..06e894d 100644
--- a/block_int.h
+++ b
This results in an output like:
$ ./x86_64-softmmu/qemu-system-x86_64 -device virtio-net-pci,?
...
virtio-net-pci.mac=macaddr, The MAC address for the NIC.
virtio-net-pci.vlan=vlan, The VLAN to associate the NIC with.
virtio-net-pci.netdev=netdev, The peer net device to associate with this
virt
Hello,
This is a rebase of the patchset I'd sent earlier.
I add the 4/4 patch, documenting common block device properties.
Other than that, the usual notes apply: this is just the start, just
getting the framework in place and a few examples so that people can
then pick up and start documenting t
Document the parameters for the virtserialport and virtioconsole
devices.
Example:
$ ./x86_64-softmmu/qemu-system-x86_64 -device virtserialport,?
virtserialport.nr=uint32, The 'number' for the port for \
predictable port numbers. Use this to spawn ports if you \
plan to migrate the guest.
virtse
Am 15.09.2010 14:26, schrieb Anthony Liguori:
> On 09/15/2010 03:30 AM, Kevin Wolf wrote:
>> Am 14.09.2010 17:11, schrieb Anthony Liguori:
>>
>>> On 09/14/2010 09:47 AM, Chris Wright wrote:
>>>
0.13
- if all goes well...tomorrow
>>> To tag, it may be thursday f
On Wed, Sep 15, 2010 at 02:38:18PM +0900, Isaku Yamahata wrote:
> This patch implements helper functions for pci express capability
> and pci express extended capability allocation.
> NOTE: presence detection depends on pci_qdev_init() change.
>
> Signed-off-by: Isaku Yamahata
>
> ---
> Changes
On Wed, Sep 15, 2010 at 02:38:16PM +0900, Isaku Yamahata wrote:
> introduce helper function pci_shift_{word, long}() which returns
> returns shifted word/long of given position and range.
> They will be used later.
>
> Signed-off-by: Isaku Yamahata
So I think the reason you *think* you need thes
On Wed, Sep 15, 2010 at 02:38:14PM +0900, Isaku Yamahata wrote:
> implemented msi support functions.
>
> Signed-off-by: Isaku Yamahata
>
> ---
> Changes v2 -> v3:
> - improved comment wording.
> - simplified shift/ffs dance.
>
> Changes v1 -> v2:
> - opencode some oneline helper function/macros
On Wed, Sep 15, 2010 at 02:50:01PM +0900, Isaku Yamahata wrote:
> On Wed, Sep 08, 2010 at 01:31:22PM +0300, Michael S. Tsirkin wrote:
> > > +
> > > +static void pcie_notify(PCIDevice *dev, uint16_t vector,
> > > +bool trigger, int level)
> > > +{
> > > +/* masking/maskin
On 09/15/2010 07:38 AM, Kevin Wolf wrote:
No, we don't really care if the L2 entry is on disk. If the guest want
to have its data safe it needs to issue an explicit flush anyway. The
only thing we want to achieve with bdrv_write_sync is to maintain the
right order between metadata updates to surv
Am 15.09.2010 15:21, schrieb Anthony Liguori:
> On 09/15/2010 07:38 AM, Kevin Wolf wrote:
>> No, we don't really care if the L2 entry is on disk. If the guest want
>> to have its data safe it needs to issue an explicit flush anyway. The
>> only thing we want to achieve with bdrv_write_sync is to ma
Public bug reported:
hi there,
i'm using qemu-kvm backend in version: # qemu-kvm -version
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008
Fabrice Bellard
and there are just *not working any of model=$type with combinations of
recent sunos (solaris, openindiana, openso
On 09/15/2010 08:30 AM, Kevin Wolf wrote:
Am 15.09.2010 15:21, schrieb Anthony Liguori:
On 09/15/2010 07:38 AM, Kevin Wolf wrote:
No, we don't really care if the L2 entry is on disk. If the guest want
to have its data safe it needs to issue an explicit flush anyway. The
only thing we
Am 15.09.2010 15:52, schrieb Anthony Liguori:
> On 09/15/2010 08:30 AM, Kevin Wolf wrote:
>> Am 15.09.2010 15:21, schrieb Anthony Liguori:
>>
>>> On 09/15/2010 07:38 AM, Kevin Wolf wrote:
>>>
No, we don't really care if the L2 entry is on disk. If the guest want
to have its data
On Mon, Sep 13, 2010 at 03:47:12PM +0200, Michal Novotny wrote:
> Hi,
>
> this is the patch to update serial port parameters after guest is
> already loaded.
Hi
This patch didn't apply:
% git am -s ~/.maildir/minovotn/
Applying: serial: Update parameters after load
error: patch failed: hw/seria
On Sat, Sep 11, 2010 at 03:08:32AM +0200, Alexander Graf wrote:
> There goes another round of PowerPC fixes. Originally this should only have
> been a fix for the MSR_POW issue (bug 608107), but I also stumbed over recent
> Linux kernels not booting in qemu-system-ppc64. So a fix for that is also
>
On 09/15/2010 03:53 PM, Edgar E. Iglesias wrote:
On Mon, Sep 13, 2010 at 03:47:12PM +0200, Michal Novotny wrote:
Hi,
this is the patch to update serial port parameters after guest is
already loaded.
Hi
This patch didn't apply:
% git am -s ~/.maildir/minovotn/
Applying: serial: Upda
jes.soren...@redhat.com wrote:
> From: Jes Sorensen
> value <<= 10;
> break;
> case 0:
> +if (divider) {
> +value = 0;
> +break;
changing break by goto fail here?
1.5G and 1.0G is ok, but using 1024.00 or similar should be one error,
no?
ni
On Wed, Sep 15, 2010 at 04:39:20PM +0200, Michal Novotny wrote:
> On 09/15/2010 03:53 PM, Edgar E. Iglesias wrote:
> > On Mon, Sep 13, 2010 at 03:47:12PM +0200, Michal Novotny wrote:
> >
> >> Hi,
> >>
> >> this is the patch to update serial port parameters after guest is
> >> already loaded.
>
On Wednesday 15 September 2010 05:46:55 you wrote:
> Hi Rick,
>
> 2010/9/15 Corentin Chary :
> > On Tue, Sep 14, 2010 at 10:00 PM, Rick Vernam wrote:
> >> I don't have nearly enough info to file a proper bug report.
> >>
> >> I am running qemu-kvm-0.13.0 rc1
> >> starting qemu like so:
> >> /roo
On 09/15/2010 04:45 PM, Edgar E. Iglesias wrote:
On Wed, Sep 15, 2010 at 04:39:20PM +0200, Michal Novotny wrote:
On 09/15/2010 03:53 PM, Edgar E. Iglesias wrote:
On Mon, Sep 13, 2010 at 03:47:12PM +0200, Michal Novotny wrote:
Hi,
this is the patch to update serial port para
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting qemu like so:
/root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
file=/root/qemu/w2k3_server.raw,if=virtio,aio=native -net
nic,model=virtio,macaddr=52:54:00:12:34:56 -net tap,ifname
Public bug reported:
Positng the issue here since I did not get any reply on the ML.
I was trying to update some windows XP (SP3) images in kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
is mini-setup) I
On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
> I don't have nearly enough info to file a proper bug report.
>
> I am running qemu-kvm-0.13.0 rc1
> starting qemu like so:
> /root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
> file=/root/qemu/w2k3_server.raw,if=virtio,ai
On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
> On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
> > I don't have nearly enough info to file a proper bug report.
> >
> > I am running qemu-kvm-0.13.0 rc1
> > starting qemu like so:
> > /root/qemu/bin/qemu-system-x86_64 -cpu
On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
> > On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
> > > I don't have nearly enough info to file a proper bug report.
> > >
> > > I am running qemu-kvm-0.13.0 rc
On 09/15/2010 02:23 PM, jes.soren...@redhat.com wrote:
switch (*endptr++) {
case 'K':
case 'k':
value<<= 10;
break;
case 0:
+if (divider) {
+value = 0;
+break;
+}
case 'M':
case 'm':
value<<=
On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
> On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> > On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
> > > On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
> > > > I don't have nearly enough info to fi
On 09/15/2010 10:45 AM, Paolo Bonzini wrote:
On 09/15/2010 02:23 PM, jes.soren...@redhat.com wrote:
switch (*endptr++) {
case 'K':
case 'k':
value<<= 10;
break;
case 0:
+if (divider) {
+value = 0;
+break;
+}
Anthony Liguori wrote:
> Image files have two types of data: immutable data that describes things like
> image size, backing files, etc. and mutable data that includes offset and
> reference count tables.
>
> Today, image formats aggressively cache mutable data to improve performance.
> In
> som
On Wednesday 15 September 2010 10:16:29 Rick Vernam wrote:
> I noticed this failure with qemu-0.13.0-rc0, qemu-0.13.0-rc1 & qemu-
> kvm-0.13.0-rc1
I should have also mentioned that I did not try with any previous version of
Qemu or Qemu-KVM.
If you think it would be a worth while test, I will run
On Wed, Sep 15, 2010 at 10:50:15AM -0500, Rick Vernam wrote:
> On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
> > On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> > > On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
> > > > On Wed, Sep 15, 2010 at 10:16:29AM -0
Avi Kivity wrote:
> On 09/12/2010 03:06 PM, Anthony Liguori wrote:
>>
>> Backing files and logical size shouldn't change during live migration.
>
> Why not?
It is supposed to be the same in both sides O:-)
If you want to extend a disk, you need to told qemu about that. Either
before or after mi
Avi Kivity wrote:
> On 09/12/2010 07:10 PM, Anthony Liguori wrote:
>> On 09/12/2010 11:06 AM, Avi Kivity wrote:
>>> On 09/12/2010 05:26 PM, Anthony Liguori wrote:
On 09/12/2010 08:28 AM, Avi Kivity wrote:
> On 09/12/2010 03:06 PM, Anthony Liguori wrote:
>>
>> Backing files and
Kevin Wolf wrote:
> Am 11.09.2010 16:04, schrieb Anthony Liguori:
> There is a simple generic implementation:
>
> drv = bs->drv;
> drv->close(bs);
> drv->open(bs, bs->open_flags);
>
> Note that this only reopens e.g. the qcow2 layer, but not the image
> file, which is bs->file.
>
> This works for
On Wed, Sep 15, 2010 at 05:57:10PM +0200, Gleb Natapov wrote:
> On Wed, Sep 15, 2010 at 10:50:15AM -0500, Rick Vernam wrote:
> > On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
> > > On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> > > > On Wednesday 15 September 2010 10:2
Anthony Liguori wrote:
> The use of protocols in backing_files is currently broken because of some
> checks for adjusting relative pathnames.
>
> Additionally, there's a spurious read when using an nbd protocol that can be
> quite destructive when using copy-on-read. Potentially, this can lead to
Anthony Liguori wrote:
> On 09/12/2010 05:42 AM, Avi Kivity wrote:
>> On 09/11/2010 05:04 PM, Anthony Liguori wrote:
>>> This fixes a couple nasty problems relating to live migration.
>>>
>>> 1) When dealing with shared storage with weak coherence (i.e. NFS),
>>> even if
>>> we re-read, we ma
On Wednesday 15 September 2010 10:57:10 Gleb Natapov wrote:
> On Wed, Sep 15, 2010 at 10:50:15AM -0500, Rick Vernam wrote:
> > On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
> > > On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> > > > On Wednesday 15 September 2010 10:24:
Kevin Wolf wrote:
> Am 11.09.2010 16:04, schrieb Anthony Liguori:
>> This fixes a couple nasty problems relating to live migration.
>>
>> 1) When dealing with shared storage with weak coherence (i.e. NFS), even if
>>we re-read, we may end up with undesired caching. By delaying any reads
>>
On Wed, Sep 15, 2010 at 11:26:20AM -0500, Rick Vernam wrote:
> > So how do you know it works with SDL? Also does the same happens with
> > linux guest + virtio disk?
> okay, linux guest started like so, this time on my laptop:
> qemu-system-x86_64 -cpu host -enable-kvm -drive
> file=/home/rick/qem
vring_virtqueue should be zeroed otherwise old values will be reused
after reboot.
Signed-off-by: Gleb Natapov
diff --git a/src/virtio-blk.c b/src/virtio-blk.c
index 34d7863..7a25826 100644
--- a/src/virtio-blk.c
+++ b/src/virtio-blk.c
@@ -109,6 +109,7 @@ init_virtio_blk(u16 bdf)
goto fa
From: Andrea Arcangeli
All allocated guest physical memory shall be marked MADV_DONTFORK, otherwise
fork will fail because of accounting issues preventing migration or netdev_add
when the guest allocated more than half of host physical memory.
Signed-off-by: Andrea Arcangeli
---
diff --git a/e
On Wednesday 15 September 2010 10:16:29 Rick Vernam wrote:
> I don't have nearly enough info to file a proper bug report.
>
> I am running qemu-kvm-0.13.0 rc1
> starting qemu like so:
> /root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
> file=/root/qemu/w2k3_server.raw,if=virtio,aio=n
Subject: allow more than 1T in KVM x86 guest
From: Andrea Arcangeli
When host supports 48 bits of physical address reflect that in the guest cpuid
to allow the guest to use more than 1TB of RAM.
The migration code should probably be updated accordingly checking if the size
of the guest ram is
Subject: add 40-48 physical address range to seabios
From: Andrea Arcangeli
Needed to show >1TB RAM to guests.
Signed-off-by: Andrea Arcangeli
---
diff --git a/hw/pc.c b/hw/pc.c
index 9c08573..7e1f2e9 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -360,6 +360,7 @@ void pc_cmos_init(ram_addr_t ram_size
Subject: add 40-48 bit RAM range to seabios
From: Andrea Arcangeli
Needed to show >1TB RAM to guests.
This uses a new cmos port at 0x5e that shall read zero to be backwards
compatible.
Signed-off-by: Andrea Arcangeli
---
diff --git a/src/cmos.h b/src/cmos.h
index e4b6462..e810534 100644
---
On Wed, Sep 15, 2010 at 12:13:26PM -0500, Rick Vernam wrote:
> On Wednesday 15 September 2010 10:16:29 Rick Vernam wrote:
> > I don't have nearly enough info to file a proper bug report.
> >
> > I am running qemu-kvm-0.13.0 rc1
> > starting qemu like so:
> > /root/qemu/bin/qemu-system-x86_64 -cpu
hey,how are you?
I find a nice site recently, maybe you like it.
one-stop trade services & High-quality,
competitive price & Lowest shipping cost & Fast door to door shipping
I bought some from them, good qualities with good price.
interested? visit: www.zol-us1.com
I am sure you will love it
On 15.09.2010, at 19:08, Andrea Arcangeli wrote:
> From: Andrea Arcangeli
>
> All allocated guest physical memory shall be marked MADV_DONTFORK, otherwise
> fork will fail because of accounting issues preventing migration or netdev_add
> when the guest allocated more than half of host physical
Am 15.09.2010 um 19:08 schrieb Andrea Arcangeli:
From: Andrea Arcangeli
All allocated guest physical memory shall be marked MADV_DONTFORK,
otherwise
fork will fail because of accounting issues preventing migration or
netdev_add
when the guest allocated more than half of host physical memo
On Tue, Sep 14, 2010 at 3:35 AM, Kevin Wolf wrote:
>
> Am 10.09.2010 02:08, schrieb disheng...@gmail.com:
> > From: edison
> >
> > In order to backup snapshots, created from QCOW2 iamge, we want to copy
> > snapshots out of QCOW2 disk to a seperate storage.
> > The following patch adds a new opt
From: Andreas Färber
vl.c has a Sun-specific hack to supply a prototype for madvise(),
but the call site has apparently moved to arch_init.c.
Haiku doesn't implement madvise() in favor of posix_madvise().
OpenBSD and Solaris 10 don't implement posix_madvise() but madvise().
Check for madvise()
On Thu, Sep 9, 2010 at 7:08 PM, Anthony Liguori wrote:
> On 09/09/2010 08:43 PM, disheng...@gmail.com wrote:
>>
>> From: edison
>>
>> Add a new option when "savevm": savevm -n snapshotName, which only takes
>> snapshot on disk, but doesn't save vm state(memory,cpu,devices...).
>> Saving vm state o
On 09/15/2010 12:13 PM, Andrea Arcangeli wrote:
Subject: allow more than 1T in KVM x86 guest
From: Andrea Arcangeli
When host supports 48 bits of physical address reflect that in the guest cpuid
to allow the guest to use more than 1TB of RAM.
The migration code should probably be updated accor
Am 15.09.2010 um 14:23 schrieb jes.soren...@redhat.com:
[...]
+/*
+ * Convert string to bytes, allowing either K/k for KB, M/m for MB,
+ * G/b for GB or T/t for TB. Default without any postfix is MB.
^^^ typo
+ * End pointer will be returned in *end, if end is valid.
+ * Return 0 on error
On Wed, Sep 15, 2010 at 6:09 PM, Andreas Färber wrote:
> From: Andreas Färber
>
> vl.c has a Sun-specific hack to supply a prototype for madvise(),
> but the call site has apparently moved to arch_init.c.
>
> Haiku doesn't implement madvise() in favor of posix_madvise().
> OpenBSD and Solaris 10
Hi,
I tried to test QEMU on Win2k, but there are run time errors because
of missing {get,free}{addr,name}info() functions. After adding dummy
defines in place, there are no more errors.
I found a similar case, where a compatibility patch was proposed:
http://trac.filezilla-project.org/ticket/1532
On 09/15/2010 02:11 PM, Blue Swirl wrote:
Hi,
I tried to test QEMU on Win2k, but there are run time errors because
of missing {get,free}{addr,name}info() functions. After adding dummy
defines in place, there are no more errors.
I found a similar case, where a compatibility patch was proposed:
h
On 09/15/10 16:50, Juan Quintela wrote:
> jes.soren...@redhat.com wrote:
>> From: Jes Sorensen
>> value <<= 10;
>> break;
>> case 0:
>> +if (divider) {
>> +value = 0;
>> +break;
>
> changing break by goto fail here?
> 1.5G and 1.0G is ok, but
On 09/15/10 17:45, Paolo Bonzini wrote:
> On 09/15/2010 02:23 PM, jes.soren...@redhat.com wrote:
>> switch (*endptr++) {
>> case 'K':
>> case 'k':
>> value<<= 10;
>> break;
>> case 0:
>> +if (divider) {
>> +value = 0;
>> +b
Am 15.09.2010 um 21:00 schrieb Blue Swirl:
madvise() actually
returns 0 or -1 with error code in errno. Should we try to match that?
posix_madvise() doesn't seem to... "otherwise, an error number shall
be returned to indicate the error"
It documents EINVAL for invalid advice, and so does m
Edgar E. Iglesias a écrit :
On Mon, Sep 13, 2010 at 11:02:42PM +0200, Hervé Poussineau wrote:
IEEE 802.3 standard requires Ethernet frames to be at least 64 bytes long.
If it is not the case, they will be considered as runt frames, and may be
ignored by netcard and/or OS
Signed-off-by: Herv
On Wed, Sep 15, 2010 at 7:35 PM, Andreas Färber wrote:
> Am 15.09.2010 um 21:00 schrieb Blue Swirl:
>
>> madvise() actually
>> returns 0 or -1 with error code in errno. Should we try to match that?
>
> posix_madvise() doesn't seem to... "otherwise, an error number shall be
> returned to indicate t
Am 15.09.2010 um 21:50 schrieb Blue Swirl:
On Wed, Sep 15, 2010 at 7:35 PM, Andreas Färber > wrote:
Maybe return -1 and set errno to the posix_madvise() return code?
(but is it
errno = -retval or errno = retval then?)
An advantage of posix_madvise() semantics is that no mucking with
errno i
IEEE 802.3 standard requires Ethernet frames to be at least 64 bytes long.
If it is not the case, they will be considered as runt frames, and may be
ignored by netcard and/or OS
Signed-off-by: Hervé Poussineau
---
slirp/slirp.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
Am 15.09.2010 20:46, schrieb Andreas Färber:
Am 15.09.2010 um 14:23 schrieb jes.soren...@redhat.com:
[...]
+/*
+ * Convert string to bytes, allowing either K/k for KB, M/m for MB,
+ * G/b for GB or T/t for TB. Default without any postfix is MB.
^^^ typo
+ * End pointer will be returned i
On Mon, Sep 06, 2010 at 11:04:38AM +0100, Stefan Hajnoczi wrote:
> The format supports sparse disk images. It does not rely on the host
> filesystem holes feature, making it a good choice for sparse disk images
> that need to be transferred over channels where holes are not supported.
Are these s
On Wed, Sep 15, 2010 at 07:08:24PM +0200, Andrea Arcangeli wrote:
> From: Andrea Arcangeli
>
> All allocated guest physical memory shall be marked MADV_DONTFORK, otherwise
> fork will fail because of accounting issues preventing migration or netdev_add
> when the guest allocated more than half of
On Wed, Sep 15, 2010 at 06:31:44PM +0200, Gleb Natapov wrote:
> vring_virtqueue should be zeroed otherwise old values will be reused
> after reboot.
>
> Signed-off-by: Gleb Natapov
Nice one.
Acked-by: Michael S. Tsirkin
> diff --git a/src/virtio-blk.c b/src/virtio-blk.c
> index 34d7863..7a258
On 09/15/2010 04:01 PM, Michael S. Tsirkin wrote:
On Mon, Sep 06, 2010 at 11:04:38AM +0100, Stefan Hajnoczi wrote:
The format supports sparse disk images. It does not rely on the host
filesystem holes feature, making it a good choice for sparse disk images
that need to be transferred over c
This bug was fixed in the package qemu-kvm - 0.12.5+noroms-0ubuntu6
---
qemu-kvm (0.12.5+noroms-0ubuntu6) maverick; urgency=low
* debian/fix-CMOS-info-for-drives-defined-with--device.patch: make sure
the CMOS knows about the correct geometry so Windows XP installs
properly.
** Branch linked: lp:ubuntu/qemu-kvm
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Status in “qemu-kvm” package in Ubuntu: Fix Released
Hello everybody,
I arm building VP8 (WebM) for QEMU, when I configure VP8 for ARMv6 then it run
ok on QEMU but when I build it with ARMv7
then it's not run on QEMU, I asked on WebM's forum of Google and they said that
QEMU does not support VP8 NEON code right now
I ran debug to test their replys an
** Changed in: gnome-terminal
Importance: Unknown => Wishlist
--
gnome-terminal should default to 80x25 for application compatibility
https://bugs.launchpad.net/bugs/464783
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in GN
Now , i am studying about QEMU.
I want to build QEMU for ARM and run an ARM application on it to trace guest
logical address and physical address.
I can build QEMU for ARM and run ARM application on it
But.I don't know how to trace guest logical and physical address...
I intend use the back-e
On Wed, Sep 15, 2010 at 11:03:14PM +0200, Michael S. Tsirkin wrote:
> On Wed, Sep 15, 2010 at 07:08:24PM +0200, Andrea Arcangeli wrote:
> > From: Andrea Arcangeli
> >
> > All allocated guest physical memory shall be marked MADV_DONTFORK, otherwise
> > fork will fail because of accounting issues p
Public bug reported:
I have been trying to figure out why I cannot debug a 64 bit kernel of
my own invention.
I launch qemu-system-x86_64 with the -s -S flags, we also specify -cpu
core2duo -vga std and a -hda with an ext2 FS holding our multiboot
kernel and GRUB2.
When I try to set breakpoints
90 matches
Mail list logo
