December 2008 - openSUSE Virtual - openSUSE Mailing Lists

Re: [opensuse-virtual] OS 11.1 xen boot fails if xend-config.sxp configured to use non-default "(network-script )"
by Jason Douglas 06 Jan '09

06 Jan '09

>>> On 12/29/2008 at 11:56 PM, in message <dbd51810812292256t32d895fbwe1f9ea7677189b34(a)mail.gmail.com>, PGNet <pgnet.trash(a)gmail.com> wrote: > Hi Jason, > As a 1st step, I'd best clearly understand what's changed. Can you > perhaps point to whatever documents that fact, &/or details the > changes & preferred method? I certainly haven;t found it yet :-/ > I don't know if any official documentation exists yet. There was a bug opened to get documentation created for this, but it is still open. However, there is some explanation in the bug: https://bugzilla.novell.com/show_bug.cgi?id=432709 > So only via the yast gui (curses based, I'd gather, as I'm on a > text-only, headless install ...) ? That's correct. It works the same with or without the GUI. > > Ideally, I'd like to understand the "new, right way" to configure > multiple bridges using some sort of gui-less script ... even if it > requires some customization. > To understand the reasons for the change, you need to understand a little about how the xen network-bridge script works. When that script is being used, openSUSE boots up and configures the networking in its usual way. Then, xend comes along and calls the network-bridge script which proceeds to examine the network configuration, rip it out, and set it up again using a bridge. With this method, the distributions networking scripts know nothing about the changes that network-bridge made as those changes were made outside of the distros networking framework. This results in numerous potential problems such as a complete breakdown when restarting the network ("rcnetwork restart"), for example. Therefore, beginning with openSUSE 11.1 and SLES 11, the xen networking scripts are disabled by default, and functionality has been added to yast to handle bridged network configurations. This way the networking is setup correctly the first time (no rip and replace after boot time) and functionality such as restarting the network works as expected. There is no need for any sort of special script because you configure the networking once, just like you normally would when installing openSUSE without XEN. The difference is that you either a) accept the default bridged networking proposal, or b) make customizations that more closely mirror your needs. In your case, where you already have a non-bridge network configuration, you might want to try running the "Install Hypervisor and Tools" yast module. This will setup the default bridged networking configuration and you could use it as a reference for how things should look. Sorry I don't know of any place that this is documented. Let me know if you have any other questions. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 5

[opensuse-virtual] OS 11.1 xen boot fails if xend-config.sxp configured to use non-default "(network-script )"
by PGNet 29 Dec '08

29 Dec '08

standard install of OS 11.1 boots correctly to, uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux installing Xen33x, configured with, cat /etc/xen/xend-config.sxp (logfile /var/log/xen/xend.log) (loglevel DEBUG) ... (network-script ) (vif-script vif-bridge) ... boots to 'kernel-xen', uname -a Linux server 2.6.27.7-9-xen #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux changing to an external network script, which works on OS 11.0 + Xen 32x, cat /etc/xen/xend-config.sxp (logfile /var/log/xen/xend.log) (loglevel DEBUG) ... # (network-script ) # (vif-script vif-bridge) (network-script custom-bridge) ... cat /etc/xen/scripts/custom-bridge #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 bridge=br01 netdev=eth0 "$dir/vif-bridge" vifnum=0 bridge=br01 netdev=eth0 ip link set br01 up then reboot to 'kernel-xen', startup hangs in console @ "setting up loopback interface lo" and proceeds no further ... reboot to 'kernel', checking xen log, it's empty :-/ -rw-r--r-- 1 root root 0 2008-12-24 09:58 xend.log Ideas? Thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 1

[opensuse-virtual] xen/kernel-xen on OS 11.1 not starting; OK on 11.0
by PGNet 24 Dec '08

24 Dec '08

i've been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- not working, and not clear as to why not, yet. i've partitioned, as always, as RAID-1 across two disks, sda + sdb, each part1 150 MB, LinuxRaid part2 10 GB, LinuxRaid part3 *, LinuxRaid RAID-1 /dev/md0 = sda1 + sdb1, mount_pt = '/boot', ext3 /dev/md1 = sda2 + sdb2 Volume Group "System" Logical Volume "Swap", mount_pt = 'swap', 512 MB, Logical Volume "Root", mount_pt = '/', * /dev/md2 = sda3 + sdb3 with this setup, boot to non-xen kernel works perfectly, as it did on OpenSuse 11.0, uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux lsb_release -r Release: 11.1 i've installed zypper in -t pattern xen-server rpm -qa | grep -i xen kernel-xen-base-2.6.27.7-9.1 xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 kernel-xen-2.6.27.7-9.1 kernel-xen-extra-2.6.27.7-9.1 xen-3.3.1_18494_03-1.8 on attempt to boot to xen kernel, it fails ... @ boot console I see mention of '/var' not available scroll quickly by, and something about fsck.ext3 failing ... then i'm dumped @ a console prompt. i *can* login, but ... /var exists and is populated, but nothing is written to /var/log/xen/xend.log or /var/log/messages. /boot exists, but is completely empty (?). rebooting, I can get back to non-xen kernel and all is ok again. checking, service xend start returns simply xend unused not sure if this is informative, xend ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 44, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module> import relocate File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line 28, in <module> from xen.xend import XendDomain File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 35, in <module> from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> from xen.xend import balloon, sxp, image File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, in <module> xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)') something's changed between 11.0 & 11.1. entirely possible i've missed some new config req'ts. what do I need to do to get xen behaving under 11.1? i'm happy to provide any info -- just need some guidance as to where to look ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 5