virt January 2012

virt@lists.centos.org

37 participants
23 discussions

server host keys for kvm clones
by James B. Byrne 05 Jan '12

05 Jan '12

Respecting cloning vm guests, I see in /etc/ssh the following: ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub Is there a simple script somewhere to regenerate all the server host keys for the new guest after cloning? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

7 14

turning off udev for eth0
by James B. Byrne 04 Jan '12

04 Jan '12

I have set up a kvm host and configured a standard clone prototype for generating new guests. One persistent (pun intended) annoyance when cloning is the behaviour of udev with respect to the virtual network interface. The prototype is configured with just eth0 having a dedicated IP addr. When the prototype is cloned udev creates rules for both eth0 and eth1 in the clone. Because eth1 does not exist in the cloned guest one has to manually edit /etc/udev/rules.d/70-persistent-net.rules to get rid of the bogus entries and then restart the clone instance to have the changes take effect. All this does is return the new guest to the prototype eth0 configuration. Is there no way to alter udev's behaviour? Is udev even needed on a server system using virtual hardware? Altering the rules file not a big deal in itself but it adds needless busywork when setting up a new guest. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

iscsi target rescan means connections hang for five seconds
by Dennis Jacobfeuerborn 03 Jan '12

03 Jan '12

Hi, I'm starting to experiment with iscsi based volumes and while this works fine so far I ran into a problem. When I add a LUN to a target and refresh tgtd all i/o to that target seems to hang for five seconds. This is obviously less than ideal if the plan is to use the target for lots of guests. There is also the possibility to create one target with one LUN for each guest disk but that sounds like a management nightmare and the libvirt pool functions become useless. Is there a way to make this less intrusive? How do you guys cope with this issue? Regards, Dennis

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt January 2012