[Prev Page][Next Page]
- Re: Extending libvirt to probe NUMA topology
- [PATCH] Fix enum virDrvOpenRemoteFlags
- Re: Extending libvirt to probe NUMA topology
- Re: libvirt statistics
- Re: libvirt statistics
- Extending libvirt to probe NUMA topology
- Re: libvirt statistics
- Re: feature sujestions
- From: Márcio Parise Boufleur
- libvirt statistics
- Re: [PATCH] Remove warning when dumping XML from an inactive domain with Xen < 3.1
- Re: [PATCH] Remove warning when dumping XML from an inactive domain with Xen < 3.1
- Re: Compiling libvirt v0.3.2 on centos5
- [PATCH] Remove warning when dumping XML from an inactive domain with Xen < 3.1
- Re: Compiling libvirt v0.3.2 on centos5
- Re: Compiling libvirt v0.3.2 on centos5
- Re: [PATCH]OpenVZ Enhancements - Cleaned up
- Re: [PATCH]OpenVZ Enhancements - Cleaned up
- [PATCH]OpenVZ Enhancements - Cleaned up
- Re: Compiling libvirt v0.3.2 on centos5
- Re: Compiling libvirt v0.3.2 on centos5
- Compiling libvirt v0.3.2 on centos5
- Re: libvirt on Windows
- Re: Ruby bindings for libvirt
- Re: Ruby bindings for libvirt
- libvirt on Windows
- Re: --without-*
- Re: --without-*
- --without-*
- Re: Ruby bindings for libvirt
- Re: [PATCH] Fix endless loop of VirBufferVSprintf()
- Re: Ruby bindings for libvirt
- Ruby bindings for libvirt
- Re: [PATCH] Fix endless loop of VirBufferVSprintf()
- ANNOUNCE: virt-top 0.3.2.5 released
- Re: [PATCH] TX/RX network stats are swapped
- [PATCH] TX/RX network stats are swapped
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Fix return value of virsh vncdisplay
- [PATCH] Fix return value of virsh vncdisplay
- Re: [PATCH] Delete a harmful variable in xend_parse_sexp_desc()
- [PATCH] Delete a harmful variable in xend_parse_sexp_desc()
- Re: feature sujestions
- Re: feature sujestions
- Re: feature sujestions
- Re: OpenVZ driver enhancements
- Re: Segfault with invalid virConnectPtr
- Segfault with invalid virConnectPtr
- [PATCH] Fix endless loop of VirBufferVSprintf()
- Re: feature sujestions
- Re: feature sujestions
- Re: feature sujestions
- OpenVZ driver enhancements
- feature sujestions
- From: Márcio Parise Boufleur
- Libvirt with Gentoo and Udev
- Re: Release of libvirt-0.3.2
- ANNOUNCE: ocaml-libvirt 0.3.2.0 (libvirt bindings for OCaml) released
- Release of libvirt-0.3.2
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Show Xen vif<domid>.<n> device name in domain XML
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Cleanup xs_internal.c
- Re: [PATCH] Show Xen vif<domid>.<n> device name in domain XML
- Re: [PATCH] Cleanup xs_internal.c
- Re: [PATCH] Update hvsupport page
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Check availability of driver calls
- Re: [PATCH] Cleanup xs_internal.c
- Re: [PATCH] Check availability of driver calls
- Re: [PATCH] Update hvsupport page
- Re: [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Cleanup xs_internal.c
- Re: [PATCH] Show Xen vif<domid>.<n> device name in domain XML
- [PATCH] Show Xen vif<domid>.<n> device name in domain XML
- [PATCH] Update hvsupport page
- Re: [PATCH] Check availability of driver calls
- [PATCH] Block device and network stats (version 2)
- Re: [PATCH] Check availability of driver calls
- Re: [PATCH] Check availability of driver calls
- Re: [PATCH] virDomainMigrate version 5 (repost)
- Re: [PATCH] Check availability of driver calls
- [PATCH] virDomainMigrate version 5 (repost)
- [PATCH] Check availability of driver calls
- Re: [PATCH] check the file name for --log
- Re: [PATCH] Cleanup xs_internal.c
- Re: question about --quiet option
- Re: [PATCH] check the file name for --log
- Re: [PATCH] check the file name for --log
- Re: [PATCH] Cleanup xs_internal.c
- Re: Re: [et-mgmt-tools] ANNOUNCE: virt-viewer release 0.0.1
- Re: Set memory (decrease) from Virt Manager
- question about --quiet option
- Set memory (decrease) from Virt Manager
- Re: Stability of virsh / libvirt interfaces
- Re: Stability of virsh / libvirt interfaces
- Re: [et-mgmt-tools] ANNOUNCE: virt-viewer release 0.0.1
- Re: Stability of virsh / libvirt interfaces
- Re: Re: [et-mgmt-tools] ANNOUNCE: virt-viewer release 0.0.1
- Re: [et-mgmt-tools] ANNOUNCE: virt-viewer release 0.0.1
- Stability of virsh / libvirt interfaces
- Re: [PATCH] Fix some memory leaks of virsh schedinfo
- Re: [PATCH] Fix some memory leaks in xs_internal.c
- [PATCH] Fix some memory leaks of virsh schedinfo
- [PATCH] Fix some memory leaks in xs_internal.c
- [PATCH] Cleanup xs_internal.c
- Re: [PATCH] Check the version of Xen in xenDaemonAttachDevice()
- Re: [PATCH] Check the version of Xen in xenDaemonAttachDevice()
- Re: [PATCH] Check the version of Xen in xenDaemonAttachDevice()
- Re: [PATCH] Check a value in vshCommandOptInt()
- [PATCH] Check the version of Xen in xenDaemonAttachDevice()
- [PATCH] Check a value in vshCommandOptInt()
- Re: Networking functions in libvirt
- Networking functions in libvirt
- Re: [patch] virsh setvcpus range check for negative value case
- Re: [patch] virsh setvcpus range check for negative value case
- [patch] virsh setvcpus range check for negative value case
- Re: [PATCH] fix UUID lookup when using the proxy
- [PATCH] fix UUID lookup when using the proxy
- Re: fix SYNOPSIS of virsh --help schedinfo
- Re: several typo fixes on man virsh
- fix SYNOPSIS of virsh --help schedinfo
- several typo fixes on man virsh
- Re: [PATCH 0/7] QEMU/KVM save/restore support, take 3
- Re: [PATCH 0/7] QEMU/KVM save/restore support, take 3
- Re: [PATCH] Add KVM restore support using migration.
- Re: [PATCH] Add KVM save support using migration.
- Re: [PATCH] Add signal-safe read/write wrappers
- Re: [PATCH] Add qemudEscapeShellArg for passing commandlines to qemu.
- Re: [PATCH] Add migration support to QEMU startup.
- Re: [PATCH] Add option to pass stdin fd to virExec
- Re: [PATCH] Fix issues with QEMU monitor interface.
- Re: [PATCH 0/7] QEMU/KVM save/restore support, take 3
- [PATCH] Add migration support to QEMU startup.
- [PATCH] Add signal-safe read/write wrappers
- [PATCH] Add option to pass stdin fd to virExec
- [PATCH] Add KVM restore support using migration.
- [PATCH 0/7] QEMU/KVM save/restore support, take 3
- [PATCH] Add KVM save support using migration.
- [PATCH] Add qemudEscapeShellArg for passing commandlines to qemu.
- [PATCH] Fix issues with QEMU monitor interface.
- Re: [PATCH 7/7] Add KVM restore support using migration.
- Re: [PATCH 6/7] Add KVM save support using migration.
- Re: [PATCH 3/7] Add option to pass stdin fd to virExec
- Re: [PATCH 2/7] Fix issues with QEMU monitor interface.
- Re: [PATCH 3/7] Add option to pass stdin fd to virExec
- Re: [PATCH 2/7] Fix issues with QEMU monitor interface.
- Re: [PATCH] Block device and network stats
- Re: [PATCH 3/7] Add option to pass stdin fd to virExec
- Re: [PATCH 2/7] Fix issues with QEMU monitor interface.
- Re: [PATCH] Block device and network stats
- Re: [PATCH 3/7] Add option to pass stdin fd to virExec
- Re: [PATCH 2/7] Fix issues with QEMU monitor interface.
- Re: [PATCH 1/7] Fix memory leak
- Re: [PATCH] Block device and network stats
- [PATCH 6/7] Add KVM save support using migration.
- [PATCH 7/7] Add KVM restore support using migration.
- [PATCH 2/7] Fix issues with QEMU monitor interface.
- [PATCH 3/7] Add option to pass stdin fd to virExec
- [PATCH 4/7] Add migration support to QEMU startup.
- [PATCH 5/7] Add qemudEscapeShellArg for passing commandlines to qemu.
- [PATCH 1/7] Fix memory leak
- Re: save/restore support for KVM
- Re: save/restore support for KVM
- Re: save/restore support for KVM
- Re: PATCH: Fix paravirt FB with xm driver
- Re: PATCH: Fix virtual neworks with xm driver
- Re: save/restore support for KVM
- Re: PATCH: Improve performance on Xen
- Re: PATCH: Fix paravirt FB with xm driver
- Re: save/restore support for KVM
- Re: save/restore support for KVM
- Re: PATCH: Fix virtual neworks with xm driver
- Re: PATCH: Fix paravirt FB with xm driver
- Re: PATCH: Fix paravirt FB with xm driver
- Re: PATCH: Fix paravirt FB with xm driver
- Re: PATCH: Fix virtual neworks with xm driver
- Re: save/restore support for KVM
- Re: PATCH: Fix virtual neworks with xm driver
- PATCH: Fix paravirt FB with xm driver
- PATCH: Fix virtual neworks with xm driver
- Re: [PATCH] Block device and network stats
- Re: [PATCH] Block device and network stats
- Re: [PATCH] Block device and network stats
- Re: Proposal: Block device and network stats
- Re: Proposal: Block device and network stats
- [PATCH] Block device and network stats
- Re: Proposal: Block device and network stats
- Re: Proposal: Block device and network stats
- Re: Proposal: Block device and network stats
- Re: Proposal: Block device and network stats
- Re: PATCH: Improve performance on Xen
- Re: PATCH: Improve performance on Xen
- Re: save/restore support for KVM
- Re: Proposal: Block device and network stats
- Proposal: Block device and network stats
- Re: [Xen-users] Re: Xen physical host statistics
- Re: Xen physical host statistics
- Re: PATCH: Improve performance on Xen
- Re: [Xen-users] Re: Xen physical host statistics
- Re: save/restore support for KVM
- Re: Xen physical host statistics
- Re: save/restore support for KVM
- Re: save/restore support for KVM
- Xen physical host statistics
- Re: PATCH: Improve performance on Xen
- PATCH: Improve performance on Xen
- Re: PATCH: UUID code cleanup
- Re: save/restore support for KVM
- save/restore support for KVM
- ANNOUNCE: Virt-top 0.3.1.5 - a top-like utility for displaying virtualization stats
- Re: PATCH: UUID code cleanup
- Re: PATCH: UUID code cleanup
- PATCH: UUID code cleanup
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- Re: libvirt daemon UNIX socket auth with PolicyKit
- libvirt daemon UNIX socket auth with PolicyKit
- Re: [PATCH] A variety of fixes for Debian, old versions of GnuTLS
- Re: [PATCH] Fix libvirtd --config / -f option
- Re: [PATCH] A variety of fixes for Debian, old versions of GnuTLS
- Re: [PATCH] Fix libvirtd --config / -f option
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: [PATCH] Fix libvirtd --config / -f option
- Re: [PATCH] Fix libvirtd --config / -f option
- Re: [PATCH] A variety of fixes for Debian, old versions of GnuTLS
- [PATCH] Fix libvirtd --config / -f option
- [PATCH] A variety of fixes for Debian, old versions of GnuTLS
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- Re: ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- ANNOUNCE: Virt-top - a top-like utility for displaying virtualization stats
- ANNOUNCE: OCaml bindings 0.3.1.0 released
- Re: [PATCH] check file format in virsh attach/detach-device
- Re: [PATCH] check the file name for --log
- Re: [PATCH] check file format in virsh attach/detach-device
- Re: [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Re: Re: [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Re: [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Re: [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Re: [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Exporting calls just to libvirtd
- [PATCH] Re: Proposal: Check availability of driver calls (repost)
- Re: Proposal: Check availability of driver calls (repost)
- Re: [PATCH] check the file name for --log
- Re: [PATCH] check the file name for --log
- Re: Proposal: Check availability of driver calls (repost)
- Re: Proposal: Check availability of driver calls (repost)
- Re: PATCH: Check for bogus default architecture
- Proposal: Check availability of driver calls (repost)
- Re: PATCH: Overhaul the test driver
- Re: PATCH: Check for bogus default architecture
- Re: [PATCH] check the file name for --log
- Re: [PATCH] check the file name for --log
- Re: [PATCH] check file format in virsh attach/detach-device
- Re: [PATCH] check file format in virsh attach/detach-device
- [PATCH] check the file name for --log
- [PATCH] check file format in virsh attach/detach-device
- Re: PATCH Fix a couple of mem leaks
- Re: PATCH Fix a couple of mem leaks
- Re: PATCH Fix a couple of mem leaks
- Re: PATCH Fix a couple of mem leaks
- PATCH Fix a couple of mem leaks
- Re: Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- Re: Re: PATCH 1/2: Qemu feature reporting
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- Re: Re: PATCH 1/2: Qemu feature reporting
- Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- Re: [PATCH] virsh Range check in Credit Scheduler
- PATCH: Check for bogus default architecture
- Re: [PATCH] add a ttyconsole command
- Re: [PATCH] add a ttyconsole command
- Re: PATCH: Overhaul the test driver
- PATCH: Overhaul the test driver
- Re: PATCH: Separate QEMU impl of nodeinfo API
- Re: [PATCH] add a ttyconsole command
- Re: PATCH: Separate QEMU impl of nodeinfo API
- Re: [PATCH] add a ttyconsole command
- [PATCH] add a ttyconsole command
- Re: Re: PATCH 1/2: Qemu feature reporting
- Re: PATCH: Separate QEMU impl of nodeinfo API
- Re: Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- Re: Re: PATCH 1/2: Qemu feature reporting
- Re: PATCH: Separate QEMU impl of nodeinfo API
- Re: Re: PATCH 1/2: Qemu feature reporting
- Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- PATCH: Separate QEMU impl of nodeinfo API
- Re: PATCH 2/2: Reporting of ACPI/APIC features for HVM Xen
- Re: PATCH 1/2: Qemu feature reporting
- PATCH 0/2: Capabilities and features
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Release of libvirt-0.3.1
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Re: PATCH: Make QEMU driver honour 'listen' flag for VNC
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Proposal: Check availability of driver calls
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: PATCH: Fix crash in cleanup when VM creation fails
- Re: Remote daemon & virDomainFree interaction
- Re: PATCH: Make QEMU driver honour 'listen' flag for VNC
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: Remote daemon & virDomainFree interaction
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: Remote daemon & virDomainFree interaction
- Re: PATCH: Fix crash in cleanup when VM creation fails
- Re: PATCH: Make QEMU driver honour 'listen' flag for VNC
- Re: PATCH: Make QEMU driver honour 'listen' flag for VNC
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: Remote daemon & virDomainFree interaction
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Remote daemon & virDomainFree interaction
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- PATCH: Fix crash in cleanup when VM creation fails
- Re: PATCH: Make QEMU driver honour 'listen' flag for VNC
- PATCH: Make QEMU driver honour 'listen' flag for VNC
- Re: [PATCH] virDomainMigrate (version 5) (for discussion only, but getting there)
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- [PATCH] virDomainMigrate (version 5) (for discussion only, but getting there)
- Re: [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- Re: OpenVZ XML format and VPS properties get/set interface [long]
- OpenVZ XML format and VPS properties get/set interface [long]
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] Document VIRSH_DEFAULT_CONNECT_URI
- [PATCH] Document VIRSH_DEFAULT_CONNECT_URI
- Re: FW: [et-mgmt-tools] Release 0.200.0 of virtinst
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] xen/?/privcmd.h
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: [PATCH] xen/?/privcmd.h
- Re: [PATCH]0/3 OpenVZ driver : Some clean ups
- Re: [PATCH]0/3 OpenVZ driver : Some clean ups
- Re: Xen reboot does not work with Sys::Virt perl binding
- Re: RFC: format for mapping host devices to guest
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: RFC: format for mapping host devices to guest
- Re: [PATCH]0/3 OpenVZ driver : Some clean ups
- [PATCH]3/3 OpenVZ driver : qemu_driver.c changes
- [PATCH]2/3 OpenVZ driver : generic utils
- [PATCH]1/3 OpenVZ driver : Cleanups
- [PATCH]0/3 OpenVZ driver : Some clean ups
- Re: RFC: format for mapping host devices to guest
- Re: PATCH: Fix accident close of monitor FD & leak of logfile FD to child
- Re: [PATCH] xen/?/privcmd.h
- FW: [et-mgmt-tools] Release 0.200.0 of virtinst
- PATCH: Fix accident close of monitor FD & leak of logfile FD to child
- Re: Re: XM config <-> XML config
- RFC: format for mapping host devices to guest
- Re: XM config <-> XML config
- Re: XM config <-> XML config
- XM config <-> XML config
- Re: PATCH: Support input devices in XML format
- [PATCH] virDomainMigrate version 4 (for discussion only!)
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Re: [PATCH] xen/?/privcmd.h
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Re: Asynchronous notifications of domain start/stop
- Re: [PATCH] xen/?/privcmd.h
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Re: Asynchronous notifications of domain start/stop
- Re: PATCH: Support input devices in XML format
- Re: PATCH: Support input devices in XML format
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Asynchronous notifications of domain start/stop
- Re: [PATCH] xen/?/privcmd.h (was: Re: [PATCH] virsh Range check in Credit Scheduler)
- Re: Re: Asynchronous notifications of domain start/stop
- [PATCH] xen/?/privcmd.h (was: Re: [PATCH] virsh Range check in Credit Scheduler)
- Re: virDomainConfigureDevice?
- Re: virDomainConfigureDevice?
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: virDomainConfigureDevice?
- Re: virDomainConfigureDevice?
- Re: Re: Asynchronous notifications of domain start/stop
- Re: virDomainConfigureDevice?
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Re: Asynchronous notifications of domain start/stop
- Re: PATCH: Support input devices in XML format
- Re: Asynchronous notifications of domain start/stop
- Re: Re: Asynchronous notifications of domain start/stop
- Re: virDomainConfigureDevice?
- Re: Re: Asynchronous notifications of domain start/stop
- Re: PATCH: Support input devices in XML format
- Re: Re: Asynchronous notifications of domain start/stop
- Re: Asynchronous notifications of domain start/stop
- Re: [PATCH] cleanup of virDeviceMode
- Asynchronous notifications of domain start/stop
- Re: virDomainConfigureDevice?
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: PATCH: Support input devices in XML format
- virDomainConfigureDevice?
- Re: Third version of virDomainMigrate API
- Re: [PATCH] virsh Range check in Credit Scheduler
- Re: [PATCH] cleanup of virDeviceMode
- [PATCH] cleanup of virDeviceMode
- Re: Initial OpenVZ Support Patches
- Re: Initial OpenVZ Support Patches
- Re: Initial OpenVZ Support Patches
- Re: Third version of virDomainMigrate API
- Re: [PATCH] virsh Range check in Credit Scheduler
- [PATCH] virsh Range check in Credit Scheduler
- Re: Initial OpenVZ Support Patches
- PATCH: Support input devices in XML format
- Re: PATCH: Specify BIOS clock offset for HVM
- Re: Initial OpenVZ Support Patches
- Re: Third version of virDomainMigrate API (was: Re: [PATCH 0/2] virDomainMigrate (for discussion only!))
- Third version of virDomainMigrate API (was: Re: [PATCH 0/2] virDomainMigrate (for discussion only!))
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- Re: PATCH: Specify BIOS clock offset for HVM
- [PATCH 2/2] virDomainMigrate test program
- [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
- [PATCH 0/2] virDomainMigrate (for discussion only!)
- Initial OpenVZ Support Patches
- Re: PATCH: Specify BIOS clock offset for HVM
- Re: Regarding Libvirt & VirtManager
- Regarding Libvirt & VirtManager
- OCaml binding 0.3.0.1 released
- PATCH: Specify BIOS clock offset for HVM
- Re: [PATCH] Add the check of the format of MAC address on virsh attach-interface
- Re: [PATCH] Fix strange message on virsh attach-device
- Re: [PATCH] Fix strange message on virsh attach-device
- Re: [PATCH] Add the check of the format of MAC address on virsh attach-interface
- Re: [PATCH] Add the check of the format of MAC address on virsh attach-interface
- [PATCH] Fix strange message on virsh attach-device
- [PATCH] Add the check of the format of MAC address on virsh attach-interface
- Small remote doc update and little checking script
- Re: PATCH: Report errors against virConnectPtr object
- Re: PATCH: Fix crash if client acl check fails
- Re: PATCH: More useful error messages with missing certs
- Re: PATCH: More useful error messages with missing certs
- Re: Xen reboot does not work with Sys::Virt perl binding
- Re: Next features and target for development
- Xen reboot does not work with Sys::Virt perl binding
- From: Keck, Christian (ext)
- Re: Starting a domain
- Starting a domain
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: xen long-list s-expression
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: PATCH: Fix crash if client acl check fails
- Re: PATCH: More useful error messages with missing certs
- Re: PATCH: Report errors against virConnectPtr object
- Re: PATCH: Force close of virConnectPtr if client quits abnormally
- Re: [PATCH] Add the check of the device source
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: PATCH: Force close of virConnectPtr if client quits abnormally
- Re: [PATCH] Add the check of the device source
- [PATCH] Add the check of the device source
- PATCH: Force close of virConnectPtr if client quits abnormally
- Re: PATCH: Report errors against virConnectPtr object
- Re: PATCH: Report errors against virConnectPtr object
- Re: PATCH: More useful error messages with missing certs
- Re: PATCH: Fix crash if client acl check fails
- PATCH: Report errors against virConnectPtr object
- PATCH: More useful error messages with missing certs
- PATCH: Fix crash if client acl check fails
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: Re: Next features and target for development
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: Re: Next features and target for development
- Re: [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- Re: [PATCH] Get rid of QEMUD_PID_FILE
- Re: Re: Next features and target for development
- [PATCH] If ./configure --enable-debug=yes, print libvirt calls
- [PATCH] Get rid of QEMUD_PID_FILE
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: Re: Next features and target for development
- Re: Next features and target for development
- Re: Double call to domainSuspend callback
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Re: Virtualization things.
- Re: Next features and target for development
- Re: Next features and target for development
- Re: [PATCH] Fix memory leak on virDomainParseXMLDiskDesc()
- Re: [PATCH] Fix memory leak on virDomainParseXMLDiskDesc()
- [PATCH] Fix memory leak on virDomainParseXMLDiskDesc()
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Double call to domainSuspend callback
- Double call to domainSuspend callback
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Howto: install libvirt on Debian Etch (the ugly way)
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Next features and target for development
- Re: Updating an existing libvirt installation
- Next features and target for development
- Re: Updating an existing libvirt installation
- Re: Re: Virtualization things.
- Re: Re: Virtualization things.
- Re: Re: Virtualization things.
- Re: Re: Virtualization things.
- Re: Re: Virtualization things.
- Re: Updating an existing libvirt installation
- Re: Updating an existing libvirt installation
- Updating an existing libvirt installation
- Re: Virtualization things.
- Re: Virtualization things.
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: xen long-list s-expression
- xen long-list s-expression
- Release of libvirt-0.3.0
- Re: XML escaping patch
- Re: XML escaping patch
- Re: XML escaping patch
- Re: XML escaping patch
- Re: XML escaping patch
- Re: XML escaping patch
- Re: XML escaping patch
- XML escaping patch
- Re: Some doubts for OpenVZ
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: Some doubts for OpenVZ
- Re: Some doubts for OpenVZ
- Re: Some doubts for OpenVZ
- Re: Some doubts for OpenVZ
- Some doubts for OpenVZ
- Re: virsh vcpupin does not work with xend
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: virsh vcpupin does not work with xend
- Re: big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- big-endian support for libvirt - introduce GUEST_HANDLE infrastructure ?
- Re: LSBization of libvirt init script
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: LSBization of libvirt init script
- LSBization of libvirt init script
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: [RFC]OpenVZ XML def
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: [RFC]OpenVZ XML def
- Re: [RFC]OpenVZ XML def
- Re: [RFC]OpenVZ XML def
- Re: [RFC]OpenVZ XML def
- Re: [RFC]OpenVZ XML def
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: [RFC]OpenVZ XML def
- Re: [RFC]OpenVZ XML def
- Re: [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
- Re: Howto: install libvirt on Debian Etch (the ugly way)
- Re: virsh vcpupin does not work with xend
- Re: Howto: install libvirt on Debian Etch (the ugly way)
- Howto: install libvirt on Debian Etch (the ugly way)
- Re: [PATCH] #4: Change interface between xen_unified & its underlying drivers
- OCaml binding 0.3.0.0 released
- Re: [PATCH] Fix xm_internal configCache
- Re: [PATCH] Fix xm_internal configCache
[Index of Archives]
[Libvirt Users]
[Fedora Users]
[Red Hat Install]
[Red Hat Sound]
[Red Hat Development]
[Linux Kernel]