#1753 Issue `closed`: Unable to do rear restore with XEN¶

Labels: support / question, fixed / solved / done

rakon2 opened issue at 2018-03-10 10:29:¶

Relax-and-Recover (ReaR) Issue Template¶

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

rear version (/usr/sbin/rear -V):
rear-2.3-1.x86_64.rpm
OS version (cat /etc/rear/os.conf or lsb_release -a):

cluster-box2:/tmp/rear # cat /etc/SuS*
SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 3
# This file is deprecated and will be removed in a future service pack or release.
# Please check /etc/os-release for details about this release.
cluster-box2:/tmp/rear #

rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):

cluster-box2:/tmp/rear # cat /etc/rear/local.conf
OUTPUT=ISO
MODULES_LOAD=(autofs4 scsi_mod scsi_dh_alua scsi_dh_emc scsi_dh_rdac dm_mod dm_multipath sg usb_common usbcore libata libahci ahci ehci_hcd crc32c_intel ohci_hcd ehci_p
ci ohci_pci us \
bhid hid_generic sd_mod cdrom sr_mod raid6_pq xor btrfs xen_privcmd sunrpc xenfs grace lockd nfs_acl auth_rpcgss nfsd ac97_bus i2c_piix4 e1000 parport processor button 
\ video ac battery fjes soundcore parport_pc serio_raw snd snd_timer ppdev pcspkr snd_pcm joydev snd_ac97_codec snd_intel8x0 dm_service_time xen_evtchn xen_gntdev xen_g
nt alloc xen_blkback xen_netback xen_pciback iscsi_boot_sysfs iscsi_ibft llc stp bridge br_netfilter af_packet x_tables ip_tables iptable_filter ip6_tables ip6table_fil
ter )
BACKUP=NETFS
BACKUP_OPTIONS="nfsvers=3,nolock"
BACKUP_URL=nfs://192.168.56.4/reardata
REQUIRED_PROGS=( "${REQUIRED_PROGS[@]}" snapper chattr lsattr )
COPY_AS_IS=( "${COPY_AS_IS[@]}" /usr/lib/snapper/installation-helper /etc/snapper/config-templates/default )
BACKUP_PROG_INCLUDE=( '/var/cache/*' '/var/lib/mailman/*' '/var/tmp/*' '/var/lib/pgsql/*' '/usr/local/*' '/opt/*' '/var/lib/libvirt/images/*' '/boot/grub2/i386/*' '/var
/opt/*' '/srv/*' '/boot/grub2/x86_64/*' '/var/lib/mariadb/*' '/var/spool/*' '/var/lib/mysql/*' '/tmp/*' '/home/*' '/var/log/*' '/var/lib/named/*' '/var/lib/machines/*' 
'/.snapshots/*'  '/var/crash/*' )

Are you using legacy BIOS or UEFI boot?
BIOS and also UEFI
Brief description of the issue:

unable to create xl create it shows vm created but no vm create below is the log found

2018-03-05T11:49:40.551751+05:30 cluster-box2 root: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/51712
2018-03-05T11:49:41.411844+05:30 cluster-box2 root: /etc/xen/scripts/block: Writing backend/vbd/4/51712/physical-device 8:10 to xenstore.
2018-03-05T11:49:41.421337+05:30 cluster-box2 root: /etc/xen/scripts/block: Writing backend/vbd/4/51712/physical-device-path /dev/sdb to xenstore.
2018-03-05T11:49:41.431562+05:30 cluster-box2 root: /etc/xen/scripts/block: Writing backend/vbd/4/51712/hotplug-status connected to xenstore.
2018-03-05T11:49:46.853247+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/4/0
2018-03-05T11:49:47.442821+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif4.0, bridge br0.
2018-03-05T11:49:47.466905+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: Writing backend/vif/4/0/hotplug-status connected to xenstore.
2018-03-05T11:49:47.605549+05:30 cluster-box2 kernel: [ 1609.839484] device vif4.0 entered promiscuous mode
2018-03-05T11:49:47.605604+05:30 cluster-box2 kernel: [ 1609.843350] IPv6: ADDRCONF(NETDEV_UP): vif4.0: link is not ready
2018-03-05T11:49:47.669175+05:30 cluster-box2 kernel: [ 1610.069449] br0: port 2(vif4.0) entered disabled state
2018-03-05T11:49:47.669227+05:30 cluster-box2 kernel: [ 1610.069499] device vif4.0 left promiscuous mode
2018-03-05T11:49:47.669237+05:30 cluster-box2 kernel: [ 1610.069500] br0: port 2(vif4.0) entered disabled state
2018-03-05T11:49:47.806153+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/4/0
2018-03-05T11:49:47.806244+05:30 cluster-box2 root: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/51712
2018-03-05T11:49:48.512181+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: brctl delif br0 vif4.0 failed
2018-03-05T11:49:48.726424+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 down failed
2018-03-05T11:49:48.731996+05:30 cluster-box2 root: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif4.0, bridge br0.

Also while taking backup below line found
Driver 'xennet' for 'eth0' not loaded - is that okay? for rear

Work-around, if any:
No work around found so far .

jsmeix commented at 2018-03-12 08:43:¶

@rakon2
I do not understand what exactly you are talking about.
I only notice xen in what you wrote above.
I do not use XEN so that I cannot help with XEN related issues.

I know that XEN and ReaR could be somewhat special,
cf. the section "Virtual machines" in
https://en.opensuse.org/SDB:Disaster_Recovery

In general regarding debugging issues with ReaR
see "Debugging issues with Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery

rakon2 commented at 2018-03-30 03:26:¶

Thanks a lot this was about backup and restore for xen virtual machine this
issue has been rectified .

Thanks And Regards
Sunil KJ

On Mon 12 Mar, 2018, 2:13 PM Johannes Meixner, notifications@github.com
wrote:

@rakon2 https://github.com/rakon2
I do not understand what exactly you are talking about.
I only notice xen in what you wrote above.
I do not use XEN so that I cannot help with XEN related issues.

I know that XEN and ReaR could be somewhat special,
cf. the section "Virtual machines" in
https://en.opensuse.org/SDB:Disaster_Recovery

In general regarding debugging issues with ReaR
see "Debugging issues with Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rear/rear/issues/1753#issuecomment-372231775, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AjV-SdQP_vndmgNcySS4ebbUpBovK2FXks5tdjUpgaJpZM4SlOem
.

jsmeix commented at 2018-04-03 10:12:¶

@rakon2
thanks for your feedback!

[Export of Github issue for rear/rear.]