[Qemu-devel] Da lau khong hoi tham suc khoe!

Xin chào và chúc anh/chị một ngày vui vẻ! Có phải bạn đang đi tìm phần mềm quản trị kinh doanh như thế này? HỆ THỐNG PHẦN MỀM QUẢN TRỊ KINH DOANH HTSOFT BIZMAN.NET “Không chỉ là công cụ ghi chép, báo cáo mà còn là công cụ tư vấn, định hướng và hỗ trợ ra quyết định cho nhà quản lý!” HTsoft

Re: [Qemu-devel] [PATCH] qdev: Reset hotplugged devices

On Fri, Aug 20, 2010 at 10:56:57AM -0500, Anthony Liguori wrote: > The real problem is how we do reset. We shouldn't register a reset > handler for every qdev device but rather register a single reset handler > that walks the device tree and calls reset on every reachable device. > > Then we c

Re: [Qemu-devel] Re: Unusual physical address when using 64-bit BAR

On Tue, Aug 24, 2010 at 10:52:36AM -0600, Cam Macdonell wrote: > Hi, 64-bit BARs still do not seem to be working. > > When using the latest seabios the guest does not hit a "BUG:" > statement, but booting still fails > > HPET: 1 timers in total, 0 timers will be used for per-cpu timer > divide er

[Qemu-devel] vhost_net.c broken by --kerneldir

I'm scratching my head on this one, but here's my problem: % ./configure --target-list=x86_64-softmmu --kerneldir=/home/hollisb/work/linux-2.6.hg % make V=1 [...] gcc -I/home/hollisb/work/qemu.git/slirp -Werror -m32 -fstack-protector-all -Wold-style-definition -Wold-style-declaration -I. -I/ho

[Qemu-devel] [PATCH][v2] Introduce NBD named exports.

This patch allows to connect Qemu using NBD protocol to an nbd-server using named exports. For instance, if on the host "isoserver", in /etc/nbd-server/config, you have: [generic] [debian-500-ppc-netinst] exportname = /ISO/debian-500-powerpc-netinst.iso [Fedora-10-ppc-netinst] exp

[Qemu-devel] Re: [syslinux] Bug#592875: pxelinux: incompatible with qemu with kvm enabled

On 08/24/2010 12:15 PM, Vagrant Cascadian wrote: > it seems versions of pxelinux 4.00 and later hangs qemu (0.12.x, 0.13.x) when > network booting using etherboot or gPXE and qemu's kvm support is enabled. > > pxelinux 3.86 and earlier do not appear to trigger the problem. i also didn't > experien

Re: [Qemu-devel] [PATCH] Introduce NBD named exports.

Le mardi 24 août 2010 à 10:59 +0200, Kevin Wolf a écrit : > Am 24.08.2010 03:04, schrieb Laurent Vivier: > > This patch allows to connect Qemu using NBD protocol to an nbd-server > > using named exports. > > > > For instance, if on the host "isoserver", in /etc/nbd-server/config, you > > have: >

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On 24.08.2010, at 20:35, Anthony Liguori wrote: > On 08/24/2010 08:44 AM, Daniel P. Berrange wrote: >> Actually this SCSI example I give above is appending a drive to an existing bus (scsi0), in slot 1 (scsi-id=1). To best of my knowledge there is no remaining use case that requi

[Qemu-devel] Re: Bug#592875: pxelinux: incompatible with qemu with kvm enabled

it seems versions of pxelinux 4.00 and later hangs qemu (0.12.x, 0.13.x) when network booting using etherboot or gPXE and qemu's kvm support is enabled. pxelinux 3.86 and earlier do not appear to trigger the problem. i also didn't experience the problem with qemu-kvm (formerly known as kvm). qemu

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On 08/24/2010 08:44 AM, Daniel P. Berrange wrote: Actually this SCSI example I give above is appending a drive to an existing bus (scsi0), in slot 1 (scsi-id=1). To best of my knowledge there is no remaining use case that requires use of IF_SCSI, IF_IDE, etc. The IF_NONE approach can cope with

