similar to: Use of qemu-kvm command line arguments in libguestfs (was: Re: Fwd: ...)

On Monday 02 December 2013 09:09:44 Richard W.M. Jones wrote: > On Mon, Dec 02, 2013 at 01:17:09AM +0100, Pino Toscano wrote: > > On Friday 29 November 2013 18:53:38 you wrote: > > > > > I'm marking options with NONE (not used at all), or M (used in > > > > > master) and/or RH7 (used in rhel-7.0). > > > > > > > > > > > *

The latter is a better way to disable the qemu display output as we need to, without enabling extra devices (which are disabled already, anyway). Also, related to the change above, ban the -display parameter from the ones that can be supplied by the user. --- configure.ac | 8 ++++---- src/launch-direct.c | 12 ++++++++---- src/launch.c | 1 + 3 files changed, 13 insertions(+), 8

This set of 10 patches removes the need for any vmchannel implementation, although we can still choose to use vmchannel if we want. In this so-called "null vmchannel" configuration, the appliance connects directly to a port on the library. The exact method is described in patch 9/10. This method still requires SLIRP (user mode networking) so it is not a panacea, because recent

These assorted patches end up with adding virtio-scsi support to libguestfs. It passes libguestfs-test-tool, but I haven't yet tried to run the full set of tests. In theory > 26 devices can be added, but it's likely that certain parts of the daemon will break if you actually try this. This of course needs to be fixed. Thanks Paolo Bonzini for invaluable help. Rich.

More comprehensive support for virtio-scsi. Passes all the tests. Rich.

Hi I have recently installed samba on a RH7.0 box. This box has win98 + linux rh7 installed and both os's are running well. The F drive on windows is FAT32 and is mounted r/w on linux RH7. Works fine. I also have a Win98se machine that needs to have full read/write access to some partitions on the RH7 box. Samba was found ideal for such setup. The problem I have is that I can't write to

Tested with 'make check-release'. tests/parallel (in check-slow) failed, although it does regularly and that seems to be because of libvirt. Rich.

If the guest uses SELinux, then make sure to run a relabel (or at least schedule one) after the image build: this way the template is relabelled, or at least it will do that at the next boot, without the need for the user to ask for a relabel. This just covers the case of building a new image with no additional operations on it though. --- builder/website/centos.sh | 2 ++

Hi, I'm trying to move from UW-IMAP to Dovecot. This is on a RedHat 7.3 system and I'm using the Dovecot RPM from Dag Weirs site. dovecot-0.99.13-1.0.rh7.rf.i386.rpm http://rpmfind.net/linux/RPM/dag/redhat/7.3/i386/dovecot-0.99.13-1.0.rh7.rf.i386.html When I start up Dovecot, I get the following: dovecot: Dovecot starting up Feb 28 01:41:54 yelofsrv dovecot: Auth process died too early

v1 -> v2: - Rebase on top of Pino's version work. Two patches went upstream, these are the two remaining patches. Note the generation number is still inside the qemu.stat file. We could put it in the filename, I have no particular preference. Rich.

Hi, I am trying to install a C6 VM on C6 using the text installer using: # virt-install -n C6_1 -r 3072 --os-variant=rhel6 -l \ ftp://ftp.nluug.nl/site/centos.org/CentOS/6.3/os/x86_64/ --disk \ path=/dev/VG1/vm_c6_1 -w network:default --nographics \ -x "console=ttyS0" --autostart /dev/VG1/vm_c6_1 has been successfully created. The installation starts but once I get to the disk

Hi, Would anyone be interested in developing a LatticeMico32 backend in LLVM? LatticeMico32 [1] is an open source microprocessor core designed by Lattice Semiconductor and typically used in FPGAs. It is comparable to the Microblaze processor that you already support. It is already supported by GNU Binutils and GCC (4.5+). It is used by the Milkymist [2] and RTEMS [3] projects. The Milkymist

Supplied by Pene on IRC who got libguestfs to compile and run on Mac OS X 10.9 with qemu 1.6.0. My notes in [] below. Rich. libguestfs on Mac OS X, recipe so far: -------------------------------------- - libtool-kill-dependency_libs.sh: replace chmod --reference="$output.tmp" "$output" -> chmod `stat -f "%p" "$output.tmp"` "$output" -

This attempts to implement the idea proposed in https://www.redhat.com/archives/libguestfs/2010-April/msg00087.html The idea is that an externally managed QEMU (manual, or via libvirt) can boot the appliance kernel/initrd. libguestfs can then be just told of the UNIX domain socket associated with the guest daemon. An example based on guestfish. 1. Step one, find the appliance kernel/initrd

Just bringing that up as I did not get any reply so far. Thanks, Sébastien On Tuesday 18 May 2010 18:38:41 Sébastien Bourdeauducq wrote: > Hi, > > Would anyone be interested in developing a LatticeMico32 backend in LLVM? > > LatticeMico32 [1] is an open source microprocessor core designed by Lattice > Semiconductor and typically used in FPGAs. It is comparable to the >

Hi guys, I hope you can help me on this issue with kvm/libvirt: using this command to install a kvm virtual machine: virt-install --connect qemu:///system \ --name p3k0401 \ --ram 2048 \ --file //dev/VolGroup01/p3k0401logvol \ --accelerate \ -s 10 \ --nographics \ --hvm \ --location='http://10.1.4.80' I get: Starting install... Retrieving file vmlinuz... | 1.8 MB 00:00

Hello all: Here's the problem [on a RH7 running kernel 2.2.17-14 with Samba 2.0.7-21ssl and xinetd-2.1.8.9pre14]: http://localhost:901 does bring up the SWAT login dialog box.. but upon entering root as the user, followed by my root passwd in the next entry... it tells me "Authentication failed. Retry?" I can tell you that I did enter the correct root passwd, because I am root

Doing qemu feature detection in the direct backend takes ~100ms because we need to run `qemu -help' and `qemu -devices ?', and each of those interacts with glibc's very slow link loader. Fixing the link loader is really hard. Instead memoize the output of those two commands. This patch series first separates all the code dealing with qemu into a separate module (src/qemu.c) and

2015-01-28 12:47 GMT+03:00 Kashyap Chamarthy <kchamart@redhat.com>: > I don't have immediate steps with `virt-manager` as I don't use it much > in my workflow. But if you have users who're comfortable with CLI, you > can import disk images into libvirt (and which will also be accessible > via `virt-manager`) tribvially: > > $ virt-install --name f21vm --ram

Heya, With latest Fedora Rawhide Kernel, I see a nested KVM guest hanging at boot (not unusual). Rich once suggested this[1] to try to attach gdb to the nested L2 guest to find out where_ it's stuck, tonight I set out to try it out (with KVM & TCG). Below is all what I tried. In guest hypervisor (L1): $ git clone git://github.com/libguestfs/libguestfs.git $ git log | head -1