public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Charles Duffy <Charles_Duffy@messageone.com>
Cc: libvir-list@redhat.com, kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: [libvirt] qemu-kvm-0.10.5, kvm-kmod-2.6.30,   libvirt-0.6.4 - save/restore still unreliable
Date: Fri, 12 Jun 2009 22:10:43 +0200	[thread overview]
Message-ID: <20090612201043.GA4852@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <h0trsn$geh$1@ger.gmane.org>

Hello Charlie,
thanks for the reply
> That should work fine. Your "..." sets up the drives, memory amount,  
> etc., right? Why do you say it "doesn't seem to be the proper way"? What  
> fails?
sure, I'm (hopefully) providing all the needed arguments.

>
> BTW, you might also do this: -incoming 'exec:cat .../img.vm', avoiding  
> the need to pipe through stdin.
yup, I tried that, but it allways ends with following:

cat  /home/LVS/hibernated/vmroo55.vm | /usr/bin/qemu-kvm -M pc -m 768 -smp 2 -name vmroo55 -uuid 987e7a85-0e15-11de-a522-00304892f672 -monitor pty -boot c -kernel /home/LVS/boot/vmlinuz-2.6.29lb.00_01_PRE14-x86_64 -initrd /home/LVS/boot/kvm-initrd-2.6.29lb.00_01_PRE14-x86_64.cpio.gz -append "root=/dev/sda ro vmhostname=vmroo55" -drive file=/dev/vgshared/vmroo55-1,if=ide,index=0,boot=on -drive file=/dev/vgshared/vmroo55-2,if=ide,index=1 -drive file=/dev/vgshared/vmroo55-3,if=virtio,index=0 -net nic,macaddr=00:16:3e:18:37:00,vlan=0,model=virtio -net tap,script=/etc/qemu-ifup.sh,vlan=0 -serial none -parallel none -usb -vnc0.0.0.0:24155 -incoming exec:cat

Executing /etc/qemu-ifup
Bringing up tap0 for bridged mode...
Adding tap0 to br0...
char device redirected to /dev/pts/7
qemu_popen: returning result of qemu_fopen_ops
load of migration failed
cat: write error: Broken pipe
/etc/qemu-ifdown: could not launch network script


using 
... -incoming exec:cat /home/...image.vm
seems to start the machine, but it seems to be stuck, even though I removed -S parameter.

>
> --
> Libvir-list mailing list
> Libvir-list@redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
>

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2009-06-12 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 14:01 [libvirt] qemu-kvm-0.10.5, kvm-kmod-2.6.30, libvirt-0.6.4 - save/restore still unreliable Nikola Ciprich
2009-06-12 15:23 ` Charles Duffy
2009-06-12 20:10   ` Nikola Ciprich [this message]
2009-06-12 20:17     ` Charles Duffy
2009-06-13  6:32       ` Nikola Ciprich
2009-06-14  9:26         ` Avi Kivity
     [not found]         ` <9E5B4A2291F9AD418AB1A2E89090064785B7EE@ausx3mpc124.aus.amer.dell.com>
2009-06-16 20:35           ` [libvirt] qemu-kvm-0.10.5, kvm-kmod-2.6.30, libvirt-0.6.4 -save/restore " Nikola Ciprich

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=20090612201043.GA4852@nik-comp.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=Charles_Duffy@messageone.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=nikola.ciprich@linuxbox.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox