From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: one out of four existing kvm guest's not starting after system upgrade Date: Tue, 28 Feb 2012 10:13:25 +0100 Message-ID: <4F4C9AB5.4090904@web.de> References: <201202172149.36904.thomas@fjellstrom.ca> <4F3F67A4.5050309@web.de> <201202180257.48987.thomas@fjellstrom.ca> <201202191313.58710.thomas@fjellstrom.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3D670CF4C875B0515E1654F3" Cc: KVM To: thomas@fjellstrom.ca Return-path: Received: from fmmailgate05.web.de ([217.72.192.243]:35940 "EHLO fmmailgate05.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752867Ab2B1JNe (ORCPT ); Tue, 28 Feb 2012 04:13:34 -0500 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate05.web.de (Postfix) with ESMTP id A83DF6A7E6E6 for ; Tue, 28 Feb 2012 10:13:32 +0100 (CET) In-Reply-To: <201202191313.58710.thomas@fjellstrom.ca> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3D670CF4C875B0515E1654F3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 2012-02-19 21:13, Thomas Fjellstrom wrote: > I'm pretty much stumped on this. So I decided to try re-creating the vm= =20 > through virt-manager. Its up and running now. The only to major differe= nces I=20 > can see in the old and new config is the machine (-M pc-0.12 vs -M pc-1= =2E0)=20 > parameter, and the uuid. The rest of the parameters I played with a lot= trying=20 > to get it to work by starting up the vm manually from the cli. I can't = really=20 > see how those two changes would do much of anything considering the oth= er=20 > three VM's still are configured to use -M pc-0.12, and they work fine. >=20 To pick up this topic again: The trace contains no clear indication what is going on. Now I'm trying to understand what works and what not. Please correct / extend as required: - qemu-kvm-0.12 problematic-vm.img [OK] - qemu-kvm-1.0 -M pc-0.12 problematic-vm.img [HANG] - qemu-kvm-1.0 -M pc-1.0 problematic-vm.img [OK] In all cases, the image is the same, never reinstalled? BTW, what is your guest again? What is your VM configuration? That IOCTL error messages you find in the kernel log likely relate to direct cdrom access from the qemu process. Do you pass a host drive throu= gh? Jan --------------enig3D670CF4C875B0515E1654F3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9MmrgACgkQitSsb3rl5xSYKgCgueqIye3IkvYOFKVy21Wa8XGa N4oAni/N0kkUsVH12jXnFwyePz6yZnMd =VqgH -----END PGP SIGNATURE----- --------------enig3D670CF4C875B0515E1654F3--