Re: [Users] Ovirt Live CD root password
On 07/07/2013 10:38 PM, Ryan Barry wrote: I am trying to install ovirt using the Live CD Image located at http://resources.ovirt.org/releases/3.2/tools/ovirt-live-1.0.iso but the install to HDD menu is prompting for root password? Could someone please point me to the root password for the installation of oVirt using install to HDD menu? Best Regards, Moto Moto, please use the oVirt Node release found here instead: http://resources.ovirt.org/releases/3.2/iso/ovirt-node-iso-2.6.1-20120228.fc18.iso that's ovirt node, not ovirt-live (which is a live cd of the engine + all-in-one). ohad - can you review original question? thanks, Itamar ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] libgovirt 0.2.0
Hey, I've just made a new release of libgovirt. libgovirt is a GObject C library to access oVirt/RHEV[1] REST API[2]. At the moment, it's able to get the list of VMs available on an oVirt instance, and to get the connection details for a given VM. This release mainly consists of internal refactoring to make it easier to support new parts of oVirt REST API, and to get it to work with older glib versions. However, it also has minor API breaks, and changes the library soname because of ABI breakage. It can be downloaded from http://people.freedesktop.org/~teuf/govirt/libgovirt-0.2.0.tar.xz It's signed with my GPG key: A525 E3EA 186A AB45 DD0F 86AF 24A4 69FB 7A56 F78E Changes since 0.1.0 - Rename OvirtVm::uuid to OvirtVm::guid to match oVirt terminology - Break ABI :( - Switch back to using GSimpleAsyncResult (from GTask) to gain compatibility with older glib versions - Refactor internals to make it much easier to add support for more REST collections - Parse more VM states from the OvirtVm resource Christophe [1] http://www.ovirt.org/Home [2] https://access.redhat.com/site/documentation//en-US/Red_Hat_Enterprise_Virtualization/3.2/html/Developer_Guide/index.html pgpGdPKYWrsi9.pgp Description: PGP signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt Live CD root password
- Original Message - > From: "Itamar Heim" > To: "Ryan Barry" > Cc: users@ovirt.org, "Ohad Basan" > Sent: Monday, July 8, 2013 1:26:22 PM > Subject: Re: [Users] Ovirt Live CD root password > > On 07/07/2013 10:38 PM, Ryan Barry wrote: > > I am trying to install ovirt using the Live CD Image located at > > http://resources.ovirt.org/releases/3.2/tools/ovirt-live-1.0.iso > > > > but the install to HDD menu is prompting for root password? > > > > Could someone please point me to the root password for the > > installation of > > oVirt using install to HDD menu? > > > > Best Regards, > > Moto > > > > > > Moto, please use the oVirt Node release found here instead: > > http://resources.ovirt.org/releases/3.2/iso/ovirt-node-iso-2.6.1-20120228.fc18.iso > > that's ovirt node, not ovirt-live (which is a live cd of the engine + > all-in-one). > ohad - can you review original question? password is "ovirt" I will add it to the wiki > > thanks, > Itamar > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] SPM and VM migrations
- Original Message - | From: "Christian Kolquist" | To: users@ovirt.org | Sent: Tuesday, July 2, 2013 11:01:55 PM | Subject: [Users] SPM and VM migrations | | I currently have an issue where when we migrate more than one VM from the | host that is the SPM to another host it will cause connectivity to the SPM | Host to fail which the ovirt engine then sees the host being down. It then | reboots the SPM Host and stops all of the VM's running on there. | | | Our setup | | Nodes: Fedora 18 | em1: ovirtmgmt (mgmt, storage and migrations) | em2: VM network trunks | | Engine: Fedora 17 (will be upgrading that to fedora 18 shortly) | | Both NICS are 1 GB. The storage is NFS which is on the same VLAN and subnet | as the hosts. The ovirt-engine is on a standalone server but is NOT on the | same vlan/subnet yet. | | Is this normal behavior for the SPM to have issue when migrating hosts to and | from it? I don't have any further network interfaces to add to the hosts at | this time (we are planning on adding a 2x 10GB card to each node in the | future but we don't have that option at this time). Is there anyway to limit | the number of active migrations and have the migrations be a lower priority | traffic than others? | | | Thanks | Christian | | | --- | This email, along with any attachments, is confidential. If you | believe you received this message in error, please contact the | sender immediately and delete all copies of the message. | Thank you. | Hi Christian, Apparently the migration is eating up your bandwidth. Currently it is possible to hard-limit the migration using The /usr/share/doc//vdsm.conf.sample file with # Maximum bandwidth for migration, in mbps, 0 means libvirt's default (30mbps?). # migration_max_bandwidth = 0 In the coming oVirt 3.3 we should be able to handle this by separating the migration network, and then use- http://www.ovirt.org/Features/Network_QoS Doron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] RAID1 mirror on ovirt-node + engine nfs server
On 07/04/2013 12:18 PM, Jason Keltz wrote: Hi. I've been reading about ovirt, and ready to try my own experiments with it. I have two small questions.. When an ovirt-node is installed from the standard ISO, there's no mention in the documentation about setting up a RAID1 mirror for the root disk on the node. I'm sure that once I get around to working out kickstarting the node, I could easily install the raid1 mirror, but I'm just wondering why I don't see that in the default ISO. Maybe I'm just missing something. Is redundancy of the disk on the node not important? Sure, if the node goes down, I guess the VMs could be run on other nodes, but if we can prevent the node from going down in the first place, then why not? If your server has hardware raid and presents the array as a single device to oVirt Node, then it should work. If it's not true hardware raid (it generates a dmraid or mdraid device), it won't work. In general, the disk image for the node is not important. The important storage is usually shared from an external system (NFS, iSCSI, FC). Installation/Re-installation is usually very easy to do, so Raid arrays of local disks in oVirt Node was not a requirement. We may add support for this in the future (or will accept patches adding support), but it was not an important enough requirement previously. As for Engine...I'll defer that to the people who know engine better... Mike I also have a question about the storage backend. In particular, I have a pretty powerful server that I intend to use as the NFS server, and a few servers to use as nodes. On the other hand, I don't have a powerful machine (at the moment) to use for the ovirt-engine. Would it be poor practice to run the ovirt-engine ON the NFS server? During engine setup, I see that you can setup an NFS share for ISOs from the ovirt-engine, but I don't think there's mention of just generalized storage there. I suspect it's "poor practice", but I thought I'd ask anyway. My setup will be relatively small (say, 4 nodes), and this would let me reduce 1 general server from the infrastructure (dedicated ovirt-engine). Thanks! :) Jason. ps: At the moment, I am not subscribed to users - please cc: me on responses. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] ovirt-engine-sdk-java 1.0.0.10-1 released
* Thu Jul 8 2013 Michael Pasternak - 1.0.0.10-1 - to cluster.add()/.update() added [trusted_service] property - implement Secure Socket Layer (SSL) host verification (CA certificate) - allow nullifying headers via passing NULL as header value More details can be found at [1]. [1] http://www.ovirt.org/Java-sdk-changelog -- Michael Pasternak RedHat, ENG-Virtualization R&D ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [URGENT]
Hi, I need to get ovirt to production as my XEN environment is falling apart. I've been dealing with the problem of been unable to run any VM on the updated- reinstalled ovirt from 3.1 to 3.2 Any VM I try to start exits with this error: VM SambaDC1 is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC . The VMs are centos 6.4 and were fresh installed in each VM iscsi LUN while using 3.1 but though I deleted the original VMs (purged the database with engine-cleanup as part of the reinstall process) and created them in 3.2, it fails to work. Please let me know what info I need to get this running. Regards, Juan Pablo Lorier ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [URGENT]
Juan Pablo Lorier wrote: Hi, I need to get ovirt to production as my XEN environment is falling apart. I've been dealing with the problem of been unable to run any VM on the updated- reinstalled ovirt from 3.1 to 3.2 Any VM I try to start exits with this error: VM SambaDC1 is down. Exit message: internal error process exited while connecting to monitor: Supported machines are: pc RHEL 6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default) rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC rhel5.4.0 RHEL 5.4.0 PC . The VMs are centos 6.4 and were fresh installed in each VM iscsi LUN while using 3.1 but though I deleted the original VMs (purged the database with engine-cleanup as part of the reinstall process) and created them in 3.2, it fails to work. Please let me know what info I need to get this running. Regards, From a thread from a couple of days back: our host is EL, and engine sends non-EL values for 'emulatedMachine' are you using engine from latest master? if so, you need to select for the cluster the correct emulated machine (rhel 6.4) if not, change with ovirt-config the "EmulatedMachine" value to rhel6.4.0 for the right cluster compatibility version (i assume 3.3 or 3.2) engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.3 Look at the cluster version of your installation and adapt the above. run a engine-config -g EmulatedMachine first and make sure you have backups. Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
