- openSUSE Virtual

[opensuse-virtual] autoyast installation in Xen DomUs -- defining /etc/fstab ?
by lssl＠ssl-mail.com 14 Feb '17

14 Feb '17

I'm setting up autoyast for autoinstall of Xen DomUs. Both Xen Host & Guests run Opensuse Leap 42.2. >From my Dom0 I pass pre-formatted, but not yet populated, LVMs as disks to the DomU config guest.cfg ... disk = [ 'phy:/dev/VG0/EFI,xvda,w','phy:/dev/VG0/ROOT,xvde,w'] ... I want my Guest /etc/fstab to end up as UUID=AAAA-BBBB /boot/efi vfat [ ... efi fstab options ... ] 0 2 UUID=111...111 / ext4 [ ... root fstab options ... ] 1 1 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 My question is how 'best' to set the 'proc', 'sysfs', debugfs', 'devpts' mounts & their respective fstopts? In the autoyast.xml that'll get passed to the xen.cfg, IIUC, I can use <partitioning> for the passed-in devices, with 'initialize', 'create' & 'format' all == "false", <partitioning config:type="list"> <drive> <device>/dev/xvda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/boot/efi</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... efi fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">vfat</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> <drive> <device>/dev/xvde</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... root fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">ext4</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> </partitioning> Where in that case would I set the 'proc', 'sysfs', debugfs', & 'devpts' mounts? They're not *additional* partitions, and from the docs, for a given partition I can only have one <mount>...</mount>. One option would be to use a postpartitioning script <scripts> <postpartitioning-scripts config:type="list"> <script> cat EOF >> /etc/fstab ( ... fstab entries for 'proc', 'sysfs', debugfs', & 'devpts' ... ) EOF </script> </postpartitioning-scripts> </scripts> , modifying the just-created-fstab immediately after the <partitioning> step. That's doable, but seems messy. What's the recommended way to get to a completely defined fstab in the Xen-DomU-install case above? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 3

Re: [opensuse-virtual] Xen was loaded above 4Gb
by Gary Lin 12 Jan '17

12 Jan '17

On Wed, Jan 11, 2017 at 10:08:00PM +1100, Jan Beulich wrote: > >>> On 11.01.17 at 11:06, <GLin(a)suse.com> wrote: > > I'm trying to install the Xen server (openSUSE 42.2) in a machine with > > 16GB RAM. After installing the hypervisor tools, if I choose the > > hypervisor option in the grub2 menu, a message showed quickly and the > > system backed to grub2. It stated: "Xen must be loaded below 4Gb." > > > > Is there any parameter to work around this? > > No, this would require quite a bit of code rework before it could > work at all. But why would grub choose a location above 4Gb as > long as there's enough memory available below that boundary? > It might be firmware-related since I also tried to load xen.efi directly (from the firmware menu and shell) and got the same error. Gary Lin -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] Xen was loaded above 4Gb
by Gary Lin 11 Jan '17

11 Jan '17

Hi, I'm trying to install the Xen server (openSUSE 42.2) in a machine with 16GB RAM. After installing the hypervisor tools, if I choose the hypervisor option in the grub2 menu, a message showed quickly and the system backed to grub2. It stated: "Xen must be loaded below 4Gb." Is there any parameter to work around this? Thanks, Gary Lin -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] Xen 4.8 upgrade missing /usr/bin/domu-xenstore, fails to start xencommons
by lists＠ssl-mail.com 08 Jan '17

08 Jan '17

After upgrading to latest xen now available rpm -qa | egrep -i ^xen" xen-4.8.0_01-465.1.x86_64 xen-libs-4.8.0_01-465.1.x86_64 xen-tools-4.8.0_01-465.1.x86_64 on boot ... [FAILED] Failed to start xencommons. See 'systemctl status xencommons.service' for details. Starting Xendomains - start and stop guests on boot and shutdown... ... but it proceeds to prompt [ OK ] Started Xendomains - start and stop guests on boot and shutdown. Welcome to openSUSE Leap 42.2 - Kernel 4.9.0-6.ge989b9d-default (hvc0). checking at shell systemctl status xencommons -l ● xencommons.service - xencommons Loaded: loaded (/usr/lib/systemd/system/xencommons.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-01-06 13:26:32 PST; 6min ago Process: 1947 ExecStart=/usr/bin/xenstore-ls -f (code=exited, status=203/EXEC) Process: 1942 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS) Main PID: 1947 (code=exited, status=203/EXEC) because cd /usr/bin/ ls -al xenstore-ls lrwxrwxrwx 1 root root 13 Jan 6 13:14 xenstore-ls -> domu-xenstore ls -al domu-xenstore -bash: /usr/bin/xenstore-ls: No such file or directory rpm -q --whatprovides /usr/bin/xenstore-ls xen-tools-4.8.0_01-465.1.x86_64 rpm -q --whatprovides /usr/bin/domu-xenstore error: file /usr/bin/domu-xenstore: No such file or directory rpm -ql xen-tools-4.8.0_01-465.1.x86_64 | egrep "xenstore-ls|domu-xenstore" /usr/bin/xenstore-ls /usr/share/man/man1/xenstore-ls.1.gz this can NOT be fixed with a reinstall rm -f /usr/bin/xenstore-ls zypper in --force xen-tools ls -al /usr/bin/xenstore-ls lrwxrwxrwx 1 root root 13 Jan 6 13:40 /usr/bin/xenstore-ls -> domu-xenstore -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 15

[opensuse-virtual] Xen 4.8 plans?
by lists＠ssl-mail.com 04 Jan '17

04 Jan '17

What are the plans for build & support of Xen 4.8 pkgs in the Virtualization repo? It's starting to be available in some distros, for example https://packages.debian.org/stretch/xen-hypervisor-4.8-amd64 Unless I missed it, there's no discussion yet on this list, and nothing in buildsystem even for Tumbleweed. Some idea of if & when Opensuse will have it would really help in planning. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 2

[opensuse-virtual] Leap 42.2 + Xen: Missing Independent Wallclock
by Rieß Norman 30 Nov '16

30 Nov '16

Hello, i just installed our first Leap 42.2 DomU and as i wanted to adapt our usual scriptset i noticed, that the settings for independent wallclock seem to be missing. While the doc is stating that independent wallclock settings should apply for Leap 42.2, /proc/sys/xen is not showing the appropriate file. /proc/sys/xen # ls balloon Has something gone wrong during installation, or is the documentation faulty? Regards, Norman Doc: https://doc.opensuse.org/documentation/leap/virtualization/html/book.virt/s… To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

