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 da_merlin over 12 years ago
Any specific reasons you want to have paravirtual support?

For paravirtual support, remove lines kernel, builder and boot. Then add the following lines:
bootloader = "/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda1:/boot/vmlinuz,/boot/initrd"
extra="root=/dev/disk/by-label/root rootflags=data=ordered"

To access the console, you have to edit /etc/inittab within the virtual UTM
and replace "tty1" by "hvc0".

Cheers
Ulrich
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 da_merlin over 12 years ago
Any specific reasons you want to have paravirtual support?

For paravirtual support, remove lines kernel, builder and boot. Then add the following lines:
bootloader = "/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda1:/boot/vmlinuz,/boot/initrd"
extra="root=/dev/disk/by-label/root rootflags=data=ordered"

To access the console, you have to edit /etc/inittab within the virtual UTM
and replace "tty1" by "hvc0".

Cheers
Ulrich
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Goodwin over 12 years ago in reply to da_merlin

Thank You.
Paravirtual drivers should deliver much better prerformance for network, disks, etc...

According to the change, you mean before I start the instance in paravirtual mode, I should edit the given file? Will this then work again with full virtualizatiobn? Can it be configured so, it supports both? I am not so deep in such low-level stuff...
Cancel
Vote Up 0 Vote Down

Cancel
0 Goodwin over 12 years ago in reply to Goodwin

Thank You.
Paravirtual drivers should deliver much better prerformance for network, disks, etc...

According to the change, you mean before I start the instance in paravirtual mode, I should edit the given file? Will this then work again with full virtualizatiobn? Can it be configured so, it supports both? I am not so deep in such low-level stuff...

Also the shutdown from the Xen environment should theoretically work then (in paravirt mode) as well as the better monitoring of the devices, etc...
Cancel
Vote Up 0 Vote Down

Cancel

0 Goodwin over 12 years ago in reply to da_merlin

Any specific reasons you want to have paravirtual support?

For paravirtual support, remove lines kernel, builder and boot. Then add the following lines:
bootloader = "/usr/lib/xen/boot/domUloader.py"

bootargs="--entry=xvda1:/boot/vmlinuz,/boot/initrd"

extra="root=/dev/disk/by-label/root rootflags=data=ordered"
To access the console, you have to edit /etc/inittab within the virtual UTM
and replace "tty1" by "hvc0".

Cheers
Ulrich

Hello,since domUloader.py is a SUSE specific way, and I use Debian, Ihad to use pygrub instead...

But I have independently on the fact which loader is specified following error if trying to start the domain:


Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')

and in the xend.log I can see following:


[2012-10-23 15:33:09 3924] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm', ['name', 'vun-acc-1.v4'], ['memory', '1024'], ['on_po

weroff', 'destroy'], ['on_reboot', 'restart'], ['on_xend_start', 'start'], ['on_xend_stop', 'shutdown'], ['vcpus', 1], ['localtime', 1],

 ['oos', 1], ['bootloader', '/usr/lib/xen/bin/pygrub'], ['bootloader_args', '--entry=xvda1:/boot/vmlinuz,/boot/initrd'], ['image', ['lin

ux', ['videoram', 4], ['args', 'root=/dev/disk/by-label/root rootflags=data=ordered'], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integri

ty', 1], ['device', ['vbd', ['uname', 'phy:/dev/VG_MAIN/DomU.vun-acc-1.v4.DISK1'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vif', [

'bridge', 'perbr'], ['model', 'e1000'], ['mac', '00:16:3e:01:e2:00']]]])

[2012-10-23 15:33:09 3924] DEBUG (XendDomainInfo:2508) XendDomainInfo.constructDomain

[2012-10-23 15:33:09 3924] DEBUG (balloon:220) Balloon: 8331548 KiB free; need 16384; done.

[2012-10-23 15:33:09 3924] DEBUG (XendDomain:464) Adding Domain: 49

[2012-10-23 15:33:09 3924] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 49 256

[2012-10-23 15:33:09 20439] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen/bin/pygrub', '--args=root=/dev/disk/by-lab

el/root rootflags=data=ordered', '--output=/var/run/xend/boot/xenbl.4941', '--entry=xvda1:/boot/vmlinuz,/boot/initrd', '/dev/VG_MAIN/Dom

U.vun-acc-1.v4.DISK1'].

[2012-10-23 15:33:09 3924] DEBUG (XendDomainInfo:2845) _initDomain:shadow_memory=0x0, memory_static_max=0x40000000, memory_static_min=0x

