Cole Robinson | 2 Sep 18:22
Picon
Favicon

Re: [PATCH] virt-manager: Use avahi to poll for local servers

Cole Robinson wrote:
> Cole Robinson wrote:
>> The attached patch adds support for avahi polling
>> to the virt-manager 'Open Connection' dialog.
>> libvirtd advertises itself via avahi so we get the
>> hard stuff for free :). To test this you will need
>> to make sure Multicast DNS (mDNS, port 5353 udp) is
>> open on your machine.
>>
> 
> Second cut of this patch. Issues resolved:
> 
> - Removed the check box, unconditionally poll for
>   connections if the user selects a remote conn
>   option.
> 
> - Only use advertised 'name' as the list entry.
> 
> - Don't add duplicate list entries.
> 
> - If creating the initial avahi dbus interface
>   fails, just disable all polling, and never
>   activate the connection list.
> 
> - Sort list entries alphabetically by default,
>   and add ability to sort ascend/descend
> 

I've committed this:

(Continue reading)

Cole Robinson | 2 Sep 18:23
Picon
Favicon

Re: [PATCH] virt-manager: Option to add sound device for vm create

Cole Robinson wrote:
> The attached patch adds options to virt-manager's preferences
> section for adding an audio device to new VMs.
> 
> The new option defaults to adding audio for all new local
> VMs, but skipping audio for remote VMs.
> 
> I opted for the preferences screen approach since it seems
> like the type of thing users will either always or never
> want, and the new VM wizard is kind of cluttered as it is.
> 
> Couple of screenshots:
> 
> http://fedorapeople.org/~crobinso/virt-manager/virt-manager-sound-prefs.png
> http://fedorapeople.org/~crobinso/virt-manager/virt-manager-sound-summary.png
> 
> Thanks,
> Cole
> 
> 

I've committed this:

http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=138ad06915c4

Thanks,
Cole
Cole Robinson | 5 Sep 13:56
Picon
Favicon

Heads Up: virt-manager + virtinst releases pending

Hi all, just wanted to send out a note that new releases
for virt-manager and virtinst are close.

Fedora 10 beta freeze is next Tuesday, September 9th, so
We will probably push new releases on either Monday or early
Tuesday.

So if anyone has any pending patches, or some small thing
they would really like to see fixed, please post about it
soon and we can try to fit it in.

Thanks,
Cole
irraz rulez | 5 Sep 14:25
Picon

error bad superblock on /dev/mapper/debian-root

Hi,

My system root is in /dev/mapper/debian-root but virt-p2v-0.9.7
result error:

 mount '/dev/debian/root' /mnt/root
mount: wrong fs type, bad option, bad superblock on /dev/mapper/debian-root,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Command failed:
mount '/dev/debian/root' /mnt/root



~$ mount
/dev/mapper/debian-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
/dev/mapper/debian-home on /home type ext3 (rw)
/dev/mapper/debian-tmp on /tmp type ext3 (rw)
/dev/mapper/debian-usr on /usr type ext3 (rw)
/dev/mapper/debian-var on /var type ext3 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

Can you help me, please?

--
irraz




--
::[ 1rr4c10n4l ]::
web: www.lacuevadelchivo.com
jabber/msn: irraz.rulez (at) gmail.com


**************************************************

virt-p2v starting up at 2008-09-05 11:54:00

