The Buildbot has detected a new failure on builder ppc-next_x86_64_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/ppc-next_x86_64_debian_6_0/builds/321
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuk
The Buildbot has detected a new failure on builder ppc-next_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/ppc-next_i386_debian_6_0/builds/321
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Bu
Signed-off-by: Deep Debroy
---
hw/vmware_utils.h | 126 +
1 file changed, 126 insertions(+)
create mode 100644 hw/vmware_utils.h
diff --git a/hw/vmware_utils.h b/hw/vmware_utils.h
new file mode 100644
index 000..73b039e
--- /dev/null
+++
Options vendor_name and product_nameadded for SCSI
disks.
Signed-off-by: Deep Debroy
---
hw/scsi-disk.c | 31 +++
1 file changed, 23 insertions(+), 8 deletions(-)
diff --git a/hw/scsi-disk.c b/hw/scsi-disk.c
index ae25194..a774c3c 100644
--- a/hw/scsi-disk.c
+++
Signed-off-by: Deep Debroy
---
cutils.c |7 +++
qemu-common.h |1 +
2 files changed, 8 insertions(+)
diff --git a/cutils.c b/cutils.c
index af308cd..68a7d10 100644
--- a/cutils.c
+++ b/cutils.c
@@ -27,6 +27,13 @@
#include "qemu_socket.h"
+void strpadcpy(char *buf, int buf_siz
Below is a re-submission of VMWare PVSCSI device implementation
patches (earlier submitted by Dmitry Fleytman) so that it gets applied
to the qemu master. Details from Dmitry's earlier submission can be
found at: http://lists.gnu.org/archive/html/qemu-devel/2012-03/msg03438.html
New changes since
XkbGetKeyboard may return zero instead of a valid atom
in names->keycodes in some cases. XGetAtomName(dpy, 0)
results in BadAtom error and crashes qemu.
Signed-off-by: Alex Suykov
---
ui/sdl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ui/sdl.c b/ui/sdl.c
index f6f711c..
Under 1.0.1 a pop-up window reports a Vis C++ runtime error, the result
is the same. -m 966 works fine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/538808
Title:
qemu-system-x86_64 0.12.2 crashes
Debug output ports (enabled by DEBUG_BIOS define) can be replaced by:
-chardev stdio,id=debugcon,mux=on
-device isa-debugcon,iobase=0x402,chardev=debugcon
-device isa-debugcon,iobase=0x403,chardev=debugcon
-device isa-debugcon,iobase=0x500,chardev=debugcon
-device isa-debugcon,iobase=0x503,chardev=
Add generic support for simple I/O port which, when written to, cause
QEMU to exit with the given written value.
There is no vmstate associated with the debugging port, simply because
the entire interface is a single, stateless, write-only port.
Signed-off-by: Hervé Poussineau
---
hw/debugexit.
Hi all,
the upstream qemu v1.1.0-rc4 x86_64
/opt/qemu/bin/qemu-system-x86-64 -s -kernel vmlinuz-3.0.0-22-generic
-initrd initrd.img-3.0.0-22-generic -hda ./linux-0.2.img -append
root=/dev/sda -boot c -monitor stdio --enable-kvm
no --enable-kvm no -m guest os will oops (out of memory) durin
On Thu, Jul 05, 2012 at 09:04:18PM -0300, Marcelo Tosatti wrote:
> On Mon, May 21, 2012 at 01:53:36PM -0400, Jason Baron wrote:
> > On Fri, May 04, 2012 at 05:23:51PM -0400, Jason Baron wrote:
> > > Add a command line parameter to not dump guest memory in the core dump,
> > > the
> > > command lin
The third parameter of unix_listen in the line:
int fd = unix_listen(path, NULL, strlen(path));
makes an unnecessary call to strlen. That parameter will not be used unless
the second parameter is not NULL, which is not the case here.
---
qga/channel-posix.c |2 +-
1 file changed, 1 insertion
yes, there is a measurement published in KVM conference.
http://www.linux-kvm.org/wiki/images/e/ea/2010-forum-mtosatti_walkthrough_entry_exit.pdf
Xin
On Thu, Jul 5, 2012 at 4:51 AM, wrote:
> Hi Xin Tong,
>
> Do you get any estimation on that?
>
> Regards,
> chenwj
>
On 17.06.2012 17:14, Avi Kivity wrote:
> On 06/17/2012 04:06 PM, Blue Swirl wrote:
>
>>> strtosz() is much too general. We could do it in vl.c without trouble.
>>> However, it takes away our ability to emulate a "640k should be enough
>>> for everyone" machine.
>>
>> Then how about current max o
On 07/06/2012 01:40 PM, Corey Bryant wrote:
On 07/06/2012 05:11 AM, Kevin Wolf wrote:
Am 05.07.2012 19:00, schrieb Eric Blake:
On 07/05/2012 10:35 AM, Corey Bryant wrote:
1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 with
refcount of 0; fd=4's in-use flag is turned on
2. cl
Alexander Graf writes:
> On 05.07.2012, at 18:20, Markus Armbruster wrote:
[...]
>> When it comes to block device models, IDE is *always* the troublemaker.
>> And a big reason for that is the messy data structures that are
>> impractical to clean up while we still support non-qdevified IDE. Whic
On 2012-07-06 19:16, Jan Kiszka wrote:
> On 2012-06-24 16:08, Jan Kiszka wrote:
>> On 2012-06-24 10:49, Avi Kivity wrote:
>>> On 06/23/2012 02:45 PM, Jan Kiszka wrote:
Hmm, we may need the iothread lock around cpu_set_apic_tpr for
!kvm_irqchip_in_kernel(). And as we are at it, apic_b
On 07/06/2012 05:11 AM, Kevin Wolf wrote:
Am 05.07.2012 19:00, schrieb Eric Blake:
On 07/05/2012 10:35 AM, Corey Bryant wrote:
1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 with
refcount of 0; fd=4's in-use flag is turned on
2. client calls 'device-add' with /dev/fdset/1 as th
Ugh... please disregard this. I hit send accidentally.
On 07/06/2012 01:14 PM, Corey Bryant wrote:
On 07/06/2012 05:11 AM, Kevin Wolf wrote:
Am 05.07.2012 19:00, schrieb Eric Blake:
On 07/05/2012 10:35 AM, Corey Bryant wrote:
1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 wi
On 2012-06-24 16:08, Jan Kiszka wrote:
> On 2012-06-24 10:49, Avi Kivity wrote:
>> On 06/23/2012 02:45 PM, Jan Kiszka wrote:
>>>
>>> Hmm, we may need the iothread lock around cpu_set_apic_tpr for
>>> !kvm_irqchip_in_kernel(). And as we are at it, apic_base manipulation
>>> can be but there as well.
On 07/06/2012 05:11 AM, Kevin Wolf wrote:
Am 05.07.2012 19:00, schrieb Eric Blake:
On 07/05/2012 10:35 AM, Corey Bryant wrote:
1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 with
refcount of 0; fd=4's in-use flag is turned on
2. client calls 'device-add' with /dev/fdset/1 as th
On 06.07.2012, at 17:58, Andreas Färber wrote:
> Am 06.07.2012 15:43, schrieb Alexander Graf:
>>
>> On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
>>
>>> From: Li Zhang
>>>
>>> pSeries machine needs to enable USB to add a USB
>>> keyboard or USB mouse. -usb option won't be used in
>>> the
Am 06.07.2012 18:03, schrieb Alexander Graf:
>
> On 06.07.2012, at 17:58, Andreas Färber wrote:
>
>> Am 06.07.2012 15:43, schrieb Alexander Graf:
>>>
>>> On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
>>>
From: Li Zhang
pSeries machine needs to enable USB to add a USB
key
On 2012-07-06 17:36, Alexander Graf wrote:
>
> On 02.07.2012, at 09:24, Jan Kiszka wrote:
>
>> On 2012-07-02 06:28, Alexey Kardashevskiy wrote:
>>> Ping?
>>>
>>>
>>> On 22/06/12 11:15, Alexey Kardashevskiy wrote:
Added (msi|msix)_set_message() function for whoever might
want to use them
Am 06.07.2012 15:43, schrieb Alexander Graf:
>
> On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
>
>> From: Li Zhang
>>
>> pSeries machine needs to enable USB to add a USB
>> keyboard or USB mouse. -usb option won't be used in
>> the future, and machine options are a better way to
>> enable U
Signed-off-by: Maksim Kozlov
---
hw/exynos4210_pmu.c | 34 +-
1 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/hw/exynos4210_pmu.c b/hw/exynos4210_pmu.c
index 7f09c79..2ae3b60 100644
--- a/hw/exynos4210_pmu.c
+++ b/hw/exynos4210_pmu.c
@@ -25,6 +25,
Mainly to make 'exynos4210_pmu_regs' array more readable.
Signed-off-by: Maksim Kozlov
---
hw/exynos4210_pmu.c | 324 ++-
1 files changed, 164 insertions(+), 160 deletions(-)
diff --git a/hw/exynos4210_pmu.c b/hw/exynos4210_pmu.c
index c12d750..2
It make possible to set DEBUG_PMU and DEBUG_PMU_EXTEND
independently of each other
Signed-off-by: Maksim Kozlov
---
hw/exynos4210_pmu.c | 23 +--
1 files changed, 17 insertions(+), 6 deletions(-)
diff --git a/hw/exynos4210_pmu.c b/hw/exynos4210_pmu.c
index 2be7e08..26a726f
This patch just introduces exynos4210_pmu_get_register_index function
to get index of the register's value in the array on its offset. And
functions _read and _write were modified accordingly.
Signed-off-by: Maksim Kozlov
---
hw/exynos4210_pmu.c | 56 ---
This patchset created mainly to add software reset support, but includes some
other things.
1. fix formatting of the exynos4210_pmu_regs structure
2. fix PRINT_DEBUG macro set to be able to enable extend and non-extend output
independently of each other
3. introduce new function to get register
On 6 July 2012 16:34, Peter Maydell wrote:
> I've also just realised that I'm assuming that the pointer returned
> by fdt_getprop() is naturally aligned for a 32 bit integer if the
> property is a 32 bit integer -- is that valid?
To answer my own question here, the dtb format mandates that
proper
On 02.07.2012, at 09:24, Jan Kiszka wrote:
> On 2012-07-02 06:28, Alexey Kardashevskiy wrote:
>> Ping?
>>
>>
>> On 22/06/12 11:15, Alexey Kardashevskiy wrote:
>>> Added (msi|msix)_set_message() function for whoever might
>>> want to use them.
>>>
>>> Currently msi_notify()/msix_notify() write
On 6 July 2012 02:56, Peter Crosthwaite wrote:
> Can we generalise and get functionality for reading cells with offsets
> as well? Your function assumes (and asserts) that the property is a
> single cell, but can we add a index parameter for reading a non-0th
> property out of a multi-cell prop? N
On 03.07.2012, at 01:03, Scott Wood wrote:
> [resent with the proper address for qemu-devel, sorry...]
>
> The current ppc_mpc8544ds.c is split into a generic (eventually) e500
> backend, and two platform frontends (mpc8544ds and a generic paravirt
> e500 platform) that instantiate the backend.
Hi,
On 07/06/2012 04:30 PM, Hans de Goede wrote:
Hi,
On 06/07/2012 11:31 AM, Gerd Hoffmann wrote:
Kick async schedule when we get a wakeup
notification from a usb device.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-ehci.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff -
Commit 0f588df8b3688b00e77aabaa32e26ece5f19bd39, added code
to ehci_wakeup to kick the async schedule on wakeup, but the else
was positioned wrong making it trigger for devices which are routed
to the companion rather then to the ehci controller itself.
This patch fixes this. Note that the "progra
On 05.07.2012, at 18:20, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 29.06.2012 17:34, schrieb Markus Armbruster:
>>> New limits straight from ATA4 6.2 Register delivered data transfer
>>> command sector addressing.
>>>
>>> I figure the old sector limit 63 was blindly copied from the
Add functions deposit32(), deposit64(), extract32() and extract64()
to extract and deposit bitfields in 32 and 64 bit words. Based on
ideas by Jia Liu and Avi Kivity.
Suggested-by: Jia Liu
Suggested-by: Avi Kivity
Signed-off-by: Peter Maydell
Reviewed-by: Eric Blake
Reviewed-by: Andreas Färber
Hi,
On 06/07/2012 11:31 AM, Gerd Hoffmann wrote:
Kick async schedule when we get a wakeup
notification from a usb device.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-ehci.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
index
Am 06.07.2012 16:01, schrieb Peter Maydell:
> On 6 July 2012 14:41, Andreas Färber wrote:
>> Small improvement would be to replace "Returns the" with "Returns: The"
>> in line with how you annotated the arguments, and the function summary
>> should go into its own paragraph between @foo: and Retur
On 6 July 2012 14:48, Andreas Färber wrote:
> Am 05.07.2012 19:00, schrieb Peter Maydell:
>> Make the RAM size in arm_boot_info a target_phys_addr_t so
>> it can express RAM sizes up to the limit imposed by the
>> physical address size.
> Didn't we conclude in lengthy and emotional discussions th
Am 06.07.2012 15:54, schrieb Alexander Graf:
>
> On 06.07.2012, at 15:48, Andreas Färber wrote:
>
>> Am 05.07.2012 19:00, schrieb Peter Maydell:
>>> Make the RAM size in arm_boot_info a target_phys_addr_t so
>>> it can express RAM sizes up to the limit imposed by the
>>> physical address size.
>>
On 6 July 2012 14:41, Andreas Färber wrote:
> Small improvement would be to replace "Returns the" with "Returns: The"
> in line with how you annotated the arguments, and the function summary
> should go into its own paragraph between @foo: and Returns:.
>
> http://developer.gnome.org/gtk-doc-manua
Am 06.07.2012 15:50, schrieb Alexander Graf:
>
> On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
>
>> @@ -712,6 +730,11 @@ static void ppc_spapr_init(ram_addr_t ram_size,
>> spapr_vscsi_create(spapr->vio_bus);
>> }
>>
>> +/* Graphics */
>> +if (spapr_vga_init(QLIST_FIRST(&s
On 06.07.2012, at 15:48, Andreas Färber wrote:
> Am 05.07.2012 19:00, schrieb Peter Maydell:
>> Make the RAM size in arm_boot_info a target_phys_addr_t so
>> it can express RAM sizes up to the limit imposed by the
>> physical address size.
>>
>> Signed-off-by: Peter Maydell
>> ---
>> hw/arm-mis
On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
> From: Li Zhang
>
> Also instanciate the USB keyboard and mouse when that option is used
> (you can still use -device to create individual devices without all
> the defaults)
>
> Signed-off-by: Benjamin Herrenschmidt
> Signed-off-by: Li Zhan
Am 05.07.2012 19:00, schrieb Peter Maydell:
> Make the RAM size in arm_boot_info a target_phys_addr_t so
> it can express RAM sizes up to the limit imposed by the
> physical address size.
>
> Signed-off-by: Peter Maydell
> ---
> hw/arm-misc.h |2 +-
> 1 files changed, 1 insertions(+), 1 dele
On 02.07.2012, at 07:25, zhlci...@gmail.com wrote:
> From: Li Zhang
>
> pSeries machine needs to enable USB to add a USB
> keyboard or USB mouse. -usb option won't be used in
> the future, and machine options are a better way to
> enable USB.
>
> So this patch is to add USB option to machine o
Am 28.06.2012 14:55, schrieb Peter Maydell:
> Add functions deposit32(), deposit64(), extract32() and extract64()
> to extract and deposit bitfields in 32 and 64 bit words. Based on
> ideas by Jia Liu and Avi Kivity.
>
> Suggested-by: Jia Liu
> Suggested-by: Avi Kivity
> Signed-off-by: Peter May
On 07/06/12 12:09, Hans de Goede wrote:
> Here are USB 2 bug-fixes, please also cherry-pick these into the
> stable-1.1 branch, esp. the second one as that fixes an easily triggerable
> assert.
>
> Note these patches are against 1.1.0, not against master, but they are
> relevant
> for, and should
On 2012년 07월 06일 03:49, Blue Swirl wrote:
On Thu, Jul 5, 2012 at 1:43 PM, Peter Maydell wrote:
On 5 July 2012 14:23, Yeongkyoon Lee wrote:
Add extended MMU helpers to softmmu targets, where the targets are alpha, arm,
cris, i386, lm32, m68k, microblaze, mips, ppc, s390x, sh4, sparc and xtens
On (Tue) 26 Jun 2012 [08:01:20], Anthony Liguori wrote:
> On 06/26/2012 05:48 AM, Amit Shah wrote:
> >On (Mon) 25 Jun 2012 [17:59:28], Anthony Liguori wrote:
> >>On 06/25/2012 05:46 PM, Anthony Liguori wrote:
> >>>From: Amit Shah
> >
> >>>diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c
> >
> >>>+sta
On 2012년 07월 05일 23:06, Peter Maydell wrote:
On 5 July 2012 14:23, Yeongkyoon Lee wrote:
Add an option "--enable-ldst-optimization" to enable
CONFIG_QEMU_LDST_OPTIMIZATION macro for TCG qemu_ld/st optimization. It only works with
CONFIG_SOFTMMU and doesn't work with CONFIG_TCG_PASS_AREG0.
Th
On 6 July 2012 12:20, Yeongkyoon Lee wrote:
>
>>> +#ifdef CONFIG_QEMU_LDST_OPTIMIZATION
>>> +/* jne slow_path */
>>> +tcg_out_opc(s, OPC_JCC_long + JCC_JNE, 0, 0, 0);
>>> +if (!label_ptr) {
>>> +tcg_abort();
>>> +}
>>
>> There's no point in this check and abort -- label_ptr
Is it really worth having this as a CONFIG_ switch? If we think
it's better to do this out of line we should just switch to
always generating the out of line code, I think. There's not much
point in retaining the old code path if it's disabled -- it will
just bitrot.
I agree.
However, it is just
On 2012-07-06 12:50, Wen Congyang wrote:
> At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
>> On 2012-07-06 11:38, Wen Congyang wrote:
>>> Signed-off-by: Wen Congyang
>>
>> Which kvm.git hash is this referring? Please state this to avoid that we
>> are merging support for kernel features that are still
On 2012-07-06 11:41, Wen Congyang wrote:
> The onpanic parameter can have the following value:
> 1. none
> 2. pause
> 3. poweroff
> 4. reset
>
> The action for each value when the guest is panicked:
> 1. none: emit QEVENT_GUEST_PANICKED only
> 2. pause: emit QEVENT_GUEST_PANICKED and pause the gue
On 2012-07-06 11:41, Wen Congyang wrote:
> The action is the same as -onpanic parameter.
As explained in patch 5, now that we have a related device, this no
longer needs to be a machine property.
Would could be a machine property is enabling/disabling this device.
That's probably useful as it use
On 2012-07-06 11:41, Wen Congyang wrote:
> If the target is x86/x86_64, the guest's kernel will write 0x01 to the
> port KVM_PV_PORT when it is panciked. This patch introduces a new qom
> device kvm_pv_ioport to listen this I/O port, and deal with panicked
> event according to panicked_action's val
> > Which kvm.git hash is this referring? Please state this to avoid that we
> > are merging support for kernel features that are still under review.
>
> The following kvm.git:
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=summary
What Jia ask for is git hash, should be something like,
8ac
At 07/06/2012 06:25 PM, Jan Kiszka Wrote:
> On 2012-07-06 11:38, Wen Congyang wrote:
>> Signed-off-by: Wen Congyang
>
> Which kvm.git hash is this referring? Please state this to avoid that we
> are merging support for kernel features that are still under review.
The following kvm.git:
http://gi
The current virtqueue_avail_bytes() is oddly named, and checks if a
particular number of bytes are available in a vq. A better API is to
fetch the number of bytes available in the vq, and let the caller do
what's interesting with the numbers.
Introduce virtqueue_get_avail_bytes(), which returns t
The virtqueue_avail_bytes() function counts bytes in an int. Use an
unsigned int instead.
Signed-off-by: Amit Shah
---
hw/virtio.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/virtio.c b/hw/virtio.c
index 168abe4..b21dcac 100644
--- a/hw/virtio.c
+++ b/hw/virtio.
Using the virtqueue_avail_bytes() function had an unnecessarily
crippling effect on the number of bytes needed by the guest as reported
to the chardev layer in the can_read() callback.
Using the new virtqueue_get_avail_bytes() function will let us advertise
the exact number of bytes we can send to
The current virtqueue_avail_bytes() is a weird API: it's oddly-named:
doesn't tell us what the API is going to do, and also suits just one
use-case (that in virtio-net.c).
Introduce virtqueue_get_avail_bytes(), which returns the number of
bytes in the vq available for input as well as output.
virt
> > Also, please line wrap your commit messages.
> I didn't know the line wrap rule of commit message. Is the rule included
> in checkpatch.pl? Let me check it.
I guess it's 80 char length rule?
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Aca
Add declarations and templates of extended MMU helpers which can take return
address argument to what helper functions return. These extended helper
functions are called only by generated code.
It's not entirely clear from this description what the
return address argument actually is.
My commit
On 2012-07-06 11:38, Wen Congyang wrote:
> Signed-off-by: Wen Congyang
Which kvm.git hash is this referring? Please state this to avoid that we
are merging support for kernel features that are still under review.
Jan
> ---
> linux-headers/asm-x86/kvm_para.h |2 ++
> linux-headers/linux/kvm
This patch adds the multiqueues support for emulated nics. Each VLANClientState
pairs are now abstract as a queue instead of a nic, and multiple VLANClientState
pointers were stored in the NICState. A queue_index were also introduced to let
the emulated nics know which queue the packet were came fr
This patch converts the vhost to support multiqueue queues. It implement a 1:1
mapping of vhost devs and tap fds. That it to say, the patch creates and uses
N vhost devs as the backend of the N queues virtio-net deivce.
The main work is to convert the virtqueue index into vhost queue index, this i
hcd-ehci.c is missing an usb_packet_init() call for the ipacket UsbPacket
it uses for isoc transfers, triggering an assert (taking the entire vm down)
in usb_packet_setup as soon as any isoc transfers are done by a high speed
USB device.
Signed-off-by: Hans de Goede
---
hw/usb/hcd-ehci.c |1
Signed-off-by: Hans de Goede
---
hw/usb/redirect.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
index 5f55d78..c6358c0 100644
--- a/hw/usb/redirect.c
+++ b/hw/usb/redirect.c
@@ -1058,6 +1058,8 @@ static int usbredir_handle_status(USBRedirDevice *d
Here are USB 2 bug-fixes, please also cherry-pick these into the
stable-1.1 branch, esp. the second one as that fixes an easily triggerable
assert.
Note these patches are against 1.1.0, not against master, but they are relevant
for, and should apply to, master too.
Regards,
Hans
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_PORT when it is panciked. This patch introduces a new qom
device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value. The possible actions are:
1. emit QEVENT_GUES
The onpanic parameter can have the following value:
1. none
2. pause
3. poweroff
4. reset
The action for each value when the guest is panicked:
1. none: emit QEVENT_GUEST_PANICKED only
2. pause: emit QEVENT_GUEST_PANICKED and pause the guest
3. poweroff: emit QEVENT_GUEST_PANICKED and poweroff the
The action is the same as -onpanic parameter.
Signed-off-by: Wen Congyang
---
qemu-config.c |4
qemu-options.hx |4 +++-
vl.c|7 +++
3 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/qemu-config.c b/qemu-config.c
index 5c3296b..805e7c4 100644
---
Some operating system ( such as Linux ) supports multiqueue tap, this is done
through attaching multiple sockets to the net device and expose multiple file
descriptors.
This patch let qemu utilizes this kind of backend, and introduces helpter for:
- creating a multiple capable tap device
- increa
Based on the multiqueue support for taps and NICState, this patch add the
capability of multiqueue for virtio-net. For userspace virtio-net emulation,
each pair of VLANClientState peers were abstracted as a tx/rx queue. For vhost,
the vhost net devices were created per virtio-net tx/rx queue pairs,
Sometimes, we need to pass option like -netdev tap,fd=100,fd=101,fd=102 which
can not be properly parsed by qemu_find_opt() because it only returns the first
matched option. So qemu_get_opt_all() were introduced to return an array of
pointers which contains all matched option.
Signed-off-by: Jason
Hello all:
This seires is an update of last version of multiqueue support to add multiqueue
capability to both tap and virtio-net.
Some kinds of tap backends has (macvatp in linux) or would (tap) support
multiqueue. In such kind of tap backend, each file descriptor of a tap is a
qeueu and ioctls
This event will be emited when 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
+++ b/monitor.c
@@ -458,6 +458,7 @@ sta
Using -device sga fixes the problem, but also means I cannot see what
it's trying to wait for.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1021649
Title:
qemu 1.1.0 waits for a keypress at boot
The guest will be in this state when it is panicked.
Signed-off-by: Wen Congyang
---
qapi-schema.json |6 +-
qmp.c|3 ++-
vl.c |7 ++-
3 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 3b6e346..00
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.
We don't set runstate to RUN_STATE_PAUSED when reseting the guest,
so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or
RUN_STATE_PAUSED to RUN_STATE_RUNNING(no
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
** Attachment added: "test-qemu.sh"
https://bugs.launchpad.net/bugs/1021649/+attachment/3214808/+files/test-qemu.sh
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1021649
Title:
qemu 1.1.0 waits
Also affects upstream qemu from git.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1021649
Title:
qemu 1.1.0 waits for a keypress at boot
Status in QEMU:
New
Bug description:
qemu 1.1.0 waits
Public bug reported:
qemu 1.1.0 waits for a keypress at boot. Please don't ever do this.
Try the attached test script. When run it will initially print nothing,
until you hit a key on the keyboard.
Removing -nographic fixes the problem.
Using virtio-scsi instead of virtio-blk fixes the proble
Am 05.07.2012 20:07, schrieb Blue Swirl:
> On Wed, Jul 4, 2012 at 8:34 AM, Kevin Wolf wrote:
>> Am 03.07.2012 21:19, schrieb Blue Swirl:
>>> On Tue, Jul 3, 2012 at 10:07 AM, Kevin Wolf wrote:
Am 09.06.2012 14:12, schrieb Blue Swirl:
> Move logging functions from exec.c to qemu-log.c,
>>>
Am 05.07.2012 19:00, schrieb Eric Blake:
> On 07/05/2012 10:35 AM, Corey Bryant wrote:
>> 1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 with
>> refcount of 0; fd=4's in-use flag is turned on
>> 2. client calls 'device-add' with /dev/fdset/1 as the backing filename,
>> so qemu_open()
Am 05.07.2012 18:39, schrieb Markus Armbruster:
> Markus Armbruster writes:
>
>> Kevin Wolf writes:
>>
>>> Am 29.06.2012 17:34, schrieb Markus Armbruster:
New limits straight from ATA4 6.2 Register delivered data transfer
command sector addressing.
I figure the old sector lim
Am 05.07.2012 18:37, schrieb Corey Bryant:
> There is one case I'm aware of where we need to be careful: Before
> opening an image, qemu may probe the format. In this case, the image
> gets opened twice, and the first close comes before the second open.
> I'm
> not entirely sure
On 28 June 2012 13:55, Peter Maydell wrote:
> Add functions deposit32(), deposit64(), extract32() and extract64()
> to extract and deposit bitfields in 32 and 64 bit words. Based on
> ideas by Jia Liu and Avi Kivity.
NB: I'm planning to put this v3 into a target-arm pullreq at the end
of next wee
On 28 June 2012 15:35, Peter Maydell wrote:
> This patch series adds support for the ARM Large Physical Address
> Extensions, which allow 40 bit physical addressing by means of
> a new translation table format.
Advance notice: I intend to put these patches into a pullreq at
the end of next week,
Commit f3d54fc4 factored it out of hw/ide.c for reuse. Sensible,
except it was put into block.c. Device-specific functionality should
be kept in device code, not the block layer. Move it to
hw/hd-geometry.c, and make stylistic changes required to keep
checkpatch.pl happy.
Signed-off-by: Markus
I've got a (longish) bugreport about qemu-kvm not
working on an AMD bulldozer CPU. In particular,
winXP guests which worked fine before, after upgrade
of the host CPU stopped working with a BSOD, and no
new winXP install can be completed due to installer
freezing somewhere in process.
I don't hav
When hd_geometry_guess() picks a geometry, it also picks the
appropriate translation, but only when the prior translation hint is
BIOS_ATA_TRANSLATION_AUTO. Looks wrong, because such a prior
translation would be passed to the BIOS whether it's suitable for the
geometry or not.
Fortunately, that c
32 patches may look discouraging, but most patches are small, and the
ones that aren't just move code around.
Goals of this series:
1. One more step towards a clean separation block device host and
guest part.
2. Purge CHS geometry from the block layer
Part I[PATCH 01-02/32]: Floppy geom
1 - 100 of 138 matches
Mail list logo
