Displaying 20 results from an estimated 30000 matches similar to: "Disk not bootable from yesterday resolved"
2012 Feb 15
2
a problem with using qcow2 format image files as virtual disks
Hi,
In most cases we use image files as virtual disks under the full-virtualization situation.On the version 4.1.2 of xen,I do the following command:
############################################################
dd if=/dev/zero of=myraw.img bs=1M seek=8K count=1
#Before the command below I install the operating system in myraw.img
qemu-img-xen create -b myraw.img -f qcow2 myqcow1.img 20000M
2016 Mar 30
2
p2v a single bootable partition
2016 Mar 30
0
Re: p2v a single bootable partition
On Wed, Mar 30, 2016 at 11:06:57AM +0200, arnaud.bougeard@univ-rennes1.fr wrote:
>Hello
>
>How to convert a bootable linux partition to virtual disk ?
>I tried :
>
>|dd if=/dev/sda1 of=/mnt/mydisk3/sda1.raw|
>
>|||qemu-img convert -f raw -O qcow2 sda1.raw sda1.qcow2|
>
>|but the disk ||sda1.qcow2|is not bootable
>
>
>The second partition contains data and is
2014 Dec 22
7
Using virsh blockcopy -- what's it supposed to accomplish?
I am experimenting with the blockcopy command, and after figuring out
how to integrate qemu-nbd, nbd-client and
dumpxml/undefine/blockcopy/define/et. al. I have one remaining question:
What's the point?
The "replication" disk file is not, from what I can ascertain, bootable.
I expect this operation to create a pristine copy of my source qcow2
file (at a given point in time)
2015 Mar 27
2
Re: Point-in-time snapshots (was: Re: Inspection of disk snapshots)
On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote:
> [Added Stefan Hajnoczi, who wrote the 'drive-backup' QMP command and
> Eric Blake.]
>
> On Wed, Mar 25, 2015 at 07:41:23PM +0000, Richard W.M. Jones wrote:
> > On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote:
> > > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones
2023 Aug 07
3
[PATCH libnbd] copy/copy-file-to-qcow2-compressed.sh: Skip test for all zeroes disk
Occasionally this test will choose a random seed which results in an
all-zeroes disk. The test tries to convert this to a compressed qcow2
file, and fails because no compressed clusters are detected in the
resulting file. This happens because qcow2 stores zero clusters with
a special sparse representation, they are never stored compressed, so
a disk with only zeroes in it will never contain
2015 Aug 12
1
[PATCH 1/2] disk-create: Allow preallocation off/metadata/full.
For raw, this allows "off" as a synonym for "sparse" (to make it
consistent with qcow2).
For qcow2, this allows "sparse" as a synonym for "off".
It also adds qcow2 "full" preallocation, which is actually mapped to
the qemu option "falloc" (see arguments about this on the qemu-devel
mailing list, which we lost).
This also updates the
2015 May 28
2
Re: Concurrent scanning of same disk
2015-05-28 10:40 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>:
> On Thu, May 28, 2015 at 10:33:48AM +0300, NoxDaFox wrote:
> > To create the snapshots I'm using the libvirt command snapshotCreateXML
> > with no flag set. Does libvirt support consistent snapshotting or shall I
> > rely on QEMU backup new feature only?
>
> According to:
2019 Aug 01
3
Detach disk from VM - virsh (working) vs. PHP (not working)
Hi all,
i created a script in PHP for create a virtual server with two QCOW2 discs … one is our system for installation and second is target system.
After successfully instalation (create a blank Debian system, prepare all files and grub partitions) i need a restart virtual without a installation disk.
If i use Virsh:
detach-disk --domain debian-test2 --persistent --target vda
reset
2019 Apr 25
1
Live Disk Backup with Active Blockcommit
Hi!
I was reading the Wiki about 'Live Disk Backup with Active Blockcommit, https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit
and see that example shown seems to be using two different names for the same file.
First showing the current block device in use:
$ virsh domblklist vm1
Target Source
------------------------------------------------
vda
2015 Mar 23
2
Re: Inspection of disk snapshots
On Mon, Mar 23, 2015 at 10:41:01PM +0000, Richard W.M. Jones wrote:
> On Mon, Mar 23, 2015 at 04:34:21PM +0200, NoxDaFox wrote:
> > Greetings,
> >
> > I have the following typical scenario: given one or more qcow2 base images
> > I clone them with COW and start the VMs.
> >
> > At a certain point I'd like to inspect them in order to see their evolution
2023 Aug 08
1
[PATCH libnbd] copy/copy-file-to-qcow2-compressed.sh: Skip test for all zeroes disk
On 8/8/23 00:28, Richard W.M. Jones wrote:
> Occasionally this test will choose a random seed which results in an
> all-zeroes disk. The test tries to convert this to a compressed qcow2
> file, and fails because no compressed clusters are detected in the
> resulting file. This happens because qcow2 stores zero clusters with
> a special sparse representation, they are never stored
2015 Mar 27
0
Re: Point-in-time snapshots (was: Re: Inspection of disk snapshots)
On Fri, Mar 27, 2015 at 12:15:34PM +0000, Stefan Hajnoczi wrote:
> On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote:
> > So, something like?
> >
> > . . .
> > { 'execute': 'drive-backup', 'arguments':
> > { 'device': 'drive-virtio-disk1', 'sync': 'full', 'target':
>
2015 May 06
1
Re: Proper way to reference a disk
On Wed, May 6, 2015 at 4:14 PM, Eric Blake <eblake@redhat.com> wrote:
> > The source file / source dev thing really has me wondering.
> Hopefully I answered it.
>
Yes you did, thanks.
Furthermore,
> which can give more accurate numbers when doing things like
> qcow2 format atop an LVM block device).
>
...This has me intrigued. We are running qcow2 format in
2012 Nov 28
1
error: argument unsupported: unable to handle disk requests in snapshot
Hello, a problem occurred during making a snapshot for a guest, ask for help...
1. the xml for snapshotdomain like this:
# cat deployment.1
<domainsnapshot>
<name>a</name>
<disks>
<disk name='/home/qcow2/disk.0'>
<driver type='qcow2'/>
<source file='/home/qcow2/disk.3'/>
</disk>
</disks>
2015 Mar 25
0
Re: Point-in-time snapshots (was: Re: Inspection of disk snapshots)
[Added Stefan Hajnoczi, who wrote the 'drive-backup' QMP command and
Eric Blake.]
On Wed, Mar 25, 2015 at 07:41:23PM +0000, Richard W.M. Jones wrote:
> On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote:
> > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones wrote:
[. . .]
> > > > If you want lightweight, consistent, point-in-time snapshots
2016 Jul 26
2
Live Disk Backup
Dear All,
using CentOS 7.2.1511, and libvirt from ovirt repositories (currently 1.2.17-13.el7_2.5, but without otherwise using ovirt) I am regularly backing up my VMs which are on qcow2 files. In general, I am trying to follow http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit
A typical backup script would be
#!/bin/bash
dt=`date +%y%m%d`
if virsh dominfo dockers10a | grep
2015 Oct 14
2
failed to pivot job for disk vdc
Hello,
I did a virsh snapshot-create-as --domain meta sn1 --diskspec
vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only
--atomic --no-metadata
Then I successfully blockcommitted 2 disks:
virsh blockcommit meta vda --active --verbose --pivot
virsh blockcommit meta vdb --active --verbose --pivot
But when doing
virsh blockcommit meta vdc --active --verbose --pivot
I got:
Block commit:
2013 Dec 10
2
virsh attach makes qcow2 format disk to raw format
Hi all
I have a problem when I use `virsh attach` to attach a qcow2 disk to vm without argument --subdirver=qcow2
and this makes the qcow2 disk become a raw format disk, and the data in this disk is missing in guest os
and also I have used guestmout to confirm this, the same result.
Is there any way to let me find back the data in this disk ?
the version of libvirt and kvm is :
Compiled
2015 Mar 27
3
Re: Point-in-time snapshots (was: Re: Inspection of disk snapshots)
On Fri, Mar 27, 2015 at 12:31:41PM +0000, Richard W.M. Jones wrote:
> On Fri, Mar 27, 2015 at 12:15:34PM +0000, Stefan Hajnoczi wrote:
> > On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote:
> > > So, something like?
> > >
> > > . . .
> > > { 'execute': 'drive-backup', 'arguments':
> > > {