sh: setterm -blank 0
all_block_devices: block devices: sda
shget: blockdev --getsize64 '/dev/sda'
all_block_devices: non-removable block devices: sda [40007761920]
shget: lvs --noheadings -o vg_name,lv_name,devices,lv_size
all_partitions: PVs: sda5
all_partitions: LVs: /dev/debian/home; /dev/debian/root; /dev/debian/swap_1; /dev/debian/tmp;
/dev/debian/usr; /dev/debian/var
all_partitions: all partitions: /dev/sda5; /dev/sda2; /dev/sda1
all_partitions: partitions after removing PVs: /dev/sda2; /dev/sda1
shget: file -sbL '/dev/debian/home'
shwithstatus: mount -o ro '/dev/debian/home' /mnt/root
sh: umount /mnt/root
partition detection: /dev/debian/home is Mountable non-root
shget: file -sbL '/dev/debian/root'
shwithstatus: mount -o ro '/dev/debian/root' /mnt/root
shget: file -bL '/mnt/root/sbin/init'
sh: umount /mnt/root
partition detection: /dev/debian/root is Linux i386
shget: file -sbL '/dev/debian/swap_1'
partition detection: /dev/debian/swap_1 is Linux swap
shget: file -sbL '/dev/debian/tmp'
shwithstatus: mount -o ro '/dev/debian/tmp' /mnt/root
sh: umount /mnt/root
partition detection: /dev/debian/tmp is Mountable non-root
shget: file -sbL '/dev/debian/usr'
shwithstatus: mount -o ro '/dev/debian/usr' /mnt/root
sh: umount /mnt/root
partition detection: /dev/debian/usr is Mountable non-root
shget: file -sbL '/dev/debian/var'
shwithstatus: mount -o ro '/dev/debian/var' /mnt/root
sh: umount /mnt/root
partition detection: /dev/debian/var is Mountable non-root
shget: file -sbL '/dev/sda2'
shwithstatus: mount -o ro '/dev/sda2' /mnt/root
mount: you must specify the filesystem type
partition detection: /dev/sda2 is Unknown
shget: file -sbL '/dev/sda1'
shwithstatus: mount -o ro '/dev/sda1' /mnt/root
sh: umount /mnt/root
partition detection: /dev/sda1 is Linux /boot
shget: dmesg
shget: grep ^processor /proc/cpuinfo | tail -1 | awk '{print $3+1}'
shwithstatus: ifconfig 'eth0' '192.168.30.56' netmask '255.255.255.0'
shwithstatus: route add default gw '192.168.30.1' 'eth0'
shwithstatus: echo nameserver '195.160.224.37' > /etc/resolv.conf
ssh_connect: ssh -l 'root' -p '22' '195.160.226.132' /bin/ls '/xen'
ssh_disconnect
Warning: Permanently added '195.160.226.132' (RSA) to the list of known hosts.
sh: vgchange -a n
sh: rm -f /etc/lvm/cache/.cache
sh: rm -f /etc/lvm.new/cache/.cache
shget: blockdev --getsz '/dev/sda'
sh: dmsetup create snapsda_org --table='0 78140160 snapshot-origin /dev/sda'
sh: dmsetup create snapsda --table='0 78140160 snapshot /dev/mapper/snapsda_org /dev/ram1 n 64'
shfailok: kpartx -a '/dev/mapper/snapsda'
sh: vgscan
sh: vgchange -a y
sh: mount '/dev/debian/root' /mnt/root
mount: wrong fs type, bad option, bad superblock on /dev/mapper/debian-root,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Command failed:

mount '/dev/debian/root' /mnt/root
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
Cole Robinson | 5 Sep 16:16
Picon
Favicon

[PATCH] virt-install: use --disk to specify size and sparse

The attached patch expands the options that can be
lumped onto virt-install's new --disk option to
specify size of new storage, and whether we want to
create it as sparse.

The format for these options is:

  --disk path=/some/new/file,size=5,sparse=true|false

This acts similar to the current options: if the file
doesn't exist, size is required, and we default to
sparse=True if it isn't specified.

This effectively deprecates --file, --file-size, and
--nonsparse, and in my opinion is much simpler. It also
helps overcome some problems we had with the original
options for cases of specifying multiple disks: there
was no way to specify one sparse disk and one nonsparse
disk, and generally specifying multiple disks was
unclear and a pain.

I also added a manpage section for the --disk option.

Any comments appreciated.

Thanks,
Cole
diff -r c20df049889e man/en/virt-install.pod
--- a/man/en/virt-install.pod	Fri Sep 05 09:15:55 2008 -0400
+++ b/man/en/virt-install.pod	Fri Sep 05 10:15:39 2008 -0400
@@ -1,4 +1,4 @@
-=od
+=pod

 =head1 NAME

