ANNOUNCE: This mailing list is now closed / moved

As previously announced here

  http://www.redhat.com/archives/et-mgmt-tools/2009-July/msg00046.html

we are now closing et-mgmt-tools mailing list to any new traffic
with immediate effect.

All future postings to this list will be rejected with a message
refering users to one of the new mailing lists. For more details
read on....

This list originally came into being as a place for discussing projects
under Red Hat's 'emerging technology' moniker, hence the prefix 'et-'.
In retrospect this was a really bad choice of names for a mailing list
and causes endless confusion for people wrt what to discuss where. Most 
of the emerging technology projects have lists of their own (cobbler,
augeas, libguestfs, libvirt) and it is about time that virt-manager
and friends joined them.

To that end we have created a new mailing list  'virt-tools-list'. This
will be the new home for all developer & user discussions relating to
the following applications

  - virt-manager
  - virt-viewer
  - virt-install
  - virt-clone
  - virt-image
  - virt-convert

p2v and linux software RAID

I've got a bunch of machines I'd like to migrate to virtual machines,but
they are all running software RAID.  I found this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=465587 but wanted to check
on the status.  I found that the live CD for p2v has mdadm on it, so I
can start the RAID manually from tty2, but I can't figure out how to get
p2v to redetect the drives (and I'm not sure it will even detect the
RAID devices if I start them).   

I was wondering, what would it take to make this work?  I could split
the drives, and change the partition type from FD (RAID autodetect) to
83 (Linux).  I could then edit the fstab to look at a single drive
instead of an md device.  Would that do it or does RAID write something
else to the disk that would throw p2v off?   I'd *REALLY* love it if p2v
would just detect and use the RAID. 

The bug mentions that Rich has no hardware to test this on...I've
gotboxen o'plenty, and am willing to test if that helps.

Trey Nolen

I need your help about virt-image

Hi,all
I am working on virt-image automation testing scripts,and I get some 
information from "man virt-image" and "virt-image -h",according to these 
info, I have could install a guest by commands,like this "virt-image 
--vnc image.xml",but I don't know how to use other options?I try to do 
something, but the result are failed,and interactive mode don't be 
supported by  "virt-image --prompt image.xml" like virt-install and 
virt-clone, in addition,I want to know whether can to install 
automaticly para-virt guest by virt-image?and if I have a guest image, 
whether can to boot it by virt-image + image.xml?virt-image man page is 
too old,given example can't run well in page.I hope developer update it.

your any information are very helpful to me,and thank you very much.

Alex,
regards

ANNOUNCE: New release virtinst 0.500.0

I'm happy to announce a new virtinst release, version 0.500.0. The
release can be downloaded from:

http://virt-manager.org/download.html

The direct download link is:

http://virt-manager.org/download/sources/virtinst/virtinst-0.500.0.tar.gz

This release includes:

 - New virt-install device options --serial, --parallel, and --video
 - Allow various auth types for libvirt connections (PolicyKit, SASL, ...)
 - New virt-clone option --auto-clone: generates all needed input.
 - Option to specify network device model via virt-install --network
     (Guido Gunther)
 - New virt-install option --virt-type for specifying hypervisor type
     (kvm, qemu). --accelerate is now the default behavior: To provision a
     plain qemu VM on a KVM enabled host, use '--virt-type qemu'
 - OVF input support for virt-convert
 - Many bug fixes and improvements

Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!

Thanks,
Cole

ANNOUNCE: New release virt-manager 0.8.0

I'm happy to announce a new virt-manager release, version 0.8.0. The
release can be downloaded from:

http://virt-manager.org/download.html

The direct download link is:

http://virt-manager.org/download/sources/virt-manager/virt-manager-0.8.0.tar.gz

This release includes:

 - New 'Clone VM' Wizard
 - Improved UI, including an overhaul of the main 'manager' view
 - System tray icon for easy VM access (start, stop, view console/details)
 - Wizard for adding serial, parallel, and video devices to existing VMs.
 - CPU pinning support (Michal Novotny)
 - Ability to view and change VM security (sVirt) settings (Dan Walsh)
 - Many bug fixes and improvements

Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!

Thanks,
Cole

[PATCH] virt-manager: Add system tray icon

