April 2015 - openSUSE Virtual - openSUSE Mailing Lists

[opensuse-virtual] after changes to 'xen.cfg' on a grub2 chainloaded Xen instance, what addl steps (mkconfig? mkinitrd? cp?) need to be exec'd?
by lyndat3＠your-mail.com 23 Apr '15

23 Apr '15

I boot Xen on UEFI + grub2. uname -rm 3.19.4-1.g74c332b-xen x86_64 rpm -qa | grep -i xen-4 xen-4.5.0_03-367.1.x86_64 Xen is chainloaded from grub2 config cat /boot/grub2/custom.cfg menuentry 'xen' { ... chainloader /efi/xen/xen.efi } cat /boot/efi/efi/xen/xen.cfg [global] default=xen [xen] options=... kernel=vmlinuz-xen ... ramdisk=initrd-xen ... each time a change is made to 'xen.cfg' which of these steps need to be executed to propagate fully to next boot? grub2-mkconfig -o /boot/grub2/grub.cfg mkinitrd /bin/cp -f /usr/lib64/efi/xen.efi /boot/vmlinuz-xen /boot/initrd-xen /boot/efi/efi/xen/ all of them? in that order? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 3

[opensuse-virtual] regular updates to Xen pkgs, but no changes in 'changelog'. Where are differences viewable?
by lyndat3＠your-mail.com 21 Apr '15

21 Apr '15

I'm seeing regular upgrades of Xen pkgs from http://download.opensuse.org/repositories/Virtualization/openSUSE_13.2 For example, from zypper history 2015-04-14 17:52:43|install|xen|4.5.0_03-366.5|x86_64||XEN4|f41fd5e7cf75ce69ba159ef1282f5905af96acea9df3f256d11afb072236e562| then, today 2015-04-20 17:32:03|install|xen|4.5.0_03-366.6|x86_64||XEN4|d2bd0baa5bbe27560bfb8e2bf32e1581199fe8b3e01404a556dd465677d56b73| Checking the changelogs rpm -q --changelog xen after each upgrade, I'm not seeing any difference. This happens often. Where are the actual differences logged? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 2

[opensuse-virtual] configuring the chainloader 'workaround' for grub2 booting of Xen on EFI ?
by lyndat3＠your-mail.com 13 Apr '15

13 Apr '15

I'm setting up GRUB2-booting of Xen on EFI Reading http://lists.xenproject.org/archives/html/xen-users/2014-03/msg00142.html http://wiki.xenproject.org/wiki/Xen_EFI Booting Xen.gz via GRUB2 can't be done directly, but needs a chainloader workaround. The example GRUB2 config given is: menuentry 'Xen EFI' { insmod part_gpt insmod search_fs_uuid insmod chain chainloader (hd0,gpt1)/EFI/XEN/xen.efi } On EFI opensuse with grub2 & Xen installed, find / | egrep "xen|grub" | grep "\.efi$" /boot/grub2/x86_64-efi/grub.efi /boot/grub2/x86_64-efi/core.efi /boot/efi/EFI/opensuse/grubx64.efi /usr/lib/grub2/x86_64-efi/grub.efi /usr/lib64/efi/grub.efi /usr/lib64/efi/xen.efi /usr/lib64/efi/xen-4.efi /usr/lib64/efi/xen-4.5.0_03-359.efi /usr/lib64/efi/xen-4.5.efi The xen.efi file is located /usr/lib64/efi/xen.efi not at the target path chainloader (hd0,gpt1)/EFI/XEN/xen.efi (1) Is the right procedure to simply mkdir -p /boot/efi/EFI/XEN cp /usr/lib64/efi/xen.efi /boot/efi/EFI/XEN/ (2) If the Xen install doesn't populate xen.efi into that directory, then at every Xen update/upgrade, will xen.efi need to be re-copied manually? (3) With the GRUB2-installed opensuse, I find no more 'device.map' file under /boot/... Is device.map still used? If none exists, what's the default mapping? For a given location, how do you query/return the device-map drive ? E.g., grub2-probe --target=device /boot/efi returns /dev/sdc2 In order to correctly modify the example's "(hd0,gpt1)" in chainloader (hd0,gpt1)/EFI/XEN/xen.efi I need to know whether /dev/sdc2 is (hd0) or (hd1) etc. LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 4