@@ -80,13 +80,82 @@
 If the value 'auto' is passed, virt-install attempts to automatically determine
 an optimal cpu pinning using NUMA data, if available.

+=item --disk=DISKOPTS
+
+Specifies media to use as storage for the guest, with various options. The
+general format of a disk string is
+
+    --disk opt1=val1,opt2=val2,...
+
+To specify media, one of the following options is required:
+
+=over 4
+
+=item B<path>
+
+A path to some storage media to use, existing or not. Existing media can be
+a file or block device. If installing on a remote host, the existing media
+must be shared as a libvirt storage volume.
+
+Specifying a non-existent path implies attempting to create the new storage,
+and will require specifyng a 'size' value. If the base directory of the path
+is a libvirt storage pool on the host, the new storage will be created as a
+libvirt storage volume. For remote hosts, the base directory is required to be
+a storage pool if using this method.
+
+=item B<pool>
+
+An existing libvirt storage pool name to create new storage on. Requires
+specifying a 'size' value.
+
+=item B<vol>
+
+An existing libvirt storage volume to use. This is specified as
+'poolname:volname'.
+
+=back
+
+Other available options:
+
+=over 4
+
+=item B<device>
+
+Disk device type. Value can be 'cdrom', 'disk', or 'floppy'. Default is
+'disk'. If a 'cdrom' is specified, and no install method is chosen, the
+cdrom is used as the install media.
+
+=item B<perms>
+
+Disk permissions. Value can be 'rw' (Read/Write), 'ro' (Readonly),
+or 'sh' (Shared Read/Write). Default is 'rw'
+
+=item B<size>
+
+size (in GB) to use if creating new storage
+
+=item B<sparse>
+
+whether to skip fully allocating newly created storage. Value is 'true' or
+'false'. Default is 'true' (do not fully allocate).
+
+=back
+
+See the examples section for some uses. This option deprecates C<--file>,
+C<--file-size>, and C<--nonsparse>.
+
+=item --nodisks
+
+Request a virtual machine without any local disk storage, typically used for
+running 'Live CD' images or installing to network storage (iSCSI or NFS root).
+
 =item -f DISKFILE, --file=DISKFILE

 Path to the file, disk partition, or logical volume to use as the backing store
 for the guest's virtual disk. If the path does not exist, then C<--file-size>
 option should also be specified, allowing the disk to be created. This parameter
-can be repeated multiple times to add many disk. This parameter will be prompted 
-for if omitted on the command line. 
+can be repeated multiple times to add many disk. This option is deprecated in
+favor of --disk.

 =item -s DISKSIZE, --file-size=DISKSIZE

@@ -103,12 +172,6 @@
 by faster install times inside the guest. Thus use of this optional is recommended 
 to ensure consistently high performance and to avoid I/O errors in the guest 
 should the host filesystem fill up. 
-
-=item --nodisks
-
-Request a virtual machine without any local disk storage, typically used for 
-running 'Live CD' images or installing to network storage (iSCSI or NFS root).
-This disables all interactive prompts for disk setup.

 =item -m MAC, --mac=MAC

@@ -248,9 +311,9 @@
 File to use a virtual CD-ROM device for fully virtualized guests. It can be
 path to an ISO image, or to a CDROM device. It can also be a URL from which
 to fetch/access a minimal boot ISO image. The URLs take the same format as
-described for the C<--location> argument. If this parameter is omitted then
-the C<--location> argument must be given to specify a location for the kernel
-and initrd, or the C<--pxe> argument used to install from the network.
+described for the C<--location> argument. If a cdrom has been specified via
+the C<--disk> option, and neither C<--cdrom> nor any other install option is
+specified, the C<--disk> cdrom is used as the install media.

 =item  --pxe

@@ -504,8 +567,60 @@

 =head1 EXAMPLES

