July 2010 - openSUSE Virtual - openSUSE Mailing Lists

[opensuse-virtual] latest Xen4 OBS -- multiple DomU launch fail.
by 0bo0 31 Jul '10

31 Jul '10

just an FYI ... got a remote 'ping' from the office. latest update to XEN4 repos on 11.3 Dom0 -> launch of multiple DomUs fails. >= 2nd DomU 'stuck @ p-state' (no other diagnostics in message). Dropped server back to 11.3 RELEASE XEN, all's OK. will troubleshoot when not remote. hth. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

[opensuse-virtual] 11.3 on Xen 3.1 (oS 10.3)
by Wolfgang Rosenauer 28 Jul '10

28 Jul '10

Hi, I just tried to install openSUSE 11.3 as guest on a 10.3 (aka Xen 3.1) host but booting the kernel failed immediately. I haven't found useful logfiles but the vm disappears basically immediately again. Should it be possible to run/install 11.3 on Xen 3.1? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

3 7

[opensuse-virtual] Shared Folder in Virtualbox
by Sascha 'saigkill' Manns 19 Jul '10

19 Jul '10

Hello Mates, i've tried to add a shared Folder into VirtualBox. The adding was good, but if i type mount -t vboxsf torrents /mnt i'm getting: linux-lp52:/home/sascha # mount -t vboxsf /multimedia/torrents /mnt mount: wrong fs type, bad option, bad superblock on /multimedia/torrents, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) Manchmal liefert das Syslog wertvolle Informationen – versuchen Sie dmesg | tail oder so Has anyone an Idea, how to fix it? -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

4 4

Re: [opensuse-virtual] @ 11.3 xen Dom0 boot, "microcode: error! Wrong microcode patch file"
by Jan Beulich 13 Jul '10

13 Jul '10

>>> On 09.07.10 at 17:15, 0bo0 <0.bugs.only.0(a)gmail.com> wrote: > On Fri, Jul 9, 2010 at 12:46 AM, Jan Beulich <JBeulich(a)novell.com> wrote: >> The question then is why request_firmware() succeeds. We're not >> talking about a kernel you built yourself, do we? > > no, not custom. atm, this is, > > uname -a > Linux server 2.6.34.1-2-xen #1 SMP 2010-07-06 15:11:07 +0200 x86_64 > x86_64 x86_64 GNU/Linux > lsb_release -a > LSB Version: > core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4. > 0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:g > raphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch > Distributor ID: SUSE LINUX > Description: openSUSE 11.3 (x86_64) > Release: 11.3 > Codename: n/a > grep base /etc/zypp/repos.d/Kernel_113.repo > > baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/open > SUSE_11.3 > >> Again, this is a different thing. Can we please finally get to know how >> a native kernel of the same version behaves? >> >> You may want to set udev_log="info" in /etc/udev/udev.conf and >> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get >> relevant output from /lib/udev/firmware.sh. > >> You may want to set udev_log="info" in /etc/udev/udev.conf and >> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get > > mkdir -p /etc/sysconfig/hardware > > udev_log="info" < -- /etc/udev/udev.conf > USE_SYSLOG="yes" <-- /etc/sysconfig/hardware/config to get > > reboot > uname -a > Linux server 2.6.34.1-2-default #1 SMP 2010-07-06 15:11:07 +0200 > x86_64 x86_64 x86_64 GNU/Linux > > egrep -i "amd|microcode" /var/log/* > ... And for comparison the same with 2.6.34.1-2-xen ? On -default, the messages clearly indicate that request_firmware() is failing on that file (as expected), but the fact that Xen gets presented with a firmware image at all requires that request_firmware() is not failing as expected on -xen. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 3

Re: [opensuse-virtual] @ 11.3 xen Dom0 boot, "microcode: error! Wrong microcode patch file"
by 0bo0 09 Jul '10

09 Jul '10