[opensuse-virtual] Intermittent crash on reboot of opensuse 13.2 + Xen 4.5 ?
by lyndat3＠your-mail.com 13 Apr '15

13 Apr '15

I can't reproduce this on-demand. It doesn't happen every time. But rebooting a running Xen instance does crash - occasionally - and when it does, it reports this in serial console ... (XEN) [2015-04-08 16:15:05] irq.c:2120: dom0: forcing unbind of pirq 201 (XEN) [2015-04-08 16:15:05] irq.c:2120: dom0: forcing unbind of pirq 202 (XEN) [2015-04-08 16:15:05] irq.c:2120: dom0: forcing unbind of pirq 203 (XEN) [2015-04-08 16:15:05] irq.c:2120: dom0: forcing unbind of pirq 190 [38366.449320] e1000e: EEE TX LPI TIMER: 00000011 [38366.468732] reboot: Restarting system (XEN) [2015-04-08 16:15:05] Domain 0 shutdown: rebooting machine. (XEN) [2015-04-08 16:15:06] ----[ Xen-4.5.0_03-363 x86_64 debug=n Not tainted ]---- (XEN) [2015-04-08 16:15:06] CPU: 0 (XEN) [2015-04-08 16:15:06] RIP: e008:[<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-08 16:15:06] RFLAGS: 0000000000010247 CONTEXT: hypervisor (XEN) [2015-04-08 16:15:06] rax: 000000009e670340 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) [2015-04-08 16:15:06] rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) [2015-04-08 16:15:06] rbp: 0000000000000000 rsp: ffff82d080457dd0 r8: 0000000000000000 (XEN) [2015-04-08 16:15:06] r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000008 (XEN) [2015-04-08 16:15:06] r12: 0000000000000000 r13: 0000000000000061 r14: 00000000fee1dead (XEN) [2015-04-08 16:15:06] r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526f0 (XEN) [2015-04-08 16:15:06] cr3: 00000008459d5000 cr2: 000000009e6c4000 (XEN) [2015-04-08 16:15:06] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) [2015-04-08 16:15:06] Xen stack trace from rsp=ffff82d080457dd0: (XEN) [2015-04-08 16:15:06] 000000009efe42f6 00000000fee1dead ffff82d0802278a4 efff00000000000a (XEN) [2015-04-08 16:15:06] ffff82d080262000 00000008459d5000 ffff82d080227a7a 000000069ed2a000 (XEN) [2015-04-08 16:15:06] 0000000000000000 0000000000152670 0000000000000700 0000000000000061 (XEN) [2015-04-08 16:15:06] 0000000000000000 00000000fffffffe ffff82d08018477c ffff82d080457e98 (XEN) [2015-04-08 16:15:06] 0000000080457e58 000036363338335b 0000000000000000 0000000000000001 (XEN) [2015-04-08 16:15:06] 0000000000000001 ffff830845989000 ffff830845989138 00000000fee1dead (XEN) [2015-04-08 16:15:06] ffff82d080129c99 0000000000a0fb00 ffff82d080105721 ffffffffffffffff (XEN) [2015-04-08 16:15:06] 0000000000000000 0000000028121969 ffffffff80a1f100 0000000000000002 (XEN) [2015-04-08 16:15:06] ffff82d080128d3f 000000010007c000 ffff83009e786000 0000000000000029 (XEN) [2015-04-08 16:15:06] ffffffff80ab47e0 ffff8800bea23b1c ffff83009e786000 0000000028121969 (XEN) [2015-04-08 16:15:06] ffff82d080224119 0000000000000000 0000000000000147 0000000000000008 (XEN) [2015-04-08 16:15:06] 0000000000000000 0000000028121969 0000000000000000 0000000000000282 (XEN) [2015-04-08 16:15:06] 0000000000000064 0000000000000523 0000000000000000 000000000000001d (XEN) [2015-04-08 16:15:06] ffffffff800113aa 0000000000000001 ffff8800a9f93e1c 0000000000000002 (XEN) [2015-04-08 16:15:06] 0001010000000000 ffffffff800113aa 000000000000e033 0000000000000282 (XEN) [2015-04-08 16:15:06] ffff8800a9f93df8 000000000000e02b 0000000000000000 0000000000000000 (XEN) [2015-04-08 16:15:06] 0000000000000000 0000000000000000 0000000000000000 ffff83009e786000 (XEN) [2015-04-08 16:15:06] 0000000000000000 0000000000000000 (XEN) [2015-04-08 16:15:06] Xen call trace: (XEN) [2015-04-08 16:15:06] [<000000009e6c4000>] 000000009e6c4000 (XEN) [2015-04-08 16:15:06] [<ffff82d0802278a4>] efi_rs_enter+0xf4/0x110 (XEN) [2015-04-08 16:15:06] [<ffff82d080227a7a>] efi_reset_system+0x3a/0x60 (XEN) [2015-04-08 16:15:06] [<ffff82d08018477c>] machine_restart+0xcc/0x220 (XEN) [2015-04-08 16:15:06] [<ffff82d080129c99>] hwdom_shutdown+0x89/0x90 (XEN) [2015-04-08 16:15:06] [<ffff82d080105721>] domain_shutdown+0xf1/0x100 (XEN) [2015-04-08 16:15:06] [<ffff82d080128d3f>] do_sched_op+0x1af/0x440 (XEN) [2015-04-08 16:15:06] [<ffff82d080224119>] syscall_enter+0xa9/0xae (XEN) [2015-04-08 16:15:06] (XEN) [2015-04-08 16:15:06] Pagetable walk from 000000009e6c4000: (XEN) [2015-04-08 16:15:06] L4[0x000] = 00000008459d4063 ffffffffffffffff (XEN) [2015-04-08 16:15:07] L3[0x002] = 000000008c674063 ffffffffffffffff (XEN) [2015-04-08 16:15:07] L2[0x0f3] = 000000009e5ff063 ffffffffffffffff (XEN) [2015-04-08 16:15:07] L1[0x0c4] = 0000000000000000 ffffffffffffffff (XEN) [2015-04-08 16:15:07] (XEN) [2015-04-08 16:15:07] **************************************** (XEN) [2015-04-08 16:15:07] Panic on CPU 0: (XEN) [2015-04-08 16:15:07] FATAL PAGE FAULT (XEN) [2015-04-08 16:15:07] [error_code=0010] (XEN) [2015-04-08 16:15:07] Faulting linear address: 000000009e6c4000 (XEN) [2015-04-08 16:15:07] **************************************** (XEN) [2015-04-08 16:15:07] (XEN) [2015-04-08 16:15:07] Manual reset required ('noreboot' specified) Is this a known or obvious problem? I'll try to figure out how to reliably reproduc it. LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 5

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015, at 12:50 PM, Charles Arnold wrote: > > Did `zypper in vm-install` miss some dependencies? > > By default vm-install will use libvirt to create VMs. Using the '--use-xl' flag when > starting vm-install will ignore libvirt and just use Xen's 'xl' toolstack directly. > > Also when you were asked, > > Please specify the type of virtualized graphics hardware. > 1: No Graphics Support > 2: Paravirtualized Graphics Adapter > [2] > > > You should select '1' here and it won't start a graphical installation (should run in the > same window as vm-install is running). vm-install --use-xl Gathering settings... Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > Virtual machines can use paravirtualization or full virtualization. Paravirtualization is faster but requires operating system support. Full virtualization runs a broader range of operating systems but requires hardware support. Which do you prefer? 1: Full virtualization 2: Paravirtualization [2] > PXE Boot (Y / N) [N] > Please choose a name for the virtual machine. [opensuse13] > Description > Specify the amount of memory and number of processors to allocate for the VM. Initial Memory [768] > Maximum Memory [768] > Virtual Processors [1] > Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > 1 <------------------------------------------------ Virtual Disks: (None) Do you want to add another virtual disk? (Y / N) [Y] > Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 2 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvda] > Size (GB) [8.0] > 1 Create a sparse image file for the virtual disk? (Y / N) [Y] > Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) Do you want to add another virtual disk? (Y / N) [N] > y Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 1 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvdb] > /home/lt/work/openSUSE-13.2-DVD-x86_64.iso Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) 4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso) Do you want to add another virtual disk? (Y / N) [N] > Network Adapters (None) Do you want to add another virtual network adapter? (Y / N) [Y] > Network Adapters Paravirtualized; Randomly generated MAC address Do you want to add another virtual network adapter? (Y / N) [N] > Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) 2: Virtual Disk (4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso)) [1] > 2 Some operating systems support automating the installation by specifying a URL or file(s). Select a directory to include multiple files. AutoYaST file > Some operating systems accept additional arguments, used to customize the installation or boot process. Additional Arguments > Preparing to start the installation... Installing... Error: [Errno 2] No such file or directory Performing post-installation checks... Error: [Errno 2] No such file or directory: '/var/lib/xen/images/opensuse13/xvda' Exception OSError: (2, 'No such file or directory', '/etc/xen/vm/opensuse13.xml') in <bound method Job.__del__ of <vminstall.job.Job object at 0x7fbd5dc18210>> ignored Where ls -al /var/lib/xen/images/opensuse13 /etc/xen/vm/ /etc/xen/vm/: total 8.0K drwxr-xr-x 2 root root 4.0K Apr 9 13:03 ./ drwx------ 6 root root 4.0K Apr 9 06:19 ../ /var/lib/xen/images/opensuse13: total 8.0K drwxr-xr-x 2 root root 4.0K Apr 9 13:03 ./ drwx------ 3 root root 4.0K Apr 9 12:28 ../ The script doesn't create/dd the xvda HD? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 5

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by Charles Arnold 09 Apr '15

