public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: thomas@fjellstrom.ca
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: one out of four existing kvm guest's not starting after system upgrade
Date: Tue, 28 Feb 2012 10:13:25 +0100	[thread overview]
Message-ID: <4F4C9AB5.4090904@web.de> (raw)
In-Reply-To: <201202191313.58710.thomas@fjellstrom.ca>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

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 
> through virt-manager. Its up and running now. The only to major differences I 
> can see in the old and new config is the machine (-M pc-0.12 vs -M pc-1.0) 
> parameter, and the uuid. The rest of the parameters I played with a lot trying 
> to get it to work by starting up the vm manually from the cli. I can't really 
> see how those two changes would do much of anything considering the other 
> three VM's still are configured to use -M pc-0.12, and they work fine.
> 

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 through?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2012-02-28  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  4:49 one out of four existing kvm guest's not starting after system upgrade Thomas Fjellstrom
2012-02-18  8:39 ` Jan Kiszka
2012-02-18  8:50   ` Thomas Fjellstrom
2012-02-18  8:53     ` Thomas Fjellstrom
2012-02-18  8:56     ` Jan Kiszka
2012-02-18  9:00       ` Thomas Fjellstrom
2012-02-18  9:57       ` Thomas Fjellstrom
2012-02-19 20:13         ` Thomas Fjellstrom
2012-02-22 17:58           ` Jan Kiszka
2012-02-28  9:13           ` Jan Kiszka [this message]
2012-02-28 17:32             ` Thomas Fjellstrom

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=4F4C9AB5.4090904@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=thomas@fjellstrom.ca \
    /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