[opensuse-virtual] Bug (Maybe?) with finding Xen Guest installation repository
Hello List! Because with a friend's Ubuntu machine I can do a similar creation, I think it's now maybe a bug. In Xen or OpenSuse I don't understand. I have also read that installing Fedora and Redhat in this method is also successfull. I have installed the very newest OpenSuse Version11 from the Factory Repository. It uses a quite new Xen Hypervisor, "xen-3.2.1_16881_04-2" And I have started the machine in the Xen Kernel uname -a Linux server 2.6.25.4-8-xen #1 SMP 2008-05-26 15:23:05 +0200 x86_64 x86_64 x86_64 GNU/Linux Now I attempt to create a Guest domain, also OpenSuse. I am using the method with xm create The Test-configuration is the most simple I can make. It is exactly only cat test.cfg name='test' builder='linux' kernel='/home/tetsu/test/vmlinuz-xen' ramdisk='/home/tetsu/test/initrd-xen' maxmem=1024 memory=1024 vcpus=1 extra='install=http://134.76.12.5/pub/opensuse/distribution/SL-OSS-factory/inst-source?devi... hostip=192.168.1.10/24 gateway=192.168.1.1 nameserver=192.168.1.1' root='/dev/xvda1' disk=['phy:/dev/v2/test,xvda,w'] vif=['mac=00:16:3E:01:01:01,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy' To install the Guest, I create it xm create -c test.cfg In the VNC display of the output I see a "Red" Error message from the Linuxrc program. Could not find the OpenSuse Repository. Activating manual setup program. Following the advise I have read I check all the entries in the Manual Linurc dialogue. When continuing, I see again another "Red" Error message, No Repository Found. It appears not to use corectly the Guest's interface, eth0? But I see in the Domain 0 the interface is added at the bridge, brctl show bridge name bridge id STP enabled interfaces xenTEST 8000.00504300415e no peth0 vifTEST Is it a bug? Can someone help? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello List! I have searched more widely on the net yesterday to find a good example or explanation of instaling a Xen Guest with LVM and Virtual Interface. I have not found an exact explanation but many parts that are the same as I am trying. I can not understand my mistake. Has anyone an explanation or success with this simple method? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Thu, May 29, 2008 at 11:41 AM, in message <61e814a80805291041l3ea6b9e7ve47155e9d48693f3@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Hello List!
Because with a friend's Ubuntu machine I can do a similar creation, I think it's now maybe a bug. In Xen or OpenSuse I don't understand. I have also read that installing Fedora and Redhat in this method is also successfull.
I have installed the very newest OpenSuse Version11 from the Factory Repository. It uses a quite new Xen Hypervisor, "xen-3.2.1_16881_04-2"
And I have started the machine in the Xen Kernel
uname -a Linux server 2.6.25.4-8-xen #1 SMP 2008-05-26 15:23:05 +0200 x86_64 x86_64 x86_64 GNU/Linux
Now I attempt to create a Guest domain, also OpenSuse. I am using the method with
xm create
Is there a reason that you are not using vm-install (YaST -> Create Virtual Machines) to create your virtual machine? Those tools are provided to make VM installation as simple as possible.
The Test-configuration is the most simple I can make. It is exactly only
cat test.cfg name='test' builder='linux' kernel='/home/tetsu/test/vmlinuz-xen' ramdisk='/home/tetsu/test/initrd-xen' maxmem=1024 memory=1024 vcpus=1
extra='install=http://134.76.12.5/pub/opensuse/distribution/SL-OSS-factory/ins t-source?device=eth0 hostip=192.168.1.10/24 gateway=192.168.1.1 nameserver=192.168.1.1' root='/dev/xvda1' disk=['phy:/dev/v2/test,xvda,w'] vif=['mac=00:16:3E:01:01:01,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy'
To install the Guest, I create it
xm create -c test.cfg
In the VNC display of the output I see a "Red" Error message from the Linuxrc program.
Could not find the OpenSuse Repository. Activating manual setup program.
Following the advise I have read I check all the entries in the Manual Linurc dialogue. When continuing, I see again another "Red" Error message,
No Repository Found.
It appears not to use corectly the Guest's interface, eth0?
But I see in the Domain 0 the interface is added at the bridge,
brctl show bridge name bridge id STP enabled interfaces xenTEST 8000.00504300415e no peth0 vifTEST
It appears as though you have overridden the default xen networking configuration since xenTEST is not a default bridge name. There are several things that could be going wrong with your custom configuration, but it is tough to tell what those might be. Have you tried running the basic networking config (network-bridge)? What happens there? Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason!
Is there a reason that you are not using vm-install (YaST -> Create Virtual Machines) to create your virtual machine? Those tools are provided to make VM installation as simple as possible.
Yes I have tried to. I tried to enter the interactive mode as I have read, but get many errors. vm-install No protocol specified /usr/lib64/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: invalid (NULL) pointer instance self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: Screen for GtkWindow not set; you must always set a screen for a GtkWindow before using the window self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_font_description: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_base_dir: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_language: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_new: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_text: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_attributes: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_justify: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_alignment: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_ellipsize: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_single_paragraph_mode: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_width: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_get_extents: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_wrap: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gdk_screen_get_width: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_get_line_count: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) Floating exception Anyways I have decided to try the "xm create" maethod because it is closer to the ground floor and does not have added complexity of python.
It appears as though you have overridden the default xen networking configuration since xenTEST is not a default bridge name. There are several things that could be going wrong with your custom configuration, but it is tough to tell what those might be. Have you tried running the basic networking config (network-bridge)? What happens there?
Yes I have tried the basic configuration and the same things happens. But with vif1.0 or vif2.0. It depends on how many times I have done the creation steps. Inside this PC I have now two NIC cards plus on the Motherbord. I have in Dom0 changed the "/etc/xen/xend-config.sxp" file #(network-script network-bridge) #(vif-script vif-multi-bridge) (network-script network-CUSTOM-bridge) And I have edited to create "/etc/xen/scripts/network-CUSTOM-bridge" which is #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 bridge=xenTEST netdev=eth0 "$dir/vif-bridge" add vifnum=0 bridge=xenTEST netdev=eth0 ip link set xenTEST up route -A inet add default gw 192.168.1.1 dev xenTEST With my friend I can test this configuration on his Ubuntu and Centos. His PC has the same Motherbord and NIC, which I have copied for my PC. This configuration there can make the installtion of the Guest with no such problem. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason
Have you tried running the basic networking config (network-bridge)? What happens there?
So to reassure your question I have returned to the normal version of the "/etc/xen/xend-config.sxp" file (network-script 'network-bridge netdev=eth0') (vif-script 'vif-bridge netdev=eth0') And I changed in the "test.cfg" file vif=[''] And again created the Guest. Where on the Dom0 I am successful to see the standard bridge name bridge id STP enabled interfaces eth0 8000.00504300415e no peth0 vif1.0 But still I see as repeated in the earlier event "Could not find the OpenSuse Repository. Activating manual setup program." Then "No Repository Found." -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
I just ran into the problem you are seeing with no repository found, but only on 32-bit guests. A 64-bit openSUSE guest seemed to work just fine. I'm in the process of investigating the 32-bit issue, but for now, let me address some of these other issues inline.
On Fri, May 30, 2008 at 12:24 PM, in message <61e814a80805301124n10210dc1ob8fcbe3e5a622669@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Yes I have tried to. I tried to enter the interactive mode as I have read, but get many errors.
vm-install No protocol specified /usr/lib64/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: invalid (NULL) pointer instance self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: Screen for GtkWindow not set; you must always set a screen for a GtkWindow before using the window self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_font_description: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_base_dir: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_context_set_language: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_new: assertion `context != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_text: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_attributes: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_justify: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_alignment: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_ellipsize: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_single_paragraph_mode: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_width: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_get_extents: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_set_wrap: assertion `PANGO_IS_LAYOUT (layout)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: GtkWarning: gdk_screen_get_width: assertion `GDK_IS_SCREEN (screen)' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) /usr/lib64/python2.5/site-packages/vminstall/gtk/interface.py:120: PangoWarning: pango_layout_get_line_count: assertion `layout != NULL' failed self.window = gtk.glade.XML(vminstall.paths.gladedir + 'vm-install.glade', self.WINDOW_NAME) Floating exception
These errors are very strange and I have been unable to duplicate the problem. It appears to me as though your GNOME or KDE install is incomplete, or you installed from factory when things weren't quite right. I'm not sure what exactly to tell you, but I definitely don't see these errors with RC1.
Anyways I have decided to try the "xm create" maethod because it is closer to the ground floor and does not have added complexity of python.
It appears as though you have overridden the default xen networking configuration since xenTEST is not a default bridge name. There are several things that could be going wrong with your custom configuration, but it is tough to tell what those might be. Have you tried running the basic networking config (network-bridge)? What happens there?
Yes I have tried the basic configuration and the same things happens. But with vif1.0 or vif2.0. It depends on how many times I have done the creation steps.
Inside this PC I have now two NIC cards plus on the Motherbord.
This custom script needs to be changed to work correctly with openSUSE. It obviously is not the source of your error (since I have been able to duplicate the problem as well), but you are most likely going to run into some problems if you run your script the way it is here.
I have in Dom0 changed the "/etc/xen/xend-config.sxp" file
#(network-script network-bridge) #(vif-script vif-multi-bridge) (network-script network-CUSTOM-bridge)
This is fine.
And I have edited to create "/etc/xen/scripts/network-CUSTOM-bridge" which is
#!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 bridge=xenTEST netdev=eth0
This should be: $dir/network-bridge" "$@" netdev=eth0
"$dir/vif-bridge" add vifnum=0 bridge=xenTEST netdev=eth0
Not sure what this is for. What is the purpose?
ip link set xenTEST up route -A inet add default gw 192.168.1.1 dev xenTEST
I don't think these are needed. The bridge should already be up and default route added (if appropriate) to the bridge.
With my friend I can test this configuration on his Ubuntu and Centos. His PC has the same Motherbord and NIC, which I have copied for my PC.
If my research is correct, neither Ubuntu nor Centos contain xen 3.2.x. On older versions of xen, your script would theoretically work, but the networking changes in xen 3.2 are incompatible with many older scripts. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason! On 5/30/08, Jason Douglas <jdouglas@novell.com> wrote:
I just ran into the problem you are seeing with no repository found, but only on 32-bit guests. A 64-bit openSUSE guest seemed to work just fine. I'm in the process of investigating the 32-bit issue, but for now, let me address some of these other issues inline.
I can helpfuly assure you that my PC is using a 64-bit AMD X86_64. Maybe I can tell you more information that you need. Please request me for anything!
These errors are very strange and I have been unable to duplicate the problem. It appears to me as though your GNOME or KDE install is incomplete, or you installed from factory when things weren't quite right. I'm not sure what exactly to tell you, but I definitely don't see these errors with RC1.
The System I installed in the origin is the "Minimal Server Installation". Becuase this is a Domain 0 "Light Weight" system I then decided to install not KDE or GNOME, only XFCE. This also is the same as I have done on the tests with Ubuntu or Dabien. Even though I used Zypper application to assure the dependencies, maybe I must check for anything specific?
This custom script needs to be changed to work correctly with openSUSE. It obviously is not the source of your error (since I have been able to duplicate the problem as well), but you are most likely going to run into some problems if you run your script the way it is here.
I am searching and reading as much as I can find, but find not much that say so. I do read at the page "http://en.opensuse.org/Installing_Xen3" that "The instructions for installing Xen have changed considerably since this article was written.". This has left me in confusion to how to do this. Is there a good Documentation for me to read and learn?
"$dir/network-bridge" "$@" vifnum=0 bridge=xenTEST netdev=eth0
You will see in a later message I have sent the problem also is with normal scripst.
This should be: $dir/network-bridge" "$@" netdev=eth0
How is it to know the bridge name that I will assign? I will have several bridges, and must definite the names.
"$dir/vif-bridge" add vifnum=0 bridge=xenTEST netdev=eth0
Not sure what this is for. What is the purpose?
The vif-script is not called in the "xend-config.sxp" script so it must be here I think.
ip link set xenTEST up route -A inet add default gw 192.168.1.1 dev xenTEST
I don't think these are needed. The bridge should already be up and default route added (if appropriate) to the bridge.
I have sometimes in tests needed this to be here. And so I do not think they are harmful?
If my research is correct, neither Ubuntu nor Centos contain xen 3.2.x. On older versions of xen, your script would theoretically work, but the networking changes in xen 3.2 are incompatible with many older scripts.
In Centos it is correct that the Xen version is old. My friend has tested on both that system and on one he has built the new Xen 3.2.1 from sources. On Ubuntu the version is shown as Xen 3.2 apt-cache search xen | grep 3.2 python-xen-3.2 - python bindings for Xen, a Virtual Machine Monitor xen-docs-3.2 - documentation for XEN, a Virtual Machine Monitor xen-hypervisor-3.2 - The Xen Hypervisor for i386 and amd64. xen-utils-3.2 - XEN administrative tools -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason
or you installed from factory when things weren't quite right of these other issues inline.
Maybe I forgot to ansewr to you. I am very sorry. I have installed from the "openSUSE-11.0-Beta3-DVD-x86_64.torrent" DVD then using the NetInstall from the Factory repository "http://ftp5.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source". Since then I have updated to everything that is the newest using the Zypper application zypper ref zypper up zypper dup So that I think I have the newest. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason! I have done yet another experiment. I have read many results about Fedora as being a Xen Guest too. With this same OpenSuse Version 11 Factory Dom0 I edit two quite similar Xen configuration files, "testOpenSuse.cfg" and "testFedora.cfg". [1] cat testOpenSuse.cfg name='testOpenSuse' builder='linux' kernel='/home/tetsu/testOpenSuse/vmlinuz-xen' ramdisk='/home/tetsu/testOpenSuse/initrd-xen' maxmem=1024 memory=1024 vcpus=1 extra='install=http://134.76.12.5/pub/opensuse/distribution/SL-OSS-factory/inst-source?devi... hostip=192.168.1.10/24 gateway=192.168.1.1 nameserver=192.168.1.1' root='/dev/xvda' disk=['phy:/dev/v2/testOpenSuse,xvda,w'] vif=['mac=00:16:3E:01:01:01,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy' [2] cat testFedora.cfg name='testFedora' builder='linux' kernel='/home/tetsu/testFedora/vmlinuz' ramdisk='/home/tetsu/testtFedora/initrd.img' maxmem=1024 memory=1024 vcpus=1 extra = 'method=http://ftp.uni-bayreuth.de/linux/fedora/linux/releases/9/Fedora/x86_64/os ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.1 selinux=0 noshell headless text' root='/dev/xvda' disk=['phy:/dev/v2/testFedora,xvda,w'] vif=['mac=00:16:3E:01:01:02,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy' So when I create a Guest doing "xm create -c ./testFedora.cfg" it is completely successful. All of the repositories are found and the installation is completed. And the Guest can start as a working system. Only when I create a Guest doing "xm create -c ./testOpenSuse.cfg" I still as before read the errors about the repositories not found. So it is that the Fedora Guest is Okay but the OpenSuse Guest is not. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
See Novell bugzilla #394575 (https://bugzilla.novell.com/show_bug.cgi?id=394575) Jason
On Sat, May 31, 2008 at 9:48 AM, in message <61e814a80805310848k715da0a3q217dff39cd2f5886@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Hello Jason!
I have done yet another experiment. I have read many results about Fedora as being a Xen Guest too.
With this same OpenSuse Version 11 Factory Dom0 I edit two quite similar Xen configuration files, "testOpenSuse.cfg" and "testFedora.cfg".
[1] cat testOpenSuse.cfg
name='testOpenSuse' builder='linux' kernel='/home/tetsu/testOpenSuse/vmlinuz-xen' ramdisk='/home/tetsu/testOpenSuse/initrd-xen' maxmem=1024 memory=1024 vcpus=1
extra='install=http://134.76.12.5/pub/opensuse/distribution/SL-OSS-factory/ins t-source?device=eth0 hostip=192.168.1.10/24 gateway=192.168.1.1 nameserver=192.168.1.1' root='/dev/xvda' disk=['phy:/dev/v2/testOpenSuse,xvda,w'] vif=['mac=00:16:3E:01:01:01,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy'
[2] cat testFedora.cfg
name='testFedora' builder='linux' kernel='/home/tetsu/testFedora/vmlinuz' ramdisk='/home/tetsu/testtFedora/initrd.img' maxmem=1024 memory=1024 vcpus=1 extra = 'method=http://ftp.uni-bayreuth.de/linux/fedora/linux/releases/9/Fedora/x86_6 4/os ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.1 selinux=0 noshell headless text' root='/dev/xvda' disk=['phy:/dev/v2/testFedora,xvda,w'] vif=['mac=00:16:3E:01:01:02,bridge=xenTEST,vifname=vifTEST'] vfb=['type=vnc,vncdisplay=1,vnclisten=127.0.0.1'] on_crash='destroy' on_reboot='destroy' on_shutdown='destroy'
So when I create a Guest doing "xm create -c ./testFedora.cfg" it is completely successful. All of the repositories are found and the installation is completed. And the Guest can start as a working system.
Only when I create a Guest doing "xm create -c ./testOpenSuse.cfg" I still as before read the errors about the repositories not found.
So it is that the Fedora Guest is Okay but the OpenSuse Guest is not.
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason! On Mon, Jun 2, 2008 at 1:25 PM, Jason Douglas <jdouglas@novell.com> wrote:
See Novell bugzilla #394575 (https://bugzilla.novell.com/show_bug.cgi?id=394575)
In the bug report the recommendation is to use the RC1 installer. As I have said my current Domain 0 system has been installed from the Beta3 installer but used the Factory repositories. And I have updated everything with Zypper app often. So my System is newer even that RC1 I think and I would be Downgraiding to use RC1. Am I maybe wrong? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On 6/2/2008 at 2:38 PM, in message <61e814a80806021338w6100eb0fr36981baf055b560a@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Hello Jason!
On Mon, Jun 2, 2008 at 1:25 PM, Jason Douglas <jdouglas@novell.com> wrote:
See Novell bugzilla #394575 (https://bugzilla.novell.com/show_bug.cgi?id=394575)
In the bug report the recommendation is to use the RC1 installer.
As I have said my current Domain 0 system has been installed from the Beta3 installer but used the Factory repositories.
And I have updated everything with Zypper app often.
So my System is newer even that RC1 I think and I would be Downgraiding to use RC1. Am I maybe wrong?
You can ignore that request. This is an issue in all builds. That comment was an old comment. At this point, the only thing you can do is wait for a fix. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason
You can ignore that request. This is an issue in all builds. That comment was an old comment. At this point, the only thing you can do is wait for a fix.
Okay and Thank you. If you will need more informations I can do what I can to provide them from my systems. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason! With my know-how limitations I have run through things I can think to test just now. Except there is one - but I do not know. Is it worth while to also test Novell SLES? Are its Xen functions working different than OpenSuse? I do not know that it makes any proper sense. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On 6/2/2008 at 2:30 PM, in message <61e814a80806021330w52209141j66f847e2b95fa07c@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Hello Jason!
With my know-how limitations I have run through things I can think to test just now. Except there is one - but I do not know.
Is it worth while to also test Novell SLES? Are its Xen functions working different than OpenSuse?
SLES is definitely different than openSUSE, and works very well. However, even using SLES 10 SP2 as the host, you are going to have problems running openSUSE 11.0 as a paravirtualized guest (since this is a guest issue). However, you should have no problem running SLES 10 SP2 as a guest on openSUSE 11.0. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason
SLES is definitely different than openSUSE, and works very well. However, even using SLES 10 SP2 as the host, you are going to have problems running openSUSE 11.0 as a paravirtualized guest (since this is a guest issue). However, you should have no problem running SLES 10 SP2 as a guest on openSUSE 11.0.
I did not know that SLES was so different! That helps me to know too. Will it help further to test the SLES 10 SP2 as a Guest to OpenSuse 11 Domain 0? Do you still know enough to make progress without the test? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On 6/2/2008 at 2:41 PM, in message <61e814a80806021341r7b62297cs124a1be82916807b@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: Hello Jason
SLES is definitely different than openSUSE, and works very well. However, even using SLES 10 SP2 as the host, you are going to have problems running openSUSE 11.0 as a paravirtualized guest (since this is a guest issue). However, you should have no problem running SLES 10 SP2 as a guest on openSUSE 11.0.
I did not know that SLES was so different! That helps me to know too.
Will it help further to test the SLES 10 SP2 as a Guest to OpenSuse 11 Domain 0? Do you still know enough to make progress without the test?
We have done all of that testing in house. At this point we just need to track down where the failure lies and fix it. Thanks for your willingness to help. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason,
We have done all of that testing in house. At this point we just need to track down where the failure lies and fix it. Thanks for your willingness to help.
Youre Welcome! I very much hope to use Opensuse where I can rather than other Distros - It is much better to understand and use. So I am please that your team will look for the problem now. Thank you one more time with this quite odd problem. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason!
We have done all of that testing in house. At this point we just need to track down where the failure lies and fix it. Thanks for your willingness to help.
As you have recommended I have watched the bug report https://bugzilla.novell.com/show_bug.cgi?id=394575. I see that a fix has been discovered and commited. Yes just this morning I see. I think this fix is for the Factory that I use so I have updated with "zypper ref" and "zypper dup". There were many changes but not in Xen or Kernel as I have seen. I have made the update changes and tried this test again but the problem is still the same as before. Is it also required to do something else to now have the updated Xen Guest? I am not expert at installing these fixes so maybe I have done some thing still wrong? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Thu, Jun 5, 2008 at 8:06 AM, in message <61e814a80806050706n3787d576t9434c128aa57ac6@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: I see that a fix has been discovered and commited. Yes just this morning I see.
I think this fix is for the Factory that I use so I have updated with "zypper ref" and "zypper dup". There were many changes but not in Xen or Kernel as I have seen. I have made the update changes and tried this test again but the problem is still the same as before.
Is it also required to do something else to now have the updated Xen Guest? I am not expert at installing these fixes so maybe I have done some thing still wrong?
Even though the fix has been submitted, it might take a while for a new kernel to show up in factory. Hopefully it will be there very soon, as many people are anxious to get the fix, and we would like to do some additional testing on the official build. Once the new kernel appears, you will have to install your VM directly from factory (or patch your local install source with the vmlinuz-xen and initrd-xen from the /boot/arch directory, and then add factory as an additional install source). Hope that helps. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason, On Thu, Jun 5, 2008 at 9:30 AM, Jason Douglas <jdouglas@novell.com> wrote:
Even though the fix has been submitted, it might take a while for a new kernel to show up in factory. Hopefully it will be there very soon, as many people are anxious to get the fix, and we would like to do some additional testing on the official build.
It was my mistake then because I thought the commitments are made to the Factory. There is then another repository I think. I'm sorry for the confusion.
Once the new kernel appears, you will have to install your VM directly from factory (or patch your local install source with the vmlinuz-xen and initrd-xen from the /boot/arch directory, and then add factory as an additional install source).
Okay that is clear now. To ask, how can I know that the new-kernel appears with the fix? Do I have to do a test to know? Is it some where announce? I want to learn the right way to know of these informations.
Hope that helps.
Yes Thank you. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Thu, Jun 5, 2008 at 1:10 PM, in message <61e814a80806051210v620e98bau30a76c5004053387@mail.gmail.com>, "Tetsu Asaka" <tetsuichi.asaka@gmail.com> wrote: To ask, how can I know that the new-kernel appears with the fix? Do I have to do a test to know? Is it some where announce? I want to learn the right way to know of these informations.
The easiest way will be to watch factory for a change in the kernel version. Once it changes, you can verify that the fix is there by checking the changelog (rpm -qp kernel-xen.rpm --changelog | less). It should reference the bug number that was fixed. Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
Hello Jason, On Thu, Jun 5, 2008 at 12:43 PM, Jason Douglas <jdouglas@novell.com> wrote:
The easiest way will be to watch factory for a change in the kernel version. Once it changes, you can verify that the fix is there by checking the changelog (rpm -qp kernel-xen.rpm --changelog | less). It should reference the bug number that was fixed.
I did not know that changelog command for only one rpm. Thank you for your help. -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
participants (2)
-
Jason Douglas -
Tetsu Asaka