On Wed, Dec 23, 2009 at 04:33:32AM +0800, Scott Tsai wrote:
> On Tue, Dec 22, 2009 at 11:05 PM, Anthony Liguori
> wrote:
> > On 12/22/2009 02:52 AM, Aurelien Jarno wrote:
> >>
> >> In version 0.12.1, using -usbdevice with an inexistent device exits
> >> without any error message, thus confusing t
On Wed, 23 Dec 2009 01:21:43 am Anthony Liguori wrote:
> On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
> > On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
> >
> >> The following fixes a class of long-standing bugs in qemu:
> >> when kvm is enabled, guest might access dev
On Tue, Dec 22, 2009 at 02:45:17PM +0100, Alexander Graf wrote:
> When we get an MMIO request, we always get variables in host endianness. The
> only time we need to actually reverse byte order is when we read bytes from
> guest memory.
>
> Apparently the DBDMA implementation is different there. A
Andreas,
Thanks for the tip about qemu-system-x86_64 - I didn't see that anywhere in
the documentation:
http://www.qemu.org/qemu-doc.html
Now that I'm running the right qemu, it loads the kernel and the initrd, but
hangs following these lines:
Setting APIC routing to flat
.TIMER: vector=0
Anthony Liguori wrote:
> It would be insane to emulate sse3 too.
It doesn't sound too ridiculous if TCG is involved, provided the
switching between TCG and KVM isn't too rapid. TCG is slower, but
it's not ridiculously slow.
Though, I don't expect anyone to volunteer to implement it :-)
> how li
> > Given this is supposed to be portable code, I wonder if we should have
> > atomic ordered memory accessors instead.
> >
> > Paul
>
> Could you clarify please?
>
> The infiniband bits I used as base are very portable,
> I know they build on a ton of platforms. I just stripped
> a couple of inf
Paolo Bonzini wrote:
>
> >>No, Windows tries to detect changes in your hardware and assumes that
> >>if too many things change, you might be a pirate and requires you to
> >>phone their offices to re-authenticate.
> >
> >'Just' the CPU is not big deal. Might hit you with two 'bad' points.
> >Netwo
Michael S. Tsirkin wrote:
> Bootup on different machines has some of the same issues as migration.
> Consider a 64 bit guest as an example, I think it can not boot on a 32
> bit host OS with kvm. I think you can use tcg, but it will be slower.
> Same thing applies to other CPU features.
Alas, perh
TAKEDA, toshiya wrote:
> @@ -940,7 +966,15 @@ void cpu_x86_set_a20(CPUX86State *env, int a20_state)
> /* when a20 is changed, all the MMU mappings are invalid, so
> we must flush everything */
> tlb_flush(env, 1);
> -env->a20_mask = ~(1 << 20) | (a20_state << 2
On 12/22/2009 11:49 AM, Amit Shah wrote:
This patch migrates virtio-console to the qdev infrastructure and
creates a new virtio-serial bus on which multiple ports are exposed as
devices. The bulk of the code now resides in a new file with
virtio-console.c being just a simple qdev device.
This in
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC i386-softmmu/vl.o
> cc1: warnings being treated as errors
> /usr/src/RPM/BUILD/qemu-0.11.92/vl.c: In function 'qemu_event_increment':
> /usr/src/RPM/BUILD/qemu-0.11.92/vl.c:3404: error: ignoring return value of
> 'write', declare
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC block/bochs.o
> cc1: warnings being treated as errors
> block/bochs.c: In function 'seek_to_sector':
> block/bochs.c:202: error: ignoring return value of 'read', declared with
> attribute warn_unused_result
> make: *** [block/boc
Anthony Liguori wrote:
On 12/21/2009 01:43 PM, Gleb Natapov wrote:
Please stop thinking so :) Especially about "user driven upgrades".
Why combine disadvantages of vitalization with pain of physical HW
management? Or may be next step will be to require uploading of CPU
microcode to take advantag
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC libuser/path.o
> cc1: warnings being treated as errors
> /usr/src/RPM/BUILD/qemu-0.11.92/path.c: In function 'new_entry':
> /usr/src/RPM/BUILD/qemu-0.11.92/path.c:49: error: ignoring return value of
> 'asprintf', declared with at
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC i386-softmmu/pc.o
> cc1: warnings being treated as errors
> /usr/src/RPM/BUILD/qemu-0.11.92/hw/pc.c: In function 'load_multiboot':
> /usr/src/RPM/BUILD/qemu-0.11.92/hw/pc.c:614: error: ignoring return value of
> 'fread', declared
On Tue, Dec 22, 2009 at 11:05 PM, Anthony Liguori wrote:
> On 12/22/2009 02:52 AM, Aurelien Jarno wrote:
>>
>> In version 0.12.1, using -usbdevice with an inexistent device exits
>> without any error message, thus confusing the user:
>
> Would be good to file in launchpad since I think a lot of fo
When an non-existent USB device is specified on the command line,
print "qemu: could not add USB device 'X'".
Likewise for the usb_{add,del} monitor commands.
Signed-off-by: Scott Tsai
---
vl.c | 17 ++---
1 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/vl.c b/vl.c
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC savevm.o
> cc1: warnings being treated as errors
> savevm.c: In function 'file_put_buffer':
> savevm.c:342: error: ignoring return value of 'fwrite', declared with
> attribute warn_unused_result
> make: *** [savevm.o] Error 1
>
>
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC usb-linux.o
> cc1: warnings being treated as errors
> usb-linux.c: In function 'usb_host_read_file':
> usb-linux.c:1204: error: ignoring return value of 'fgets', declared with
> attribute warn_unused_result
> make: *** [usb-linux
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC net/slirp.o
> cc1: warnings being treated as errors
> net/slirp.c: In function 'slirp_smb_cleanup':
> net/slirp.c:470: error: ignoring return value of 'system', declared with
> attribute warn_unused_result
> make: *** [net/slirp.
On Sun, Dec 20, 2009 at 1:39 AM, Kirill A. Shutemov
wrote:
> CC block.o
> cc1: warnings being treated as errors
> block.c: In function 'bdrv_open2':
> block.c:400: error: ignoring return value of 'realpath', declared with
> attribute warn_unused_result
>
> Signed-off-by: Kirill A. Shutemov
>
On (Tue) Dec 22 2009 [19:08:40], Alexander Graf wrote:
> >
> > -/* Add virtio console devices */
> > -if (pci_enabled) {
> > -for(i = 0; i < MAX_VIRTIO_CONSOLES; i++) {
> > -if (virtcon_hds[i]) {
> > -pci_create_simple(pci_bus, -1, "virtio-console-pci")
Amit Shah wrote:
> This patch migrates virtio-console to the qdev infrastructure and
> creates a new virtio-serial bus on which multiple ports are exposed as
> devices. The bulk of the code now resides in a new file with
> virtio-console.c being just a simple qdev device.
>
> This interface enables
On (Tue) Dec 22 2009 [18:55:16], Alexander Graf wrote:
> Amit Shah wrote:
> > This patch migrates virtio-console to the qdev infrastructure and
> > creates a new virtio-serial bus on which multiple ports are exposed as
> > devices. The bulk of the code now resides in a new file with
> > virtio-cons
Amit Shah wrote:
> This patch migrates virtio-console to the qdev infrastructure and
> creates a new virtio-serial bus on which multiple ports are exposed as
> devices. The bulk of the code now resides in a new file with
> virtio-console.c being just a simple qdev device.
>
> This interface enables
This patch migrates virtio-console to the qdev infrastructure and
creates a new virtio-serial bus on which multiple ports are exposed as
devices. The bulk of the code now resides in a new file with
virtio-console.c being just a simple qdev device.
This interface enables spawning of multiple virtio
VIRTIO_PCI_QUEUE_MAX is redefined in hw/virtio.c. Let's just keep it in
hw/virtio.h.
Also, bump up the value of the maximum allowed virtqueues to 32. This is
in preparation to allow multiple ports per virtio-console device.
Signed-off-by: Amit Shah
---
hw/virtio.c |2 --
hw/virtio.h |2
This patch adds generic serial ports over the virtio serial bus.
These ports have a few more options that are not relevant for
virtio console ports: the ability to cache buffers that are
received for a port while it's disconnected, setting of limits
to the bytes that are cached so as to prevent OOM
Hello,
Here's the latest patch series for enabling support for generic serial
ports over the virtio-console device.
This series converts virtio-console to the qdev infrastructure, creates
a new virtio-serial bus on which console and generic ports are put and
adds support for multiple devices, eac
Signed-off-by: TAKEDA, toshiya
---
hw/ne2000-isa.c | 71 --
1 files changed, 63 insertions(+), 8 deletions(-)
diff --git a/hw/ne2000-isa.c b/hw/ne2000-isa.c
index 03a5a1f..4a1733b 100644
--- a/hw/ne2000-isa.c
+++ b/hw/ne2000-isa.c
@@ -61,6 +6
Signed-off-by: TAKEDA, toshiya
---
hw/ide/core.c | 13 +++--
hw/ide/internal.h |1 +
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/hw/ide/core.c b/hw/ide/core.c
index 76c3820..4c77415 100644
--- a/hw/ide/core.c
+++ b/hw/ide/core.c
@@ -1801,8 +1801,10 @@ void id
Signed-off-by: TAKEDA, toshiya
---
hw/i8259.c | 63 ---
1 files changed, 55 insertions(+), 8 deletions(-)
diff --git a/hw/i8259.c b/hw/i8259.c
index 3de22e3..eaf75dd 100644
--- a/hw/i8259.c
+++ b/hw/i8259.c
@@ -59,6 +59,7 @@ struct PicSta
Signed-off-by: TAKEDA, toshiya
---
hw/i8254.c | 57 +++--
1 files changed, 51 insertions(+), 6 deletions(-)
diff --git a/hw/i8254.c b/hw/i8254.c
index faaa884..155f879 100644
--- a/hw/i8254.c
+++ b/hw/i8254.c
@@ -47,6 +47,7 @@ typedef struct
Signed-off-by: TAKEDA, toshiya
---
hw/pcspk.c | 32 +++-
1 files changed, 27 insertions(+), 5 deletions(-)
diff --git a/hw/pcspk.c b/hw/pcspk.c
index 26a0ecb..4a21aae 100644
--- a/hw/pcspk.c
+++ b/hw/pcspk.c
@@ -38,6 +38,7 @@ typedef struct {
QEMUSoundCard card
Signed-off-by: TAKEDA, toshiya
---
hw/pc.c |4 ++--
hw/pc.h |7 +--
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index db7d58e..ddefb7f 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -67,7 +67,7 @@
static fdctrl_t *floppy_controller;
static RTCState *rtc_s
Signed-off-by: TAKEDA, toshiya
---
hw/fdc.c | 591 --
hw/fdc.h |1 +
hw/hw.h | 12 ++
3 files changed, 472 insertions(+), 132 deletions(-)
diff --git a/hw/fdc.c b/hw/fdc.c
index 0579b03..3041a22 100644
--- a/hw/fdc.c
+++ b/hw/fd
Signed-off-by: TAKEDA, toshiya
---
hw/ide.h |3 +
hw/ide/pc98.c | 288 +
2 files changed, 291 insertions(+), 0 deletions(-)
create mode 100644 hw/ide/pc98.c
diff --git a/hw/ide.h b/hw/ide.h
index 0e7d540..0a94bac 100644
--- a/hw/
Signed-off-by: TAKEDA, toshiya
---
hw/pc98sys.c | 482 ++
1 files changed, 482 insertions(+), 0 deletions(-)
create mode 100644 hw/pc98sys.c
diff --git a/hw/pc98sys.c b/hw/pc98sys.c
new file mode 100644
index 000..43a910a
--- /dev/nul
Signed-off-by: TAKEDA, toshiya
---
hw/pc98kbd.c | 395 ++
1 files changed, 395 insertions(+), 0 deletions(-)
create mode 100644 hw/pc98kbd.c
diff --git a/hw/pc98kbd.c b/hw/pc98kbd.c
new file mode 100644
index 000..04e1fa5
--- /dev/nul
Signed-off-by: TAKEDA, toshiya
---
hw/pc98.c | 317 +
hw/pc98.h | 65 +
2 files changed, 382 insertions(+), 0 deletions(-)
create mode 100644 hw/pc98.c
create mode 100644 hw/pc98.h
diff --git a/hw/pc98.c b/hw/pc98.c
new
Dear members,
Sorry too late reply for comments of previous patch.
(I was busy in these months for my business...)
This is new patch.
Change from v3 to v4:
- use vmstate for save/load state
- remove sound device with MAME opna sound core
Thanks,
TAKEDA, toshiya
Signed-off-by: TAKEDA, toshiya
---
hw/dma.c | 186 --
hw/isa.h |1 +
2 files changed, 181 insertions(+), 6 deletions(-)
diff --git a/hw/dma.c b/hw/dma.c
index 44c642e..28219e7 100644
--- a/hw/dma.c
+++ b/hw/dma.c
@@ -45,6 +45,8 @@
Signed-off-by: TAKEDA, toshiya
---
hw/pc98mouse.c | 266
1 files changed, 266 insertions(+), 0 deletions(-)
create mode 100644 hw/pc98mouse.c
diff --git a/hw/pc98mouse.c b/hw/pc98mouse.c
new file mode 100644
index 000..0868180
--- /d
Signed-off-by: TAKEDA, toshiya
---
Makefile.target |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Makefile.target b/Makefile.target
index 7c1f30c..18c8428 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -195,6 +195,7 @@ obj-i386-y += cirrus_vga.o apic.o ioapic.o pa
Signed-off-by: TAKEDA, toshiya
---
sysemu.h |3 +++
vl.c | 32
2 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/sysemu.h b/sysemu.h
index 9d80bb2..51c7ac8 100644
--- a/sysemu.h
+++ b/sysemu.h
@@ -45,13 +45,16 @@ void cpu_enable_ticks(void)
Signed-off-by: TAKEDA, toshiya
---
hw/pc98mem.c | 861 ++
1 files changed, 861 insertions(+), 0 deletions(-)
create mode 100644 hw/pc98mem.c
diff --git a/hw/pc98mem.c b/hw/pc98mem.c
new file mode 100644
index 000..36a60cc
--- /dev/nul
Signed-off-by: TAKEDA, toshiya
---
target-i386/cpu.h|3 +++
target-i386/helper.c | 46 --
2 files changed, 43 insertions(+), 6 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index f3834b3..271cc20 100644
--- a/target-i386/cpu
On 12/22/2009 06:25 PM, Paul Brook wrote:
On Tuesday 22 December 2009, Anthony Liguori wrote:
On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
The following fixes a class of long-standing bugs in qemu:
when
On Tue, Dec 22, 2009 at 04:25:32PM +, Paul Brook wrote:
> On Tuesday 22 December 2009, Anthony Liguori wrote:
> > On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
> > > On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
> > >> The following fixes a class of long-standing bugs
On Tuesday 22 December 2009, Anthony Liguori wrote:
> On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
> > On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
> >> The following fixes a class of long-standing bugs in qemu:
> >> when kvm is enabled, guest might access device structu
On 12/22/2009 09:54 AM, Paul Brook wrote:
Ram allocations should be associated with a device. The VMState stuff
this should make this fairly straightforward.
Right, but for the sake of simplicity, you don't want to treat that ram
any differently than main ram wrt live migration. That's
On 12/21/2009 02:28 AM, Dor Laor wrote:
John's new cpu definitions are the exact solution for this issue - all
users, whether using mgmt app or direct qemu (this is no user, this is
a developer/hacker/other, let's do not optimize this case) should use
the various 'real' cpu definitions like -cp
On 12/22/2009 03:27 AM, Laurent Desnogues wrote:
+#if TCG_TARGET_REG_BITS == 64
+tcg_gen_op4i_i64(INDEX_op_setcond_i64, ret, arg1, arg2, cond);
+#else
+tcg_gen_op6i_i32(INDEX_op_setcond2_i32, TCGV_LOW(ret),
+ TCGV_LOW(arg1), TCGV_HIGH(arg1),
+ TCGV_
> > Ram allocations should be associated with a device. The VMState stuff
> > this should make this fairly straightforward.
>
> Right, but for the sake of simplicity, you don't want to treat that ram
> any differently than main ram wrt live migration. That's why I proposed
> adding a context id f
Dor Laor wrote:
> On 12/22/2009 12:51 AM, john cooper wrote:
>> Dor Laor wrote:
>>
>>> Qemu will check the required cpuid of the cpu model on the host and
>>> refuse to load otherwise. When moving to this model, migration can be
>>> simplified too since there are fewer combination, and one can choo
On 12/22/2009 07:04 AM, Paul Brook wrote:
We should just qemu_ram_alloc() that memory regardless of whether we
every map it into the guest. Since roms can be large, we want to send
their contents over during the live part of migration. If we use
qemu_ram_alloc(), we get that for free.
On 12/22/2009 02:52 AM, Aurelien Jarno wrote:
In version 0.12.1, using -usbdevice with an inexistent device exits
without any error message, thus confusing the user:
$ qemu-system-x86_64 -usbdevice null ;
echo $?
1
$
Would be good to file in launchpad since I think a lot of folks are out
On 12/22/2009 01:58 AM, Gleb Natapov wrote:
Your cable TV provider does likely also control what beside the FW (if anything)
runs on your set-top-box. So he can verify the FW upgrade doesn't break anything
in the field. That pre-deployment verification is not possible in non closed
environments.
On 12/22/2009 04:50 PM, Anthony Liguori wrote:
On 12/22/2009 03:57 AM, Avi Kivity wrote:
The first such option rom will load at address 0, which isn't very nice,
and the second will report a conflict and abort, which is horrible.
Signed-off-by: Avi Kivity
This fixes extboot in qemu-kvm?
Yes
On 12/22/2009 05:26 AM, Michael S. Tsirkin wrote:
On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
The following fixes a class of long-standing bugs in qemu:
when kvm is enabled, guest might access device structures
in memory while they are updated by qemu on another CPU.
On 12/22/2009 03:57 AM, Avi Kivity wrote:
The first such option rom will load at address 0, which isn't very nice,
and the second will report a conflict and abort, which is horrible.
Signed-off-by: Avi Kivity
This fixes extboot in qemu-kvm?
Regards,
Anthony Liguori
On Tue, Dec 22, 2009 at 1:02 AM, Richard Henderson wrote:
> On 12/21/2009 03:08 PM, Laurent Desnogues wrote:
>>
>> If you wanted to use movcond, you'd have to make
>> cond + move a special case...
>
> You'd certainly want the ARM front-end to use movcond more often than that.
> For instance:
>
>
Mark Cave-Ayland wrote:
> Alexander Graf wrote:
>
>> OpenBIOS is missing an implementation for local variables. See this
>> thread:
>> http://www.openfirmware.info/pipermail/openbios/2009-July/003796.html
>>
>> Alex
>
> How do local variables work? Are they just substitutions for stack
> places?
I
On 12/22/2009 12:51 AM, john cooper wrote:
Dor Laor wrote:
Qemu will check the required cpuid of the cpu model on the host and
refuse to load otherwise. When moving to this model, migration can be
simplified too since there are fewer combination, and one can choose
performance over migration fl
When we get an MMIO request, we always get variables in host endianness. The
only time we need to actually reverse byte order is when we read bytes from
guest memory.
Apparently the DBDMA implementation is different there. A lot of the logic
in there depends on values being big endian. Now, qemu d
Alexander Graf wrote:
OpenBIOS is missing an implementation for local variables. See this
thread:
http://www.openfirmware.info/pipermail/openbios/2009-July/003796.html
Alex
How do local variables work? Are they just substitutions for stack places?
If you can point me towards a specification
On 12/22/2009 03:04 PM, Paul Brook wrote:
We should just qemu_ram_alloc() that memory regardless of whether we
every map it into the guest. Since roms can be large, we want to send
their contents over during the live part of migration. If we use
qemu_ram_alloc(), we get that for free.
> > We should just qemu_ram_alloc() that memory regardless of whether we
> > every map it into the guest. Since roms can be large, we want to send
> > their contents over during the live part of migration. If we use
> > qemu_ram_alloc(), we get that for free.
>
> Currently live migration uses ra
On Tue, Dec 22, 2009 at 01:07:20PM +0100, Alexander Graf wrote:
> Michael S. Tsirkin wrote:
> > On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
> >
> >> When we get an MMIO request, we always get variables in host endianness.
> >> The
> >> only time we need to actually reverse b
> http://thread.gmane.org/gmane.comp.emulators.qemu/44869
>
> I'm not sure why Paul never pushed it but I think he was able to create
> the syborg board purely from a device tree.
The patches referenced above include purely device-tree based Syborg and
Stellaris boards.
It works fairly nicely f
On Sun, Dec 20, 2009 at 12:11 AM, Aurelien Jarno wrote:
> On Sat, Dec 19, 2009 at 10:46:38AM -0800, Richard Henderson wrote:
>> Signed-off-by: Richard Henderson
>
> This looks ok, though I would appreciate someone else to review it in
> details.
It looks good to me too (though I didn't test it e
Michael S. Tsirkin wrote:
> On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
>
>> When we get an MMIO request, we always get variables in host endianness. The
>> only time we need to actually reverse byte order is when we read bytes from
>> guest memory.
>>
>> Apparently the DBDMA
Anyone just tried it yet ?
François.
-- Forwarded Message: --
To: qemu-devel@nongnu.org
From: "François Revol"
Subject: [PATCH] block/vdi: allow disk sizes not multiple of block size
Date: Tue, 08 Dec 2009 15:34:18 +0100 CET
The disk image I created from my old laptop disk with VBoxMana
On Tue, Dec 22, 2009 at 11:24:18AM +0100, Alexander Graf wrote:
> When we get an MMIO request, we always get variables in host endianness. The
> only time we need to actually reverse byte order is when we read bytes from
> guest memory.
>
> Apparently the DBDMA implementation is different there. A
On Tue, Dec 08, 2009 at 06:18:18PM +0200, Michael S. Tsirkin wrote:
> The following fixes a class of long-standing bugs in qemu:
> when kvm is enabled, guest might access device structures
> in memory while they are updated by qemu on another CPU.
> In this scenario, memory barriers are necessary t
On Sat, Dec 19, 2009 at 7:01 PM, Richard Henderson wrote:
> Defines setcond_{i32,i64} and setcond2_i32 for 64-on-32-bit.
>
> Signed-off-by: Richard Henderson
> ---
> tcg/README | 20 +++-
> tcg/tcg-op.h | 47 +++
> tcg/tcg-opc.h
When we get an MMIO request, we always get variables in host endianness. The
only time we need to actually reverse byte order is when we read bytes from
guest memory.
Apparently the DBDMA implementation is different there. A lot of the logic
in there depends on values being big endian. Now, qemu d
The first such option rom will load at address 0, which isn't very nice,
and the second will report a conflict and abort, which is horrible.
Signed-off-by: Avi Kivity
---
Changes from v1:
- use ->fw_file instead of ->addr to distinguish between host-loaded and
firmware-loaded roms
- add the sa
On 12/22/2009 11:35 AM, Aurelien Jarno wrote:
On Tue, Dec 22, 2009 at 11:25:13AM +0200, Avi Kivity wrote:
The first such option rom will load at address 0, which isn't very nice,
and the second will report a conflict and abort, which is horrible.
Signed-off-by: Avi Kivity
---
hw/loader.c
On Tue, Dec 22, 2009 at 11:25:13AM +0200, Avi Kivity wrote:
> The first such option rom will load at address 0, which isn't very nice,
> and the second will report a conflict and abort, which is horrible.
>
> Signed-off-by: Avi Kivity
> ---
> hw/loader.c |3 +++
> 1 files changed, 3 insertio
The first such option rom will load at address 0, which isn't very nice,
and the second will report a conflict and abort, which is horrible.
Signed-off-by: Avi Kivity
---
hw/loader.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/hw/loader.c b/hw/loader.c
index 2ceb8e
In version 0.12.1, using -usbdevice with an inexistent device exits
without any error message, thus confusing the user:
$ qemu-system-x86_64 -usbdevice null ;
echo $?
1
$
In 0.11.X, the error is ignored, but at least a message is displayed:
$ qemu-system-x86_64 -usbdevice null
Warning: could not
82 matches
Mail list logo