09 Apr '15

>>> On 4/9/2015 at 01:41 PM, <lyndat3(a)your-mail.com> wrote: >> > It is much easier to use this tool graphically. Does your host not have > graphics or are you ssh'ing without X forwarding? >> >> No, no graphics. > > > I installed xterm and it's dependencies. > > When I ssh -X into the server, and exec 'xterm', it opens graphically > locally. So that works. > > But when I exec vm-install, I get the error > > vm-install > libvirt: XML-RPC error : Failed to connect socket to > '/var/run/libvirt/libvirt-sock': No such file or directory > Error: Failed to open a connection to libvirt. Please verify the libvirt > daemon is running. > > Did `zypper in vm-install` miss some dependencies? By default vm-install will use libvirt to create VMs. Using the '--use-xl' flag when starting vm-install will ignore libvirt and just use Xen's 'xl' toolstack directly. Also when you were asked, Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > You should select '1' here and it won't start a graphical installation (should run in the same window as vm-install is running). - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

> At this point you should add a second disk that is the ISO file you want to use as > an installation source. Select '1: CD-ROM or DVD' and then enter the full path to the ISO file. ... > If you added an ISO above, it will show up here as [2] and you can select it. That's it. The question suggested PHYSICAL cd/dvd to me; hadn't thought to add the iso there. Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) 2: Virtual Disk (4.4 GB CD-ROM or DVD (file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso)) [1] > 2 which gets past THAT error. But fails later Preparing to start the installation... Installing... Failed to display the VM's console. Please connect a viewer manually. Performing post-installation checks... Error: No kernel was found. The installation may have failed. > It is much easier to use this tool graphically. Does your host not have graphics or are you ssh'ing without X forwarding? No, no graphics. It really should be possible to read good docs and install on a minimal install without installing a graphical environment. LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

