This is the log I got doing the restore. It's says that it coun't get the image, but the image is ok, because I can startup the guest.
Neither I can migrate the guest, so I suppose I've a problem in my configuration.
Thank you very much in advance.
Marcela.
2011/4/5 Michal Novotny <minovotn@xxxxxxxxxx>
Hi Marcela,
is any other guest on the host that cannot restore this VM working fine ?
You could also try running the:
*/# LIBVIRT_DEBUG=1 virsh restore sv-chubut-2011-04-04-17:38 2>
virsh-restore.log
/*command which would enable the libvirt logging and output the debug
log into the virsh-restore.log file. This file could be sent to the list
for analysis what's wrong.
Thanks,
Michal
> <mailto:berrange@xxxxxxxxxx>>
On 04/05/2011 11:57 AM, Marcela Castro León wrote:
> Hello Daniel
> Thank you for all your information, but I still didn't solve the
> problem. I tried the option you mention, with two differents guest
> into two differents host, but all the cases I've got:
>
> */virsh # restore sv-chubut-2011-04-04-17:38/*
> */error: Failed to restore domain from sv-chubut-2011-04-04-17:38/*
> */error: monitor socket did not show up.: Connection refused/*
>
> I cannot get any useful information (at least form me) on the log you
> mention.
> I'd appreciate a lot a new suggestion.
> Thanks
> Marcela
>
>
>
>
> 2011/4/4 Daniel P. Berrange <berrange@xxxxxxxxxx
> <http://search.cpan.org/%7Edanberr/> :|>
> On Sun, Apr 03, 2011 at 10:43:45AM +0200, Marcela Castro León wrote:
> > Hello:
> > I need to know if I can use the restore operation (virsh o the
> equivalent in
> > libvirt) to recover a previous state of a guest, but recovered
> previously in
> > another host.
> > I did a test, but I got an error:
> >
> > The exactly sequence using virsh I testes is:
> > On [HOST SOURCE]: Using virsh
> > 1) save [domain] [file]
> > 2) restore file
> > 3) destroy [domain]
> >
> > On [HOST SOURCE] using ubuntu sh
> > 4) cp [guest.img] [guest.xml] [file] to HOST2
> >
> > On [HOST TARGET] using virsh
> > 5) define [guest.xml] (using image on destination in HOST2)
> > 6) restore [file]
>
> As a general rule you should only ever 'restore' from a
> file *once*. This is because after the first restore
> operation, the guest may have made writes to its disk.
> Restoring a second time the guest OS will likely have
> an inconsistent view of the disk & will cause filesystem
> corruption.
>
> If you want to be able to restore from a saved image
> multiple times, you need to also take a snapshot of
> the disk image at the same time, and restore that
> snapshot when restoring the memory image.
>
>
> That aside, saving on one host & restoring on a
> different host is fine. So if you leave out steps
> 2+3 in your example above, then your data would
> still be safe.
>
> > The restore troughs the following message:
> > *virsh # restore sv-chubut-2011-04-01-09:58
> > error: Failed to restore domain from sv-chubut-2011-04-01-09:58
> > error: monitor socket did not show up.: Connection refused*
>
> There is probably some configuration difference on your 2nd host
> that prevented the VM from starting up. If you're lucky the file
> /var/log/libvirt/qemu/$NAME.log will tell you more
>
> Daniel
> --
> |: http://berrange.com -o-
> http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org -o-
> http://virt-manager.org :|
> |: http://autobuild.org -o-
> http://search.cpan.org/~danberr/
> --
> libvir-list mailing list
> libvir-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/libvir-list
--
Michal Novotny <minovotn@xxxxxxxxxx>, RHCE
Virtualization Team (xen userspace), Red Hat
6:28:17.439: debug : virInitialize:336 : register drivers 16:28:17.439: debug : virRegisterDriver:837 : registering Test as driver 0 16:28:17.439: debug : virRegisterNetworkDriver:675 : registering Test as network driver 0 16:28:17.439: debug : virRegisterInterfaceDriver:706 : registering Test as interface driver 0 16:28:17.439: debug : virRegisterStorageDriver:737 : registering Test as storage driver 0 16:28:17.439: debug : virRegisterDeviceMonitor:768 : registering Test as device driver 0 16:28:17.439: debug : virRegisterSecretDriver:799 : registering Test as secret driver 0 16:28:17.439: debug : virRegisterDriver:837 : registering Xen as driver 1 16:28:17.439: debug : virRegisterDriver:837 : registering OPENVZ as driver 2 16:28:17.439: debug : vboxRegister:109 : VBoxCGlueInit failed, using dummy driver 16:28:17.440: debug : virRegisterDriver:837 : registering VBOX as driver 3 16:28:17.440: debug : virRegisterNetworkDriver:675 : registering VBOX as network driver 1 16:28:17.440: debug : virRegisterStorageDriver:737 : registering VBOX as storage driver 1 16:28:17.440: debug : virRegisterDriver:837 : registering remote as driver 4 16:28:17.440: debug : virRegisterNetworkDriver:675 : registering remote as network driver 2 16:28:17.440: debug : virRegisterInterfaceDriver:706 : registering remote as interface driver 1 16:28:17.440: debug : virRegisterStorageDriver:737 : registering remote as storage driver 2 16:28:17.440: debug : virRegisterDeviceMonitor:768 : registering remote as device driver 1 16:28:17.440: debug : virRegisterSecretDriver:799 : registering remote as secret driver 1 16:28:17.440: debug : virConnectOpenAuth:1337 : name=qemu+ssh://rionegro/system, auth=0x7f3136287b80, flags=0 16:28:17.440: debug : do_open:1106 : name "qemu+ssh://rionegro/system" to URI components: scheme qemu+ssh opaque (null) authority (null) server rionegro user (null) port 0 path /system 16:28:17.440: debug : do_open:1116 : trying driver 0 (Test) ... 16:28:17.440: debug : do_open:1122 : driver 0 Test returned DECLINED 16:28:17.440: debug : do_open:1116 : trying driver 1 (Xen) ... 16:28:17.440: debug : do_open:1122 : driver 1 Xen returned DECLINED 16:28:17.440: debug : do_open:1116 : trying driver 2 (OPENVZ) ... 16:28:17.440: debug : do_open:1122 : driver 2 OPENVZ returned DECLINED 16:28:17.440: debug : do_open:1116 : trying driver 3 (VBOX) ... 16:28:17.440: debug : do_open:1122 : driver 3 VBOX returned DECLINED 16:28:17.440: debug : do_open:1116 : trying driver 4 (remote) ... 16:28:17.440: debug : doRemoteOpen:564 : proceeding with name = qemu:///system 16:28:17.440: debug : virExecWithHook:620 : ssh rionegro nc -q 2>&1 | grep -q 'requires an argument';if [ $? -eq 0 ] ; then CMD='-q 0';else CMD='';fi;nc $CMD -U /var/run/libvirt/libvirt-sock 16:28:17.440: debug : remoteIO:8455 : Do proc=66 serial=0 length=28 wait=(nil) 16:28:17.440: debug : remoteIO:8517 : We have the buck 66 0x7f31364da010 0x7f31364da010 16:28:19.405: debug : remoteIODecodeMessageLength:7939 : Got length, now need 64 total (60 more) 16:28:19.405: debug : remoteIOEventLoop:8381 : Giving up the buck 66 0x7f31364da010 (nil) 16:28:19.405: debug : remoteIO:8548 : All done with our call 66 (nil) 0x7f31364da010 16:28:19.405: debug : remoteIO:8455 : Do proc=1 serial=1 length=56 wait=(nil) 16:28:19.405: debug : remoteIO:8517 : We have the buck 1 0xd428b0 0xd428b0 16:28:19.406: debug : remoteIODecodeMessageLength:7939 : Got length, now need 56 total (52 more) 16:28:19.406: debug : remoteIOEventLoop:8381 : Giving up the buck 1 0xd428b0 (nil) 16:28:19.406: debug : remoteIO:8548 : All done with our call 1 (nil) 0xd428b0 16:28:19.406: debug : doRemoteOpen:917 : Adding Handler for remote events 16:28:19.406: debug : doRemoteOpen:924 : virEventAddHandle failed: No addHandleImpl defined. continuing without events. 16:28:19.406: debug : do_open:1122 : driver 4 remote returned SUCCESS 16:28:19.406: debug : do_open:1142 : network driver 0 Test returned DECLINED 16:28:19.406: debug : do_open:1142 : network driver 1 VBOX returned DECLINED 16:28:19.406: debug : do_open:1142 : network driver 2 remote returned SUCCESS 16:28:19.406: debug : do_open:1161 : interface driver 0 Test returned DECLINED 16:28:19.406: debug : do_open:1161 : interface driver 1 remote returned SUCCESS 16:28:19.406: debug : do_open:1181 : storage driver 0 Test returned DECLINED 16:28:19.406: debug : do_open:1181 : storage driver 1 VBOX returned DECLINED 16:28:19.406: debug : do_open:1181 : storage driver 2 remote returned SUCCESS 16:28:19.406: debug : do_open:1201 : node driver 0 Test returned DECLINED 16:28:19.406: debug : do_open:1201 : node driver 1 remote returned SUCCESS 16:28:19.406: debug : do_open:1228 : secret driver 0 Test returned DECLINED 16:28:19.406: debug : do_open:1228 : secret driver 1 remote returned SUCCESS 16:28:19.406: debug : virDomainRestore:2283 : conn=0xd3cbe0, from=sv-chubut-2011-04-04-17:38 16:28:19.406: debug : remoteIO:8455 : Do proc=54 serial=2 length=100 wait=(nil) 16:28:19.406: debug : remoteIO:8517 : We have the buck 54 0xd42450 0xd42450 16:28:19.407: debug : remoteIODecodeMessageLength:7939 : Got length, now need 172 total (168 more) 16:28:19.407: debug : remoteIOEventLoop:8381 : Giving up the buck 54 0xd42450 (nil) 16:28:19.407: debug : remoteIO:8548 : All done with our call 54 (nil) 0xd42450 error: Failed to restore domain from sv-chubut-2011-04-04-17:38 error: operation failed: cannot read domain image 16:28:19.407: debug : virConnectClose:1355 : conn=0xd3cbe0 16:28:19.407: debug : virUnrefConnect:259 : unref connection 0xd3cbe0 1 16:28:19.407: debug : remoteIO:8455 : Do proc=2 serial=3 length=28 wait=(nil) 16:28:19.407: debug : remoteIO:8517 : We have the buck 2 0xd42450 0xd42450 16:28:19.407: debug : remoteIODecodeMessageLength:7939 : Got length, now need 56 total (52 more) 16:28:19.407: debug : remoteIOEventLoop:8381 : Giving up the buck 2 0xd42450 (nil) 16:28:19.408: debug : remoteIO:8548 : All done with our call 2 (nil) 0xd42450 16:28:19.409: debug : virReleaseConnect:216 : release connection 0xd3cbe0
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list