On Sun, 2007-09-23 at 22:26 -0400, Peter Sjoberg wrote:
I have just updated my 10.2 XEN system to 10.3RC1 and
found a few
2: XEN failures:
After disabling autostart of the xen guests I booted the XEN version of
I tried to start one of my domU with "vm create
-c sato" but it did
just hang, didn't get anything at all out on the screen. Looked around a
little and it seems like the migration from xen 3.0 to 3.1 isn't that
trivial and requires some work (RTFD for a start)
After some more testing I have
found a few things:
1: documentation is sparese. Xensource still shows 3.0 doc and braks
about 3.0 download (but it links to 3.1). I tried to find out some tings
like form at of /etx/xen/vm/domU and where the "xm list" info is stored
etc and foudn the answer ins misc forums. Once I found some info I tried
to reverse the findings to see if I just missed it at first but for
example "uuid" or a pointer to say that domain info is now stored
in /var/lib/xend/domains/<uuid>/config.sxp is no where to be found.
2: To be able to even start a domain created in opensuse 10.2 you need
to change the obsolete "bootentry" line yast created
-bootentry = 'hda1:/boot/vmlinuz-xen,/boot/initrd-xen'
+bootargs = '--entry=hda1:/boot/vmlinuz-xen,/boot/initrd-xen'
The strange thing is that if you have "bootentry" it doesn't give you an
error, it just hangs.
3: After this it does at least start up but something seems to be
missing since "xm list" shows even stopped domains created under 10.3.
Looking around and guessing I found that I need to do
#wait for it to die
xm new domU
grep -l domU /var/lib/xend/domains/*/config.sxp
#add the uuid returned above to the config
echo 'uuid="0c29be6f-cb1a-a9e8-67b2-83b8cce822cc"' >>domU
#verify that domU now shows up in the list despite it's not running
xm create domU
# and now it's only one domU line.
# if you don't add uuid to the config file you get two lines,
# one running and one down
4: I still haven't checked out that the domains works and at least one
where I now export a pile of xen bridges for a total of 5 NICs (its a
fw) doesn't work.
Right now I'm considering building new 10.3 domU and just move the
configuration but since building domains also fails I can't do that yet.
I did also try to build a new domU using yast and for
a start the
interface makes it a lot harder then before since I have to type in the
install source manually despite it's the same as dom0 (an nfs mount
The install started but when it rebooted an error box came up that it
was no kernel there. Tried again with a text only build and there it did
the same (after complaining about ntp config failing since ntp wasn't
Techwiz, Peter Sjoberg PGP key (12F506C8) on keyserver & homepage
Key fingerprint = 3DC2 CEBA 1590 B41A 3780 955A DB42 02BB 12F5 06C8
mailto:peters AT techwiz.ca http://www.techwiz.ca/~peters
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org