Re: [Qemu-devel] Re: Unusual physical address when using 64-bit BAR

On Tue, Jul 20, 2010 at 9:49 PM, Isaku Yamahata wrote: > Added Cc: seab...@seabios.org > > On Wed, Jul 21, 2010 at 06:31:01AM +0300, Michael S. Tsirkin wrote: >> On Tue, Jul 20, 2010 at 06:52:23PM +0900, Isaku Yamahata wrote: >> > On Wed, Jul 14, 2010 at 09:10:28AM -0600, Cam Macdonell wrote: >> >

[Qemu-devel] Build error - target i386-linux-user on RHEL4.8 x86_64

Hi, I tried to build qemu's user mode linux emulation on RHEL 4.8 x86_64 - but I run into this issue - ARi386-linux-user/libqemu.a LINK i386-linux-user/qemu-i386 /usr/bin/ld:/home/ckk/lab/qemu-0.12.5/x86_64.ld:41: syntax error collect2: ld returned 1 exit status make[1]: *** [qemu-i386] Er

[Qemu-devel] Triburile Online - Tribal-Speed

Triburile Speed REGISTER

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 08:44 AM, Avi Kivity wrote: On 08/24/2010 04:40 PM, Anthony Liguori wrote: 1. Allocate a cluster (increase refcount table) 2. Link cluster to L2 table 3. Second operation makes it to disk; first still in pagecache 4. Crash 5. Dangling pointer from L2 to freed cluster Yes, h

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On Tue, Aug 24, 2010 at 03:46:14PM +0200, Alexander Graf wrote: > Daniel P. Berrange wrote: > > On Tue, Aug 24, 2010 at 03:40:25PM +0200, Alexander Graf wrote: > > > >> Daniel P. Berrange wrote: > >> > >>> On Tue, Aug 24, 2010 at 12:45:19PM +0200, Alexander Graf wrote: > >>> > >

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On Tue, Aug 24, 2010 at 03:40:25PM +0200, Alexander Graf wrote: > Daniel P. Berrange wrote: > > On Tue, Aug 24, 2010 at 12:45:19PM +0200, Alexander Graf wrote: > > > >> Daniel P. Berrange wrote: > >> > >>> On Tue, Aug 24, 2010 at 12:02:30AM +0200, Alexander Graf wrote: > >>> > >>>

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

Daniel P. Berrange wrote: > On Tue, Aug 24, 2010 at 03:40:25PM +0200, Alexander Graf wrote: > >> Daniel P. Berrange wrote: >> >>> On Tue, Aug 24, 2010 at 12:45:19PM +0200, Alexander Graf wrote: >>> > The key is that you should use if=none for all cases. Here are two > exampl

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 04:40 PM, Anthony Liguori wrote: 1. Allocate a cluster (increase refcount table) 2. Link cluster to L2 table 3. Second operation makes it to disk; first still in pagecache 4. Crash 5. Dangling pointer from L2 to freed cluster Yes, having this discussion in IRC. The problem

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 08:39 AM, Avi Kivity wrote: On 08/24/2010 04:35 PM, Anthony Liguori wrote: It's about metadata writes. If an operation changes metadata, we must sync it to disk before writing any data or other metadata which depends on it, regardless of any promises to the guest. Why? If th

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

Daniel P. Berrange wrote: > On Tue, Aug 24, 2010 at 12:45:19PM +0200, Alexander Graf wrote: > >> Daniel P. Berrange wrote: >> >>> On Tue, Aug 24, 2010 at 12:02:30AM +0200, Alexander Graf wrote: >>> >>> The monitor command for hotplugging is in i386 specific code. This is just

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 04:35 PM, Anthony Liguori wrote: It's about metadata writes. If an operation changes metadata, we must sync it to disk before writing any data or other metadata which depends on it, regardless of any promises to the guest. Why? If the metadata isn't sync, we loose the write.

[Qemu-devel] KVM call cancelled [was: Re: KVM call agenda for August 24]

