- openSUSE Virtual

[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