similar to: Summary of current test failures

On Tue, Feb 14, 2017 at 09:12:10AM +0100, Pino Toscano wrote: > Introduce a new API to create a new squashfs filesystem out of a path > in the guest. It can be configured to exclude paths based on patterns, > and to select which compression use for the filesystem. > > The advantage of running mksquashfs directly in the appliance is that > ownerships are properly saved, as

Hi, this patch series does changes mostly in virt-dib, few bug fixes and a couple of new features (mostly implemented upstream already). In addition, one new API is added, and a new optional argument for an existing API is added (the latter is not needed, but could be useful anyway). Thanks, Pino Toscano (10): dib: fix listing envvars in fake-sudo dib: source dib "die" script in

2014-07-16 0:58 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > BTW is there any reason to use FUSE instead of using the libguestfs > API directly? Using the API is going to be much more robust. I'm need to create squashfs from root file system. I see some methods like tar and cpio, but i can't find anything suitable for creating squashfs. Also i can't use root

Ray Van Dolson wrote: > On Tue, Apr 22, 2008 at 12:47:39PM +0100, Plant, Dean wrote: >> I would like one of my kickstart scripts to prompt for disk and >> networking only. Commenting out the disk and network settings makes >> the installer prompt for disk settings but not for network settings, >> they default to DHCP. Any idea's how to fix this? > > I'm

I tried making my own LiveCD according to the instructions on the project site. First, applause, the basic procedure works like a charm. It's really easy to do and works right from the beginning (I'm building it inside a VM). I tried the minimal and the desktop version (with a few changes). I have encountered a few problems and have some questions. The German keyboard I set in the

2014-07-16 1:12 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > I believe I investigates making a squashfs from within libguestfs, and > although it's possible, it is not possible to stream the output > (unlike, say, guestfs_tar_out or guestfs_cpio_out). This means that > the maximum size of the squashfs would be quite small. > > Nevertheless we could add an API to

I may have asked about this before, but I can't find any records of so doing in my saved mail (which includes almost everything I ever read or write): All of a sudden, I am not getting flash drives automatically mounted in CentOS 5.3 with GNOME - they are recognized by the hardware, but there seems to be a (new?) problem with the maps. Here's the tail end of dmesg: usb 1-10: new high

I just tried this with CentOS 5.3 as well, and got exactly the same symptoms and dmesg output. (As a point of comparison, Ubunu 8.04 on my work laptop is able to access the drive.) Obviously "not detected" is a misapprehension, though I'm puzzled why "lsusb" doesn't show it. The device is there even though the partition table can't be read. ---------- Forwarded

I have a new machine I'm trying to install Centos 5.0 on and I'm not getting very far. The system is 2 dual core xeons (5160, 3.0 GHZ) w/ 8GB ram. It has two 320 GB disks on the motherboard controller (Supermicro X7DAE+), and 8 750 GB disks on a 3ware 9650SE-8ml, pcie (x4) controller card. The 8 disks are set up as two raid 5 volumes (4 disks each). There is a scsi card in the machine

Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv

Patch set fixes issues with image size increase when using edit-livecd Also address issue with ext4 root fs

Hi, I know that IBM SDD(Subsystem Device Driver) for linux are all for kernel version 2.6.9 or lower - for RHEL4 or less, SLES9 or less I installed IBMsdd rpm, but failed to command "sdd start". I use XenExpress version (xen-3.0.4 version) with 2.6.16 kernel. My questions are 1. Is there anyone who use IBM SDD module with the dom0''s 2.6.16 kernel on Xen-3.0.4 ???? if then,

I am running R 2.3.1 on a Windows XP machine. I am trying to import some data into R that is stored as an S-Plus 7.0 .sdd file. When I run the following command, I get this error: > library(foreign) > d <- read.S(file='H:\\Research\\data.sdd') Error in read.S(file = "H:\\Research\\data.sdd") : not an S object The dataset is fairly large, roughly 13000 rows

I am running R 2.3.1 on a Windows XP machine. I am trying to import some data into R that is stored as an S-Plus 7.0 .sdd file. When I run the following command, I get this error: > library(foreign) > d <- read.S(file='H:\\Research\\data.sdd') Error in read.S(file = "H:\\Research\\data.sdd") : not an S object The dataset is fairly large, roughly 13000 rows

By natively, I take it using kernel /vmlinuz (vs kernel /xen) Not yet, but working on setting up such an environment. (At this time, I was using virt-install to reproduce the problem, and the original server we are testing on did not support kvm but the 2nd server does). On 2016-04-12 03:26 AM, George Dunlap wrote: > On Mon, Apr 11, 2016 at 9:14 PM, Nathan Coulson <nathan at

Dear friends - I hope you will accept a naive question on lm: R version 3.4.1, Windows 10 I have 204 "baskets" of three types corresponding to factor F, each of size from 2 to 33 containing measurements, and need to know if the standard deviation on the measurements in each basket,sdd, is different across types, F. Plotting the observed sdd versus the sizes from 2 to 33, called

Dear R-Help, I've never had any trouble importing data into R until I had to import an .sdd file for a class. The file can be found here: http://www.math.umt.edu/steele/Math%20549/Farms.sdd. It begins with the line "## Dump S Version 4 Dump ##". I first attempted read.S which issued the message "not an S object". I then checked the Import/Export manual which seemed to

I am seeing what seems to be a notable limit on read performance of an ext3 filesystem. If anyone could offer some insight it would be helpful. Background: 12 x 500G SATA disks in a Hardware RAID enclosure connected via 2Gb/s FC to a 4 x 2.6 Ghz system with 4GB ram running RHEL4.5. Initially the enclosure was configured RAID5 10+1 parity, although I've also tried RAID 50 and currently RAID 0.

We have a machine that's a distro mirror - a *lot* of data, not just CentOS. We had the data on /dev/sdc. I added another drive, /dev/sdd, and created that as /dev/md4, with --missing, made an ext4 filesystem on it, and rsync'd everything from /dev/sdc. Note that we did this on *raw*, unpartitioned drives (not my idea). I then umounted /dev/sdc, and mounted /dev/md4, and it looked fine; I

I am using centos5.3 x86_64 on a gigabyte GA-MA78GM-US2H motherboard. When I insert a USB thumbdrive its detected with dmesg, I mount it and start to copy files. Then I start getting errors: sdd: assuming drive cache: write through sdd: sdd1 sdd2 sd 7:0:0:0: Attached scsi removable disk sdd sd 7:0:0:0: Attached scsi generic sg4 type 0 usb-storage: device scan complete usb 1-5: reset high speed