search for: czarcinski

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

Given that no 1.36 has appeared from Fedora Core, I thought I would create the rpm myself. I took the 1.35-11.2 src.rpm from FC3 and updated the spec file for 1.36. However, the build fails. Has anyone successfully created a 1.36 rpm for FC3? If so, what did you need to do? Gene

I was looking through some of the archives and notice a patch submitted to implement: btrfs subvolume show <path-to-subvolume> command. I also noticed that is does not appear to be in the git. This looks like a useful capability. I was trying to find out what the UUID was for a newly created subvolume and have not found out how to do that. Gene -- To unsubscribe from this

I am a relative newcomer to using extlinux. I am running Fedora 20 which means I am using syslinux 4.05. When I noticied that all of your documentation said that booting off ext234 and btrfs was supported, I gave it a try. Indeed, this does work with the boot files and the extlinux directory installed into the btrfs (root) volume. Has any thought been given to supporting supporting

Currently, extlinux does not support multi-device BTRFS volumes. Is anything planned to add this support? I believe I understand that it has to be a lot more complicated with multi-devices because you are doing the device I/O at a very low level. However, grub2 does support booting from multi-device BTRFS volumes (actually subvolumes on multi-device BTRFS volumes). I cannot be impossible

I was under the impression that the value of /etc/machine-id was unqiue for every OS installation on a system. This seems to be the case on real hardware. That is, if I install Fedora 19, Fedora 20, and Fedora-rawhide on a system, they will each have a different value for /etc/machine-id. This does not seem to be the case for qemy-kvm-libvirt virtual systems. SOmetimes they are different

Is there any documentation/tutorial that explains how to use virt-sandbox-service? After looking at some writeups about virt-sandbox-service, this looks like a good tool for something I need to do. But, following the "examples" I cannot get anything to work correctly. With a simple xfce install with httpd, lighttpd, and libvirt-sandbox installed, I tried: 1. virt-sandbox-service

On Wed, 24 Sep 2014, Gene Czarcinski wrote: > It sure would be nice if someone who knows what they are doing took a look at > this problem: > https://bugzilla.redhat.com/show_bug.cgi?id=1135762 > The current situation on Fedora 21 is that virt-sandbox and > virt-sandbox-service simply do not work if a network is def...

OK, either I have taken a stupid pill and am missing something basic or routed network do not work. I assume that, if they did work, it would be in more or less that same manner as a nat network as far as ping'ing, ssh'ing, etc. to another real host on the same real LAN as the virtualization host. At least that is what I believe I should expect. I have googled for info and everything

I have had a number of occasions lately where a virtual "NAT" network (such as default) has stopped working. I have attempted to stop and then restart the network from the "network details" but the only thing that seems to work is to restart all of the virtual guests which use that network. I don't believe that I should have to do that. Is there some command which

Recently, I had some experiences that raises the question as to how compatible (how safe) it is to mount and then read/write a partition using a system such as FC1 or debian where the partition was created under FC3. 1. I recently attempted to run e2fsck running on a FC1 system against a FC3 ext3 partition ... the program refused to run. When I took the e2fsprogs package from FC3 and

Give some of the messages and bugzilla reports about file system problems which are fixed by using e2fsprogs 1.36, I am curious why an update/errata has not been issued yet. Anyone like to comment on thissituation? Gene

Some of you may be interested in running your qemu-kvm (or other) disk image files on BTRFS. After some fumbling around, I have found out how to do it so it works and works very well (especially if it is on an SSD). Anyone investigating running on BTRFS immediately finds out that there is a fragmentation problem (just putting image files on btrfs can result in them having between 50,000 and

Adam Williamson (adamw) has done a fine job at determining how to get bridged networking working with NetworkManager: https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with-networkmanager-2014-fedora-21/ According to Adam, he did the work on Fedora 21 whereas I did it on Fedora 20. the undesirable features (problems) I found may be corrected on F21 but I believe that

I have been "playing with" Secure Containers running a lighttpd server and have it up and running. I used Adam's process (https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with-networkmanager-2014-fedora-21/) for getting a bridge defined when also running NetworkManager. I then created a virtual network definition: > <network> >