public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: qemu-kvm-0.14.x regression - windows 2K8 R2 stopped booting
Date: Thu, 26 May 2011 13:50:35 +0200	[thread overview]
Message-ID: <20110526115035.GC2172@nik-comp.lan> (raw)
In-Reply-To: <20110526102237.GK29458@redhat.com>

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

OK, I tried copying the whole image to my test box running 0.14.0 again and it crashes with exactly the same BSOD!
So now I have the test environment to play with...
What should I check/try now?
n.
PS: I'm not sure what You mean by permissions, but I'm using LVM partitions and qemu-kvm is started by root user anyways..

On Thu, May 26, 2011 at 01:22:37PM +0300, Gleb Natapov wrote:
> On Thu, May 26, 2011 at 12:20:56PM +0200, Nikola Ciprich wrote:
> > > You can make a copy from your production image, install 0.14 version in
> > > different place from 0.13 and experiment.
> > yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon.
> Then check image file permission please.
> 
> --
> 			Gleb.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-05-26 11:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  9:59 qemu-kvm-0.14.x regression - windows 2K8 R2 stopped booting Nikola Ciprich
2011-05-26 10:05 ` Gleb Natapov
2011-05-26 10:20   ` Nikola Ciprich
2011-05-26 10:22     ` Gleb Natapov
2011-05-26 11:50       ` Nikola Ciprich [this message]
2011-05-26 11:54         ` Gleb Natapov
2011-05-26 12:03           ` Nikola Ciprich
2011-05-26 12:13             ` Gleb Natapov
2011-05-26 12:30               ` Nikola Ciprich
2011-05-26 12:32                 ` Gleb Natapov
2011-05-26 12:46                   ` Nikola Ciprich
2011-05-26 12:49                     ` Gleb Natapov
2011-05-26 12:56                       ` Nikola Ciprich
2011-05-26 13:08                         ` Gleb Natapov
2011-05-26 13:15                           ` Nikola Ciprich
2011-05-26 13:27                             ` Gleb Natapov
2011-05-26 13:32                               ` Nikola Ciprich
2011-05-26 14:57                                 ` Gleb Natapov
2011-05-26 18:37                                   ` Nikola Ciprich
2011-05-27  8:53                         ` Avi Kivity
2011-05-27  9:05                           ` Nikola Ciprich
2011-06-09  8:36                             ` Avi Kivity
2011-06-15  5:26                               ` Nikola Ciprich
2011-07-03 18:35                                 ` Nikola Ciprich

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=20110526115035.GC2172@nik-comp.lan \
    --to=nikola.ciprich@linuxbox.cz \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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