The attached patch adds an option for a virt-manager system tray icon. Here's
a screenshot:

http://fedorapeople.org/~crobinso/virt-manager/vmm-systray.png

The icon can be used to quit the app, or start, stop, pause, or open a VM.
Showing the icon needs to be opted in via Edit->Preferences. This should be
handy for people that keep virt-manager running for a long time, and just need
a simple interface to start/stop a VM, or open a graphical console.

Questions or comments appreciated.

Thanks,
Cole

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools

[PATCH] virt-manager: Redesigned 'New VM' wizard ver 2

Attached is an updated version of the redesigned 'New VM' wizard.
Changes since the first posting:

- Connection list shows a human readable string, rather than the full
  connection URI. Ex:

http://fedorapeople.org/~crobinso/virt-manager/newvm3/vmm-newvm-3-connlist.png

We explicitly show QEMU/KVM if the connection supports KVM. This helps
clear up the confusion that a 'qemu' connection is needed for kvm usage.

- Sparse vs. Non-sparse option added for storage. Ex:

http://fedorapeople.org/~crobinso/virt-manager/newvm3/vmm-newvm-3-sparse.png

- Distro Type/Variant detection implemented for URL installs (only fully
  works for RH distros at the moment). Ex:

http://fedorapeople.org/~crobinso/virt-manager/newvm3/vmm-newvm-3-detect.png

If the user selects a previously entered distro from the drop down, or
press activates (presses 'enter' in) the text entry, it kicks of detection.

Questions or comments appreciated.

Thanks,
Cole

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

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.

I had a few more screenshots but fedorapeople isn't
responding. The basic flow is: 'Open Conn' defaults
to selecting a local connection, so the 'browse'
checkbox and list are inactive. If a remote conn
type is selected, the 'browse' checkbox and 
'hostname' field become active, but we don't
immediately default to actually browsing the
network. Once the 'browse' checkbox is clicked the
list becomes active and starts asynchronously
populating. When an entry in the list is selected
its hostname (or IP address if the hostname wasn't
resolved) is placed in the "hostname" field.

Thanks,
Cole

# HG changeset patch
# User "Cole Robinson <crobinso@...>"
# Date 1219071936 14400
# Node ID 19528b5595715d4d2779097a44c283d7e214e725
# Parent  da5c4a5581fee539ff6bf99b1edc74d16438a279
Add avahi browsing to 'Open Connection' dialog.

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

*

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

Thanks,
Cole

diff -r 0c2ab6040585 src/virtManager/connect.py
--- a/src/virtManager/connect.py	Fri Aug 22 13:41:17 2008 -0400
+++ b/src/virtManager/connect.py	Fri Aug 22 14:51:15 2008 -0400
@@ -23,6 +23,7 @@
 import os
 import virtinst
 import logging

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:

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

Thanks,
Cole

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

*

On Mon, Aug 18, 2008 at 11:28:18AM -0400, 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.
> 
> I had a few more screenshots but fedorapeople isn't
> responding. The basic flow is: 'Open Conn' defaults
> to selecting a local connection, so the 'browse'
> checkbox and list are inactive. If a remote conn
> type is selected, the 'browse' checkbox and 
> 'hostname' field become active, but we don't
> immediately default to actually browsing the
> network. Once the 'browse' checkbox is clicked the
> list becomes active and starts asynchronously
> populating. When an entry in the list is selected
> its hostname (or IP address if the hostname wasn't
> resolved) is placed in the "hostname" field.

If the avahi daemon isn't running virt-manager isn't toohappy.
We probably need to make sure we fallback & disable this mDNS
stuff when avahi fails

Traceback (most recent call last):
  File "/home/berrange/src/xen/virt-manager--devel/src/virtManager/engine.py", line 183, in _do_show_connect
    self.show_connect()
  File "/home/berrange/src/xen/virt-manager--devel/src/virtManager/engine.py", line 248, in show_connect
    self.windowConnect = vmmConnect(self.get_config(), self)
  File "/home/berrange/src/xen/virt-manager--devel/src/virtManager/connect.py", line 91, in __init__
    self.server = dbus.Interface(self.bus.get_object("org.freedesktop.Avahi", "/")
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Avahi was not provided by any .service files

Regards,
Daniel
--

-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|