From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IkTWS-0007CW-T5
	for qemu-devel@nongnu.org; Tue, 23 Oct 2007 19:50:56 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IkTWR-0007Ah-8X
	for qemu-devel@nongnu.org; Tue, 23 Oct 2007 19:50:56 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IkTWR-0007AV-3E
	for qemu-devel@nongnu.org; Tue, 23 Oct 2007 19:50:55 -0400
Received: from fk-out-0910.google.com ([209.85.128.184])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <joe.ross@gmail.com>) id 1IkTWP-0000qr-VY
	for qemu-devel@nongnu.org; Tue, 23 Oct 2007 19:50:54 -0400
Received: by fk-out-0910.google.com with SMTP id 19so42280fkr
	for <qemu-devel@nongnu.org>; Tue, 23 Oct 2007 16:50:51 -0700 (PDT)
Message-ID: <925c62fc0710231650l53fe5d62jeb967ada0237eb97@mail.gmail.com>
Date: Tue, 23 Oct 2007 16:50:51 -0700
From: "Joe Ross" <joe.ross@gmail.com>
Subject: Re: [Qemu-devel] Strange behaviour
In-Reply-To: <200710221741.53069.christian.fontana@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3210_27003596.1193183451486"
References: <200710221741.53069.christian.fontana@gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

------=_Part_3210_27003596.1193183451486
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Do you think your problems are related to either of the following Ubuntu
bugs?

https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/144368
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/154960

Joe

On 10/22/07, Christian Fontana <christian.fontana@gmail.com> wrote:
>
> Hello.
>
> I'm using QEMU to expirement configuration, sw,... so I've create some
> images
> with different linux distros.
>
> Yesterday I've upgraded my Kubuntu from 7.04 to 7.10 and so also qemu was
> upgraded from 0.8.2 to 0.9.0. What I discovered is that some VM I've
> created
> (in particular suse) now are not working: they aren0t able to mount disk.
>
> What can I do? I tried the same disks on a not-upgraded kubuntu and
> everything
> works fine.
>
> Ciao
> Christian
>
>
>

------=_Part_3210_27003596.1193183451486
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Do you think your problems are related to either of the following Ubuntu bugs?<br><br><a href="https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/144368">https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/144368</a><br><a href="https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/154960">
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/154960</a><br><br>Joe<br><br><div><span class="gmail_quote">On 10/22/07, <b class="gmail_sendername">Christian Fontana</b> &lt;<a href="mailto:christian.fontana@gmail.com">
christian.fontana@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello.<br><br>I&#39;m using QEMU to expirement configuration, sw,... so I&#39;ve create some images
<br>with different linux distros.<br><br>Yesterday I&#39;ve upgraded my Kubuntu from 7.04 to 7.10 and so also qemu was<br>upgraded from 0.8.2 to 0.9.0. What I discovered is that some VM I&#39;ve created<br>(in particular suse) now are not working: they aren0t able to mount disk.
<br><br>What can I do? I tried the same disks on a not-upgraded kubuntu and everything<br>works fine.<br><br>Ciao<br>Christian<br><br><br></blockquote></div><br>

------=_Part_3210_27003596.1193183451486--