qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work


From: Stefan Priebe
Subject: Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work
Date: Fri, 09 May 2014 22:08:12 +0200
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0


Am 09.05.2014 18:29, schrieb Dr. David Alan Gilbert:
* Stefan Priebe - Profihost AG (address@hidden) wrote:

Am 09.05.2014 um 15:41 schrieb "Dr. David Alan Gilbert" <address@hidden>:

* Stefan Priebe - Profihost AG (address@hidden) wrote:
Hello list,

i was trying to migrate older Qemu (1.5 and 1.7.2) to a machine running
Qemu 2.0.

I started the target machine with:

-machine type=pc-i440fx-1.5 / -machine type=pc-i440fx-1.7

I'd expect you to have to run with the same machine type on both sides.
I ran some simple virt-test migrate tests (just the basic one) and got
v1.5.3->v1.6.2
v1.5.3->v1.7.1
v1.5.3->v2.0.0-rc1
   working for most machine types, pc-i440fx-1.5 passed with all of those.
Note that's only the simplest test.

My test involved USB Controller virtio Network cards and rbd virtio-scsi drives.

That probably makes things more interesting :-) I'd start with the simplest
config you can find and add each one of those until it breaks.

Can you give me your simple start line so I could test if this works for me 
while adding some more arguments.

I've got a slightly hacked up libvirt, but I'm doing

   ./run -t qemu --machine-type=$MACTYPE -g Linux.JeOS.19.x86_64.i440fx 
--qemu-bin=$SRC --qemu-dst-bin=$DST --qemu_sandbox=off --tests 
migrate.default.tcp --disk-bus=ide

and looking at the logs we have:

/opt/qemu/v1.5.3/bin/qemu-system-x86_64 \
     -S  \
     -name 'virt-tests-vm1'  \
     -sandbox off  \
     -M pc-i440fx-1.5  \
     -nodefaults  \
     -vga std  \
     -chardev 
socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20140415-104517-rAfzfDef,server,nowait
 \
     -mon chardev=hmp_id_hmp1,mode=readline  \
     -chardev 
socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140415-104517-rAfzfDef,server,nowait
 \
     -device isa-serial,chardev=serial_id_serial0  \
     -chardev 
socket,id=seabioslog_id_20140415-104517-rAfzfDef,path=/tmp/seabios-20140415-104517-rAfzfDef,server,nowait
 \
     -device 
isa-debugcon,chardev=seabioslog_id_20140415-104517-rAfzfDef,iobase=0x402 \
     -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \
     -drive 
id=drive_image1,if=none,file=/home/dgilbert/virt-test/shared/data/images/jeos-19-64.qcow2
 \
     -device 
virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \
     -device 
virtio-net-pci,mac=9a:18:19:1a:1b:1c,id=idz0uWFP,vectors=4,netdev=idMwmdMc,bus=pci.0,addr=05
  \
     -netdev user,id=idMwmdMc,hostfwd=tcp::5000-:22  \
     -m 1024  \
     -smp 2,maxcpus=2,cores=1,threads=1,sockets=2  \
     -cpu 'SandyBridge' \
     -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
     -vnc :1  \
     -rtc base=utc,clock=host,driftfix=none  \
     -boot order=cdn,once=c,menu=off \
     -enable-kvm

Dave

OK biggest bummer it works fine with all freshly started VMs. No idea why.

So i'll try with paolos idea migrating old VMs.


Thanks!

Stefan


Dave
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK




reply via email to

[Prev in Thread] Current Thread [Next in Thread]