Re: [opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015, at 10:47 AM, Charles Arnold wrote: > > What's missing from the config ^^ to get past the grub prompt and 'start' > > the installer? > > Given that you are using 'xl' to create your VM (instead of libvirt's virsh/virt-install) you might > want to try using 'vm-install --use-xl' and step through the vm-install's setup and see if > that creates the type of VM you need. The configuration file created by vm-install will be > found in /etc/xen/vm/. Vm-install will create an install time configuration file that will later > be replaced by a runtime version when the installation is complete. I prefer to use Xen's default/included xl toolstack to keep my install minimal, and it's likely best supported. Installing 'vm-install' further requires The following 34 NEW packages are going to be installed: atftp cyrus-sasl cyrus-sasl-digestmd5 dbus-1-python girepository-1_0 gnutls kdump libavahi-client3 libavahi-common3 libcacard0 libesmtp libfreebl3 libgirepository-1_0-1 libgnutls28 libhogweed2 libnettle4 libsnappy1 libsoftokn3 libvirt-client libvirt-python makedumpfile mozilla-nss mozilla-nss-certs python-bottle python-CherryPy python-gobject python-libxml2 python-pycurl python-simplejson python-urlgrabber qemu-tools udhcp usbutils vm-install which is unfortunate, but if it's required to get an answer here, ok. Creating a vm with it fails vm-install --use-xl Gathering settings... Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > Virtual machines can use paravirtualization or full virtualization. Paravirtualization is faster but requires operating system support. Full virtualization runs a broader range of operating systems but requires hardware support. Which do you prefer? 1: Full virtualization 2: Paravirtualization [2] > PXE Boot (Y / N) [N] > Please choose a name for the virtual machine. [opensuse13] > Description > Specify the amount of memory and number of processors to allocate for the VM. Initial Memory [768] > Maximum Memory [768] > Virtual Processors [1] > Please specify the type of virtualized graphics hardware. 1: No Graphics Support 2: Paravirtualized Graphics Adapter [2] > Virtual Disks: (None) Do you want to add another virtual disk? (Y / N) [Y] > Create a virtual disk based on a device (CD or other block device), an existing image file (ISO), or a new file. Specify a device by its device node, such as /dev/cdrom, not its mount point. What type of virtual disk do you want to add? 1: CD-ROM or DVD 2: Hard Disk [2] > 2 Where will the virtual disk physically reside? [/var/lib/xen/images/opensuse13/xvda] > Size (GB) [8.0] > 1 Create a sparse image file for the virtual disk? (Y / N) [Y] > Virtual Disks: 1.0 GB Hard Disk (file:/var/lib/xen/images/opensuse13/xvda) Do you want to add another virtual disk? (Y / N) [N] > Network Adapters (None) Do you want to add another virtual network adapter? (Y / N) [Y] > Network Adapters Paravirtualized; Randomly generated MAC address Do you want to add another virtual network adapter? (Y / N) [N] > Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) [1] > Type the install URL: > file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso Some operating systems support automating the installation by specifying a URL or file(s). Select a directory to include multiple files. AutoYaST file > Some operating systems accept additional arguments, used to customize the installation or boot process. Additional Arguments > ERROR No installation source was defined. Error: No installation source was defined. Please correct the error and try again. ======================================== Please specify the type of operating system that will run within the virtual machine. This defines many defaults, and helps decide how to start paravirtualized operating systems. Press 'q' or the Escape key to exit. 1: Novell Open Enterprise Server 2 (Linux) 2: Novell Open Enterprise Server 2 (NetWare) 3: Novell Open Enterprise Server 11 4: Other operating system 5: PXE 6: RedHat (other) 7: RedHat Enterprise Linux 3 8: RedHat Enterprise Linux 4 9: RedHat Enterprise Linux 5 10: RedHat Enterprise Linux 6 11: RedHat Enterprise Linux 7 12: Relax and Recover 13: SUSE (other) 14: SUSE Linux Enterprise Desktop 10 15: SUSE Linux Enterprise Desktop 11 16: SUSE Linux Enterprise Desktop 12 17: SUSE Linux Enterprise Server 8 18: SUSE Linux Enterprise Server 9 19: SUSE Linux Enterprise Server 10 20: SUSE Linux Enterprise Server 11 21: SUSE Linux Enterprise Server 12 22: Solaris 9 and older 23: Solaris 10 24: Ubuntu 10 (Lucid Lynx, Maverick Meerkat) 25: Ubuntu 11 (Natty Narwhal, Oneiric Ocelot) 26: Ubuntu 12 (Precise Pangolin) 27: Ubuntu (other) 28: Windows 8 29: Windows 8 (x64) 30: Windows (other) 31: Windows (other, x64) 32: Windows NT 33: Windows Server 2008 34: Windows Server 2008 (x64) 35: Windows Server 2012 (x64) 36: Windows Vista, Windows 7 37: Windows Vista, Windows 7 (x64) 38: Windows XP, 2000, 2003 39: Windows XP, 2003 (x64) 40: openSUSE 41: openSUSE 11 42: openSUSE 12 43: openSUSE 13 [43] > q There's no config file created ls -al /etc/xen/vm total 8.0K drwxr-xr-x 2 root root 4.0K Apr 8 16:16 ./ drwx------ 6 root root 4.0K Apr 9 06:19 ../ I'll guess it's this ERROR No installation source was defined. Error: No installation source was defined. Please correct the error and try again. How is the installer iso supposed to be passed to the vm-install script if not as a file:/ ? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] Booting opensuse installer iso as Xen PV DomU drops to grub prompt?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

