From: Guido Winkelmann <guido-kvml@thisisnotatest.de>
To: Brian Jackson <iggy@theiggy.com>
Cc: kvm@vger.kernel.org
Subject: Re: I/O errors in guest OS after repeated migration
Date: Wed, 17 Oct 2012 13:54 +0200 [thread overview]
Message-ID: <1510481.QTrF9SkzaV@pc10> (raw)
In-Reply-To: <201210161244.28183.iggy@theiggy.com>
Am Dienstag, 16. Oktober 2012, 12:44:27 schrieb Brian Jackson:
> On Tuesday, October 16, 2012 11:33:44 AM Guido Winkelmann wrote:
[...]
> > The commandline, as generated by libvirtd, looks like this:
> >
> > LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> > QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.15 -enable-kvm -m 1024
> > -smp 1,sockets=1,cores=1,threads=1 -name migratetest2 -uuid
> > ddbf11e9-387e-902b-4849-8c3067dc42a2 -nodefconfig -nodefaults -chardev
> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/migratetest2.monitor,serv
> > e
> > r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
> > -no-reboot -no- shutdown -device
> > piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
> > file=/data/migratetest2_system,if=none,id=drive-virtio-
> > disk0,format=qcow2,cache=none -device virtio-blk-
> > pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-
> > disk0,bootindex=1 -drive file=/data/migratetest2_data-1,if=none,id=drive-
> > virtio-disk1,format=qcow2,cache=none -device virtio-blk-
> > pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -
> > netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-
> > pci,netdev=hostnet0,id=net0,mac=02:00:00:00:00:0c,bus=pci.0,addr=0x3 -vnc
> > 127.0.0.1:2,password -k de -vga cirrus -incoming tcp:0.0.0.0:49153 -device
> > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
>
> I see qcow2 in there. Live migration of qcow2 was a new feature in 1.0. Have
> you tried other formats or different qemu/kvm versions?
Are you sure about that? Because I'm fairly certain I have been using live
migration since at least 0.14, if not 0.13, and I have always been using qcow2
as the image format for the disks...
I can still try with other image formats, though.
Guido
next prev parent reply other threads:[~2012-10-17 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 16:33 I/O errors in guest OS after repeated migration Guido Winkelmann
2012-10-16 17:44 ` Brian Jackson
2012-10-17 11:54 ` Guido Winkelmann [this message]
2012-10-17 18:24 ` Brian Jackson
2012-10-17 15:45 ` Guido Winkelmann
2012-10-17 18:25 ` Brian Jackson
2012-10-18 15:50 ` Guido Winkelmann
2012-10-18 16:05 ` Avi Kivity
2012-10-19 12:55 ` Guido Winkelmann
2012-10-29 11:29 ` Stefan Hajnoczi
2012-11-06 11:07 ` Guido Winkelmann
2012-11-08 8:23 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1510481.QTrF9SkzaV@pc10 \
--to=guido-kvml@thisisnotatest.de \
--cc=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.