* Anthony Liguori (anth...@codemonkey.ws) wrote: > On 08/23/2010 05:30 PM, Chris Wright wrote: > >Please send in any agenda items you are interested in covering. > > There are quite a few important discussions on the list but I think > they should stay on the list right now. > > So it sounds like

[Qemu-devel] [Bug 621950] Re: qemu not able to run 64 bit OS when -enable-kvm is used with a 64 bit processor

oops I made a mistake there were old binaries left out. It is working fine now. ** Changed in: qemu Status: New => Invalid -- qemu not able to run 64 bit OS when -enable-kvm is used with a 64 bit processor https://bugs.launchpad.net/bugs/621950 You received this bug notification because

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 08:31 AM, Avi Kivity wrote: On 08/24/2010 04:29 PM, Anthony Liguori wrote: I'm not sure this patch is needed in the first place. If you have a sequence of operations like: 0) receive guest write request Z 1) submit write A 2) write A completes 3) submit write B 4) write B compl

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 04:29 PM, Anthony Liguori wrote: I'm not sure this patch is needed in the first place. If you have a sequence of operations like: 0) receive guest write request Z 1) submit write A 2) write A completes 3) submit write B 4) write B completes 5) report guest write Z complete You'

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 08:16 AM, Kevin Wolf wrote: Am 24.08.2010 15:01, schrieb Anthony Liguori: On 08/24/2010 05:40 AM, Kevin Wolf wrote: This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. This fix has caused severe slowdowns on recent kernels that actually do flush when they are

[Qemu-devel] [PATCH 4/4] Rename PCI_FUNC_MAX to PCI_FUNCTIONS_PER_DEVICES in pci.[ch]

PCI_FUNC_MAX is introduced by 6eab3de16d36c48a983366b09d0a0029a5260bc3 and 6fa84913eccec4266a27c81ae88465f6790742b9 which should be safe to rename to PCI_FUNCTIONS_PER_DEVICES. Signed-off-by: Ken CC --- hw/pci.c |4 ++-- hw/pci.h |1 - 2 files changed, 2 insertions(+), 3 deletions(-) di

[Qemu-devel] [PATCH 3/4] Check pci slot number against PCIBUS_MAX_DEVICES in parse_pci_devfn

If pci addr provided from command line is bigger than 32, PCIBUS_MAX_DEVICES, return error -EINVAL. 32 << 3 | 7 == 256 (PCIBUS_MAX_FUNCTIONS) PCIBUS_MAX_FUNCTIONS = PCIBUS_MAX_DEVICES * PCI_FUNCTIONS_PER_DEVICE Signed-off-by: Ken CC --- hw/qdev-properties.c |4 +++- 1 files changed, 3 inser

[Qemu-devel] [PATCH 2/4] pci init: fail qemu if devfn exceeding the max function number supported on bus

Check if devfn < PCIBUS_MAX_DEVICES * PCI_FUNCTIONS_PER_DEVICE Signed-off-by: Ken CC --- hw/pci.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/hw/pci.c b/hw/pci.c index 9234fe3..fc4becd 100644 --- a/hw/pci.c +++ b/hw/pci.c @@ -747,6 +747,7 @@ static PCIDevice *do_pci_

[Qemu-devel] [PATCH 1/4] PCI: define PCIBUS_MAX_DEVICES and PCI_FUNCTIONS_PER_DEVICE in pci.h

And update the max function number used in struct PCIBus{} to PCIBUS_MAX_FUNCTIONS = PCI_FUNCTIONS_PER_DEVICE * PCIBUS_MAX_DEVICES TODO: according to Avi Kivity, PCIBus.devices[] should be renamed to functions[] Signed-off-by: Ken CC --- hw/pci.c |2 +- hw/pci.h |2 ++ 2 files chang

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Am 24.08.2010 15:01, schrieb Anthony Liguori: > On 08/24/2010 05:40 AM, Kevin Wolf wrote: >> This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. >> >> This fix has caused severe slowdowns on recent kernels that actually do flush >> when they are told so. Reverting this patch hurts correct

[Qemu-devel] Re: KVM call agenda for August 24

