WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Cloning VM from Xen

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Cloning VM from Xen
From: Benjamin Knoth <knoth@xxxxxxxxxxx>
Date: Fri, 20 Aug 2010 14:02:14 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Aug 2010 05:07:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=VfC-qdYGo7dqm3Ss_hoLKZ4Fbfs=6K96cze0j@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <8CBB53B8098D4544A6FF75CFFAD77DF2CA3C0C@xxxxxxxxxxxxxxxxxxxxx> <4C6D3C0F.80701@xxxxxxxxxxx> <AANLkTim0sBfAexN=BT16TfvvKx3ydf16q3nYPq=6Rr6d@xxxxxxxxxxxxxx> <4C6E3DCC.4060600@xxxxxxxxxxx> <AANLkTi=VfC-qdYGo7dqm3Ss_hoLKZ4Fbfs=6K96cze0j@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
Hi

Am 20.08.2010 13:20, schrieb Fajar A. Nugraha:
On Fri, Aug 20, 2010 at 3:33 PM, Benjamin Knoth <knoth@xxxxxxxxxxx> wrote:
If i start brctl show i get on both server this with other interface
numbers.

bridge name    bridge id        STP enabled    interfaces
eth0        8000.001d096deb32    no        peth0
                                                                vif56.0
                                                                vif8.0
                                                                vif4.0
So your dom0 bridge name is eth0. Remember that.

VM on SLES 11


xm_vars.check()


#kernel = "/boot/vmlinuz-xen"
kernel = "/boot/vmlinuz-2.6.16.60-0.34-xen"
ramdisk = "/boot/initrd-2.6.16.60-0.34-xen"
#ramdisk = "/boot/initrd-xen"
You need to copy original vmlinuz-xen and initrd-xen from old server,
and use that.
Do you still have module loading issue with kernel and initrd from the
old server?
On the old server i haven't issues with kernel or initrd.
I copied the the old kernel and initrd to sles 11 changed the entry in the config to
kernel = "/boot/vmlinuz-2.6.16.60-0.23-xen"
ramdisk = "/boot/initrd-2.6.16.60-0.23-xen"
and changed the bridge to eth0.



      
vif = [ 'mac=00:16:3e:00:00:d5, bridge=br0', ]
change the bridge to eth0. That's what "brctl show" says.

netmask="255.255.255.0"
# Set default gateway.
gateway="134.76.28.254"
hostname="vm35"
irrelevant, as domU sets its own hostname and networking parameters.
Might as well delete those lines.

But if i boot with the modified config, old kernel and initrd i find some failed on boot log

Setting up the hardware clockCannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
                                                                     failed
Setting up network interfaces:
    lo       
    lo        IP address: 127.0.0.1/8  
Checking for network time protocol daemon (NTPD):                    unused
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver                                      done
    eth1     
              No configuration found for eth1                        unused
Waiting for mandatory devices:  eth-id-00:16:3e:00:00:12 __NSC__
19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
    eth-id-00:16:3e:00:00:12            No interface found           failed
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . failed



On my config the entry is vif = [ 'mac=00:16:3e:00:00:d5, bridge=eth0', ].
On boot i see eth-id-00:16:3e:00:00:12 which is the mac of the old network device. In YaST i get the same device with mac.

best regards

Benjamin
-- 
Benjamin Knoth
Max Planck Digital Library (MPDL)
Systemadministration
Amalienstrasse 33
80799 Munich, Germany
http://www.mpdl.mpg.de

Mail: knoth@xxxxxxxxxxx
Phone:  +49 89 38602 202
Fax:    +49-89-38602-280
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users