This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Xen Support

I have searched the forums for a definitive answer to this and have not found one. Currently running Xen 4.x on SLES 11 sp2. What I am trying to find out is if astaro is supported running on this platform. I have tried the following.

I have tried with both 8.3.x installer and 9.x.

1. Install as a HVM using any type of network adapter whether full or para
virtualized will hang the installer at finding network adapters. It hard locks.

2. Attempt to install as paravirtualized os just hangs upon booting the cd. I am using the iso to install from saying it is not a supported boot device or something like that.

I have tried as sles 11 and also as other for the type of virtual machine.

Thank you for any advice.

This thread was automatically locked due to age.

Parents

0 warper over 12 years ago

I just tried the newest iso available for version 9. Same issue that hangs when " Detecting Network Devices".
Cancel
Vote Up 0 Vote Down

Cancel
0 Goodwin over 12 years ago in reply to warper
Hello,
I have found, I have downloaded the 8.003 ISO one year ago and still did not delete it... But I would propose, Astaro (Sophos) could place the 8.003 version again on the ftp server for people,who want toinstall the firewall in Xen envronment,until the problems in the installer in version 9 are fixed...

For such people one more advice: it is absolutely necessary to specify in the virutal instance configuration file for every network interface also the MAC address.
In version 7.5 there it was OK to let the MAC generate by Xen, the interfaces have been assigned in the order how the HW has been found, so even if Xen generated different MAC for address after the domain shutdown and start, this has caused no
problem.
In version 8.003 there came a new paradigm - now the udev stuff is handling the identification of network interfaces based on MAC addresses. So, if there is not specified the MAC address in the vif configuration - something like this:

vif = [
             'type=ioemu, model=e1000, bridge=eth0',
             'type=ioemu, model=e1000, bridge=locbr',
             'type=ioemu, model=e1000, bridge=perbr',
      ]

what was completely OK for ASG 7.5xx, then already after first reboot after installation all network interfaces are regenerated with new MAC addresses what leads to the creation of new ethX interfaces, what implies the impossibility to install ASG under Xen at all (the eth0 interface configured during the installation from iso does not physically exist after the first reboot, the same interface is now in ASG recognized like eth2 - if there were only 2 NIC defined - because of its new MAC, after the next reboot again otherwise - like eth4, etc.)

Correctly specified vif setting in the VM configuration file for 8.x ASG underXen should look like

vif = [
             'type=ioemu, model=e1000, bridge=eth0, mac=00:16:3e:01:eb:00',
             'type=ioemu, model=e1000, bridge=locbr, mac=00:16:3e:01:eb:01',
             'type=ioemu, model=e1000, bridge=perbr, mac=00:16:3e:01:eb:02',
      ]
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Goodwin over 12 years ago in reply to warper
Hello,
I have found, I have downloaded the 8.003 ISO one year ago and still did not delete it... But I would propose, Astaro (Sophos) could place the 8.003 version again on the ftp server for people,who want toinstall the firewall in Xen envronment,until the problems in the installer in version 9 are fixed...

For such people one more advice: it is absolutely necessary to specify in the virutal instance configuration file for every network interface also the MAC address.
In version 7.5 there it was OK to let the MAC generate by Xen, the interfaces have been assigned in the order how the HW has been found, so even if Xen generated different MAC for address after the domain shutdown and start, this has caused no
problem.
In version 8.003 there came a new paradigm - now the udev stuff is handling the identification of network interfaces based on MAC addresses. So, if there is not specified the MAC address in the vif configuration - something like this:

vif = [
             'type=ioemu, model=e1000, bridge=eth0',
             'type=ioemu, model=e1000, bridge=locbr',
             'type=ioemu, model=e1000, bridge=perbr',
      ]

what was completely OK for ASG 7.5xx, then already after first reboot after installation all network interfaces are regenerated with new MAC addresses what leads to the creation of new ethX interfaces, what implies the impossibility to install ASG under Xen at all (the eth0 interface configured during the installation from iso does not physically exist after the first reboot, the same interface is now in ASG recognized like eth2 - if there were only 2 NIC defined - because of its new MAC, after the next reboot again otherwise - like eth4, etc.)

Correctly specified vif setting in the VM configuration file for 8.x ASG underXen should look like

vif = [
             'type=ioemu, model=e1000, bridge=eth0, mac=00:16:3e:01:eb:00',
             'type=ioemu, model=e1000, bridge=locbr, mac=00:16:3e:01:eb:01',
             'type=ioemu, model=e1000, bridge=perbr, mac=00:16:3e:01:eb:02',
      ]
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data