On 08/23/2010 05:30 PM, Chris Wright wrote: Please send in any agenda items you are interested in covering. There are quite a few important discussions on the list but I think they should stay on the list right now. So it sounds like we don't have an agenda for today. Regards, Anthony

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 05:40 AM, Kevin Wolf wrote: This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. This fix has caused severe slowdowns on recent kernels that actually do flush when they are told so. Reverting this patch hurts correctness and means that we could get corrupted images in case

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Am 24.08.2010 14:39, schrieb Avi Kivity: > On 08/24/2010 03:35 PM, Kevin Wolf wrote: >> >>> I don't know how bad the performance regression is, and how large the >>> integrity risk is. I'd default towards preserving integrity, but maybe >>> this situation is different. >> I have reports of insta

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Kevin Wolf wrote: > This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. > > This fix has caused severe slowdowns on recent kernels that actually do flush > when they are told so. Reverting this patch hurts correctness and means that > we > could get corrupted images in case of a host cr

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 03:35 PM, Kevin Wolf wrote: I don't know how bad the performance regression is, and how large the integrity risk is. I'd default towards preserving integrity, but maybe this situation is different. I have reports of installations taking like 50 min instead of 14 min. My own qem

Re: [Qemu-devel] [PATCH 0/5] CODING_STYLE amendments

Anthony Liguori writes: > On 08/22/2010 01:36 PM, malc wrote: > > But how would you do that? Drop the CODING_STYLE (and accept > anything)? Switch to a new CODING_STYLE that is widely appreciated and > so all bikeshedding will cease? Enforce current style? > I w

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Am 24.08.2010 14:27, schrieb Avi Kivity: > On 08/24/2010 03:21 PM, Alexander Graf wrote: >> Avi Kivity wrote: >>> On 08/24/2010 03:12 PM, Alexander Graf wrote: > Well, safety is not boolean. Considering to make it mostly safe instead > of completely safe because of the performance doesn

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