+Install a KVM guest, creating a new storage file, virtual networking,
+booting from the host CDROM, using VNC server/viewer
+
+  # virt-install \
+       --connect qemu:///system \
+       --name demo \
+       --ram 500 \
+       --disk path=/var/lib/libvirt/images/demo.img,size=5 \
+       --network network:default \
+       --accelerate \
+       --vnc \
+       --cdrom /dev/cdrom
+
+
+Install a Fedora 9 KVM guest, using LVM partition, virtual networking,
+booting from PXE, using VNC server/viewer
+
+  # virt-install \
+       --connect qemu:///system \
+       --name demo \
+       --ram 500 \
+       --disk path=/dev/HostVG/DemoVM \
+       --network network:default \
+       --accelerate \
+       --vnc \
+       --os-variant fedora9
+
+Install a QEMU guest, with a real partition, for a different architecture
+using SDL graphics, using a remote kernel and initrd pair:
+
+  # virt-install \
+       --connect qemu:///system \
+       --name demo \
+       --ram 500 \
+       --disk path=/dev/hdc \
+       --network bridge:eth1 \
+       --arch ppc64 \
+       --sdl \
+       --location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
+
+Run a Live CD image under Xen fullyvirt, in diskless environment
+
+  # virt-install \
+       --hvm \
+       --name demo \
+       --ram 500 \
+       --nodisks \
+       --livecd \
+       --vnc \
+       --cdrom /root/fedora7live.iso
+
 Install a paravirtualized Xen guest, 500 MB of RAM, a 5 GB of disk, and
-Fedora Core 6 from a web server, in text-only mode:
+Fedora Core 6 from a web server, in text-only mode, with old style --file
+options:

   # virt-install \
        --paravirt \
@@ -516,67 +631,23 @@
        --nographics \
        --location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/

-Install a QEMU guest, with a real partition, for a different architecture
-using SDL graphics, using a local ISO image:
-
-  # virt-install \
-       --connect qemu:///system \
-       --name demo \
-       --ram 500 \
-       --file /dev/hdc \
-       --network bridge:eth1 \
-       --arch ppc64 \
-       --sdl \
-       --cdrom /root/boot.iso
-
-Install a QEMU guest, with a real partition, for a different architecture
-using SDL graphics, using a remote kernel and initrd pair:
-
-  # virt-install \
-       --connect qemu:///system \
-       --name demo \
-       --ram 500 \
-       --file /dev/hdc \
-       --network bridge:eth1 \
-       --arch ppc64 \
-       --sdl \
-       --location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
-
-Install a KVM guest, using LVM partition, virtual networking, booting from
-the host CDROM, using VNC server/viewer
-
-  # virt-install \
-       --connect qemu:///system \
-       --name demo
-       --ram 500 \
-       --file /dev/HostVG/DemoVM \
-       --network network:default \
-       --accelerate \
-       --vnc \
-       --cdrom /dev/cdrom 
-
-Run a Live CD image under Xen fullyvirt, in diskless environment
-
-  # virt-install \
-       --hvm \
-       --name demo \
-       --ram 500 \
-       --nodisk \
-       --livecd \
-       --vnc \
-       --cdrom /root/fedora7live.iso

 =head1 AUTHOR

-Written by Daniel P. Berrange, Hugh Brock, Jeremy Katz and a team of many
-other contributors. See the AUTHORS file in the source distribution for
-the complete list of credits.
+Written by Daniel P. Berrange, Hugh Brock, Jeremy Katz, Cole Robinson and a
+team of many other contributors. See the AUTHORS file in the source
+distribution for the complete list of credits.

 =head1 BUGS

-Report bugs to the mailing list C<http://www.redhat.com/mailman/listinfo/et-mgmt-tools>
+Report bugs to the mailing list
+C<http://www.redhat.com/mailman/listinfo/et-mgmt-tools>
 or directly to BugZilla C<http://bugzilla.redhat.com/bugzilla/> against the
 C<Fedora> product, and the C<python-virtinst> component.