I'm trying to launch the openSUSE 13.2 installer in a Xen DomU via pvgrub2. It looks like the installer iso contains all the Xen PV pieces. mount -o loop openSUSE-13.2-DVD-x86_64.iso /mnt/iso cd /mnt/iso find . | grep xen | egrep "/xen|/initrd|/vmlinuz|/grub|/kernel" ./boot/x86_64/initrd-xen ./boot/x86_64/vmlinuz-xen ./suse/x86_64/grub2-x86_64-xen-2.02~beta2-20.5.1.x86_64.rpm ./suse/x86_64/kernel-xen-3.16.6-2.1.x86_64.rpm ./suse/x86_64/kernel-xen-devel-3.16.6-2.1.x86_64.rpm ./suse/x86_64/xen-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-doc-html-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-kmp-default-4.4.1_06_k3.16.6_2-3.3.x86_64.rpm ./suse/x86_64/xen-kmp-desktop-4.4.1_06_k3.16.6_2-3.3.x86_64.rpm ./suse/x86_64/xen-libs-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-tools-4.4.1_06-3.3.x86_64.rpm ./suse/x86_64/xen-tools-domU-4.4.1_06-3.3.x86_64.rpm Using this for the Guest config at the Dom0 cat /home/lt/work/test.cfg boot = 'd' disk = ['file:/home/lt/work/openSUSE-13.2-DVD-x86_64.iso,hdd:cdrom,r', ] kernel = "/usr/lib/grub2/x86_64-xen/grub.xen" name = 'test' netif = 'yes' sdl = 0 stdvga = 1 vif = [ 'mac=00:16:3E:01:01:01, bridge=br0, vifname=vif0',] vnc = 0 creating the Guest xl create -c ./test.cfg just drops to a "grub>" prompt. What's missing from the config ^^ to get past the grub prompt and 'start' the installer? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] How to conditionally configure & use bridge interface only when booting to Xen?
by lyndat3＠your-mail.com 09 Apr '15

09 Apr '15

I have a server with a single ethernet interface, eno1. When booting to kernel-default, the interface is configured in /etc/sysconfig/network/ifcfg-eno1 and gets brought up by the wicked networking stack If I switch to Xen, booting to kernel-xen, I can bring up the Dom0 in this configuration too. But for PV DomUs, I need a bridge interface to pass in vif=[...] I know how to create & configure the bridge interface (/etc/sysconfig/network/ifcfg-br0) to 'take over' eno1 I can't figure out how to create & use the bridge only conditionally -- in the Xen-boot case. In other words, if boot to non-Xen, use intfc "eno1" and, if boot to Xen, use intfc "br0" instead On my previous servers I'd use if-up & if-down scripts to handle it. The up/down scripts don't seem to work with the opensuse wicked stack. How do you handle conditional network configuration with wicked, depending on which boot environment -- Xen or non-Xen -- you're booting to? IIUC the advice has been to use opensuse networking config to setup the interfaces. To do this ^^ do you have to step outside the OS config? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0