I have installed qemu-slof from trusty and ran again:
qemu-slof:
Installed: 20151103+dfsg-1ubuntu1
Candidate: 20151103+dfsg-1ubuntu1
Version table:
*** 20151103+dfsg-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
100 /var/lib/dpkg/status
Same issue with -m 2048
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifications about this bug go
Same issue. Stopped on the exact same spot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage
Yes. I only mounted (a different file) to troubleshoot what was going
on. The issue was happening before and after mounting. I have since
unmounted it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Public bug reported:
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
ubuntu@alpine01:~$ qemu-system-ppc64 -m 256
In Ubuntu 14.04.4 running on the same hardware, the fix was to update
qemu-system-ppc from cloud-archive:kilo. This repository is only
supported on trusty and contains an earlier version of qemu-system-ppc
than what is available on xenial.
** Description changed:
qemu-system-ppc64 running on
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897
Title:
multipath creates binding for
The following shows that the 0.4.9-3ubuntu7.6 version of multipath-tools
does in fact ignore USB when creating the bindings. Marking as
verification-done.
ubuntu@cameron:~$ cat /etc/multipath/bindings
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0
Verification failed:
ubuntu@cameron:~$ apt-cache policy multipath-tools
multipath-tools:
Installed: 0.4.9-3ubuntu7.6
Candidate: 0.4.9-3ubuntu7.6
Version table:
*** 0.4.9-3ubuntu7.6 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el
Packages
100
Tested multipath-tools version Installed: 0.4.9-3ubuntu7.5 from the
proposed repository in Trusty. The test shows the problem resolved.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Updated information. It seems the issue only comes about with USB 3.0
devices. USB 2.0 devices do not get lumped in with multipath upon
detection.
dmesg output from inserting a USB 3.0 device and then a USB 3.0 device.
Both into USB 3.0 ports:
[ 223.050845] usb 4-4: new SuperSpeed USB device
Public bug reported:
Release: Ubuntu 14.04.2 installed on IBM Power 8 (Tuleta)
kernel: 3.16.0-43-generic
Arch: ppc64le
When trying to run qemu-system-ppc64 to create a new VM, we get the
following error:
qemu: hardware error: qemu: could not load bios image 'ppc_rom.bin'
ppc_rom.bin is located
Public bug reported:
On a system with a multipath configuration, multipath bindings are being
created for removable(USB) drives rendering them inaccessible as normal
removable drives.
in this case, the usb drive is detected as /dev/sdi:
# lsblk|grep -A2 sdi
sdi8:128 1
After following this post: https://www.redhat.com/archives/dm-
devel/2008-September/msg00235.html
I have prepended the following to /lib/udev/rules.d/95-multipath.rules:
#Weed out the linear map.
KERNEL==dm-*, PROGRAM==/sbin/dmsetup table -j %M -m %m, RESULT==*linear*,
OPTIONS=last_rule
# And
I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:
#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
Installed: 0.1.0~bzr214-0ubuntu1
Candidate: 0.1.0~bzr214-0ubuntu1
Version table:
*** 0.1.0~bzr214-0ubuntu1 0
I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:
#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
Installed: 0.1.0~bzr214-0ubuntu1
Candidate: 0.1.0~bzr214-0ubuntu1
Version table:
*** 0.1.0~bzr214-0ubuntu1 0
I tried following the above workaround on the IBM Power 8 twice on new
deployments. Attached is the log.
** Attachment added: multipath.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log
--
You received this bug notification because you
I have confirmed after adding the above package from proposed, logging
into MAAS and running the discovery script probe-and-enlist-ucsm within
MAAS we are now able to properly discover the nodes with proper power
settings configured. I can also confirm full control of the nodes using
the MAAS web
18 matches
Mail list logo
