[Top][All Lists]

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

Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs

From: ciprian . barbu
Subject: Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs
Date: Tue, 4 Apr 2017 11:07:53 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0


On 03.04.2017 21:52, Kashyap Chamarthy wrote:
On Fri, Mar 31, 2017 at 05:49:52PM +0000, Ciprian Barbu wrote:


We also use libvirt v1.3.4, which might be a problem, but at least we
want to understand if the commit in question introduced an obvious
problem or if it's all in the details.

A tangential question -- Just curious, your environment
seems...interesting: given you are using a bit old (but above the
MIN_LIBVIRT_VERSION for Nova, which is currently 1.2.1) libvirt version,
with *RC2* of QEMU 2.9 with Nova, and testing live migration.  Me
wonders if this some kind of a custom OpenStack environment, or an
official upstream release that you're simply testing with a newer
version of QEMU...

Here in the OPNFV ARMBAND Team, the primary goal is to make the OPNFV release work on ARM aarch64 servers. We have clusters of servers from different vendors, this on in particular is based on the ThunderX cn8890 SoC, which has received work for live migration from different sources. The problem is they have only been upstreamed in new versions of kernel and qemu. We tried to backport the changes to earlier versions, previously we were running kernel 4.4 and qemu v2.6.1.

But all of this is on top of Openstack Newton, and yes, we basically bumped the kernel, qemu and more recently libvirt too (v1.3.4). But as described earlier we were kind of forced into this situation.


Btw, the qemu command generated by libvirt is this one, sorry about that:

2017-03-31 17:40:10.956+0000: starting up libvirt version: 1.3.4, package: 
0+amos3~u16.04 (Enea Armband Devops Team <address@hidden> Fri, 13 Jan 2017 
02:06:05 +0100), qemu version: 2.8.50(Debian 1:2.9+amos2~u16.04), hostname: 
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm -name instance-00000076,debug-threads=on -S 
 -machine virt-2.8,accel=kvm,usb=off,gic-version=3 -cpu host -m 256 -realtime 
mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
2812f3c9-f564-499b-a8c7-e9e7ccf24143 -no-user-config -nodefaults -chardev 
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-no-shutdown -boot strict=on -kernel 
/var/lib/nova/instances/2812f3c9-f564-499b-a8c7-e9e7ccf24143/kernel -initrd 
/var/lib/nova/instances/2812f3c9-f564-499b-a8c7-e9e7ccf24143/ramdisk -append 
'root=/dev/vda1 rw rootwait console=tty0 console=ttyS0 console=ttyAMA0' -device 
i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1 -device 
pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x0 -usb -drive 
 -device virtio-blk-device,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1 
-netdev tap,fd=27,id=hostnet0 -device 
virtio-net-device,netdev=hostnet0,id=net0,mac=fa:16:3e:82:0a:2b -serial 
-serial pty -vnc -k en-us -device 
VGA,id=video0,vgamem_mb=16,bus=pci.2,addr=0x1 -device 
virtio-balloon-device,id=balloon0 -msg timestamp=on
Domain id=14 is tainted: high-privileges


reply via email to

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