+
+When filing a bug, please run the failing command with the --debug command
+line flag and post the output to the bug report, along with
+$HOME/.virtinst/virt-install.log

 =head1 COPYRIGHT

diff -r c20df049889e virt-install
--- a/virt-install	Fri Sep 05 09:15:55 2008 -0400
+++ b/virt-install	Fri Sep 05 10:15:39 2008 -0400
@@ -52,6 +52,7 @@
     devtype = None
     ro = False
     shared = False
+    sparse = True

     origpath = path

@@ -66,27 +67,44 @@
         fail(_("--disk path must start with path=, pool=, or vol=."))
     path = path[len(path_type):]

-    # Parse endings for perms and device type
+    # Parse out comma separated options
+    opts = {}
     while True:
         if not path.count(","):
             break
-        path, opts = path.split(",", 1)
-        for opt in opts.split(","):
+        path, tmpopts = path.split(",", 1)
+        for opt in tmpopts.split(","):
             opt_type = None
             opt_val = None
             if opt.count("="):
                 opt_type, opt_val = opt.split("=", 1)
-            if opt_type == "device":
-                devtype = opt_val
-            elif opt_type == "perms":
-                if opt_val == "ro":
-                    ro = True
-                elif opt_val == "sh":
-                    shared = True
-                else:
-                    fail(_("Unknown perms value '%s'." % opt_val))
+                opts[opt_type.lower()] = opt_val.lower()
+
+    for opt in opts.items():
+        opt_type, opt_val = opt
+        if opt_type == "device":
+            devtype = opt_val
+        elif opt_type == "perms":
+            if opt_val == "ro":
+                ro = True
+            elif opt_val == "sh":
+                shared = True
             else:
-                fail(_("Unknown disk option '%s'." % opt))
+                fail(_("Unknown '%s' value '%s'" % (opt_type, opt_val))
+        elif opt_type == "size":
+            try:
+                size = float(opt_val)
+            except Exception, e:
+                fail(_("Improper value for 'size': %s" % str(e)))
+        elif opt_type == "sparse":
+            if opt_val == "true":
+                sparse = True
+            elif opt_val == "false":
+                sparse = False
+            else:
+                fail(_("Unknown '%s' value '%s'") % (opt_type, opt_val))
+        else:
+            fail(_("Unknown --disk option '%s'." % opt))

     # We return (path, (poolname, volname), volinst, device, readonly, shared)
     if path_type == "path=":
@@ -112,7 +130,7 @@

     if not devtype:
         devtype = virtinst.VirtualDisk.DEVICE_DISK
-    ret = (abspath, voltuple, volinst, devtype, ro, shared)
+    ret = (abspath, voltuple, volinst, devtype, ro, shared, size, sparse)
     logging.debug("parse_disk: returning %s" % str(ret))
     return ret

@@ -121,13 +139,14 @@
     try:
         # Get disk parameters
         if is_file_path:
-            (path, voltuple, volinst,
-             device, readOnly, shared) = (disk, None, None,
-                                         virtinst.VirtualDisk.DEVICE_DISK,
-                                         False, False)
+            (path, voltuple, volinst, device, readOnly, shared, size,
+             sparse) = \
+             (disk, None, None, virtinst.VirtualDisk.DEVICE_DISK, False,
+              False, size, sparse)
         else:
             (path, voltuple, volinst,
-             device, readOnly, shared) = parse_disk_option(guest, disk, size)
+             device, readOnly, shared,
+             size, sparse) = parse_disk_option(guest, disk, size)
             if not sparse and volinst:
                 volinst.allocation = volinst.capacity

@@ -162,8 +181,9 @@
         if file_paths or disk_paths or size:
             fail(_("Cannot use --file, --size, or --disk with --nodisks"))
         return
-    if file_paths and disk_paths:
-        fail(_("Cannot mix --file and --disk options."))
+    if (file_paths or size or sparse == False) and disk_paths:
+        fail(_("Cannot mix --file, --nonsparse, or --file-size with --disk "
+               "options. Please see the manual for --disk syntax."))
     elif not file_paths and not disk_paths:
         fail(_("A disk must be specified (use --nodisks to override)"))

