similar to: Libvirt-lxc packages deprecation

Hi guys, when I detach an interface from vm during boot (vm boot not finished), it always fail. I'm not sure if there is an existing bug. I have confirmed with someone that for disk, there is similar behavior, if this is also acceptable? # virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh dumpxml rhel7.2 |grep

When setting file permissions from MS environment to a file on a Samba4 share, it can be made in clear text with human readable user/group names and the rights seem to work. However when checking the permissions again from an MS environment, instead of human readable user/group names there are plain SID numbers in their place and there is an icon apparently signifying an unknown SID. How to keep

On 02/24/2015 01:15 AM, Gordon Messmer wrote: > On 02/23/2015 08:22 AM, Niki Kovacs wrote: >> 1. Users should be manageable through a GUI, probably a web interface, >> so the client can create, manage and delete them eventually. > > FreeIPA is a good option, generally. As best I understand it, it's > currently available in a Docker container for CentOS. >

I get that libguest not supported mount windows VM image from rhel7.2 now, could you help point that how to compile my own libguestfs with the ntfs support, which option to enable it when make configure with the code ? Thx a lot. http://www.libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2

Hi I'm testing cmt event of libvirt, and I have two questions. I will be very grateful if someone can give me some help. Q1:"virsh domstats --perf" and linux perf tool has different result. I have a guest with cmt event enabled, start guest and get perf statistic every 1s: # while true; do virsh domstats rhel7.2-1030 --perf; sleep 1; done In the meanwhile, I use perf tool to get

On Thu, Mar 29, 2018 at 05:26:13PM +0200, Piotr Kliczewski wrote: > Richard, > > Great progress. I really like it!!! > > Here is what I noticed: > > I see that in the yaml file we provide short-id as: > > os: > osinfo: 'rhel7.2' > > whereas kubevirt expects it in metadata: > > metadata: > labels: > kubevirt.io/os: win10 >

On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: > > Hi, > > > > I have an issue with using a UNIX filegroup for access control within a > > share. The situation is like this: > > > > Given a share "test" which exports "/test" to a NIS netgroup

On Wed, 2016-02-10 at 09:20 +0000, Rowland penny wrote: > On 10/02/16 07:44, Trond Hasle Amundsen wrote: > > On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > >> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: > >>> Hi, > >>> > >>> I have an issue with using a UNIX filegroup for access control within a >

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Roman is talking about what virt-v2v already does. This is good information:

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Firs of all you will

On Wed, 2016-02-10 at 09:57 +0000, Rowland penny wrote: > On 10/02/16 09:41, Trond Hasle Amundsen wrote: > > On Wed, 2016-02-10 at 09:20 +0000, Rowland penny wrote: > >> On 10/02/16 07:44, Trond Hasle Amundsen wrote: > >>> On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > >>>> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen

> On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: >>> On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: >>>> 1) tell which devices can be configured >>> Not sure that I fully understated

Hi, I am trying to create a VM with the IVSHMEM feature, and I specify the device using qemu command line argument in my XML by using the pass through tag as follows: <qemu:commandline> <qemu:arg value='-device ivshmem,size=2048M,shm=fd:/mnt/huge/map_1:0x0:0x40000000:/dev/zero:0x0:0x3fffc000:/var/run/.ivshmem_metadata_config_2:0x0:0x4000'/>

On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: > > > > To sum up, the packaging and naming policy of the virtio-win rpm and the > > > > virtio-win iso therein are different and neither is clear. Hardcoding > > > > the policy in v2v without actually knowing it appears risky at best. > > It's due to historical reasons mostly. The best

Fixes some of the more egregious problems with v1, and also applies properly to the head of git without needing any other patches. Rich.

+1 for freeipa. It is an extremely well integrated domain controller with a functionality similar to Microsoft Active Directory. I would highly recommend setting up an AWS Virtual Private Cloud or something similar and practice deploying freeipa a few times with a few clients. It takes some understanding of the caveats and implimentation before you will be able to deploy it successfully in a

On Mon, 2015-11-09 at 18:08 +0300, Roman Kagan wrote: > On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > > >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld

Let me preface this by saying "Yes, I know *nix filesystems don't need to worry about fragmentation". That said, is there a way to check the overall level of fragmentation of a live ext3 filesystem? I know about filefrag, but that's for specific files. And I think e2fsck tells you, but only if you take the filesystem offline for the scan. Is there anything that will give

> On 29 Oct 2015, at 10:28, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: >>> 1) tell which devices can be configured >> Not sure that I fully understated your question. but if you are going to >> create some sort of off-line automatic virtio-win drivers update >> utility, then it

Richard, Great progress. I really like it!!! Here is what I noticed: I see that in the yaml file we provide short-id as: os: osinfo: 'rhel7.2' whereas kubevirt expects it in metadata: metadata: labels: kubevirt.io/os: win10 For windows vms we need to create perset like this one [1]. We can add separator --- between the objects. Thanks, Piotr [1]