- openSUSE Virtual

[opensuse-virtual] Yast Error on "Create Virtual Machines"
by Volker Katz 18 Nov '08

18 Nov '08

Hi, I'm new to Xen and not very familiar with SuSE. I installed a minimal OpenSuSE 11 without X. Afterwards I used Yast to "Install Hypervisor and Tools". Afterwards I booted the Xen Kernel and tried "Create Virtual Machines" via Yast. First I had some errors about missing libvirt. I installed this (via Yast again) and tried "Create Virtual Machines" again: The ncurses screen quite, I see the (still blocked) console. The yast logfile says: 2008-11-18 10:57:37 <1> localhost(4456) [liby2] genericfrontend.cc(main):561 Launched YaST2 component 'y2base' '/usr/bin/vm-install' '-S' 'ncurses' 2008-11-18 10:57:37 <1> localhost(4456) [ui-component] YUIComponentCreator.cc(createInternal):113 Creating UI component for "" 2008-11-18 10:57:37 <1> localhost(4456) [ui-component] YUIComponentCreator.cc(createInternal):128 Returning existing UI component for "ncurses" 2008-11-18 10:57:37 <1> localhost(4456) [liby2] genericfrontend.cc(main):715 YAST_IS_RUNNING is yes Any hints for me? Thanks & kind regards Volker -- 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 and vnet
by Rob Verduijn 03 Nov '08

03 Nov '08

Hello, I am trying to get vnet to work on my xen installation. I am using opensuse 11.0 and xen 3.2.1_16881_04 release 4.2 I read the manual on this page : http://orgs.man.ac.uk/documentation/xen/user/user.html#SECTION0440000000000… I configured a vnet according to that manual added the vnet with the following command xm vnet-create vnet97.sxp the command xm vnet-list -l gives the following output "{'Status': 'Failure', 'ErrorDescription': ['MESSAGE_METHOD_UNKNOWN', 'xend_vnet']}" "{'Status': 'Failure', 'ErrorDescription': ['MESSAGE_METHOD_UNKNOWN', 'xend_vnet']}" After some digging I found that I needed to change the xend-config.sxp (network-script network-vnet) was needed but there is no network-vnet scriptin my installation. Did I forget to install something ? Rob -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

[opensuse-virtual] Xen cpuinfo E8200 processor (core 2 duo)
by FX Theodule 16 Sep '08

16 Sep '08

