Project

General

Profile

Actions
Copy link

Feature #2777

closed

LDV kmanager should support kernels provided as .tar and as sources

Added by Evgeny Novikov about 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeny Novikov
Category:
Infrastructure
Start date:
04/23/2012
Due date:
% Done:

0%

Estimated time:
Published in build:
015e52e

Description

At the moment it supports just kernels packed into archives like bzip2.

Actions
Copy link
 #1

Updated by Evgeny Novikov about 12 years ago

  • Status changed from New to Open
  • Assignee changed from Vadim Mutilin to Evgeny Novikov
  • Priority changed from Normal to High

I'll try to implement this.

Actions
Copy link
 #2

Updated by Evgeny Novikov about 12 years ago

  • Status changed from Open to Resolved
  • Published in build set to 46940ee

46940ee commit of our master branch implements it.

Actions
Copy link
 #3

Updated by Evgeny Novikov about 12 years ago

  • Published in build changed from 46940ee to 015e52e

Implementation is fixed in commit 015e52e, since we need to copy kernel sources with option '-a' when we use rsync. Note that rsync is used since we need to skip .git directory if so when we are coping files. Otherwise it will take much more time and disc space.

Actions
Copy link
 #4

Updated by Evgeny Novikov almost 12 years ago

  • Status changed from Resolved to Closed

Nothing bad happened, so close it.

Actions
Copy link
 #5

Updated by Evgeny Novikov almost 12 years ago

  • Status changed from Closed to Open

By some reason repeated launches with the same kernel provided as sources don't work.

Actions
Copy link
 #6

Updated by Evgeny Novikov almost 12 years ago

  • Status changed from Open to Closed

Evgeny Novikov wrote:

By some reason repeated launches with the same kernel provided as sources don't work.

Actually, this isn't the case. Just when one use kernel sources that differs from the previously used ones (say, when one checkouted another revision), then ldv-kmanager points out this:

ldv: NORMAL: ldv start.
ldv-kmanager: ERROR: Kernel description with name "linux-stable" already exists. Try to select another name.
ldv: ERROR: kmanager failed.
make: *** [tags/current/env.linux-stable] Error 1

And this should be done indeed. But I'd like our most high-level command-line interface (ldv-manager) to have an option that allows to remove information (if so) on the kernel to be used in verification process at the beginning. So I'm going to create a separate issue with lower priority.
Also sometimes it'll be very useful to have an ability to keep the whole git repository of the Linux kernel set upped by ldv-tools inside envs directory and just checkout some required revision there (say, v3.4, v3.4-rc3, abracadabra, etc.). But this isn't a common workflow nevertheless, so we can don't focus on this.

Actions
Copy link

Also available in: Atom PDF