Hi Christoph,
On Wed, Apr 13, 2011 at 08:01:58PM +0100, Prasad Joshi wrote:
The patch only implements the basic read write support for QCOW version 1
images. Many of the QCOW features are not implmented, for example
On Fri, Apr 15, 2011 at 6:24 AM, Christoph Hellwig h...@infradead.org wrote:
Kevin Wolf kw...@redhat.com writes:
Am 13.04.2011 21:26, schrieb Prasad Joshi:
The patch only implements the basic read write support for QCOW version 1
images. Many of the QCOW features are not implmented, for example
- image creation
- snapshot
- copy-on-write
- encryption
Yay,
On Fri, Apr 15, 2011 at 9:41 AM, Markus Armbruster arm...@redhat.com wrote:
What hasn't been discussed much is the other half of Kevin's remark: why
QCOW1?
QCOW1 was simpler to implement as the first non-raw image format.
Pekka
--
To unsubscribe from this list: send the
Am 15.04.2011 08:24, schrieb Pekka Enberg:
Hi Christoph,
On Wed, Apr 13, 2011 at 08:01:58PM +0100, Prasad Joshi wrote:
The patch only implements the basic read write support for QCOW version 1
images. Many of the QCOW features are not implmented, for example
On Fri, Apr 15, 2011 at 6:24
On Fri, Apr 15, 2011 at 7:45 AM, Pekka Enberg penb...@kernel.org wrote:
On Fri, Apr 15, 2011 at 9:41 AM, Markus Armbruster arm...@redhat.com wrote:
What hasn't been discussed much is the other half of Kevin's remark: why
QCOW1?
QCOW1 was simpler to implement as the first non-raw image format.
Use original hardcode network by default.
#./kvm run ... -n virtio --tapscript=./util/kvm-ifup-vbr0
# brctl show
bridge name bridge id STP enabled interfaces
vbr08000.e272c7c391f4 no tap0
guest)# ifconfig eth6
eth6 Link encap:Ethernet
* Pekka Enberg penb...@kernel.org wrote:
Add support for booting guests to host block devices in read-only mode.
Cc: Asias He asias.he...@gmail.com
Cc: Cyrill Gorcunov gorcu...@gmail.com
Cc: Prasad Joshi prasadjoshi...@gmail.com
Cc: Sasha Levin levinsasha...@gmail.com
Cc: Ingo Molnar
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX sparse raw files gives you the same
feature.
Because people have existing images they want to boot to?
--
To unsubscribe
On Fri, Apr 15, 2011 at 12:17 PM, Pekka Enberg penb...@kernel.org wrote:
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX sparse raw files gives you the same
feature.
On Fri, Apr 15, 2011 at 3:05 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
People don't have existing QCOW1 images they want to boot from :).
They have vmdk, vhd, vdi, or qcow2. You can use qemu-img to convert
them to raw. You can use qemu-nbd if you are desperate to boot from
or inspect
On 04/15/2011 06:17 AM, Pekka Enberg wrote:
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczistefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX sparse raw files gives you the same
feature.
Because people have existing
Am 15.04.2011 14:05, schrieb Stefan Hajnoczi:
On Fri, Apr 15, 2011 at 12:17 PM, Pekka Enberg penb...@kernel.org wrote:
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX
The function name sect_to_l1_offset() is changed to get_l1_index() as it
returns the l1 table index rather than offset.
Also change
- sect_to_l2_offset to get_l2_index
- sect_to_cluster_offset to get_cluster_offset
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/qcow.c
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/qcow.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/tools/kvm/qcow.c b/tools/kvm/qcow.c
index 243bfa8..9b9af86 100644
--- a/tools/kvm/qcow.c
+++ b/tools/kvm/qcow.c
@@ -115,6 +115,7 @@ static void
Add a new function qcow1_read_cluster() to read a qcow cluster size data at a
time. The function qcow1_read_sector() is modified to use the function
qcow1_read_cluster().
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/qcow.c | 123
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/qcow.c | 17 -
1 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/tools/kvm/qcow.c b/tools/kvm/qcow.c
index 219fd6b..243bfa8 100644
--- a/tools/kvm/qcow.c
+++ b/tools/kvm/qcow.c
@@ -58,7 +58,7 @@
Signed-off-by: Asias He asias.he...@gmail.com
---
tools/kvm/term.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/term.c b/tools/kvm/term.c
index 2245c8d..2bd038d 100644
--- a/tools/kvm/term.c
+++ b/tools/kvm/term.c
@@ -71,9 +71,9 @@ int term_getc_iov(int
On Thu, Apr 14, 2011 at 12:55 PM, Daniel P. Berrange
berra...@redhat.com wrote:
On Wed, Apr 13, 2011 at 10:56:21PM +0300, Blue Swirl wrote:
On Wed, Apr 13, 2011 at 4:08 PM, Luiz Capitulino lcapitul...@redhat.com
wrote:
On Tue, 12 Apr 2011 21:31:18 +0300
Blue Swirl blauwir...@gmail.com
The code is based on the following QCOW 1 image format specification:
http://people.gnome.org/~markmc/qcow-image-format-version-1.html
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/qcow.c | 148 +-
1 files changed, 147
* Asias He asias.he...@gmail.com wrote:
Signed-off-by: Asias He asias.he...@gmail.com
---
tools/kvm/term.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Mind explaining in the changelog what input problem this is about?
Thanks,
Ingo
--
To unsubscribe from this
Include the Linux kernel header file linux/stringify.h file instead of
redefining the __stringify* macros
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
tools/kvm/include/kvm/util.h |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git
Bug https://bugs.launchpad.net/qemu/+bug/754591 is caused because
the KVM module attempts to do a pci_save_state() before assigning
the device to a VM, expecting that the saved state will remain
valid until we release the device. This is in conflict with our
need to reset devices using PCI sysfs
For KVM device assignment, we'd like to save off the state of a device
prior to passing it to the guest and restore it later. We also want
to allow pci_reset_funciton() to be called while the device is owned
by the guest. This however overwrites and invalidates the struct pci_dev
buffers, so we
Store the device saved state so that we can reload the device back
to the original state when it's unassigned. This has the benefit
that the state survives across pci_reset_function() calls via
the PCI sysfs reset interface while the VM is using the device.
Signed-off-by: Alex Williamson
On 2011-04-15 21:54, Alex Williamson wrote:
Store the device saved state so that we can reload the device back
to the original state when it's unassigned. This has the benefit
that the state survives across pci_reset_function() calls via
the PCI sysfs reset interface while the VM is using the
On Fri, 2011-04-15 at 22:03 +0200, Jan Kiszka wrote:
On 2011-04-15 21:54, Alex Williamson wrote:
Store the device saved state so that we can reload the device back
to the original state when it's unassigned. This has the benefit
that the state survives across pci_reset_function() calls via
On 2011-04-15 22:13, Alex Williamson wrote:
On Fri, 2011-04-15 at 22:03 +0200, Jan Kiszka wrote:
On 2011-04-15 21:54, Alex Williamson wrote:
Store the device saved state so that we can reload the device back
to the original state when it's unassigned. This has the benefit
that the state
On 04/16/2011 02:23 AM, Ingo Molnar wrote:
* Asias He asias.he...@gmail.com wrote:
Signed-off-by: Asias He asias.he...@gmail.com
---
tools/kvm/term.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Mind explaining in the changelog what input problem this is about?
Sure.
28 matches
Mail list logo