From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60310) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bItvY-0002AY-0o for qemu-devel@nongnu.org; Fri, 01 Jul 2016 04:35:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bItvT-0003dg-QN for qemu-devel@nongnu.org; Fri, 01 Jul 2016 04:35:55 -0400 Received: from indium.canonical.com ([91.189.90.7]:53092) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bItvT-0003d9-HS for qemu-devel@nongnu.org; Fri, 01 Jul 2016 04:35:51 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bItvS-0008Ts-3b for ; Fri, 01 Jul 2016 08:35:50 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 4A9912E80D1 for ; Fri, 1 Jul 2016 08:35:49 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 01 Jul 2016 08:27:28 -0000 From: "Dr. David Alan Gilbert" Reply-To: Bug 1594239 <1594239@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160620032122.2878.51451.malonedeb@chaenomeles.canonical.com> Message-Id: <20160701082728.14997.86997.malone@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi Tom, Yeh it's just vmstate_register_with_alias_id printing vmsd->name at entry, and then after the char *id =3D .... printing that as well (that's what I = labelled as the dev/id case). Then just before the assert I was printing the se->compat and se->instance_= id values. I noticed this bug because one of our test team had hit the same assert a few weeks back on x86, but it was on a truly bizarre setup (~50 nested PCIe bridges) so I knew where to look for it. I think the idea is that if you have a se->compat string then it had better be unique (that is instance_id =3D=3D 0); and the compat string is formed by concatenation of the qdev path and the name of this device. Then we have '0.0.0' as the name of this scsi device (i.e. local to this SCSI adapter) but no path that gives a unique string for the adapter like we do on the x86. Dave -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1594239 Title: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error Status in QEMU: Confirmed Bug description: Description =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Using virt-manager to create a VM in Aarch64, Ubuntu 16.04. Add scsi disk to the VM. After add four or more scsi disks, start the VM = and will got Qemu error. Steps to reproduce =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1.Use virt-manager to create a VM. 2.After the VM is started, add scsi disk to the VM. They will be allocate= d to "sdb,sdc,sdd....." . 3.If we got a disk name > sdg, virt-manager will also assign a virtio-scs= i controller for this disk.And the VM will be shutdown. 4.Start the VM, will see the error log. = Expected result =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Start the vm smoothly.The added disks can work. Actual result =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Got the error: starting domain: internal error: process exited while connecting to monit= or: qemu-system-aarch64: /build/qemu-zxCwKP/qemu-2.5+dfsg/migration/savevm.= c:620: vmstate_register_with_alias_id: Assertion `!se->compat || se->instan= ce_id =3D=3D 0' failed. details=3DTraceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_= wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 126, in tm= pcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, i= n newfn ret =3D fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1402, in sta= rtup self._backend.create() File "/usr/local/lib/python2.7/dist-packages/libvirt.py", line 1035, in= create if ret =3D=3D -1: raise libvirtError ('virDomainCreate() failed', dom= =3Dself) libvirtError: internal error: process exited while connecting to monitor:= qemu-system-aarch64: /build/qemu-zxCwKP/qemu-2.5+dfsg/migration/savevm.c:6= 20: vmstate_register_with_alias_id: Assertion `!se->compat || se->instance_= id =3D=3D 0' failed. = Environment =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. virt-manager version is 1.3.2 2. Which hypervisor did you use? Libvirt+KVM $ kvm --version QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.1), Copyrigh= t (c) 2003-2008 Fabrice Bellard $ libvirtd --version libvirtd (libvirt) 1.3.1 3. Which storage type did you use? In the host file system,all in one physics machine. stack@u202154:/opt/stack/nova$ df -hl Filesystem Size Used Avail Use% Mounted on udev 7.8G 0 7.8G 0% /dev tmpfs 1.6G 61M 1.6G 4% /run /dev/sda2 917G 41G 830G 5% / tmpfs 7.9G 0 7.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/sda1 511M 888K 511M 1% /boot/efi cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 1.6G 0 1.6G 0% /run/user/1002 tmpfs 1.6G 0 1.6G 0% /run/user/1000 tmpfs 1.6G 0 1.6G 0% /run/user/0 4. Environment information: Architecture : AARCH64 OS: Ubuntu 16.04 The Qemu commmand of libvirt is : 2016-06-20 02:39:46.561+0000: starting up libvirt version: 1.3.1, package= : 1ubuntu10 (William Grant Fri, 15 Apr 2016 12:08:21 +1= 000), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.1), hostname: u202154 LC_ALL=3DC PATH=3D/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin= :/bin QEMU_AUDIO_DRV=3Dnone /usr/bin/kvm -name cent7 -S -machine virt,accel= =3Dkvm,usb=3Doff -cpu host -drive file=3D/usr/share/edk2.git/aarch64/QEMU_E= FI-pflash.raw,if=3Dpflash,format=3Draw,unit=3D0,readonly=3Don -drive file= =3D/var/lib/libvirt/qemu/nvram/cent7_VARS.fd,if=3Dpflash,format=3Draw,unit= =3D1 -m 2048 -realtime mlock=3Doff -smp 2,sockets=3D2,cores=3D1,threads=3D1= -uuid d5462bb6-159e-4dbd-9266-bf8c07fa1695 -nographic -no-user-config -nod= efaults -chardev socket,id=3Dcharmonitor,path=3D/var/lib/libvirt/qemu/domai= n-cent7/monitor.sock,server,nowait -mon chardev=3Dcharmonitor,id=3Dmonitor,= mode=3Dcontrol -rtc base=3Dutc -no-shutdown -boot strict=3Don -device i8280= 1b11-bridge,id=3Dpci.1,bus=3Dpcie.0,addr=3D0x1 -device pci-bridge,chassis_n= r=3D2,id=3Dpci.2,bus=3Dpci.1,addr=3D0x1 -device virtio-scsi-device,id=3Dscs= i0 -device lsi,id=3Dscsi1 -device lsi,id=3Dscsi2 -device virtio-scsi-device= ,id=3Dscsi3 -usb -drive file=3D/var/lib/libvirt/images/cent7-2.img,format= =3Dqcow2,if=3Dnone,id=3Ddrive-scsi0-0-0-0 -device scsi-hd,bus=3Dscsi0.0,cha= nnel=3D0,scsi-id=3D0,lun=3D0,drive=3Ddrive-scsi0-0-0-0,id=3Dscsi0-0-0-0,boo= tindex=3D1 -drive if=3Dnone,id=3Ddrive-scsi0-0-0-1,readonly=3Don -device sc= si-cd,bus=3Dscsi0.0,channel=3D0,scsi-id=3D0,lun=3D1,drive=3Ddrive-scsi0-0-0= -1,id=3Dscsi0-0-0-1 -drive file=3D/var/lib/libvirt/images/cent7-10.img,form= at=3Dqcow2,if=3Dnone,id=3Ddrive-scsi0-0-0-2 -device scsi-hd,bus=3Dscsi0.0,c= hannel=3D0,scsi-id=3D0,lun=3D2,drive=3Ddrive-scsi0-0-0-2,id=3Dscsi0-0-0-2 -= drive file=3D/var/lib/libvirt/images/cent7-11.img,format=3Dqcow2,if=3Dnone,= id=3Ddrive-scsi0-0-0-3 -device scsi-hd,bus=3Dscsi0.0,channel=3D0,scsi-id=3D= 0,lun=3D3,drive=3Ddrive-scsi0-0-0-3,id=3Dscsi0-0-0-3 -drive file=3D/var/lib= /libvirt/images/cent7-13.img,format=3Dqcow2,if=3Dnone,id=3Ddrive-scsi3-0-0-= 0 -device scsi-hd,bus=3Dscsi3.0,channel=3D0,scsi-id=3D0,lun=3D0,drive=3Ddri= ve-scsi3-0-0-0,id=3Dscsi3-0-0-0 -netdev tap,fd=3D33,id=3Dhostnet0,vhost=3Do= n,vhostfd=3D35 -device virtio-net-device,netdev=3Dhostnet0,id=3Dnet0,mac=3D= 52:54:00:a1:6e:75 -serial pty -msg timestamp=3Don Domain id=3D11 is tainted: host-cpu The libvirt xml is: cent7 d5462bb6-159e-4dbd-9266-bf8c07fa1695 2097152 2097152 2 hvm /usr/share/edk2.git/aarch64/= QEMU_EFI-pflash.raw /var/lib/libvirt/qemu/nvram/cent7_VARS.fd destroy restart restart /usr/bin/kvm
To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1594239/+subscriptions