On (Sat) Mar 06 2010 [21:06:35], Michael S. Tsirkin wrote:
>
> > > +r = vhost_virtqueue_set_addr(dev, vq, idx, dev->log_enabled);
> > > +if (r < 0) {
> > > +r = -errno;
> > > +goto fail_alloc;
> > > +}
> > > +if (!vdev->binding->guest_notifier || !vdev->binding->hos
On (Sat) Mar 06 2010 [21:07:57], Michael S. Tsirkin wrote:
> On Fri, Mar 05, 2010 at 06:38:35PM +0530, Amit Shah wrote:
> > On (Wed) Mar 03 2010 [19:16:09], Michael S. Tsirkin wrote:
> > > +
> > > +EventNotifier *virtio_queue_guest_notifier(VirtQueue *vq)
> > > +{
> > > +return &vq->guest_notif
qemu-system-ppc -hda debian_lenny_powerpc_small.qcow
qemu: fatal: Trying to execute code outside RAM or ROM at 0x
NIP LR CTR XER
MSR HID0 0300 HF idx 0
Segmentation fault
uname -a
Linux debian 2.6.32-2-amd64 #1 SMP Fri Feb 12 0
2010/3/8 Roy Tam :
> 2010/3/8 Keen Shoes :
>> Hi all,
>>
>> I found some regression bugs that seems relate to SeaBIOS and I hope
>> we can add back booting with Bochs BIOS in git so that we can further
>> testing that the bug is in SeaBIOS or in QEMU 0.12.
>>
>> ==
>> Try test the bios.bin-0.5
Hi all,
I found some regression bugs that seems relate to SeaBIOS and I hope
we can add back booting with Bochs BIOS in git so that we can further
testing that the bug is in SeaBIOS or in QEMU 0.12.
Following list is the regression that I encountered and which works in 0.11.1:
- Windows NT 3.51/4
Paul Brook wrote:
> > Support an inter-vm shared memory device that maps a shared-memory object
> > as a PCI device in the guest. This patch also supports interrupts between
> > guest by communicating over a unix domain socket. This patch applies to
> > the qemu-kvm repository.
>
> No. All new
> On Fri, Mar 05, 2010 at 11:15:45AM +, Paul Brook wrote:
> > > TCG internal helpers only access to the values passed in arguments, and
> > > do not modify the CPU internal state. Thus they can be declared as
> > > const and pure.
> >
> > I think this needs an explanatory comment. It's not imme
> Support an inter-vm shared memory device that maps a shared-memory object
> as a PCI device in the guest. This patch also supports interrupts between
> guest by communicating over a unix domain socket. This patch applies to
> the qemu-kvm repository.
No. All new devices should be fully qdev b
Ah, just noticed this warning is only in Jans git... For those who
were wondering :)
Cheers,
Niels
On 3/7/10, Niels de Vos wrote:
> With the added checks on the parameter for -usbdevice, the following
> warning got introduced:
>
> hw/usb-bus.c: In function ‘usbdevice_create’:
> hw/usb-bus.c:278:
With the added checks on the parameter for -usbdevice, the following
warning got introduced:
hw/usb-bus.c: In function ‘usbdevice_create’:
hw/usb-bus.c:278: error: assignment discards qualifiers from pointer target type
It is okay to drop the qualifier (const) from the empty string here.
Signed-
Hello,
Am 04.03.2010 um 22:25 schrieb Stefan Weil:
Aurelien Jarno schrieb:
On Fri, Feb 12, 2010 at 11:43:28AM +0100, Stefan Weil wrote:
today, html documentation is created using texi2html.
makeinfo can also create html output which looks different.
I think it looks better, but try it yourse
Am 07.03.2010 um 17:47 schrieb Juan Quintela:
Stefan Weil wrote:
Removing libqemu.a was technically ok, but throws a license problem:
"In particular, the QEMU virtual CPU core library (libqemu.a) is
released under the GNU Lesser General Public License."
Without libqemu.a, this part of QEMU'
Stefan Weil wrote:
> Blue Swirl schrieb:
>> Thanks, applied.
>
> Removing libqemu.a was technically ok, but throws a license problem:
>
> "In particular, the QEMU virtual CPU core library (libqemu.a) is
> released under the GNU Lesser General Public License."
>
> Without libqemu.a, this part of QE
On Sun, Mar 7, 2010 at 2:53 PM, Anthony Liguori wrote:
[...]
>>
>> Removing libqemu.a was technically ok, but throws a license problem:
>>
>
> Every file contains a copyright/license. The statement in the top level is
> just a statement of intention. It's to make sure that people do not
> introd
block.c says:
/*
* Yes, BDRV_O_NOCACHE aka O_DIRECT means we have to present a
* write cache to the guest. We do need the fdatasync to flush
* out transactions for block allocations, and we maybe have a
* volatile write cache in our backing device to deal with.
*/
On 03/06/2010 05:33 AM, Stefan Weil wrote:
Blue Swirl schrieb:
Thanks, applied.
On Wed, Jan 6, 2010 at 7:24 PM, Andreas Färber
wrote:
From: Andreas Färber
Juan has contributed a cool Makefile infrastructure that enables us
to drop
static libraries completely:
Move shared obj-y d
On Sun, Mar 07, 2010 at 02:44:50PM +0100, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Gleb Natapov wrote:
> >> On Thu, Mar 04, 2010 at 02:03:54PM +0200, Gleb Natapov wrote:
> BTW, do real systems allow to hot plug BSP as well? Or how is the case
> handled when you unplug the BSP and then re
Jan Kiszka wrote:
> Gleb Natapov wrote:
>> On Thu, Mar 04, 2010 at 02:03:54PM +0200, Gleb Natapov wrote:
BTW, do real systems allow to hot plug BSP as well? Or how is the case
handled when you unplug the BSP and then reboot the box?
>>> Did you mean hot unplug BSP? OS determines what
Kevin Wolf wrote:
> Am Freitag, 5. März 2010 04:17 schrieb David S. Ahern:
>> Jan:
>>
>> I spent some more time on the EHCI support today. With the attached
>> patch (delta to the patch from yesterday) a USB key is recognized within
>> the guest (FC-12):
>
> Looks very nice. Actually I could acces
Many usbdevice_init implementors assume params is non-NULL.
Signed-off-by: Jan Kiszka
---
Build fixed - sorry.
hw/usb-bus.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/hw/usb-bus.c b/hw/usb-bus.c
index 7c82314..3bb8986 100644
--- a/hw/usb-bus.c
+++ b/hw/usb-bus.
Many usbdevice_init implementors assume params is non-NULL.
Signed-off-by: Jan Kiszka
---
hw/usb-bus.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/usb-bus.c b/hw/usb-bus.c
index 7c82314..89e2ea6 100644
--- a/hw/usb-bus.c
+++ b/hw/usb-bus.c
@@ -275,6 +275,7 @@ USBD
Gleb Natapov wrote:
> On Thu, Mar 04, 2010 at 02:03:54PM +0200, Gleb Natapov wrote:
>>> BTW, do real systems allow to hot plug BSP as well? Or how is the case
>>> handled when you unplug the BSP and then reboot the box?
>>>
>> Did you mean hot unplug BSP? OS determines what CPU is BSP by checking
>
The missing '@' broke 'udp::@:' parsing.
Signed-off-by: Jan Kiszka
---
qemu-char.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index 86c7c5a..0d8553d 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -2333,7 +2333,7 @@ QemuOpts *qemu_chr_parse_
This fixes eg. "-nographic -serial mon:stdio [-serial ...]".
Signed-off-by: Jan Kiszka
---
vl.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/vl.c b/vl.c
index 10d8e34..bffb796 100644
--- a/vl.c
+++ b/vl.c
@@ -5369,6 +5369,9 @@ int main(int argc, char **argv, c
On 03/06/2010 11:10 PM, Aurelien Jarno wrote:
Is the slash at the end of the URL really wanted?
It works either with or without.
Paolo
25 matches
Mail list logo
