+Lev
- Original Message -
> From: "Vadim Rozenfeld"
> To: "Cole Robinson"
> Cc: "Roman Kagan" , virt-tools-list@redhat.com, "Jeff
> Nelson" , "Richard
> W.M. Jones" , "Denis Lunev" , "Yan
> Vugenfirer" ,
> mic...@redhat.com, "Amnon Ilan" , "Jin" ,
> "Alexander Burluka"
>
> Sent: Mon
Hello,
Please, help me to figure out how to convert VMWare guestId to libvirt
os-variant.
For example,
guestosid:
centos64Guest
centosGuest
os-variant:
centos6.0
centos6.1
centos6.2
centos6.3
centos6.4
centos6.5
centos7.0
The task is to start VM on KVM from disk image fom VMWare. But,
Wh
On Fri, 2016-01-22 at 15:30 -0500, Cole Robinson wrote:
> On 01/22/2016 01:27 PM, Roman Kagan wrote:
> > On Fri, Jan 22, 2016 at 06:05:01PM +0300, Roman Kagan wrote:
> >> The scripts are based on the idea that the most actual information about
> >> the suitability of a driver for a particular flavo
On 01/23/2016 10:36 AM, mkov wrote:
> Hello,
> Please, help me to figure out how to convert VMWare guestId to libvirt
> os-variant.
> For example,
>
> guestosid:
> centos64Guest
> centosGuest
>
> os-variant:
> centos6.0
> centos6.1
> centos6.2
> centos6.3
> centos6.4
> centos6.5
> centos7.0
>
On 01/24/2016 08:15 AM, Michael A Cooper wrote:
> Hey Guys,
>
> How is everyone? I am not sure how to word this question but here
> goes. I have a 3 server setup and I created a nfs share so that I could do
> Live Migration across the servers. So when I create the vm with qcow2
> everythin
On Mon, Jan 25, 2016 at 07:34:39PM +1100, Vadim Rozenfeld wrote:
> On Fri, 2016-01-22 at 15:30 -0500, Cole Robinson wrote:
> > On 01/22/2016 01:27 PM, Roman Kagan wrote:
> > >And I'm afraid this may be a legitimate situation. Assume a driver
> > >is signed for, say, 2k8 and 2k8R2, and then
As was discussed some time ago on libguestfs ML
(http://thread.gmane.org/gmane.comp.emulators.guestfs/8341/focus=8576)
there is a need in a tool that would lay out the Windows guest drivers
on a filesystem by Windows flavor and architecture in a way that is
- easy to consume by both humans and pro
This script parses ASN.1 structure of the Windows driver catalog files,
and extracts information about what architecture and windows flavor the
driver is suitable for.
Signed-off-by: Roman Kagan
---
changes since v2:
- add extracting of catalog timestamp and signing time
- minor refactoring for
This script recursively discovers the driver packages (that is, a
directory containing an .inf file, an .cat file, and possibly other
files) in the source directory. For each such package, it parses the
catalog file and determines what architectures and windows flavors this
driver is suitable for.