Hey, Does anybody knows why, on a E8200 processor system(Dell Optiplex 330), when booting with Xen ( Linux version 2.6.25.16-0.1-xen (geeko@buildhost) (gcc version 4.3.1 20080507 (p rerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00: 34:25 +0200 ), the cpu infos are changing ? I'm actually getting, with the Xen kernel, those cpuinfo (without vmx flag, and with a cpu cores of 1) : more /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping : 6 cpu MHz : 2660.056 cache size : 6144 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae cx8 apic sep mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good pni ssse3 cx16 sse4_1 l ahf_lm bogomips : 5322.08 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping : 6 cpu MHz : 2660.056 cache size : 6144 KB physical id : 0 siblings : 1 core id : 1 cpu cores : 1 ..... .. If I boot on th "normal" kernel (no Xen), the cpu flag vmx appear, and the cpu cores is 2. Amicalement, FX THEODULE INSERM U928 /TAGC Campus de Luminy 163 AVENUE DE LUMINY - CASE 928 13288 Marseille Cedex 9 Mel francois-xavier.theodule(a)inserm.fr PS : Notre installation telephonique ayant ete modifiee, merci de composer dorenavant le 04 91 82 87 24 -- 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 .cfg file for a paravirt OpenSolaris DomU ?
by Wil Decius 25 Jul '08

25 Jul '08

I'm running OpenSuse11 as my Xen Dom0. After figuring out that OpenSuse doesn't use 'pygrub', but rather 'domUloader.py', I'm able to install OpenSuse 11 as a PV DomU, using a config file format of, ... builder = 'linux' bootloader = '/usr/lib/xen/boot/domUloader.py' bootargs = '--entry=xvda1:vmlinuz-xen,/boot/initrd-xen' ... It works fine. openSuse DomU's are up and running. Now I want to install OpenSolaris as a ParaVirt Guest. Cobbling together what little I'v found for installing OpenSolaris as an /HVM/ Guest on Redhat, and what works for my OpenSuse Guests, my config is, opensolaris.cfg name = "opensolaris" builder = 'linux' bootloader = '/usr/lib/xen/boot/domUloader.py' bootargs = "--entry=xvda1:/boot/platform/i86xpv/kernel/amd64/unix,/boot/amd64/x86.miniroot' disk = ['phy:/dev/volgrp001/opensolaris,xvda,w', 'file:/home/xen/opensolaris/opensolaris.iso,hdc:cdrom,r'] boot = 'd' extra = "textmode=1 xencons=tty /platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" vif = ['mac=00:16:3E:11:10:01, bridge=br001, vifname=vif001'] vfb = ['type=vnc, vnclisten=127.0.0.1, vncdisplay=2'] maxmem = 1024 memory = 1024 vcpus = 1 on_crash = "destroy" on_poweroff = "destroy" on_reboot = "destroy" @ xm create -c ./opensolaris.cfg I get just Using config file "./opensolaris.cfg". Error: Boot loader didn't return any data! I'm guessing 'bootargs' are wrong for OpenSolaris Guest. Can anyone suggest the right instructions, or share a working config? Thanks Wil -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 4

[opensuse-virtual] Strange network problem: ping works, TCP doesn't
by Adrian von Bidder 22 Jul '08

22 Jul '08

Yodel! [cc:'s appreciated] I'm a bit confused. Bridged networking, no firewall, external host on the same network as the Xen machine. I can ping between external, domU and dom0 in all directions. I can ssh between domU and dom0, and I can ssh between dom0 and external, in both directions. I can't ssh between domU and external at all. Or any other TCP based thing. Connection opens (netstat shows an open connection), so some initial ACK seems to go through, but after that the connection is dead. ping works regardless of packet size, so it isn't an MTU issue. I assume it's not a MAC issue as ping wouldn't work, right? I'm not sure where to start looking. (Oh, yes: everything is on SLES10) cheers -- vbi -- Today is Prickle-Prickle, the 53rd day of Confusion in the YOLD 3174

1 1

[opensuse-virtual] ConVirt
by Andrew Foulsham 22 Jul '08

22 Jul '08

Dear all, Does anyone use Convirt to manage their Xen virtual machines? It seems to be a development of Xenman, and is hosted at http://xenman.sourceforge.net/ The OpenSUSE build service has RPMs for Convirt, and it installs cleanly. However, I can't find documentation that explains how to configure and use it. Has anyone got some useful pointers to documentation or other resources? Best wishes, Andrew Foulsham IT Officer, Weatherall Institute of Molecular Medicine, Oxford University -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

[opensuse-virtual] Xen Windows guest shutdown just destroys the machine instead of a neat os shutdown?
by Willem Meens 08 Jul '08

08 Jul '08

Hi All, We have a question about shutting down a Windows guest running on SLES 10 (SP1 & SP2) using xm commands and/or scripts. When a ' xm shutdown <vm name>' is given on a Linux guest it shuts down nicely. Doing the same on a Windows guest just results in a (hard) power off for the guest. Is there some extra configuration that needs to be done on the Xen host or Windows guest for this to work correctly? Thanks for your thoughts! Kind Regards, Wj -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 2

[opensuse-virtual] Error is "no disks are bootable" for a Para-Virtualized Xen Guest
by Tetsu Asaka 08 Jul '08

08 Jul '08

Hello List! Now with the fixed Bugs in Opensuse11/libvirt I am installing a Para-Virtualized Xen Guest. It is the OpenFiler NAS Applyance. Its surpising that Opensuse11 did not contain the "pygrub" application for Bootloading. I learned that the Opensuse way is with "domUloader.py" instead. So, I have saved a Configuration, cat openfiler.cfg name = "openfiler" builder = "linux" bootloader = "/usr/lib/xen/boot/domUloader.py" bootargs = "--entry=xvda1:/boot/vmlinuz-2.6.21.7-3.20.smp.gcc3.4.x86_64.xen.domU,/boot/initrd-2.6.21.7-3.20.smp.gcc3.4.x86_64.xen.domU.img" root = "/dev/xvda1" disk = ["phy:/dev/vg001/openfiler,xvda1,w"] vif = ["mac=00:16:3E:11:10:01, bridge=XenBr001, vifname=vif001"] on_crash = "restart" on_reboot = "restart" on_shutdown = "destroy" extra = "3" memory = 512 But when I create the Guest there is an Error, xm create openfiler.cfg Using config file "./openfiler.cfg". Error: Had a bootloader specified, but no disks are bootable I have found only one similar question about this error and Opensuse, http://lists.xensource.com/archives/html/xen-users/2008-02/msg01083.html But there is no answer yet there. Is there any suggestion for fixing or additions to the Configuration? Or is there yet anohter way? -- Thank you! Testu ----------------------------------- Ride On! __o o__ o__ o__ _ \<,_ _.>/ _ _.>/ _ _.>/ _ (_)/ (_) (_) \(_) (_) \(_) (_) \(_) ----------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

Re: [opensuse-virtual] DomU cannot find /dev/hda2 after upgradingtoSLES 10 SP1
by Jason Douglas 01 Jul '08

01 Jul '08

This was sent directly to me (instead of the mailing list). Replying there. BTW, happy to help. Jason >>> On Tue, Jul 1, 2008 at 1:33 PM, in message <486A8684.7070009(a)planplus.com>, Tyler D <tyler(a)planplus.com> wrote: > Just so anyone else reading this knows, the following worked: > > Make a copy of your config, and then change all of the xvdX entries to hdX. > As long as you get all of the places in the config file, it should work. > That way whatever is causing the VM to look for /dev/hda2 might actually > succeed. > > > Thanks a lot, Jason! > > -Tyler > > > Jason Douglas wrote: >> Tyler, >> >> Here are a couple of things to try (in no particular order): >> - Make a copy of your config, and then change all of the xvdX entries to > hdX. As long as you get all of the places in the config file, it should > work. That way whatever is causing the VM to look for /dev/hda2 might > actually succeed. >> - Make sure that your image file isn't mounted anywhere (in dom0, for > example). If it is, unmount it and try to launch the VM again. >> - Try mounting your disk image in dom0 and verify that the files that should > be there are actually there. This can be done using lomount in the following > fashion: >> >> lomount -diskimage /media/disk/var/lib/xen/images/vm-dev/hda -partition 2 /mnt >> >> Verify that everything appears as it should. While it is mounted, you might > also want to look at /etc/fstab. If there are any references to /dev/hda, > backup the file and change hdX to xvdX. >> >> When you're done, don't forget to umount the diskimage before you try to > launch your VM. >> >> - As a general rule, if you don't have need for the cd-rom device right away, > remove it from your disk line just to eliminate another layer of complexity. >> >> Good luck. >> >> Jason >> >> >>>>> Tyler D <tyler(a)planplus.com> 07/01/08 12:23 PM >>> >>>>> >> I tried adding root="/dev/xvda2" to the config file, but to no effect. Here > is the current config file: >> ostype="sles10" name="vm-dev" memory=1024 vcpus=2 > uuid="1c26bd7d-5bdf-565f-8471-b7589b3b900c" on_crash="destroy" > on_poweroff="destroy" on_reboot="restart" localtime=0 builder="linux" > bootloader="/usr/lib/xen/boot/domUloader.py" > bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" > root="/dev/xvda2" extra="TERM=xterm " disk=[ > 'file:/media/disk/var/lib/xen/images/vm-dev/hda,xvda,w', > 'phy:/dev/sr0,xvdb,r', ] vif=[ 'mac=00:16:3e:03:65:8f', ] > vfb=["type=vnc,vncunused=1"]Here is the console output: >> http://i30.tinypic.com/357lwyc.png >> >> And here is a link to what Novell suggested: >> http://forums.novell.com/novell-product-support-forums/.../#post1589680 >> >> Thanks for the help so far. I don't have much experience with Xen. >> >> -Tyler >> >> >> Jason Douglas wrote: >> >> Tyler, >> >> My comments are inline. >> >> Jason >> >> >> >> >> >> >> >> On Tue, Jul 1, 2008 at 10:51 AM, in message <486A6090.4000404(a)planplus.com> ( > mailto:486A6090.4000404@planplus.com ), >> Tyler D <tyler(a)planplus.com> ( mailto:tyler@planplus.com ) wrote: >> >> >> Hello, I'm midway in the process of upgrading a server from SLES 10 GA >> to SP2. >> >> I updated the Dom0 (host) to SP1, then recreated a test VM (DomU) that >> has the GA version on it (I made a new VM with the same specs, and >> pointed it to the old hda file). I then updated the VM to SP1 as well. >> When the installer first listed partitions, none were showing, until I >> ticked 'Show all partitions'. I installed to /dev/xda2. >> >> When I try to boot the VM, it says: >> >> Waiting for device /dev/hda2 to appear ... not found -- exiting to /bin/sh. >> It sounds like your root= needs to be set to /dev/xvda2 (instead of > /dev/hda2). >> >> >> >> I can run a few basic commands at this point, and I checked for >> /etc/fstab, and for any hda files in /dev - none are there. >> >> In the original config file for this VM is the following line: >> >> bootentry = 'hda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae' >> In addition to changing hda2 to xvda2 (based on your statement above), > domUloader expects different arguments with SP1 than it did with GA. In SP1, > the bootentry line should be replaced with a line that looks like this: >> >> bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" >> >> However, if you created a new vm config file using the SP1 vm-install tool, > that line should already be correct. >> >> >> >> My guess is that the VM's boot entry is still configured to search for >> /hda2, although there is no option for changing this in the new SP1 >> Virtual Machine Manager. Editing the config files for a VM under SP1 >> seems to have no effect as the settings appear to be stored elsewhere >> after the initial creation. >> If you edit the config file manually, then you need to import it into > "xenstore" by doing the following: >> >> 1. xm delete vm_name (this removes the config from xenstore) >> 2. xm new vm_config_file (this adds the config to xenstore) >> >> At that point, you can launch the VM from virt-manager. >> >> The alternative is to ignore virt-manager for starting the VM (for testing > purposes). To launch the VM using the settings in the config file, you can > run "xm create vm_config_file". Once it is launched, you can still start a > viewer from virt-manager (or if the viewer window was already open for that > VM, it should automatically connect). >> >> >> >> If you would be so kind as to >> a) suggest how I can edit the VM's boot entry (no, GRUB is not installed >> on the VM) from Dom0 or the very limited /bin/sh mode), and/or >> b) offer other suggestions or solutions, it would be much appreciated. >> Hopefully the suggestions above will help. >> >> >> >> Thank you in advance. I've read the documentation and know that there >> may be further headaches in upgrading the VMs to SP2 (you're supposed to >> update the DomUs before the Dom). I'm waiting at SP1 until I can get the >> VMs properly upgraded. >> At this point you might be better off moving dom0/hypervisor to SP2 > and deal with all the problems at the same time. The xen 3.2.0 hypervisor is > capable of running older guests, so that *shouldn't* be an issue, but I have > definitely never tried the scenario you are attempting. Good luck! >> >> Jason >> >> >> -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

