similar to: Re: [virt-tools-list] Statically compiling virt-rescue ?

I've added a few patches upstream to make static linking work, and it is [surprisingly] possible to get it to work. You'll have to check out libguestfs from git. Read the README file very carefully, and get familiar with building from source. This is easier on a recent Fedora machine or VM. Once you are comfortable building libguestfs from source, configure it like this: ./configure

To allow easier downstream tweaks to the virt-rescue welcome message, just output the content of the /etc/issue file in the appliance. Thus, a new extras.tar.gz file appeared in supermin.d containing the etc/issue file and future tweaks like this one. --- appliance/Makefile.am | 11 +++++++++++ appliance/init | 11 ++--------- appliance/issue | 9 +++++++++ 3 files changed, 22

Thank You for your reply. >What was the output of the 'virt-rescue --suggest -d XYZ'? Inspecting the virtual machine or disk image ... This disk contains one or more operating systems. You can use these mount commands in virt-rescue (at the ><rescue> prompt) to mount the filesystems. # /dev/sda1 is the root of a linux operating system # type: linux, distro: ubuntu, version:

This is a repost of a previously posted set. It's been updated following review comments. [PATCH 1/4] Add a core_pattern debug command Added missing return statements. [PATCH 2/4] Call sync after guestfsd exits Remove redundant sleep 1; sync [PATCH 3/4] Shut down the appliance cleanly [PATCH 4/4] Ignore launch() error in virt-rescue These were previously 2 patches. They are otherwise

This set of patches fixes virt-rescue rather cleanly. In particular the problems with handling ^C are completely fixed. Work still to be done before this can go upstream: - Shutdown doesn't work properly if you exit the shell. At the moment to exit you must do 'reboot -f'. Future improvements: - An escape sequence and escape commands that could be handled by virt-rescue,

Hello, I am trying to run this command virt-rescue --suggest -d XYZ virt-rescue --network -d XYZ the prompt is looking like this: I have no name!@(none): now I mounted the root partition suggested by virt-rescue to /sysroot then chroot /sysroot after that I tried to rebuild an initrd.img with the following command update-initramfs -c -k 3.2.0-58-generic But it failed with following error:

This fixes the main issues in virt-rescue and is usable. There are some enhancements which could be made (in follow up work): - An escape sequence and escape commands that could be handled by virt-rescue, eg. to shut down the appliance, mount or unmount filesystems. - `virt-rescue -i' could be implemented cleanly by performing the right API calls before handing control to the

Should 'virt-rescue -a some.img --ro' tell qemu/kvm that some.img is supposed to be read-only in the guest? I have not looked at the code yet, perhaps --ro has a meaning only when attaching to a live guest. I was expecting that all write access to some.img is denied in the rescue shell. Olaf

--autosysroot option uses suggestions to user on how to mount filesystems and change root suggested by --suggest option in virt-rescue. Commands are passed on kernel command line in format guestfs_command=command;. Command ends with a semicolon and there can be multiple commands specified. These are executed just before bash starts. On successfull run user is presented directly with bash in

Use %d to parse them as int (since the variables for them as int) instead of %u, even if they both need to be at least > 0. --smp was already checked to be >= 1 while --memsize not, so check that the specified memory size is not < 128 (which is semi-arbitrary, but enough as a minimum threshold). --- rescue/rescue.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)

Since /dev and other directories contain sub-mounts, suggest using --rbind instead of --bind. This also allows us to remove the /dev/pts line. --- rescue/rescue.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/rescue/rescue.c b/rescue/rescue.c index 53afdae..9a7c988 100644 --- a/rescue/rescue.c +++ b/rescue/rescue.c @@ -453,10 +453,9 @@ do_suggestion (struct drv

Hi, I tried to rewrite virt-rescue from C to OCaml. Goals were feature parity with C implementation, smaller codebase and hopefully better maintainability. I still don't know if I've covered everything right. So, please check it out. PS: my git send-email seems to be broken, so I'm sending it from thunderbird Thanks! maros

--autosysroot option uses suggestions to user on how to mount filesystems and change root suggested by --suggest option in virt-rescue. Commands are passed on kernel command line in format guestfs_command=command;. Command ends with a semicolon and there can be multiple commands specified. These are executed just before bash starts. On successfull run user is presented directly with bash in

Inspired by something Glauber asked me about today, I made a very simple pair of patches which add a 'virt-rescue' command to libguestfs. This uses the appliance as a "rescue appliance", so people can boot into a disk image and repair it in an unstructured, interactive way. (Specifically, Glauber's question was how to run fsck interactively - with this patch you could do

In data mercoledì 1 giugno 2016 02:04:33, Maros Zatko ha scritto: > --autosysroot option uses suggestions to user on how to mount filesystems > and change root suggested by --suggest option in virt-rescue. IMHO it should be called -i, like in the other tools, as what --autosysroot does is basically the same. > Commands are passed on kernel command line in format >

In order to keep only 3 kernel images on a CentOS 7 I edited /etc/yum.conf and I put installonly_limit=3 This parameter works for standard kernel images, but does not work for rescue images: $ ls -al /boot/vmlinuz* -rwxr-xr-x 1 root root 5027376 May 13 20:46 /boot/vmlinuz-0-rescue-2554e2ffad84452bb07401bed0a61089 -rwxr-xr-x 1 root root 3084288 Jun 27 06:42

On 03/13/2015 12:21 PM, Richard W.M. Jones wrote: > So what's happening is that /etc/resolv.conf in the appliance never > gets created. > Is the /dev/tcp test by IP evidence that the problem goes deeper than name resolution? > Run `./run virt-rescue --network --scratch' on the Ubuntu host and see if: > > - either dhclient or dhcpcd exists in the appliance > >

This way it will not try to free uninitialized memory when going out of scope, and the inspector mode is not enabled. Fixes commit 3637c42f4e521eb647d7dfae7f48eb1689d0af54. --- rescue/escape.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rescue/escape.c b/rescue/escape.c index 3bb69578b..a6af99ae1 100644 --- a/rescue/escape.c +++ b/rescue/escape.c @@ -236,7 +236,7 @@

Depends on the previous 5 patches that modified virt-rescue to work without direct mode: https://www.redhat.com/archives/libguestfs/2017-March/msg00017.html Rich.

Hi, I have been able to boot with pxe and load linux rescue, it loads loader and ask me lang, keyboard,load base from nfs, etc... then it ask me about mount chroot or skip, I just choose skip to go to shell. What I want is boot in rescue mode and get a shell directly without having to enter lang, keyboard, nfs ip and dir, skip, etc... once booted on shell I want it automatically run a script