kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: "kvm-devel@lists.sourceforge.net" <kvm@vger.kernel.org>
Subject: Re: mandrake-10 not able to boot on kvm-71-73
Date: Sat, 13 Sep 2008 12:54:16 +0300	[thread overview]
Message-ID: <48CB8DC8.8030100@qumranet.com> (raw)
In-Reply-To: <48BBC770.3090309@lfarkas.org>

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Farkas Levente wrote:
>>     
>>> ok this last one was my fault:-(
>>> but i retest is again.
>>> - kvm-74 with kmod-kvm-74 not working
>>> - kvm-71 with kmod-kvm-74 working
>>> any progress with this?
>>> anyone can test it with a simple minimal mandrake-10 install. after the
>>> install the system can't boot.
>>> yours.
>>>   
>>>       
>> Please provide a pointer to a test .iso image.
>>     
>
> ftp://carroll.aset.psu.edu/pub/linux/distributions/mandrivalinux/old/10.0/i586/
> or the isos:
> ftp://carroll.aset.psu.edu/pub/linux/distributions/mandrivalinux/official/iso/10.0/i586/
>   

The ISO for the first CD is corrupted; I downloaded it twice, yet I get
the wrong md5sum (and installation fails on some bad package).

Do you have an alternate location?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2008-09-13  9:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 14:43 mandrake-10 not able to boot on kvm-71-73 Farkas Levente
2008-08-25 16:02 ` Avi Kivity
2008-08-25 16:23   ` Farkas Levente
2008-08-25 16:36     ` Avi Kivity
2008-08-25 16:59       ` Farkas Levente
2008-08-26  7:06         ` Henrik Holst
2008-09-01  9:20           ` Farkas Levente
2008-09-01  9:28             ` Avi Kivity
2008-09-01 10:44               ` Farkas Levente
2008-09-10 17:13                 ` Farkas Levente
2008-09-13  9:54                 ` Avi Kivity [this message]
2008-09-13 12:57                   ` Farkas Levente
2008-09-13 14:42                     ` Avi Kivity
2008-09-15 15:12                       ` Farkas Levente
2008-09-16 22:36                         ` Avi Kivity
     [not found]                           ` <48DBA59C.7090907@lfarkas.org>
     [not found]                             ` <48E4B27D.10706@lfarkas.org>
2008-10-02 11:46                               ` Avi Kivity
2008-10-02 14:08                                 ` Farkas Levente
2008-10-02 14:27                                   ` Avi Kivity
2008-10-02 17:06                                     ` Farkas Levente
     [not found]                                     ` <48E4FC9A.4060701@lfarkas.org>
2008-10-05 10:16                                       ` Farkas Levente
2008-10-05 10:36                                         ` Avi Kivity
2008-10-05 11:04                                           ` Farkas Levente
2008-10-05 11:06                                             ` Avi Kivity
2008-10-07 15:22                                               ` Farkas Levente
2008-10-15 12:19                                     ` Farkas Levente

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=48CB8DC8.8030100@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=lfarkas@lfarkas.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;
as well as URLs for NNTP newsgroup(s).