0.

[2012-10-23 15:33:09 3924] INFO (image:182) buildDomain os=linux dom=49 vcpus=1

[2012-10-23 15:33:09 3924] DEBUG (image:721) domid          = 49

[2012-10-23 15:33:09 3924] DEBUG (image:722) memsize        = 1024

[2012-10-23 15:33:10 3924] DEBUG (image:723) image          = /var/run/xend/boot/boot_kernel.xtw9w_

[2012-10-23 15:33:10 3924] DEBUG (image:724) store_evtchn   = 1

[2012-10-23 15:33:10 3924] DEBUG (image:725) console_evtchn = 2

[2012-10-23 15:33:10 3924] DEBUG (image:726) cmdline        = root=/dev/disk/by-label/root vga=791 rootflags=data=ordered splash=silent

root=/dev/disk/by-label/root rootflags=data=ordered

[2012-10-23 15:33:10 3924] DEBUG (image:727) ramdisk        = /var/run/xend/boot/boot_ramdisk.g443y-

[2012-10-23 15:33:10 3924] DEBUG (image:728) vcpus          = 1

[2012-10-23 15:33:10 3924] DEBUG (image:729) features       =

[2012-10-23 15:33:10 3924] DEBUG (image:730) flags          = 0

[2012-10-23 15:33:10 3924] DEBUG (image:731) superpages     = 0

[2012-10-23 15:33:10 3924] ERROR (XendDomainInfo:2909) XendDomainInfo.initDomain: exception occurred

Traceback (most recent call last):

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2880, in _initDomain

    channel_details = self.image.createImage()

  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 165, in createImage

    return self.createDomain()

  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 184, in createDomain

    result = self.buildDomain()

  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 1069, in buildDomain

    rc = LinuxImageHandler.buildDomain(self)

  File "/usr/lib/xen-4.0/lib/python/xen/xend/image.py", line 745, in buildDomain

    superpages     = self.superpages)

Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')

[2012-10-23 15:33:10 3924] ERROR (XendDomainInfo:483) VM start failed

Traceback (most recent call last):

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 469, in start

    XendTask.log_progress(31, 60, self._initDomain)

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py", line 209, in log_progress

    retval = func(*args, **kwds)

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2912, in _initDomain

    raise VmError(str(exn))

VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')

[2012-10-23 15:33:10 3924] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: domid=49

[2012-10-23 15:33:10 3924] DEBUG (XendDomainInfo:2411) Destroying device model

[2012-10-23 15:33:10 3924] DEBUG (XendDomainInfo:2418) Releasing devices

[2012-10-23 15:33:10 3924] ERROR (XendDomainInfo:106) Domain construction failed

Traceback (most recent call last):

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 104, in create

    vm.start()

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 469, in start

    XendTask.log_progress(31, 60, self._initDomain)

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py", line 209, in log_progress

    retval = func(*args, **kwds)

  File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2912, in _initDomain

    raise VmError(str(exn))

VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')

I donot know,if the problem cannot be caused by the fact, I just use the hvm installed domain,which takes the given LVM drive and uses it like a disk, not like a partition - there are all Astaro partitions on it...
No Idea how to configure the instance and pygrub to use such data scheme...
Is there any way how to install Astaro on concrete partitions without automatically partitioning the disk?

0 zdzisekg over 12 years ago in reply to da_merlin
Any specific reasons you want to have paravirtual support?

For paravirtual support, remove lines kernel, builder and boot. Then add the following lines:
bootloader = "/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda1:/boot/vmlinuz,/boot/initrd"
extra="root=/dev/disk/by-label/root rootflags=data=ordered"

To access the console, you have to edit /etc/inittab within the virtual UTM
and replace "tty1" by "hvc0".

Cheers
Ulrich

I trying to setup ASG as a fully paravirtualized install so I can passthrough my nic for this reason.

I'm using opensuse 12.3 and xen. I can install in hvm mode, but am not able to install in pvm.

I also tried to convert fvm to pvm per your instructions above, but that does not seem to work for me. As I am on opensuse, I've tried both pvm bootloaders domUloader.py and pygrub. With domUloader.py, I just get "bootloader returned no data" error and not much else. With pygrub, the domU aborts right after start with little more logging.

I'm trying to get going with asg-9.1beta.

Any help is greatly appreciated. Thanks.
Cancel
Vote Up 0 Vote Down

Cancel