reply-all didn't get this to list ... posting. On Fri, Jul 9, 2010 at 8:15 AM, 0bo0 <0.bugs.only.0(a)gmail.com> wrote: > On Fri, Jul 9, 2010 at 12:46 AM, Jan Beulich <JBeulich(a)novell.com> wrote: >> The question then is why request_firmware() succeeds. We're not >> talking about a kernel you built yourself, do we? > > no, not custom. atm, this is, > > uname -a > Linux server 2.6.34.1-2-xen #1 SMP 2010-07-06 15:11:07 +0200 x86_64 > x86_64 x86_64 GNU/Linux > lsb_release -a > LSB Version: > core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch > Distributor ID: SUSE LINUX > Description: openSUSE 11.3 (x86_64) > Release: 11.3 > Codename: n/a > grep base /etc/zypp/repos.d/Kernel_113.repo > baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/ope… > >> Again, this is a different thing. Can we please finally get to know how >> a native kernel of the same version behaves? >> >> You may want to set udev_log="info" in /etc/udev/udev.conf and >> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get >> relevant output from /lib/udev/firmware.sh. > >> You may want to set udev_log="info" in /etc/udev/udev.conf and >> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get > > mkdir -p /etc/sysconfig/hardware > > udev_log="info" < -- /etc/udev/udev.conf > USE_SYSLOG="yes" <-- /etc/sysconfig/hardware/config to get > > reboot > uname -a > Linux server 2.6.34.1-2-default #1 SMP 2010-07-06 15:11:07 +0200 > x86_64 x86_64 x86_64 GNU/Linux > > egrep -i "amd|microcode" /var/log/* > boot.msg:<6>[ 0.000000] RAMDISK: 374ec000 - 37ff0000 > boot.msg:<4>[ 0.000000] ACPI: SSDT 00000000cff87950 0088C (v01 A M > I POWERNOW 00000001 AMD 00000001) > boot.msg:<6>[ 0.000000] #2 [00374ec000 - 0037ff0000] RAMDISK > boot.msg:<6>[ 0.108011] Performance Events: AMD PMU driver. > boot.msg:<6>[ 0.389812] CPU0: AMD Phenom(tm) II X4 920 Processor stepping 02 > boot.msg:<6>[ 6.049868] ehci_hcd 0000:00:12.2: applying AMD > SB600/SB700 USB freeze workaround > boot.msg:<6>[ 6.410466] ehci_hcd 0000:00:13.2: applying AMD > SB600/SB700 USB freeze workaround > boot.msg:<6>[ 70.960588] EDAC amd64_edac: Ver: 3.3.0 Jul 7 2010 > boot.msg:<5>[ 70.972413] EDAC amd64: This node reports that Memory > ECC is currently disabled, set F3x44[22] (0000:00:18.3). > boot.msg:<5>[ 70.995125] EDAC amd64: ECC disabled in the BIOS or no > ECC capability, module will not load. > boot.msg:<4>[ 71.052063] amd64_edac: probe of 0000:00:18.2 failed > with error -22 > boot.msg:<6>[ 101.168845] microcode: CPU0: patch_level=0x1000086 > boot.msg:<6>[ 101.179148] platform microcode: firmware: requesting > amd-ucode/microcode_amd.bin > boot.msg:<3>[ 161.196043] microcode: failed to load file > amd-ucode/microcode_amd.bin > boot.msg:<6>[ 161.209155] microcode: CPU1: patch_level=0x1000086 > boot.msg:<6>[ 161.218814] platform microcode: firmware: requesting > amd-ucode/microcode_amd.bin > boot.msg:<3>[ 183.217466] microcode: failed to load file > amd-ucode/microcode_amd.bin > boot.msg:<6>[ 183.231803] microcode: CPU2: patch_level=0x1000086 > boot.msg:<6>[ 183.244129] platform microcode: firmware: requesting > amd-ucode/microcode_amd.bin > boot.msg:<3>[ 183.947110] microcode: failed to load file > amd-ucode/microcode_amd.bin > boot.msg:<6>[ 183.960985] microcode: CPU3: patch_level=0x1000086 > boot.msg:<6>[ 183.973330] platform microcode: firmware: requesting > amd-ucode/microcode_amd.bin > boot.msg:<3>[ 184.714601] microcode: failed to load file > amd-ucode/microcode_amd.bin > boot.msg:<6>[ 184.729013] microcode: Microcode Update Driver: v2.00 > <tigran(a)aivazian.fsnet.co.uk>, Peter Oruba > boot.msg:<6>[ 184.736631] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 184.736649] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 184.784460] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 184.833775] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 184.870692] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 185.577429] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:<6>[ 186.324561] microcode: AMD microcode update via > /dev/cpu/microcode not supported > boot.msg:udevd[851]: reading '/lib/udev/rules.d/89-microcode.rules' as > rules file > boot.msg:udevadm[853]: device 0x622140 has devpath > '/bus/pci/drivers/agpgart-amd64' > boot.msg:device 0x622140 has devpath '/bus/pci/drivers/agpgart-amd64' > boot.msg:udevd[852]: mknod '/dev/cpu/microcode' c10:184 > boot.msg:udevd-work[854]: device 0x621e00 has devpath > '/bus/pci/drivers/agpgart-amd64' > messages:Jul 9 07:58:02 server kernel: [ 256.426728] powernow-k8: > Found 1 AMD Phenom(tm) II X4 920 Processor (4 cpu cores) (version > 2.20.00) > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x622140 has > devpath '/devices/platform/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x6221c0 has > devpath '/devices/virtual/misc/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc10 has > devpath '/devices/platform/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 has > devpath '/devices/virtual/misc/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x622140 has > devpath '/devices/platform/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x6221c0 has > devpath '/devices/virtual/misc/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x6402f0 has > devpath '/devices/platform/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 has > devpath '/devices/virtual/misc/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled > with db symlink data '/dev/cpu/microcode' > messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled > with db symlink data '/dev/cpu/microcode' > > if you want udev_log -> debug level, or other, output, happy to provide it. > -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

