On Sat, Feb 19, 2011 at 06:56:22PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Nothing prevented IRQ sharing on the ISA bus in principle. Not all
> boards supported this, neither each and every card nor driver and OS.
> Still, there existed valid IRQ sharing scenarios, (at least) two of them
19.02.2011 20:56, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Nothing prevented IRQ sharing on the ISA bus in principle. Not all
> boards supported this, neither each and every card nor driver and OS.
> Still, there existed valid IRQ sharing scenarios, (at least) two of them
> can also be found in Q
This patch is similar to 171e3d6b9997c98a97d0c525867f7cd9b640cadd
which fixed qcow2:
Returning -EIO is far from optimal, but at least it's an error code.
Cc: Kevin Wolf
Signed-off-by: Stefan Weil
---
block/vdi.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/block
This patch is similar to 171e3d6b9997c98a97d0c525867f7cd9b640cadd
which fixed qcow2:
Returning -EIO is far from optimal, but at least it's an error code.
In addition to read/write failures, -EIO is also returned when
decompress_cluster failed.
Cc: Kevin Wolf
Signed-off-by: Stefan Weil
---
blo
Hello,
I like the way like VMWare Server 2.x does bridging: There is no need to
change basic network interface settings and add a bridge between the
existing network interface like e.g. discussed in:
http://www.linux-kvm.com/content/using-bridged-networking-virt-manager
VMWare Server 2.x does
Am 19.02.2011 17:21, schrieb Stefan Hajnoczi:
On Sat, Feb 19, 2011 at 12:27 PM, Chunqiang Tang wrote:
I applied FVD's fully automated testing tool to the VDI block device
driver and found several bugs. Some bugs are easy to fix whereas others
need some thoughts on design. Therefore, I thought y
Hello everyone,
Following up on the QEMU & SPICE meeting at FOSDEM, is anyone
attending Embedded World (*) 1-3 March in Nuremberg?
If you're interested in meeting either on the exhibit floor or for a
social evening, please indicate which day(s) you'll be there.
Best regards,
Andreas
(*
On Thu, Feb 10, 2011 at 03:35:57PM +0200, Alon Levy wrote:
> Hi,
>
> Would be nice to have this in 0.14 - it is only documentation, and
> fixing documentation inconsistency (html help contains all this parameters
> already).
>
Ping!
> Alon
>
> On Thu, Feb 10, 2011 at 03:23:05PM +0200, Alon Le
Am 19.02.2011 um 17:25 schrieb Blue Swirl:
Signed-off-by: Blue Swirl
---
This does not get rid of the pointer property, because ISA bus doesn't
provide any method to connect multiple IRQs, unlike SysBus.
Another wart is that vmmouse uses void pointer for the IRQ, because
qemu_irq is not suppo
From: Jan Kiszka
Nothing prevented IRQ sharing on the ISA bus in principle. Not all
boards supported this, neither each and every card nor driver and OS.
Still, there existed valid IRQ sharing scenarios, (at least) two of them
can also be found in QEMU: >2 PC UARTs and the PREP IDE buses.
So rem
On Fri, Feb 18, 2011 at 7:11 PM, Kevin Wolf wrote:
> Am 18.02.2011 18:43, schrieb Stefan Weil:
>> Is maintaining an additional file format really so much work?
>> I have only some personal experience with vdi.c, and there maintainance
>> was largely caused by interface changes and done by Kevin.
>
On Fri, Feb 4, 2011 at 4:37 AM, wrote:
> The following patch adds a new block driver to QEMU/KVM for iSCSI.
> This utilizes the userspace client library for iscsi at
> https://github.com/sahlberg/libiscsi and will link with this library if
> available.
>
> This allows using iSCSI resources with
Signed-off-by: Blue Swirl
---
This does not get rid of the pointer property, because ISA bus doesn't
provide any method to connect multiple IRQs, unlike SysBus.
Another wart is that vmmouse uses void pointer for the IRQ, because
qemu_irq is not supported by qdev properties.
hw/pc.c |5
Public bug reported:
Chunqiang Tang reports the following issues with the VDI block driver,
these are present in QEMU 0.14:
"Bug 1. The most serious bug is caused by race condition in updating a new
bmap entry in memory and on disk. Considering the following operation
sequence.
O1: VM issues
On Sat, Feb 19, 2011 at 12:27 PM, Chunqiang Tang wrote:
> I applied FVD's fully automated testing tool to the VDI block device
> driver and found several bugs. Some bugs are easy to fix whereas others
> need some thoughts on design. Therefore, I thought you might be able to
> handle the bugs bette
On Fri, Feb 4, 2011 at 4:37 AM, wrote:
> From: Ronnie Sahlberg
>
> This patch adds a new block driver : block.iscsi.c
> This driver interfaces with the multiplatform posix library
> for iscsi initiator/client access to iscsi devices hosted at
> git://github.com/sahlberg/libiscsi.git
>
> The patc
** Attachment added: "2.6.35.11 kernel config"
https://bugs.launchpad.net/qemu/+bug/721793/+attachment/1859875/+files/config.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/721793
Title:
QEMU
** Attachment added: "Strace log"
https://bugs.launchpad.net/bugs/721793/+attachment/1859874/+files/strace-qemu.log.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/721793
Title:
QEMU freezes o
Public bug reported:
0.12.5 was the last version of QEMU that runs ok and boots any os image.
0.13.0-0.14.0 just freeze, and the only thing I see is a black screen and both
of them make it use 100% of CPU also.
Both kernels 2.6.35.11 and 2.6.37.1 with and without PAE support.
tested commands:
Hi Stefan,
I applied FVD's fully automated testing tool to the VDI block device
driver and found several bugs. Some bugs are easy to fix whereas others
need some thoughts on design. Therefore, I thought you might be able to
handle the bugs better than me. These bugs occur only if I/O errors or
20 matches
Mail list logo