24.08.2010 16:21, Stefan Hajnoczi wrote: > On Tue, Aug 24, 2010 at 12:40 PM, Kevin Wolf wrote: >> Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: >>> QEMU 0.12.5 has qcow2 sync metadata writes in commit >>> 37060c28e522843fbf6f7e59af745dfcb05b132c. Was the performance >>> regression spotted on 0.12

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 03:21 PM, Alexander Graf wrote: Avi Kivity wrote: On 08/24/2010 03:12 PM, Alexander Graf wrote: Well, safety is not boolean. Considering to make it mostly safe instead of completely safe because of the performance doesn't mean that we should make it completely unsafe. What is

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On Tue, Aug 24, 2010 at 12:40 PM, Kevin Wolf wrote: > Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: >> QEMU 0.12.5 has qcow2 sync metadata writes in commit >> 37060c28e522843fbf6f7e59af745dfcb05b132c.  Was the performance >> regression spotted on 0.12.5 or 0.13? > > Both. You mean we should consid

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Avi Kivity wrote: > On 08/24/2010 03:12 PM, Alexander Graf wrote: >> >>> Well, safety is not boolean. Considering to make it mostly safe instead >>> of completely safe because of the performance doesn't mean that we >>> should make it completely unsafe. >>> >> What is safety then? A vague feeling

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On 08/24/2010 03:16 PM, Chen Cao wrote: On Tue, Aug 24, 2010 at 03:04:44PM +0300, Avi Kivity wrote: On 08/24/2010 03:07 PM, Isaku Yamahata wrote: On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: On 08/24/2010 02:35 PM, Isaku Yamahata wrote: Add Cc: m...@redhat.com. MAX_PCI_SL

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On 08/24/2010 03:12 PM, Alexander Graf wrote: Well, safety is not boolean. Considering to make it mostly safe instead of completely safe because of the performance doesn't mean that we should make it completely unsafe. What is safety then? A vague feeling of "oh today is monday so my data is

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On Tue, Aug 24, 2010 at 03:04:44PM +0300, Avi Kivity wrote: > On 08/24/2010 03:07 PM, Isaku Yamahata wrote: > >On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: > >> On 08/24/2010 02:35 PM, Isaku Yamahata wrote: > >>>Add Cc: m...@redhat.com. > >>> > >>>MAX_PCI_SLOTS should be in pci.h i

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On 08/24/2010 03:24 PM, Isaku Yamahata wrote: On Tue, Aug 24, 2010 at 03:04:44PM +0300, Avi Kivity wrote: On 08/24/2010 03:07 PM, Isaku Yamahata wrote: On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: On 08/24/2010 02:35 PM, Isaku Yamahata wrote: Add Cc: m...@redhat.com. MAX

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On Tue, Aug 24, 2010 at 03:04:44PM +0300, Avi Kivity wrote: > On 08/24/2010 03:07 PM, Isaku Yamahata wrote: >> On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: >>> On 08/24/2010 02:35 PM, Isaku Yamahata wrote: Add Cc: m...@redhat.com. MAX_PCI_SLOTS should be in pci.h in

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Kevin Wolf wrote: > Am 24.08.2010 13:56, schrieb Alexander Graf: > >> Kevin Wolf wrote: >> >>> Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: >>> >>> On Tue, Aug 24, 2010 at 11:40 AM, Kevin Wolf wrote: > This reverts commit 8b3b720620a1137a1b794fc3

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Am 24.08.2010 13:56, schrieb Alexander Graf: > Kevin Wolf wrote: >> Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: >> >>> On Tue, Aug 24, 2010 at 11:40 AM, Kevin Wolf wrote: >>> This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. This fix has caused severe slowdowns

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On 08/24/2010 03:07 PM, Isaku Yamahata wrote: On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: On 08/24/2010 02:35 PM, Isaku Yamahata wrote: Add Cc: m...@redhat.com. MAX_PCI_SLOTS should be in pci.h instead of qdev.h? And the name should be start with PCI_ prefix for consistency?

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On Tue, Aug 24, 2010 at 02:42:18PM +0300, Avi Kivity wrote: > On 08/24/2010 02:35 PM, Isaku Yamahata wrote: >> Add Cc: m...@redhat.com. >> >> MAX_PCI_SLOTS should be in pci.h instead of qdev.h? >> And the name should be start with PCI_ prefix for consistency? >> >> Except that, the patches look ok

Re: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Kevin Wolf wrote: > Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: > >> On Tue, Aug 24, 2010 at 11:40 AM, Kevin Wolf wrote: >> >>> This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. >>> >>> This fix has caused severe slowdowns on recent kernels that actually do >>> flush >>> whe

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

On 08/24/2010 02:35 PM, Isaku Yamahata wrote: Add Cc: m...@redhat.com. MAX_PCI_SLOTS should be in pci.h instead of qdev.h? And the name should be start with PCI_ prefix for consistency? Except that, the patches look okay. These aren't slots, are they? They are functions. There's a lot of

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

Am 24.08.2010 13:02, schrieb Stefan Hajnoczi: > On Tue, Aug 24, 2010 at 11:40 AM, Kevin Wolf wrote: >> This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. >> >> This fix has caused severe slowdowns on recent kernels that actually do flush >> when they are told so. Reverting this patch hu

Re: [Qemu-devel] [PATCH 3/3] Check pci slot number in parse_pci_devfn

Add Cc: m...@redhat.com. MAX_PCI_SLOTS should be in pci.h instead of qdev.h? And the name should be start with PCI_ prefix for consistency? Except that, the patches look okay. thanks, On Tue, Aug 24, 2010 at 02:49:27PM +0800, Ken CC wrote: > Define MAX_PCI_SLOTS as 0x1f, if pci addr provided fr

Re: [Qemu-devel] [PATCH 12/15] piix_pci: Introduces Xen specific call for irq.

On Mon, Aug 23, 2010 at 10:50:49AM +0100, stefano.stabell...@eu.citrix.com wrote: > From: Anthony PERARD > > This patch introduces Xen specific call in piix_pci. > > The specific part for Xen is in write_config, set_irq and get_pirq. > > Signed-off-by: Anthony PERARD > Signed-off-by: Stefano

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