[opensuse-virtual] @ 11.3 xen Dom0 boot, "microcode: error! Wrong microcode patch file"
by 0bo0 09 Jul '10

09 Jul '10

all sorts of 'new' info in logs when looking closer ... again, seeming no ill effects to this. fwiw, this box's CPU is: AMD Phenom(tm) II X4 920 Processor anything to worry about? [ 10.580576] platform microcode: firmware: requesting amd-ucode/microcode_amd.bin [ 10.590598] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 10.590928] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 10.591276] scsi 6:0:0:0: Attached scsi generic sg2 type 5 [ 10.602757] IT8712 SuperIO detected. [ 10.603353] parport_pc 00:07: reported by Plug and Play ACPI [ 10.603489] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 10.606649] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [ 10.623230] floppy0: Unable to grab DMA2 for the floppy driver [ 10.639898] FDC 0 is a post-1991 82077 [ 10.751544] microcode: Microcode Update Driver: v2.00-xen <tigran(a)aivazian.fsnet.co.uk>, Peter Oruba (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] microcode: collect_cpu_info: patch_id=0x1000086 (XEN) [2010-07-06 20:46:44] microcode: error! Wrong microcode patch file magic (XEN) [2010-07-06 20:46:44] PCI add device 00:18.3 [ 10.963847] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled [ 10.988935] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 8

[opensuse-virtual] error, or noise? @ xen boot, "kernel-provided name 'pci_iomul' and NAME= 'xen/pci_iomul' disagree"
by 0bo0 08 Jul '10

08 Jul '10

i've noted this new entry in my xen boot logs, ---------------------------- Boot logging started on /dev/char/../xvc0(/dev/console) at Tue Jul 6 13:46:40 2010 Starting udevd: udevd[765]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' [ 8.956190] udev: starting version 157 done Loading drivers, configuring devices: udevd-work[780]: kernel-provided name 'pci_iomul' and NAME= 'xen/pci_iomul' disagree, please use SYMLINK+= or change the kernel to provide the proper name ---------------------------- i haven't noticed any ill effects. is this known? a bug? just noise? thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 1

[opensuse-virtual] Xen 4 - can't get guest networking
by PeanuTech 02 Jul '10

02 Jul '10

Hi, I'm using OpenSuse 11.3 - with the latest updates from the repository. I installed a guest PV OpenSuse 11.3 - RC1, and the virtual networking doesn't work. The virt-manager application isn't managing the virtual network so I can't use that. My router's log confirms that a dhcp address was given to the guest. So I don't understand what's the problem. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 1

[opensuse-virtual] a 'marketing' question ...
by 0bo0 01 Jul '10

01 Jul '10

i'll be the 1st to admit I don't always see eye-to-eye with the Suse, Opensuse & Virtualization efforts' actions, directions, etc. but in the end, it's, imo, the only solid distro-supported Xen/Virtualization solution out there. modern kernel, Xen4, PCI/USB/etc-Passthrough, etc are all there (I won't start re: PV_Grub), and, although docs can be at times ... challenging ... it works. In production. Under heavy load. As do others, I follow progress in Xen channels/mailing lists/etc. I find *many* HowTo questions that arise there would be readily handled by simply using current (or OBS repos') *Suse/Xen. That said, there seems to be a tangible ... lack of interest in, if not disdain for ... Suse+Xen. Yet the flailings about of how to get things done in Centos, Debian, etc ... continue. That's certainly fine. I'm curious: (1) Why does this tension exist? Or, in your opinion(s), does it? (2) What can be done differently in *Suse to further adoption for Virtualization? The latter question, in particular, is a purely mercenary concern for me -- the bigger/stronger the community of users, the better off my deployments are/will be. Not trolling, just interested. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

6 7