search for: fintech

Displaying 15 results from an estimated 15 matches for "fintech".

Did you mean: fintec
2014 Jan 17
1
Re: Libguestfs can't launch with one of the disk images in the RHEV cluster
----- Original Message ----- > From: "Richard W.M. Jones" <rjones@redhat.com> > To: "Исаев Виталий Анатольевич" <isaev@fintech.ru> > Cc: libguestfs@redhat.com > Sent: Tuesday, January 14, 2014 6:42:23 PM > Subject: Re: [Libguestfs] Libguestfs can't launch with one of the disk images in the RHEV cluster > > On Tue, Jan 14, 2014 at 02:57:35PM +0000, Исаев Виталий Анатольевич wrote: > This works beca...
2014 Jan 16
3
LVM mounting issue
...b: /dev/vg_kojit/lv_root: No such file or directory ><fs> ><fs> The actual information about VM's block devices can be seen on the screenshot attached to this message. I would be grateful for your help Sincerely, Vitaly Isaev Software engineer Information security department Fintech JSC, Moscow, Russia
2014 Jan 17
2
Re: LVM mounting issue
...uest libguestfs-1.16.34-2.el6.x86_64 libguestfs-winsupport-1.0-7.el6.x86_64 python-libguestfs-1.16.34-2.el6.x86_64 libguestfs-tools-c-1.16.34-2.el6.x86_64 Full trace of the guestfish session is attached to this message. Sincerely, Vitaly Isaev Software engineer Information security department Fintech JSC, Moscow, Russia
2014 Jan 17
2
Re: LVM mounting issue
...So I have no choice and I try to open /dev/dm-40 with libguestfs or guestfish. What's next, you already know. I apologize for spending your time again, but please evaluate the proposed method of disk image definition. Sincerely, Vitaly Isaev Software engineer Information security department Fintech JSC, Moscow, Russia
2014 Jan 14
2
Re: Libguestfs can't launch with one of the disk images in the RHEV cluster
...ot be accessed from libguestfs. I have an urgent need to work with a chosen VM disk images through the libguestfs layer, but I don’t know which images belong to every VM exactly. It seems like I’m going the hard way :) Sincerely, Vitaly Isaev Software engineer Information security department Fintech JSC, Moscow, Russia
2014 Jan 14
2
Libguestfs can't launch with one of the disk images in the RHEV cluster
[This email is either empty or too large to be displayed at this time]
2013 Nov 22
0
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Thanks, Itamar. Hooks are really great tool. No doubt we will use them. But I still need some clarification about interaction between hooks (on the manager's side) and libguestfs (on the side of hypervisor/storage). Виталий Исаев Инженер-программист Группа разработки и внедрения ПСЗИ Департамент информационной безопасности ОАО <Финтех> -----Original Message----- From: Itamar Heim
2013 Nov 22
0
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Thanks a lot. Yes, we have a Support and we will ask them to help with this bug. How do you think, maybe we can hack this issue quickly just putting the kernel file (desired by libguestfs) manually to some directory on the RHEV-H file system? /boot and /lib/modules do not contain kernels on RHEV-H. Виталий Исаев Инженер-программист Группа разработки и внедрения ПСЗИ Департамент информационной
2013 Nov 22
1
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Oh, you are right. Wrong filename - it's my fault. Now: ====== TEST FINISHED OK ====== Виталий Исаев Инженер-программист Группа разработки и внедрения ПСЗИ Департамент информационной безопасности ОАО «Финтех» -----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Friday, November 22, 2013 3:48 PM To: Исаев Виталий Анатольевич Cc: Fabian Deutsch;
2013 Nov 22
1
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Rich, this wasn't operational. First of all, the image on my version of RHEV-H is kept in other directory. So I did that: 1. $ export FEBOOTSTRAP_KERNEL=/dev/.initramfs/live/vmlinuz0 2. $ echo $FEBOOTSTRAP_KERNEL /dev/.initramfs/live/vmlinuz0 3. $ libguestfs-test-tool ************************************************************ *
2013 Nov 22
0
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Rich, you are right; the hypervisor is RHEV-H. As Itamar has just explained me, hooks are executed on the hypervisor’s side (not on the RHEV-M, as I used to think), so properly working libguestfs on the RHEV-H will resolve my issue. Here is the output of the test tool: ************************************************************ * IMPORTANT NOTICE * * When
2013 Nov 21
0
HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
________________________________________ От: Itamar Heim [iheim@redhat.com] Отправлено: 21 ноября 2013 г. 20:10 Кому: Richard W.M. Jones; Исаев Виталий Анатольевич Копия: libguestfs@redhat.com Тема: Re: [Libguestfs] Accessing iSCSI disc images from the RHEV Manager using libguestfs On 11/21/2013 05:56 PM, Richard W.M. Jones wrote: > [Adding Itamar: Any suggestions on where Vitaly could get
2013 Nov 21
2
Accessing iSCSI disc images from the RHEV Manager using libguestfs
Dear libguestfs developers, We are developing the protected enterprise system based on several Red Hat technologies (Red Hat Enterprise Virtualisation, the IdM server and so on). Our current goal is to prevent the booting of the virtual machine in case of integrity loss. So what we are trying to do Is to intercept the event of the VM's start (using the RHEV Manager hook scripts), mount the
2013 Nov 22
2
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Thanks to all. Symbolic link to vmlinuz image is a solution to my problem: $ ll /boot total 2536 drwxr-xr-x. 3 root root 60 2013-04-15 14:49 efi lrwxrwxrwx. 1 root root 25 2013-09-18 15:50 grub -> /dev/.initramfs/live/grub -rw-r--r--. 1 root root 185842 2013-03-29 20:59 symvers-2.6.32-358.6.1.el6.x86_64.gz -rw-r--r--. 1 root root 2407872 2013-03-29 20:58
2013 Nov 22
4
Re: HA: Accessing iSCSI disc images from the RHEV Manager using libguestfs
Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *