Known issues in SUSE Studio

From openSUSE

    Start   FAQ   Tour   Howto    API   Bugs   Support   Download     

Give feeback, report bugs!

• SUSE Studio provides a Send feedback link in the upper left corner.
  We will be happy if you send us short notes describing your problems. Your notes that your are a happy user are also welcome.
  
  Please use this feedback feature to report bugs.
  Our QA people will take care and create bugs in the Novell bugzilla tool.
  
  
• Note! If you own admin status you will see a Report bug link in the header. This link will work only for Novell employees and other selected people that have access to the internal bugzilla list.

Known Issues in SUSE Studio

Hardware changing on usb and vmx

• Hardware will be detected on firstboot. If you boot an appliance from an USB stick or from a vmware machine, and then you copy that and try to boot it on another machine, we may enconter problems with hardware, like having multiple ethernets configured. The best solution is to distribute the image that it has not been booted. If you want to make changes before distributing it , see How to change configurations on disc image and How to change configurations on vmware disc .

Not booting from usb

• It has been reported that on some machines the USB does not boot, or does boot once but the second time does not. See How to make the usb drive bootable to solve that.

• in case the Error message is "Grub Error 17" then the reason for your problem is that the partitions got changed upon the first boot to utilize all the usb disks space but grub was not rewritten and thus can't find its stage2.

A fix for the problem is to add the grub package to the appliance and rebuild it

Booting from usb but experiencing some weird problems

• In some cases, when the USB stick or the disc image contains a previous system, using dd to copy the image is not enough. See how to copy the image into the USB drive to see how to clean it before.
• Tip: It is also reported that some defect USB keys will not show problems with files but with whole systems. We recommend to create an MD5SUM from your image file before copying it onto the USB key to be able to re-check the transfer of data afterwards.

Testdrive timeout error

• Some users report time out errors with testdrive: Try to open some closed ports.

LAMP server doesn't work on LiveCD

• Running an Apache server on the LiveCD exhibits odd behaviour (Apache returns HTTP 206 "Partial Content" for a number of bits of content and the resulting pages are broken).
• Some users report success using a 3rd party server.

Xen issues

• SLE11 xen packages. The current update packages for xen do not properly work. In case you see the xend freeze upon creating a studio guest you most likely hit this problem. try to use the shipped SLE11 packages instead.

• pygrub support. Xen guests built in studio use pygrub for bootin which makes it mandatory that the host system supports pygrub. This is not the case especially for older systems like SLE10. The error message displayed in such a case: "error: bootloader isn't executable".

• X11 in xen guests does not work due to missing /dev/tty0

• The xenconfig file needs to be edited before creating a guest. Currently there are three entries in the .xenconfig file that comes with a guest that need to be adjusted:
  • disk entry: Xen wants an absolute path for its image location, it won't accept a relative entry. So you neede to edit the location of the image according to where it's on your disk
  • tap:aio entry: in rare cases after a failed guest creation attempt another guest can't be created due to tap:aio. try to change "tap:aio" to "file" in such cases
  • network setup: The vif entry (virtual network) requires the host system to have a bridge set up called "xenbr0". At least in Dom0 appliances created with Studio this bridge is not created automatically. You can either remove the entry from the config file or create the required bridge with 'brctl addbr xenbr0'