5 10

[opensuse-virtual] Abnormal behavior of openSUSE LEAP 42.1 in virtual appliance at susestudio
by Amey Abhyankar 04 Oct '16

04 Oct '16

Hello, I am facing abnormal behavior of openSUSE LEAP 42.1 at susestudio today. I was trying to demostrate LEAP 42.1 to few Linux newbies and encountered issues. Issues I encountered as follows:- - Tried to unlock KDE graphical locked screen. Failed to accept password for my user. - Screen was idle for 10 minutes. I clicked on screen and nothing happens. I switched to text mode & then again switched back to GUI mode few times, after switching for few times it worked. - I logged in to KDE GUI. When clicked on any menu it gave error. Anybody facing these issues? I have allocated 8GB ram to my virtual appliance and 16GB disk space. URL of my appliance for reference = https://susestudio.com/a/RyJgU8/amey-s-opensuse-leap-42-1-kde-4-desktop Regards, Amey. -- 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] heads up, kernel/stable upgrade -> 4.7.x breaks Xen 4.7 Dom0 boot; Xen-only hardware crash
by John Connett 10 Sep '16

10 Sep '16

I'm also experiencing this on openSUSE Tumbleweed (20160817) (x86_64): kernel-default-4.7.0-2.2.x86_64 xen-4.7.0_10-1.1.x86_64 xen-tools-4.7.0_10-1.1.x86_64 System updated today with zypper up then Xen installed with: YaST -> Virtualization -> Install Hypervisor and Tools then selecting Xen server and Xen tools. Non-Xen boot working. Xen boot crashes. Below is an excerpt from the console log. Is there a Bugzilla bug number for this? Any other useful information that I could supply? ---------------------------------------------------------------------- [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] efi: EFI_MEMMAP is not enabled. [ 0.000000] esrt: ESRT header is not in the memory map. (XEN) d0v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from 0000000000000018: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d08023098a entry.o#create_bounce_frame+0x137/0x146 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.7.0_10-1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff81f6374c>] (XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest (d0v0) (XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000100000000 (XEN) rdx: 000000081e600000 rsi: ffffffff81efb280 rdi: 000000081e600000 (XEN) rbp: 0000000000000000 rsp: ffffffff81e03e50 r8: 0000000000000200 (XEN) r9: 0000000000000000 r10: 0000000000007ff0 r11: 0000000000000067 (XEN) r12: 0000000000000000 r13: ffffffff81e03f28 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526e0 (XEN) cr3: 0000000801e06000 cr2: 0000000000000018 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81e03e50: (XEN) 0000000100000000 0000000000000067 0000000000000000 ffffffff81f6374c (XEN) 000000010000e030 0000000000010046 ffffffff81e03e98 000000000000e02b (XEN) ffffffff820e2ce0 0000000001000000 0000000001290000 0000000000000000 (XEN) ffffffff81e03f28 ffffffff81f4d940 ffffffff8118b419 ffffffff00000010 (XEN) ffffffff81e03f28 ffffffff81e03ee0 000000000000001a 0000000000000000 (XEN) ffffffffffffffff 0000000000000000 ffffffff81fe9920 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff81f42b92 ffffffff81ff62e0 (XEN) ffffffff81e03f68 ffffffff81e03f64 0000000000000000 0000000000000000 (XEN) ffffffff81f486b1 000306a900000000 0000000100100800 0300000100000032 (XEN) 0000000000000005 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 4

[opensuse-virtual] leap422 - no /proc/sys/xen/independent_wallclock ?
by Per Jessen 09 Sep '16

09 Sep '16

I don't see this in Leap422. Has it disappeared or become superfluous? /Per -- Per Jessen, Zürich (18.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- 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] should ntp be governing the clock in a guest system?
by Per Jessen 05 Sep '16

05 Sep '16

