public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Araujo <maraujo-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: lista kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM behaves weird on AMD64
Date: Wed, 12 Sep 2007 13:03:58 +0200	[thread overview]
Message-ID: <46E7C79E.9070409@Nosys.net> (raw)
In-Reply-To: <46E7C3DD.8020003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity escribió:
> Miguel Araujo wrote:
>> Hello all,
>>
>> I have recently compiled kvm-36 in my Ubuntu Desktop 7.04 64 bits 
>> running 2.6.22. I can load the AMD module without problems. The issue 
>> started when I tried to install OpenBSD 4.1 on a Virtual Machine and 
>> It could not manage to write the MBR on disk. That should not happen. 
>> I also tried to install an Ubuntu desktop and server machines 32 bits 
>> and both of them got stuck on installation when configuring fdutils, 
>> I have no idea why this happens.
>>
>> Eventually I get to install a Debian netinstall with the most basic 
>> configuration and it worked. These are the tests I have made. By the 
>> way I checked that the Ubuntu machines did write in my 4G feisty.img 
>> file.
>>
>> Is anyone having problems with AMD64 and 2.6.22 kernels? Has anyone a 
>> hint about what could I do to get these machines running?
>>
>>   
>
> What was the last kvm version where this worked correctly?
>

I'm using two machines for testing KVM. In machine "A" KVM worked good. 
This is a Feisty 7.04 32 bits with 2.6.20-16 Ubuntu standard kernel  
with kvm installed apt way.
The machine "B" is the one I have mentioned before and It's using a 
2.6.22 manually compiled kernel. It has been able to install only Debian 
netinstall. I would like to know if there is some kind of issue with kvm 
and this kernel or with AMD64.

Regards,

          Miguel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-12 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 10:26 KVM behaves weird on AMD64 Miguel Araujo
     [not found] ` <46E7BEE3.8090203-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
2007-09-12 10:47   ` Avi Kivity
     [not found]     ` <46E7C3DD.8020003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 11:03       ` Miguel Araujo [this message]
     [not found]         ` <46E7C79E.9070409-l9cVusCFpiBeoWH0uzbU5w@public.gmane.org>
2007-09-12 11:14           ` Avi Kivity
     [not found]             ` <46E7CA21.9000201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 12:27               ` Miguel Araujo
2007-09-13 22:55 ` Tobias Brink
     [not found]   ` <87k5quyy3f.fsf-eMrnMapibgNxJOgadfisgdi2O/JbrIOy@public.gmane.org>
2007-09-30 10:59     ` Avi Kivity
2007-09-30 11:41       ` Tobias Brink
     [not found]         ` <87myv4tm6j.fsf-eMrnMapibgNxJOgadfisgdi2O/JbrIOy@public.gmane.org>
2007-10-01 11:48           ` Miguel Araujo

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=46E7C79E.9070409@Nosys.net \
    --to=maraujo-l9cvuscfpibeowh0uzbu5w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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