@@ -333,13 +353,13 @@

     parser.add_option_group(insg)
     stog = OptionGroup(parser, _("Storage Configuration"))
+    stog.add_option("", "--disk", type="string", dest="diskopts",
+                    action="callback", callback=cli.check_before_append,
+                    help=_("Specify storage to use as a disk with various "
+                           "options."))
     stog.add_option("-f", "--file", type="string", dest="file_path",
                     action="callback", callback=cli.check_before_append,
                     help=_("File to use as the disk image"))
-    stog.add_option("", "--disk", type="string", dest="disk_path",
-                    action="callback", callback=cli.check_before_append,
-                    help=_("Specify storage to use as a disk with various "
-                           "options."))
     stog.add_option("-s", "--file-size", type="float",
                     action="append", dest="disksize",
                     help=_("Size of the disk image (if it doesn't exist) in "
@@ -505,7 +525,7 @@
         cli.get_sound(options.sound, guest)

     # set up disks
-    get_disks(options.file_path, options.disk_path, options.disksize,
+    get_disks(options.file_path, options.diskopts, options.disksize,
               options.sparse, options.nodisks, guest, hvm, conn)

     # set up network information
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
Daniel P. Berrange | 5 Sep 17:16
Picon
Favicon

Re: Heads Up: virt-manager + virtinst releases pending

On Fri, Sep 05, 2008 at 07:56:01AM -0400, Cole Robinson wrote:
> Hi all, just wanted to send out a note that new releases
> for virt-manager and virtinst are close.
> 
> Fedora 10 beta freeze is next Tuesday, September 9th, so
> We will probably push new releases on either Monday or early
> Tuesday.

Good plan - we'rll be doing a libvirt release before tuesday too, so
you can increment the Requires: libvirt to be >= 0.4.5  to ensure all
your libvirt fixes are pulled into as deps.

Regards,
Daniel
--

-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
Daniel P. Berrange | 5 Sep 17:17
Picon
Favicon

Re: [PATCH] virt-install: use --disk to specify size and sparse

On Fri, Sep 05, 2008 at 10:16:28AM -0400, Cole Robinson wrote:
> The attached patch expands the options that can be
> lumped onto virt-install's new --disk option to
> specify size of new storage, and whether we want to
> create it as sparse.
> 
> The format for these options is:
> 
>   --disk path=/some/new/file,size=5,sparse=true|false
> 
> This acts similar to the current options: if the file
> doesn't exist, size is required, and we default to
> sparse=True if it isn't specified.
> 
> This effectively deprecates --file, --file-size, and
> --nonsparse, and in my opinion is much simpler. It also
> helps overcome some problems we had with the original
> options for cases of specifying multiple disks: there
> was no way to specify one sparse disk and one nonsparse
> disk, and generally specifying multiple disks was
> unclear and a pain.
> 
> I also added a manpage section for the --disk option.

Great - this all looks good to me.

Daniel
--

-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
Kay Williams | 5 Sep 17:42
Favicon

Re: [libvirt] virt-install and custom distros

Can the issue be addressed in the upcoming virtinst release?

Cole Robinson wrote:
> Kay Williams wrote:
>> We have an application that builds custom distributions based on RHEL, CentOS or 
>> Fedora.  We would like to install these over the network using virt-install, but 
>> we've run into an issue with the distro check logic. Specifically, virt-install 
>> fails unless it finds a string "Red Hat Enterprise Linux", "Fedora"  or "CentOS" 
>> within the family field of the .treeinfo file.
>>
>> Our application currently sets the family field to the user-provided distro name 
>> (see below).  We have avoided using the base distro name given trademark concerns.
>>
>>      [general]
>>      family = <user provided value>
>>      variant = <user provided value>
>>
>> We can get virt-install to pass the distro check by setting the family name to 
>> one of the accepted values, e.g.
>>
>>      [general]
>>      family = Fedora
>>      variant = [user provided distro name]
>>
>> Is this the expected/desired use for the family and variant fields?  Or is there 
>> another approach we should consider?
>>
>> Thanks,
>> Kay
> 
> (cc-ing et-mgmt-tools, since that is the list for virt-install/
>  virt-manager)
> 
> We shouldn't be failing if the family/variant is unknown: it's really
> just a convenience check. We can just assume it's an unknown distro
> and continue on, checking for [images-xen] and so on.. The code may
> need to be reworked a bit to accomodate this.
> 
> Although we don't do it at the moment, I could see us in the future
> using this family/variant value to check our internal db on whether
> to set up virtio and other specific settings. So using custom values
> here may not allow virt-install to choose an optimal config, but we
> should still try and let the install proceed.
> 
> - Cole
> 
> 
Cole Robinson | 5 Sep 18:32
Picon
Favicon

Re: Re: [libvirt] virt-install and custom distros

Kay Williams wrote:
> Can the issue be addressed in the upcoming virtinst release?
> 

Sure, I'll take a look at it by Monday.

Thanks,
Cole

> Cole Robinson wrote:
>> Kay Williams wrote:
>>> We have an application that builds custom distributions based on RHEL, CentOS or 
>>> Fedora.  We would like to install these over the network using virt-install, but 
>>> we've run into an issue with the distro check logic. Specifically, virt-install 
>>> fails unless it finds a string "Red Hat Enterprise Linux", "Fedora"  or "CentOS" 
>>> within the family field of the .treeinfo file.
>>>
>>> Our application currently sets the family field to the user-provided distro name 
>>> (see below).  We have avoided using the base distro name given trademark concerns.
>>>
>>>      [general]
>>>      family = <user provided value>
>>>      variant = <user provided value>
>>>
>>> We can get virt-install to pass the distro check by setting the family name to 
>>> one of the accepted values, e.g.
>>>
>>>      [general]
>>>      family = Fedora
>>>      variant = [user provided distro name]
>>>
>>> Is this the expected/desired use for the family and variant fields?  Or is there 
>>> another approach we should consider?
>>>
>>> Thanks,
>>> Kay
>> (cc-ing et-mgmt-tools, since that is the list for virt-install/
>>  virt-manager)
>>
>> We shouldn't be failing if the family/variant is unknown: it's really
>> just a convenience check. We can just assume it's an unknown distro
>> and continue on, checking for [images-xen] and so on.. The code may
>> need to be reworked a bit to accomodate this.
>>
>> Although we don't do it at the moment, I could see us in the future
>> using this family/variant value to check our internal db on whether
>> to set up virtio and other specific settings. So using custom values
>> here may not allow virt-install to choose an optimal config, but we
>> should still try and let the install proceed.
>>
>> - Cole
>>
>>
Cole Robinson | 5 Sep 23:06
Picon
Favicon

Re: [PATCH] virt-install: use --disk to specify size and sparse

Daniel P. Berrange wrote:
> On Fri, Sep 05, 2008 at 10:16:28AM -0400, Cole Robinson wrote:
>> The attached patch expands the options that can be
>> lumped onto virt-install's new --disk option to
>> specify size of new storage, and whether we want to
>> create it as sparse.
>>
>> The format for these options is:
>>
>>   --disk path=/some/new/file,size=5,sparse=true|false
>>
>> This acts similar to the current options: if the file
>> doesn't exist, size is required, and we default to
>> sparse=True if it isn't specified.
>>
>> This effectively deprecates --file, --file-size, and
>> --nonsparse, and in my opinion is much simpler. It also
>> helps overcome some problems we had with the original
>> options for cases of specifying multiple disks: there
>> was no way to specify one sparse disk and one nonsparse
>> disk, and generally specifying multiple disks was
>> unclear and a pain.
>>
>> I also added a manpage section for the --disk option.
> 
> Great - this all looks good to me.
> 
> Daniel

Thanks, I've committed this:

http://hg.et.redhat.com/virt/applications/virtinst--devel

- Cole

Gmane