Re: [opensuse-virtual] DomU cannot find /dev/hda2 after upgradingto SLES 10 SP1
by Jason Douglas 01 Jul '08

01 Jul '08

Tyler, Here are a couple of things to try (in no particular order): - Make a copy of your config, and then change all of the xvdX entries to hdX. As long as you get all of the places in the config file, it should work. That way whatever is causing the VM to look for /dev/hda2 might actually succeed. - Make sure that your image file isn't mounted anywhere (in dom0, for example). If it is, unmount it and try to launch the VM again. - Try mounting your disk image in dom0 and verify that the files that should be there are actually there. This can be done using lomount in the following fashion: lomount -diskimage /media/disk/var/lib/xen/images/vm-dev/hda -partition 2 /mnt Verify that everything appears as it should. While it is mounted, you might also want to look at /etc/fstab. If there are any references to /dev/hda, backup the file and change hdX to xvdX. When you're done, don't forget to umount the diskimage before you try to launch your VM. - As a general rule, if you don't have need for the cd-rom device right away, remove it from your disk line just to eliminate another layer of complexity. Good luck. Jason >>> Tyler D <tyler(a)planplus.com> 07/01/08 12:23 PM >>> I tried adding root="/dev/xvda2" to the config file, but to no effect. Here is the current config file: ostype="sles10" name="vm-dev" memory=1024 vcpus=2 uuid="1c26bd7d-5bdf-565f-8471-b7589b3b900c" on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=0 builder="linux" bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" root="/dev/xvda2" extra="TERM=xterm " disk=[ 'file:/media/disk/var/lib/xen/images/vm-dev/hda,xvda,w', 'phy:/dev/sr0,xvdb,r', ] vif=[ 'mac=00:16:3e:03:65:8f', ] vfb=["type=vnc,vncunused=1"]Here is the console output: http://i30.tinypic.com/357lwyc.png And here is a link to what Novell suggested: http://forums.novell.com/novell-product-support-forums/.../#post1589680 Thanks for the help so far. I don't have much experience with Xen. -Tyler Jason Douglas wrote: Tyler, My comments are inline. Jason On Tue, Jul 1, 2008 at 10:51 AM, in message <486A6090.4000404(a)planplus.com> ( mailto:486A6090.4000404@planplus.com ), Tyler D <tyler(a)planplus.com> ( mailto:tyler@planplus.com ) wrote: Hello, I'm midway in the process of upgrading a server from SLES 10 GA to SP2. I updated the Dom0 (host) to SP1, then recreated a test VM (DomU) that has the GA version on it (I made a new VM with the same specs, and pointed it to the old hda file). I then updated the VM to SP1 as well. When the installer first listed partitions, none were showing, until I ticked 'Show all partitions'. I installed to /dev/xda2. When I try to boot the VM, it says: Waiting for device /dev/hda2 to appear ... not found -- exiting to /bin/sh. It sounds like your root= needs to be set to /dev/xvda2 (instead of /dev/hda2). I can run a few basic commands at this point, and I checked for /etc/fstab, and for any hda files in /dev - none are there. In the original config file for this VM is the following line: bootentry = 'hda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae' In addition to changing hda2 to xvda2 (based on your statement above), domUloader expects different arguments with SP1 than it did with GA. In SP1, the bootentry line should be replaced with a line that looks like this: bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" However, if you created a new vm config file using the SP1 vm-install tool, that line should already be correct. My guess is that the VM's boot entry is still configured to search for /hda2, although there is no option for changing this in the new SP1 Virtual Machine Manager. Editing the config files for a VM under SP1 seems to have no effect as the settings appear to be stored elsewhere after the initial creation. If you edit the config file manually, then you need to import it into "xenstore" by doing the following: 1. xm delete vm_name (this removes the config from xenstore) 2. xm new vm_config_file (this adds the config to xenstore) At that point, you can launch the VM from virt-manager. The alternative is to ignore virt-manager for starting the VM (for testing purposes). To launch the VM using the settings in the config file, you can run "xm create vm_config_file". Once it is launched, you can still start a viewer from virt-manager (or if the viewer window was already open for that VM, it should automatically connect). If you would be so kind as to a) suggest how I can edit the VM's boot entry (no, GRUB is not installed on the VM) from Dom0 or the very limited /bin/sh mode), and/or b) offer other suggestions or solutions, it would be much appreciated. Hopefully the suggestions above will help. Thank you in advance. I've read the documentation and know that there may be further headaches in upgrading the VMs to SP2 (you're supposed to update the DomUs before the Dom). I'm waiting at SP1 until I can get the VMs properly upgraded. At this point you might be better off moving dom0/hypervisor to SP2 and deal with all the problems at the same time. The xen 3.2.0 hypervisor is capable of running older guests, so that *shouldn't* be an issue, but I have definitely never tried the scenario you are attempting. Good luck! Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0