24.08.2010 15:02, Stefan Hajnoczi wrote: [] > Sometimes an improvement has a side effect and it makes sense to hold > back the improvement until the side effect can be resolved. The > period of time in which users could rely on qcow2 data integrity is > small to none, I feel reverting the commit m

[Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

On Tue, Aug 24, 2010 at 11:40 AM, Kevin Wolf wrote: > This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. > > This fix has caused severe slowdowns on recent kernels that actually do flush > when they are told so. Reverting this patch hurts correctness and means that > we > could get cor

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On Tue, Aug 24, 2010 at 12:45:19PM +0200, Alexander Graf wrote: > Daniel P. Berrange wrote: > > On Tue, Aug 24, 2010 at 12:02:30AM +0200, Alexander Graf wrote: > > > >> The monitor command for hotplugging is in i386 specific code. This is just > >> plain wrong, as S390 just learned how to do hot

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

Daniel P. Berrange wrote: > On Tue, Aug 24, 2010 at 12:02:30AM +0200, Alexander Graf wrote: > >> The monitor command for hotplugging is in i386 specific code. This is just >> plain wrong, as S390 just learned how to do hotplugging too and needs to >> get drives for that. >> >> So let's add a gen

[Qemu-devel] [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"

This reverts commit 8b3b720620a1137a1b794fc3ed64734236f94e06. This fix has caused severe slowdowns on recent kernels that actually do flush when they are told so. Reverting this patch hurts correctness and means that we could get corrupted images in case of a host crash. This means that qcow2 migh

Re: [Qemu-devel] Emulate character device

Thank you Stefan, I will work on this. Thanks for the support. On Tue, Aug 24, 2010 at 2:43 PM, Stefan Hajnoczi wrote: > On Tue, Aug 24, 2010 at 10:02 AM, Thisara Rupasinghe > wrote: > > Thank you very much for your information. > > > > That means i can pass web cam as usb device into the emul

Re: [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup

On 08/23/2010 07:02 PM, Anthony Liguori wrote: On 08/23/2010 10:14 AM, Avi Kivity wrote: On 08/23/2010 05:47 PM, Anthony Liguori wrote: Devices can contain references to structs and objects. If a Device contains a reference to an object, the object should be stored in a BusState which i

Re: [Qemu-devel] [PATCH 4/5] Add generic drive hotplugging

On Tue, Aug 24, 2010 at 12:02:30AM +0200, Alexander Graf wrote: > The monitor command for hotplugging is in i386 specific code. This is just > plain wrong, as S390 just learned how to do hotplugging too and needs to > get drives for that. > > So let's add a generic copy to generic code that handle

Re: [Qemu-devel] Emulate character device

On Tue, Aug 24, 2010 at 10:02 AM, Thisara Rupasinghe wrote: > Thank you very much for your information. > > That means i can pass web cam as usb device into the emulator. right? > If you can give me some directions, that will be very helpful. Please keep qemu-devel@nongnu.org CCed so others can h

Re: [Qemu-devel] [PATCH] Introduce NBD named exports.

Am 24.08.2010 03:04, schrieb Laurent Vivier: > This patch allows to connect Qemu using NBD protocol to an nbd-server > using named exports. > > For instance, if on the host "isoserver", in /etc/nbd-server/config, you have: > > [generic] > [debian-500-ppc-netinst] > exportname = /ISO/debia

Re: [Qemu-devel] Emulate character device

On Tue, Aug 24, 2010 at 6:04 AM, Thisara Rupasinghe wrote: > There I need to use machines > character device "dev/vedio0" and stream that to the qemu environment. > Therefore on the emulator that web cam stream will be available as the > emulators character device "dev/video0". So how can I able t

[Qemu-devel] Nyheter hos DokuMera

Om du har problem med att läsa detta e-postmeddelande, klicka här (http://www.anp.se/newsletterweb/846225/444059437941455D4B7142445C43) för en webb-version. Vårt nyhetsbrev skickas automatiskt till våra kunder och intressenter. Vill du inte ha detta nyhetsbrev framöver, klicka här för att avpre