Continued from opensuse-factory: > >>>> Probably other virtualization technology have the same issue, do > >>>> not use ntp. I do not know for certain. > >>> > >>> With xen, my guests run ntpd and have xen.independent_wallclock=1. > >> > >> And both host and guest try to adjust the speed of the mother board > >> hardware clock chip? (not the bios clock, that's a very different > >> one). > > > > No, only the Dom0 does that. The guests are independent when you > > use xen.independent_wallclock=1. > > >http://www.novell.com/documentation/vmserver/config_options/data/b9qzhq5.ht… > > But if you run the ntp daemon on guests, it tries to adjust the speed > of the clock there. That's how it works. Of course, that's what you want it to do. You want the guest clock synchronized. It would appear to be a good idea to have ntp on the xen Dom0 govern the clock for all the guests, but in my experience systemd does not like that. I looked into in March 2015 when I was virtualising some systems, and found the Novell page above. The Xen FAQ: https://wiki.xen.org/wiki/Xen_FAQ_DomU also recommends running ntp in each DomU. Finally, Werner Flamme wrote: > When you install SAP systems on top of Xenified VMs, there is the > recommendation to do the latter: disable the sync and run a separate > ntpd in the DomU. This is also a recommendation for VMs inside a > VMWare environment - the problem ist the same there. Back in March last year I did ask what the typical practice was, but noone had any suggestions. -- Per Jessen, Zürich (25.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 8

[opensuse-virtual] heads up, kernel/stable upgrade -> 4.7.x breaks Xen 4.7 Dom0 boot; Xen-only hardware crash
by lists＠ssl-mail.com 26 Jul '16

26 Jul '16

fyi, kernel upgrade from 4.6.x to uname -rm 4.7.0-4.g89a2ada-default x86_64 Xen 4.7.0 Dom0 boot now fails, below; boot to non-Xen ok. trace below; starting to look around. ---------------------------- Booting `OpenSUSE, with Xen hypervisor'Booting `OpenSUSE, with Xen hypervisor' Loading Xen 4.7.0_08-452 with Linux 4.7.0-4.g89a2ada-default ...Loading Xen 4.7.0_08-452 wit. /EndEntire /EndEntire file path: file path: /ACPI(a0341d0,0)/ACPI(a0341d0,0)/PCI(1,1c)/PCI(1,1c)/PCI(0,0)/PCI(0,0)r (cf31fac5-c24e-11d2-85f3-00a0c93ec93b)[1: /HardwareVendor(cf31fac5-c24e-11d2-85f3-00a0c93ec93b)[1: 88 88 ]]/HD(2,1000,96000,c5cc9661278 ,2,2)/HD(2,1000,96000,c5cc9661271ee648,2,2)/File(\EFI\OPENSUSE) /File(\EFI\OPENSUSE)/File(xen-4.7.0_08-452.efi)/File(xen-4.7.0_08-452.efi)/EndEntire /EndEntire Xen 4.7.0_08-452 (c/s ) EFI loader Using configuration file 'xen-4.7.0_08-452.cfg' vmlinuz-4.7.0-4.g89a2ada-default: 0x000000008bef9000-0x000000008c5064c0 initrd-4.7.0-4.g89a2ada-default: 0x000000008af52000-0x000000008bef8afc 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x92a26018 0x0000:0x03:0x00.0x0: ROM: 0x8000 bytes at 0x92a1d018 0x0000:0x0f:0x00.0x0: ROM: 0x10800 bytes at 0x929fc018 __ __ _ _ _____ ___ ___ ___ _ _ ____ ____ \ \/ /___ _ __ | || | |___ / _ \ / _ \ ( _ ) | || || ___|___ \ \ // _ \ '_ \ | || |_ / / | | | | | | |/ _ \ __| || ||___ \ __) | / \ __/ | | | |__ _| / /| |_| | | |_| | (_) |__|__ _|__) / __/ /_/\_\___|_| |_| |_|(_)_/(_)___/___\___/ \___/ |_||____/_____| |_____| (XEN) Xen version 4.7.0_08-452 (abuild(a)suse.de) (gcc (SUSE Linux) 4.8.5) debug=n Thu Jun 23 6 (XEN) Latest ChangeSet: (XEN) Console output is synchronous. (XEN) Bootloader: EFI (XEN) Command line: dom0_mem=4096M,max:4096M dom0_max_vcpus=1 dom0_vcpus_pin=true cpuidle=1 (XEN) Video information: (XEN) VGA is graphics mode 800x600, 32 bpp (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 6 EDD information structures (XEN) EFI RAM map: (XEN) 0000000000000000 - 0000000000008000 (reserved) (XEN) 0000000000008000 - 0000000000048000 (usable) (XEN) 0000000000048000 - 0000000000059000 (reserved) (XEN) 0000000000059000 - 000000000005f000 (usable) (XEN) 000000000005f000 - 00000000000a0000 (reserved) (XEN) 0000000000100000 - 000000008d93e000 (usable) (XEN) 000000008d93e000 - 000000008d945000 (ACPI NVS) (XEN) 000000008d945000 - 000000008e25a000 (reserved) (XEN) 000000008e25a000 - 000000008e260000 (usable) (XEN) 000000008e260000 - 000000008e6a1000 (reserved) (XEN) 000000008e6a1000 - 0000000091785000 (usable) (XEN) 0000000091785000 - 00000000919ed000 (reserved) (XEN) 00000000919ed000 - 0000000091a20000 (usable) (XEN) 0000000091a20000 - 0000000091a87000 (reserved) (XEN) 0000000091a87000 - 0000000091aee000 (usable) (XEN) 0000000091aee000 - 0000000091b89000 (reserved) (XEN) 0000000091b89000 - 0000000091bbd000 (usable) (XEN) 0000000091bbd000 - 0000000091bbe000 (reserved) (XEN) 0000000091bbe000 - 0000000091bbf000 (usable) (XEN) 0000000091bbf000 - 0000000091bc0000 (reserved) (XEN) 0000000091bc0000 - 0000000091bc2000 (usable) (XEN) 0000000091bc2000 - 0000000091bc3000 (reserved) (XEN) 0000000091bc3000 - 0000000091bca000 (usable) (XEN) 0000000091bca000 - 0000000091bcc000 (reserved) (XEN) 0000000091bcc000 - 0000000091bdf000 (usable) (XEN) 0000000091bdf000 - 0000000091bea000 (reserved) (XEN) 0000000091bea000 - 0000000091c6b000 (usable) (XEN) 0000000091c6b000 - 0000000091ce8000 (reserved) (XEN) 0000000091ce8000 - 0000000091d32000 (usable) (XEN) 0000000091d32000 - 0000000092090000 (reserved) (XEN) 0000000092090000 - 00000000920d7000 (usable) (XEN) 00000000920d7000 - 000000009214d000 (reserved) (XEN) 000000009214d000 - 0000000092180000 (usable) (XEN) 0000000092180000 - 0000000092298000 (reserved) (XEN) 0000000092298000 - 00000000922b7000 (usable) (XEN) 00000000922b7000 - 000000009235b000 (reserved) (XEN) 000000009235b000 - 0000000092365000 (usable) (XEN) 0000000092365000 - 0000000092464000 (reserved) (XEN) 0000000092464000 - 0000000092469000 (usable) (XEN) 0000000092469000 - 00000000925b8000 (reserved) (XEN) 00000000925b8000 - 00000000925ba000 (usable) (XEN) 00000000925ba000 - 00000000925c0000 (reserved) (XEN) 00000000925c0000 - 00000000925c2000 (usable) (XEN) 00000000925c2000 - 00000000925c9000 (reserved) (XEN) 00000000925c9000 - 00000000925cb000 (usable) (XEN) 00000000925cb000 - 00000000925d2000 (reserved) (XEN) 00000000925d2000 - 00000000925d5000 (usable) (XEN) 00000000925d5000 - 00000000925e8000 (reserved) (XEN) 00000000925e8000 - 00000000925eb000 (usable) (XEN) 00000000925eb000 - 00000000925ee000 (reserved) (XEN) 00000000925ee000 - 00000000925f1000 (usable) (XEN) 00000000925f1000 - 0000000092825000 (reserved) (XEN) 0000000092825000 - 0000000092827000 (usable) (XEN) 0000000092827000 - 0000000092861000 (reserved) (XEN) 0000000092861000 - 0000000092863000 (usable) (XEN) 0000000092863000 - 000000009286c000 (reserved) (XEN) 000000009286c000 - 000000009286e000 (usable) (XEN) 000000009286e000 - 0000000092874000 (reserved) (XEN) 0000000092874000 - 0000000092876000 (usable) (XEN) 0000000092876000 - 000000009e1a0000 (reserved) (XEN) 000000009e1a0000 - 000000009e430000 (usable) (XEN) 000000009e430000 - 000000009e845000 (reserved) (XEN) 000000009e845000 - 000000009e891000 (usable) (XEN) 000000009e891000 - 000000009e9c5000 (ACPI NVS) (XEN) 000000009e9c5000 - 000000009f000000 (reserved) (XEN) 00000000f0000000 - 00000000f8000000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fed00000 - 00000000fed04000 (reserved) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000085e000000 (usable) (XEN) ACPI: RSDP 9E995000, 0024 (r2 SUPERM) (XEN) ACPI: XSDT 9E995090, 009C (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FACP 9E9A32E8, 010C (r5 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: DSDT 9E9951C0, E121 (r2 SUPERM SMCI--MB 0 INTL 20120711) (XEN) ACPI: FACS 9E9C4F80, 0040 (XEN) ACPI: APIC 9E9A33F8, 0072 (r3 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FPDT 9E9A3470, 0044 (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: FIDT 9E9A34B8, 009C (r1 SUPERM SMCI--MB 1072009 AMI 10013) (XEN) ACPI: SSDT 9E9A3558, 0C7D (r2 Ther_R Ther_Rvp 1000 INTL 20120711) (XEN) ACPI: SSDT 9E9A41D8, 0539 (r2 PmRef Cpu0Ist 3000 INTL 20051117) (XEN) ACPI: SSDT 9E9A4718, 0B74 (r2 CpuRef CpuSsdt 3000 INTL 20051117) (XEN) ACPI: SSDT 9E9A5290, 02DE (r2 PmRef Cpu0Tst 3000 INTL 20051117) (XEN) ACPI: SSDT 9E9A5570, 0348 (r2 PmRef ApTst 3000 INTL 20051117) (XEN) ACPI: MCFG 9E9A58B8, 003C (r1 SUPERM SMCI--MB 1072009 MSFT 97) (XEN) ACPI: HPET 9E9A58F8, 0038 (r1 SUPERM SMCI--MB 1072009 AMI. 5) (XEN) ACPI: SSDT 9E9A5930, 0397 (r1 SataRe SataTabl 1000 INTL 20120711) (XEN) ACPI: SSDT 9E9A5CC8, 57F6 (r2 SaSsdt SaSsdt 3000 INTL 20120711) (XEN) ACPI: ASF! 9E9AB4C0, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) ACPI: DMAR 9E9AB568, 0080 (r1 INTEL BDW 1 INTL 1) (XEN) System RAM: 32494MB (33274620kB) (XEN) Domain heap initialised (XEN) Allocated console ring of 64 KiB. (XEN) ACPI: 32/64X FACS address mismatch in FADT - 9e9c4f80/0000000000000000, using 32 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) [VT-D]Host address width 39 (XEN) [VT-D]found ACPI_DMAR_DRHD: (XEN) [VT-D] dmaru->address = fed90000 (XEN) [VT-D]drhd->address = fed90000 iommu->reg = ffff82c0003e2000 (XEN) [VT-D]cap = d2008c20660462 ecap = f010da (XEN) [VT-D] IOAPIC: 0000:f0:1f.0 (XEN) [VT-D] MSI HPET: 0000:f0:0f.0 (XEN) [VT-D] flags: INCLUDE_ALL (XEN) [VT-D]found ACPI_DMAR_RMRR: (XEN) [VT-D] endpoint: 0000:00:1d.0 (XEN) [VT-D] endpoint: 0000:00:1a.0 (XEN) [VT-D] endpoint: 0000:00:14.0 (XEN) [VT-D] RMRR region: base_addr 9eea5000 end_address 9eeb3fff (XEN) mapped APIC to ffff82cfffffb000 (fee00000) (XEN) mapped IOAPIC to ffff82cfffffa000 (fec00000) (XEN) Not enabling x2APIC (upon firmware request) (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3092.924 MHz processor. (XEN) Initing memory sharing. (XEN) spurious 8259A interrupt: IRQ7. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Suppress EOI broadcast on CPU#0 (XEN) enabled ExtINT on CPU#0 (XEN) ENABLING IO-APIC IRQs (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 3092.8451 MHz. (XEN) ..... host bus clock speed is 99.7692 MHz. (XEN) ..... bus_scale = 0x662a (XEN) [2016-07-25 22:47:36] Platform timer is 14.318MHz HPET (XEN) [2016-07-25 22:47:36] VMX: Supported advanced features: (XEN) [2016-07-25 22:47:36] - APIC MMIO access virtualisation (XEN) [2016-07-25 22:47:36] - APIC TPR shadow (XEN) [2016-07-25 22:47:36] - Extended Page Tables (EPT) (XEN) [2016-07-25 22:47:36] - Virtual-Processor Identifiers (VPID) (XEN) [2016-07-25 22:47:36] - Virtual NMI (XEN) [2016-07-25 22:47:36] - MSR direct-access bitmap (XEN) [2016-07-25 22:47:36] - Unrestricted Guest (XEN) [2016-07-25 22:47:36] - VMCS shadowing (XEN) [2016-07-25 22:47:36] - VM Functions (XEN) [2016-07-25 22:47:36] HVM: ASIDs enabled. (XEN) [2016-07-25 22:47:36] HVM: VMX enabled (XEN) [2016-07-25 22:47:36] HVM: Hardware Assisted Paging (HAP) detected (XEN) [2016-07-25 22:47:36] HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) [2016-07-25 22:47:36] Suppress EOI broadcast on CPU#1 (XEN) [2016-07-25 22:47:36] masked ExtINT on CPU#1 (XEN) [2016-07-25 22:47:36] [VT-D]INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, i0 (XEN) [2016-07-25 22:47:36] [VT-D]INTR-REMAP: reason 22 - Present field in the IRTE entry isr (XEN) [2016-07-25 22:47:36] Suppress EOI broadcast on CPU#2 (XEN) [2016-07-25 22:47:36] masked ExtINT on CPU#2 (XEN) [2016-07-25 22:47:36] Suppress EOI broadcast on CPU#3 (XEN) [2016-07-25 22:47:36] masked ExtINT on CPU#3 (XEN) [2016-07-25 22:47:36] Brought up 4 CPUs (XEN) [2016-07-25 22:47:36] Dom0 has maximum 216 PIRQs (XEN) [2016-07-25 22:47:36] *** LOADING DOMAIN 0 *** (XEN) [2016-07-25 22:47:36] Xen kernel: 64-bit, lsb, compat32 (XEN) [2016-07-25 22:47:36] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2290000 (XEN) [2016-07-25 22:47:36] PHYSICAL MEMORY ARRANGEMENT: (XEN) [2016-07-25 22:47:36] Dom0 alloc.: 0000000840000000->0000000844000000 (1028185 page) (XEN) [2016-07-25 22:47:36] Init. ramdisk: 000000085d059000->000000085dfffafc (XEN) [2016-07-25 22:47:36] VIRTUAL MEMORY ARRANGEMENT: (XEN) [2016-07-25 22:47:36] Loaded kernel: ffffffff81000000->ffffffff82290000 (XEN) [2016-07-25 22:47:36] Init. ramdisk: 0000000000000000->0000000000000000 (XEN) [2016-07-25 22:47:36] Phys-Mach map: 0000008000000000->0000008000800000 (XEN) [2016-07-25 22:47:36] Start info: ffffffff82290000->ffffffff822904b4 (XEN) [2016-07-25 22:47:36] Page tables: ffffffff82291000->ffffffff822a6000 (XEN) [2016-07-25 22:47:36] Boot stack: ffffffff822a6000->ffffffff822a7000 (XEN) [2016-07-25 22:47:36] TOTAL: ffffffff80000000->ffffffff82400000 (XEN) [2016-07-25 22:47:36] ENTRY ADDRESS: ffffffff81f42180 (XEN) [2016-07-25 22:47:36] Dom0 has maximum 1 VCPUs (XEN) [2016-07-25 22:47:39] Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) [2016-07-25 22:47:39] [VT-D]iommu_enable_translation: iommu->reg = ffff82c0003e2000 (XEN) [2016-07-25 22:47:39] Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) [2016-07-25 22:47:39] ................................................................. (XEN) [2016-07-25 22:47:40] Initial low memory virq threshold set at 0x4000 pages. (XEN) [2016-07-25 22:47:40] Std. Loglevel: Errors and warnings (XEN) [2016-07-25 22:47:40] Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) [2016-07-25 22:47:40] ********************************************** (XEN) [2016-07-25 22:47:40] ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) [2016-07-25 22:47:40] ******* This option is intended to aid debugging of Xen by ensurg (XEN) [2016-07-25 22:47:40] ******* that all output is synchronously delivered on the serial. (XEN) [2016-07-25 22:47:40] ******* However it can introduce SIGNIFICANT latencies and affect (XEN) [2016-07-25 22:47:40] ******* timekeeping. It is NOT recommended for production use! (XEN) [2016-07-25 22:47:40] ********************************************** (XEN) [2016-07-25 22:47:40] 3... 2... 1... (XEN) [2016-07-25 22:47:43] Xen is relinquishing VGA console. (XEN) [2016-07-25 22:47:43] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch in) (XEN) [2016-07-25 22:47:43] Freed 328kB init memory. mapping kernel into physical memory about to get started... [ 0.000000] Linux version 4.7.0-4.g89a2ada-default (geeko@buildhost) (gcc version 6.1.1 2) [ 0.000000] efi: EFI_MEMMAP is not enabled. [ 0.000000] esrt: ESRT header is not in the memory map. (XEN) [2016-07-25 22:47:43] d0v0: unhandled page fault (ec=0000) (XEN) [2016-07-25 22:47:43] Pagetable walk from 0000000000000018: (XEN) [2016-07-25 22:47:43] L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) [2016-07-25 22:47:43] domain_crash_sync called from entry.S: fault at ffff82d08022ca4a6 (XEN) [2016-07-25 22:47:44] Domain 0 (vcpu#0) crashed on cpu#0: (XEN) [2016-07-25 22:47:44] ----[ Xen-4.7.0_08-452 x86_64 debug=n Tainted: C ]---- (XEN) [2016-07-25 22:47:44] CPU: 0 (XEN) [2016-07-25 22:47:44] RIP: e033:[<ffffffff81f6374c>] (XEN) [2016-07-25 22:47:44] RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest (d0v0) (XEN) [2016-07-25 22:47:44] rax: 0000000000000000 rbx: 0000000000000000 rcx: 000000010000 (XEN) [2016-07-25 22:47:44] rdx: 000000016f141000 rsi: ffffffff81efb2c0 rdi: 000000016f10 (XEN) [2016-07-25 22:47:44] rbp: 0000000000000000 rsp: ffffffff81e03e50 r8: 000000000000 (XEN) [2016-07-25 22:47:44] r9: 0000000000000000 r10: 0000000000007ff0 r11: 000000000007 (XEN) [2016-07-25 22:47:44] r12: 0000000000000000 r13: ffffffff81e03f28 r14: 000000000000 (XEN) [2016-07-25 22:47:44] r15: 0000000000000000 cr0: 0000000080050033 cr4: 000000000010 (XEN) [2016-07-25 22:47:44] cr3: 0000000841e06000 cr2: 0000000000000018 (XEN) [2016-07-25 22:47:44] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) [2016-07-25 22:47:44] Guest stack trace from rsp=ffffffff81e03e50: (XEN) [2016-07-25 22:47:44] 0000000100000000 0000000000000067 0000000000000000 ffffffff81c (XEN) [2016-07-25 22:47:44] 000000010000e030 0000000000010046 ffffffff81e03e98 0000000000b (XEN) [2016-07-25 22:47:44] ffffffff820e2ce0 0000000001000000 0000000001290000 00000000000 (XEN) [2016-07-25 22:47:44] ffffffff81e03f28 ffffffff81f4d940 ffffffff8118b419 ffffffff000 (XEN) [2016-07-25 22:47:44] ffffffff81e03f28 ffffffff81e03ee0 000000000000001a 00000000000 (XEN) [2016-07-25 22:47:44] ffffffffffffffff 0000000000000000 ffffffff81fe9920 00000000000 (XEN) [2016-07-25 22:47:44] 0000000000000000 0000000000000000 ffffffff81f42b92 ffffffff810 (XEN) [2016-07-25 22:47:44] ffffffff81e03f68 ffffffff81e03f64 0000000000000000 00000000000 (XEN) [2016-07-25 22:47:44] ffffffff81f486b1 000306c300000000 0000000100100800 03000001002 (XEN) [2016-07-25 22:47:44] 0000000000000005 0000000000000000 0000000000000000 00000000000 (XEN) [2016-07-25 22:47:44] 0000000000000000 0000000000000000 0000000000000000 00000000000 (XEN) [2016-07-25 22:47:44] 0000000000000000 0000000000000000 0000000000000000 00000000000 (XEN) [2016-07-25 22:47:44] 0000000000000000 0000000000000000 0000000000000000 00000000000 (XEN) [2016-07-25 22:47:44] 0000000000000000 0000000000000000 0f00000060c0c748 cccccccccc5 (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] cccccccccccccccc cccccccccccccccc cccccccccccccccc ccccccccccc (XEN) [2016-07-25 22:47:44] Hardware Dom0 crashed: rebooting machine in 5 seconds. (XEN) [2016-07-25 22:47:44] APIC error on CPU0: 40(00) (XEN) [2016-07-25 22:47:49] ----[ Xen-4.7.0_08-452 x86_64 debug=n Tainted: C ]---- (XEN) [2016-07-25 22:47:49] CPU: 0 (XEN) [2016-07-25 22:47:49] RIP: e008:[<000000009e7463c6>] 000000009e7463c6 (XEN) [2016-07-25 22:47:49] RFLAGS: 0000000000010202 CONTEXT: hypervisor (d0v0) (XEN) [2016-07-25 22:47:49] rax: 0000000000000003 rbx: 0000000000000000 rcx: 000000000000 (XEN) [2016-07-25 22:47:49] rdx: 000000009e7467a0 rsi: 0000000000000000 rdi: 000000000000 (XEN) [2016-07-25 22:47:49] rbp: 0000000000000000 rsp: ffff83008ce27d78 r8: ffff83008ce8 (XEN) [2016-07-25 22:47:49] r9: ffff83008ce27da8 r10: 0000000000000000 r11: 000000000000 (XEN) [2016-07-25 22:47:49] r12: 0000000000000000 r13: 0000000000000cf9 r14: 000000000005 (XEN) [2016-07-25 22:47:49] r15: ffff830000000000 cr0: 0000000080050033 cr4: 000000000010 (XEN) [2016-07-25 22:47:49] cr3: 000000084b4fd000 cr2: 0000000000000018 (XEN) [2016-07-25 22:47:49] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) [2016-07-25 22:47:49] Xen code around <000000009e7463c6> (000000009e7463c6): (XEN) [2016-07-25 22:47:49] 0f 48 8b 44 24 40 8b ce <ff> 50 08 3b d8 0f 4c d8 48 ff c7 48 30 (XEN) [2016-07-25 22:47:49] Xen stack trace from rsp=ffff83008ce27d78: (XEN) [2016-07-25 22:47:49] ffff83084b4bb1c0 0000000000000000 0000000000000000 ffff82d0806 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

[opensuse-virtual] resizing virtual disks on kvm
by Wolfgang Rosenauer 17 Jul '16

17 Jul '16

Hi, let me first describe my setup (and you can also give me arguments if there are better ways to achieve that) first: I'm running a virtualization host using libvirt/kvm/qemu on openSUSE Leap 42.1. The host system is based on LVM and when I create guests I always create one LV for every mountpoint I'm using within the guest. (like /dev/system/GUEST_root, /dev/system/GUEST_var) >From within the guest I just create one primary partition on those virtual disk. I basically do it this way because I did it with Xen since quite some time that way because it gave me rather easy possibilities to grow partitions w/o using LVM also within the guest. Now I'm struggling with resizing/growing certain virtual disks/partitions though. I'll explain what I'm doing and if you know better ways just let me know: - on the host: lvresize -L+10G /dev/system/GUEST_var - on the host: parted /dev/system/GUEST_VAR ; (print free); resize 1 XGB Now my LV and partition should be resized - on the guest: try to just do "resize2fs" (my default FS is ext4) This fails because the guest does not know about the changed partition table. I tried several recommendations like - partprobe - rescan-scsi-bus.sh without success. I also finally rebooted the guest (no stop/start but "reboot" command). Still the size of the partition listed by fdisk the the previous smaller one. What do I need to do to let the guest know about the changed partition table? I would expect at least non-root FS can be changed online. If a "reboot" is not enough, would stop/start fix it? (This is a production machine. I cannot easily test that w/o further maintenance windows.) How do others handle that usecase? Is there an easier/better way to manage filesystem sizes online? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] resizing virtual disks on kvm
by Wolfgang Rosenauer 16 Jul '16

16 Jul '16

Hi, let me first describe my setup (and you can also give me arguments if there are better ways to achieve that) first: I'm running a virtualization host using libvirt/kvm/qemu on openSUSE Leap 42.1. The host system is based on LVM and when I create guests I always create one LV for every mountpoint I'm using within the guest. (like /dev/system/GUEST_root, /dev/system/GUEST_var) >From within the guest I just create one primary partition on those virtual disk. I basically do it this way because I did it with Xen since quite some time that way because it gave me rather easy possibilities to grow partitions w/o using LVM also within the guest. Now I'm struggling with resizing/growing certain virtual disks/partitions though. I'll explain what I'm doing and if you know better ways just let me know: - on the host: lvresize -L+10G /dev/system/GUEST_var - on the host: parted /dev/system/GUEST_VAR ; (print free); resize 1 XGB Now my LV and partition should be resized - on the guest: try to just do "resize2fs" (my default FS is ext4) This fails because the guest does not know about the changed partition table. I tried several recommendations like - partprobe - rescan-scsi-bus.sh without success. I also finally rebooted the guest (no stop/start but "reboot" command). Still the size of the partition listed by fdisk the the previous smaller one. What do I need to do to let the guest know about the changed partition table? I would expect at least non-root FS can be changed online. If a "reboot" is not enough, would stop/start fix it? (This is a production machine. I cannot easily test that w/o further maintenance windows.) How do others handle that usecase? Is there an easier/better way to manage filesystem sizes online? Thanks, Wolfgang -- 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] KVM + Kimchi on Leap 42.1
by Ciro Iriarte 11 Jul '16

11 Jul '16

Hi!, I just did a fresh install of Leap 42.1 + updates + Virtualization repo, and trying to start the service I get a timeout on the libvirtd.service dependency, all I see is a "unable to notify systemd" message. Anybody has seen this?, any suggestion?. Regards, -- Ciro Iriarte http://iriarte.it -- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 5

[opensuse-virtual] Home virtualization Lab
by Ciro Iriarte 07 Jul '16

07 Jul '16

Hi!, I'm building a new NAS box (Leap + btrfs) which is a little over powered so I would love to use it as a personal virtualization lab. Xenserver/ESXi/Proxmox/Acropolis are out because of software R6 and having a single host, so I'm turning to openSUSE. I've worked a lot with Xen years ago but I understand the guys that get all the attention these days are KVM and docker, and Xen might be a second class citizen. Given I would like: - Software R6 on the host - Virtualization nesting - PCI passthrough - Some permanent VMs - Lots of temporary VMs Would you suggest to go with XEN or KVM or Virtualbox in this specific scenario at this point in time?, can I assume docker will place nice with any of them?. Regards, -- Ciro Iriarte http://iriarte.it -- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 4

[opensuse-virtual] Leap 42.1 guest in Virtualbox 5.0.20 => need to update initramfs after Oracle guest addition installation
by Ingmar Sittl 12 May '16

12 May '16

Hi, if you want to run Virtualbox 5.0.20 with a Leap 42.1 guest, after uninstalling the Opensuse-provided guest additions and building the proper 5.0.20 guest additions you still need to rerun the bootloader installation from yast, as the initramfs seems to still contain and load the 5.0.16_OpenSUSE vboxguest kernel module otherwise. Regards, Ingmar -- 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 Leap in Xen UEFI PVHVM DomU fails - boots to UEFI shell? non-UEFI openSUSE works. UEFI with systemd-boot works.
by PGNet Dev 04 Mar '16

04 Mar '16

I'm running openSUSE Leap 42.1 server as a Xen 4.6 Dom0. I'm working on booting UEFI, PVHVM DomUs. Current Dom0 packages include, from OBS xen-4.6.20160218T142520.046e5d0 --> includes "--with-ovmf" support for UEFI boot grub2-x86_64-xen-2.02~beta3-305.1 --> include patches for efi command line paramaeters kernel-default-4.4.4-1.1.g0c1f87e --> pvops native kernel I'm installing the Xen PVHVM DomU from openSUSE release ISO. For a non-UEFI Guest, with attached blkdevs, xvda, gpt, ext4, "/boot" xvde, gpt, swap, "swap" xvdf, gpt, ext4, "/" the installer procedure completes without error. On Guest reboot, the Guest is up & running. For a UEFI Guest, with attached blkdevs, xvda, gpt, vfat, "/boot/efi" xvde, gpt, ext4, "/boot" xvdf, gpt, swap, "swap" xvdg, gpt, ext4, "/" the installer procedure again completes without error. But, on reboot, the Guest drops to the EFI shell. Repeating install of a UEFI Guest, but this time Arch linux, with available systemd-boot UEFI bootloader rather than Grub, the UEFI Guest is up & running. systemd-boot is a simpler/leaner option for UEFI DomU, It's available for other OSs, but as I understand, a systemd upgrade will NOT be provided for Leap 42.1, and, atm, systemd builds at OBS for Leap are not working. What additional steps or config enable EUFI Guest boot of openSUSE -- as installed by installer, with its Grub2 bootloader -- to boot without dropping to the UEFI shell? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

[opensuse-virtual] Install of openSUSE in PVHVM DomU guest presents (incorrectly?) blkdevs as both 'sdX' and 'xvdX'?
by PGNet Dev 02 Mar '16

02 Mar '16

I'm installing openSUSE Leap in a Xen 4.6.x DomU guest. I'm launching the guest as PVHVM, using the openSUSE iso as cdrom. cat os-install.cfg builder = 'hvm' xen_platform_pci = 1 device_model_version="qemu-xen" boot = 'dc' hdtype = 'ahci' acpi = 1 apic = 1 disk = [ 'phy:/dev/VG_XEN/G001_BOOT,xvda,w', 'phy:/dev/VG_XEN/G001_SWAP,xvde,w', 'phy:/dev/VG_XEN/G001_ROOT,xvdf,w', 'file:/home/isos/openSUSE-Leap-42.1-DVD-x86_64.iso,hdb:cdrom,r', ] vif = [ 'mac=00:16:3E:01:01:01, model=e1000, bridge=br0, vifname=vif001',] bios = 'seabios' ... On Guest launch, connected to the openSUSE Graphical Installer via VNC, I select 'Create Partition Setup'. In the "Preparing Hard Disk" screen, available HDs present as: Hard Disk [ ] 1: 1. IDE Disk 512.00 MiB, /dev/sda, QEMU+HARDDISK [ ] 2: 2. IDE Disk 512.00 MiB, /dev/sdb, QEMU+HARDDISK [ ] 3: 3. IDE Disk 512.00 MiB, /dev/sdc, QEMU+HARDDISK [ ] 4: 1. Disk 512.00 MiB, /dev/xvda [ ] 5: 2. Disk 512.00 MiB, /dev/xvde [ ] 6: 3. Disk 512.00 MiB, /dev/xvdf On selection of "Custom Partitioning", the following screen's presented, http://snag.gy/5ywyA.jpg Showing BOTH sdX & xvdX drives to be partitioned. At best, it's confusing. In PVHVM, Xen converts/maintains disk identities as both hvX and xvdX, for internal use. However for the purposes of the installer, here, shouldn't only the intended 'xvdX' drives (4,5, & 6) should be presented, not the 'sdX' ? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] how to update the config for a xen domu
by Per Jessen 01 Mar '16

01 Mar '16

Assume something along these lines - a xen domu is created from config-file on hostA, then migrated to hostB. On hostB, a new disk is added with "xl block-attach", works very well. However "xl list --long <domu>" doesn't reflect this change. "xl config-update" seems to be a way to edit config files, but once the domU has been migrated to hostB, the original file isn't immediately available - what do I need to get the new block device reflected in the config that goes with the domU ? -- Per Jessen, Zürich (2.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

4 4

[opensuse-virtual] Requesting OVMH support be added to Virtualizaton:Xen builds
by suse.dev＠fea.st 23 Feb '16

23 Feb '16

Just fyi'ing here. I posetd the request for OVMH support in Xen builds at Bug 967869 - Virtualization/xen: Bug current Xen build missing "--with-ovmf" option needed to support UEFI guests https://bugzilla.opensuse.org/show_bug.cgi?id=967869 Thanks. -- 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] virtualbox kernel modules update
by Stephan Uhlmann 20 Feb '16

20 Feb '16

Hi, in http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/x86_… the last update for virtualbox-{host|guest}-kmp-* is for kernel 3.11.10-29. openSUSE 13.1 was recently updated to kernel 3.11.10-34. Will there be an update of the Virtualization-repo? Seems to affect 13.2 as well. Thanks, Stephan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 4

[opensuse-virtual] Xen: xm new --> xl ??
by Rieß Norman 19 Feb '16

19 Feb '16

Hello, i noticed in SLES 12.1 that xl does not have a „xl new“ command any more. I was heavily using „xm new“ with plain text configs. „virsh define“ only works with xml files. Is there any way to add a domain and not start it from a plain text config? Regards, NormanN��r��y隊Z)z{.��ۚ�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��ۚ��0��Ǩ�

3 4

[opensuse-virtual] Xen guest types on OpenSUSE. I can get PV working, but not PVHVM. Need some help figuring out what's wrong.
by suse.dev＠fea.st 25 Jan '16

25 Jan '16

I'm working on guests on a a Leap Xen server, rpm -qa kernel-default xen xen-4.6.0_08-404.1.x86_64 kernel-default-4.4.0-5.1.gb56b151.x86_64 I can set up a PV guest cat /etc/xen/vm/test_pv name = 'test' builder = 'linux' bootloader = 'pygrub' bootargs = '' disk = [ 'phy:/dev/VG0/TEST_OS,xvda,w',] root = '/dev/xvdc1' vif = [ 'mac=00:16:4f:02:02:15, bridge=br0, vifname=vif0',] extra = 'textmode=1 xencons=xvc0 console=hvc0' on_crash = 'destroy' on_shutdown = 'destroy' on_reboot = 'restart' vcpus = 4 xen_platform_pci = 0 I launch it xl create -c /etc/xen/vm/test_pv and it works okay. I want to switch the guest type from PV -> PVHVM. Reading docs on the Xen site http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers I change the config to cat /etc/xen/vm/test_pvhvm name = 'test' builder = 'linux' bootloader = 'pygrub' bootargs = '' disk = [ 'phy:/dev/VG0/TEST_OS,hda,w',] root = '/dev/hda1' vif = [ 'mac=00:16:4f:02:02:15, bridge=br0, vifname=vif0, model=e1000',] extra = 'textmode=1 xencons=xvc0 console=hvc0' on_crash = 'destroy' on_shutdown = 'destroy' on_reboot = 'restart' vcpus = 4 xen_platform_pci = 1 But when I launch this one xl create -c /etc/xen/vm/test_pvhvm It gets only this far xl create -c pvhvm.cfg pyGRUB version 0.6 ┌────────────────────────────────────────────────────────────────────────┐ │ openSUSE Leap 42.1 │ │ openSUSE Leap 42.1, with Linux 4.4.0-5.gb56b151-default │ │ openSUSE Leap 42.1, with Linux 4.4.0-5.gb56b151-default (recovery mode)│ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────┘ Use the ^ and ┴ keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Will boot selected entry in 7 seconds [ 0.116131] dmi: Firmware registration failed. [ 1.587244] mce: Unable to init device /dev/mcelog (rc: -5) I'm sure I'm missing some install and set up. Any ideas what? I'd appreciate a hand. Thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 2

[opensuse-virtual] Host-VM filesystem sharing issues using 9p
by Leroy Tennison 19 Jan '16

19 Jan '16

Hypervisor and both VMS are openSUSE 13.2, two VM definitions (template and gary respectively) have the following: <filesystem type='mount' accessmode='squash'> <source dir='/xxx/yyy/zzz/template'/> <target dir='Sec'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </filesystem> -- <filesystem type='mount' accessmode='squash'> <source dir='/xxx/yyy/zzz/gary'/> <target dir='ABC'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </filesystem> Although /xxx/yyy/zzz isn't the real path, the two subdirectories do exist under a common parent. Permissions are: (from root) drwxr-xr-x 5 root root 4096 Aug 11 13:25 xxx (from xxx) drwxr-xr-x 5 root root 1024 Jan 7 18:15 yyy (from yyy) drwxr-xr-x 8 qemu qemu 1024 Jan 11 11:48 zzz (from zzz) drwxrwxr-x 2 qemu libvirt 1024 Jan 14 12:23 gary drwxrwxr-x 2 qemu libvirt 1024 Jan 13 08:19 template On template things work template:/mnt # mount -t 9p -o trans=virtio,version=9p2000.L Sec /mnt/Demo template:/mnt # ll Demo total 3 -rw-r--r-- 1 root root 26 Jan 11 11:08 2nd-Example -rw-r--r-- 1 root root 93 Jan 11 10:45 Example -rw-r--r-- 1 478 474 8 Jan 13 08:19 test On gary I have to load the 9p modules for some reason but, after I do, I get: gary:/mnt # lsmod | grep 9p 9pnet_virtio 17529 0 9p 57012 0 9pnet 80300 2 9p,9pnet_virtio virtio_ring 21225 4 virtio_pci,virtio_rng,virtio_balloon,9pnet_virtio virtio 14474 4 virtio_pci,virtio_rng,virtio_balloon,9pnet_virtio However, gary:/mnt # mount -t 9p -o trans=virtio,version=9p2000.L ABC tmp mount: special device ABC does not exist I've used ABC on another hypervisor, that name isn't a problem. Any ideas or anything else I should check? Other questions: Is there a way to list the 9p "target dir" names on either the hypervisor or, more importantly, the VM? Can duplicate "target dir" entries be used on the same hypervisor if they are for different VMs (i.e, a target dir of ABC on different VMs)? Is so, can they have different paths? Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 2

[opensuse-virtual] 13.2 systemd update breaks udev version detection
by Andreas Färber 18 Dec '15

18 Dec '15

Hello Marcus, Today's https://build.opensuse.org/request/show/347433 seems to have broken 13.2 builds of Virtualization qemu. We have the following snippet there: %if %( echo `rpm -q --queryformat %%{version} udev` ) > 190 %define _udevrulesdir /usr/lib/udev/rules.d %else %define _udevrulesdir /lib/udev/rules.d %endif >From systemd.3661 to systemd.4042 I notice the following change: -Version: 210 +Version: 210.1448627060.53ee915 which looks _service-generated. Was this intentional? If yes, how are we supposed to handle this now? Regards, Andreas P.S. Note that we cannot check in any fix for qemu at this time as that would cause Factory's glorious checker scripts to decline our pending update once again. -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

6 8