Am 05. Nov, 2011 schwätzte Benjamin Browning so:
On Fri, Nov 4, 2011 at 5:34 PM, der.hans pl...@lufthans.com wrote:
The clone notices that it's no longer on the same (virtual) hardware, so
udev rules move to a new networking device, but the networking rules don't
get updated. In other words,
On Fri, Nov 4, 2011 at 5:34 PM, der.hans pl...@lufthans.com wrote:
The clone notices that it's no longer on the same (virtual) hardware, so
udev rules move to a new networking device, but the networking rules don't
get updated. In other words, no networking, so no talking to the dhcp
server.
There are managed switches that are designed to prevent the migration
pains, but they tend to be spendy. I tend to build from clone without
networking and configure it after I can get to the guest os. Or use
kickstart, but then you don't exactly have a clone.
On Nov 5, 2011 9:42 AM, Benjamin
Am 03. Nov, 2011 schwätzte James Crawford so:
I can't think of a virsh command that would return the IP of the guest.
Are you using DHCP to assign the Guest IP?
Ask dhcpd server.
That isn't working, but that's due to udev rules that don't make sense for
VMen.
The clone notices that it's
I can't think of a virsh command that would return the IP of the guest.
Are you using DHCP to assign the Guest IP?
Ask dhcpd server.
We setup Static IP when we build the guests, so I keep it on a spreadsheet.
Of course we only have 14 Guest across 4 Host servers.
James Crawford
Am 03. Nov, 2011 schwätzte James Crawford so:
moin moin,
I can't think of a virsh command that would return the IP of the guest.
Are you using DHCP to assign the Guest IP?
Ask dhcpd server.
True. Good idea. I should be able to script that somewhat easily.
It seems logical that if the
moin moin,
is there a way from virsh to see actual networking for a qemu/kvm guest?
I can use dumpxml to pull the interface stanza and get the guest's MAC
addy, then look at the arp cache ( ip neighbor show or arp -a ) to find
the address associated with the MAC.
However, what if the guest has
