[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-31 Thread Mike Rushton
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
 20131015+dfsg-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports trusty/universe ppc64el 
Packages
ubuntu@alpine01:~$ sudo apt-get install qemu-slof=20131015+dfsg-1ubuntu1

It froze 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 notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-31 Thread Mike Rushton
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 to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-30 Thread Mike Rushton
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-30 Thread Mike Rushton
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.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1563887] [NEW] qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-30 Thread Mike Rushton
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 -display none -nographic -net nic 
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries 
-drive file=
xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': 
No such file or directory
ubuntu@alpine01:~$ cd kvm
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive f
ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.

SLOF **
QEMU Starting
 Build Date = Jan 29 2016 18:58:37
 FW Version = buildd@ release 20151103
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
   SCSI: Looking for devices
  8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
Populating /pci@8002000
 00 1800 (D) : 1af4 1001virtio [ block ]
 00 1000 (D) : 1af4 1001virtio [ block ]
 00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
 00  (D) : 1234 qemu vga
No NVRAM common partition, re-initializing...
Installing QEMU fb

Scanning USB
  OHCI: initializing
USB Keyboard
USB mouse
No console specified using screen & keyboard

  Welcome to Open Firmware

  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php

Trying to load:  from: /pci@8002000/scsi@3 ...
E3404: Not a bootable device!
Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
Linux ppc64le
#31-Ubuntu SMP F

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic ppc64le
ApportVersion: 2.20-0ubuntu3
Architecture: ppc64el
Date: Wed Mar 30 14:10:01 2016
KvmCmdLine:
 COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
 kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
 qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
 qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
ProcLocks:
 1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
 2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
 3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
 4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
 5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -1
ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
bootlist:
 /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
 
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
 
/pci@8002018/ethernet@0,3:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
cpu_cores: Number of cores 

[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2016-03-30 Thread Mike Rushton
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 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.
+ 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 -display none -nographic -net nic 
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries 
-drive file=
  xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': 
No such file or directory
  ubuntu@alpine01:~$ cd kvm
  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive f
  ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.
  
  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.
  
  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb
  
  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard
  
    Welcome to Open Firmware
  
    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php
  
  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   

[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-10-21 Thread Mike Rushton
** 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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-10-17 Thread Mike Rushton
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   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
mpath8 3200049454505080f
ubuntu@cameron:~$ sudo sed -i '/^mpath8/d' /etc/multipath/bindings 
ubuntu@cameron:~$ cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
ubuntu@cameron:~$ sudo /etc/init.d/multipath-tools stop ; sudo 
/etc/init.d/multipath-tools start
 * Stopping multipath daemon multipathd
   ...done.
 * Starting multipath daemon multipathd
   ...done.
ubuntu@cameron:~$ cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100

** Tags removed: verification-failed
** Tags added: verification-done

-- 
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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-10-15 Thread Mike Rushton
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 /var/lib/dpkg/status
 0.4.9-3ubuntu7.4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el 
Packages
 0.4.9-3ubuntu7 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages


sudo lsblk
NAME MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda8:01   7.5G  0 disk  
├─sda1 8:11   7.5G  0 part  
└─mpath8 (dm-10) 252:10   0   7.5G  0 mpath 
  └─mpath8-part1 (dm-12) 252:12   0   7.5G  0 part  


ubuntu@cameron:~$ cat /etc/multipath/bindings
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC2A680
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC2A6E0
mpath2 1IBM IPR-0   5EC2A660
mpath3 1IBM IPR-0   5EC2A620
mpath4 1IBM IPR-0   5EC2A640
mpath5 1IBM IPR-0   5EC2A6C0
mpath6 1IBM IPR-0   5EC2A6A0
mpath7 1IBM IPR-0   5EC2A6000100
mpath8 3200049454505080f

** Tags removed: verification-needed
** 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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-08-19 Thread Mike Rushton
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, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897

Title:
  multipath creates binding for Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-08-11 Thread Mike Rushton
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 number 3 using xhci_hcd
[  223.069996] usb 4-4: New USB device found, idVendor=125f, idProduct=312b
[  223.07] usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  223.070004] usb 4-4: Product: ADATA USB Flash Drive
[  223.070006] usb 4-4: Manufacturer: ADATA
[  223.070009] usb 4-4: SerialNumber: 0454
[  223.070589] usb-storage 4-4:1.0: USB Mass Storage device detected
[  223.071125] scsi4 : usb-storage 4-4:1.0
[  224.071718] scsi 4:0:0:0: Direct-Access ADATAUSB Flash Drive  1.00 
PQ: 0 ANSI: 6
[  224.073117] sd 4:0:0:0: Attached scsi generic sg32 type 0
[  224.073458] sd 4:0:0:0: [sdi] 30869504 512-byte logical blocks: (15.8 
GB/14.7 GiB)
[  224.073729] sd 4:0:0:0: [sdi] Write Protect is off
[  224.073737] sd 4:0:0:0: [sdi] Mode Sense: 23 00 00 00
[  224.073992] sd 4:0:0:0: [sdi] Write cache: disabled, read cache: disabled, 
doesn't support DPO or FUA
[  224.079661]  sdi: sdi1
[  224.080909] sd 4:0:0:0: [sdi] Attached SCSI removable disk
[  224.675188] usb 3-3: new high-speed USB device number 3 using xhci_hcd
[  224.810797] usb 3-3: New USB device found, idVendor=13fe, idProduct=3600
[  224.810802] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  224.810805] usb 3-3: Product: MKNUFDPR2GB
[  224.810807] usb 3-3: Manufacturer: MUSHKIN
[  224.810810] usb 3-3: SerialNumber: 07C10403C8956553
[  224.811540] usb-storage 3-3:1.0: USB Mass Storage device detected
[  224.812218] usb-storage 3-3:1.0: Quirks match for vid 13fe pid 3600: 4000
[  224.812419] scsi5 : usb-storage 3-3:1.0
[  225.841184] scsi 5:0:0:0: Direct-Access MUSHKIN  MKNUFDPR2GB  PMAP 
PQ: 0 ANSI: 0 CCS
[  225.842314] sd 5:0:0:0: Attached scsi generic sg33 type 0
[  226.527048] sd 5:0:0:0: [sdj] 3911680 512-byte logical blocks: (2.00 GB/1.86 
GiB)
[  226.527209] sd 5:0:0:0: [sdj] Write Protect is off
[  226.527213] sd 5:0:0:0: [sdj] Mode Sense: 23 00 00 00
[  226.527363] sd 5:0:0:0: [sdj] No Caching mode page found
[  226.527442] sd 5:0:0:0: [sdj] Assuming drive cache: write through
[  226.560690]  sdj: sdj1
[  226.562590] sd 5:0:0:0: [sdj] Attached SCSI removable disk


lsblk for relevant devices:

sdi8:128  1  14.7G  0 disk  
├─sdi1 8:129  1  14.7G  0 part  
└─mpath4 (dm-8)  252:80  14.7G  0 mpath 
  └─mpath4-part1 (dm-10) 252:10   0  14.7G  0 part  
sdj8:144  1   1.9G  0 disk  
└─sdj1 8:145  1   1.9G  0 part

-- 
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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1473228] [NEW] qemu-system-ppc requires openhackware package

2015-07-09 Thread Mike Rushton
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 in /usr/share/qemu/ppc_rom.bin which is a link to
/usr/share/openhackware/ppc_rom.bin which gets installed from
openhackware.

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: blocks-hwcert-server

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1473228

Title:
  qemu-system-ppc requires openhackware package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1473228/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] [NEW] multipath creates binding for Removable(USB) drives

2015-06-25 Thread Mike Rushton
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  14.7G  0 disk  
├─sdi1 8:129  1  14.7G  0 part  
└─mpath4 (dm-9)  252:90  14.7G  0 mpath 
  └─mpath4-part1 (dm-10) 252:10   0  14.7G  0 part  

# cat /etc/multipath/bindings 
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0   5EC25980
# End of content generated by curtin.
# Everything below is maintained by multipath subsystem.
mpath1 1IBM IPR-0   5EC25960
mpath2 1IBM IPR-0   5EC25940
mpath3 1IBM IPR-0   5EC25920
mpath4 1ADATA   USB Flash Drive 

Upon trying to format /dev/sdi1:

# mkfs.ext4 /dev/sdi1
mke2fs 1.42.9 (4-Feb-2014)
/dev/sdi1 is apparently in use by the system; will not make a filesystem here!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: multipath-tools 0.4.9-3ubuntu7.2
ProcVersionSignature: User Name 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
Uname: Linux 3.16.0-41-generic ppc64le
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: ppc64el
Date: Thu Jun 25 20:44:13 2015
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: multipath-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug ppc64el trusty uec-images

-- 
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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1468897] Re: multipath creates binding for Removable(USB) drives

2015-06-25 Thread Mike Rushton
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 block devices that come from usb:
ACTION==add, KERNEL==sd*, SUBSYSTEM==usb, OPTIONS=last_rule


This prevents /dev/sdi from showing up under lsblk completely and is now 
missing as a block device completely:

$ ls /dev/sdi*
ls: cannot access /dev/sdi*: No such file or directory

I think this is some progress, but not working as intended yet.

-- 
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 Removable(USB) drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1447167] Re: multipath-install: Installing with multipath enabled does not install multipath-tools

2015-06-12 Thread Mike Rushton
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
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy python-curtin
python-curtin:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy maas
maas:
  Installed: 1.7.5+bzr3369-0ubuntu1~trusty1
  Candidate: 1.7.5+bzr3369-0ubuntu1
  Version table:
 1.7.5+bzr3369-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
 *** 1.7.5+bzr3369-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.5.4+bzr2294-0ubuntu1.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The deployment never fully boots up. It never gets to a console or
allows an ssh connection. Attached is a log of the deployment and first
boot process to debug.

** Attachment added: multipath.log
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1447167/+attachment/4413932/+files/multipath.log

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1447167

Title:
  multipath-install: Installing with multipath enabled does not install
  multipath-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1447167/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1371634] Re: block devices appear twice

2015-06-10 Thread Mike Rushton
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
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy python-curtin
python-curtin:
  Installed: 0.1.0~bzr214-0ubuntu1
  Candidate: 0.1.0~bzr214-0ubuntu1
  Version table:
 *** 0.1.0~bzr214-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
 0.1.0~bzr201-0ubuntu1~14.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 0.1.0~bzr201-0ubuntu1~14.04.1~ppa0 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
 0.1.0~bzr126-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
#leftyfb@maaster[0]:~$ apt-cache policy maas
maas:
  Installed: 1.7.5+bzr3369-0ubuntu1~trusty1
  Candidate: 1.7.5+bzr3369-0ubuntu1
  Version table:
 1.7.5+bzr3369-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
 *** 1.7.5+bzr3369-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ 
trusty/main amd64 Packages
100 /var/lib/dpkg/status
 1.5.4+bzr2294-0ubuntu1.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
 1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.5+bzr2252-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The deployment never fully boots up. It never gets to a console or
allows an ssh connection. Attached is a log of the deployment and first
boot process to debug.


** Attachment added: multipath.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4412768/+files/multipath.log

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1371634

Title:
  block devices appear twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1371634] Re: block devices appear twice

2015-06-04 Thread Mike Rushton
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 are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1371634

Title:
  block devices appear twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1300476] Re: Unable to setup BMC/UCS user on Cisco B200 M3

2014-05-10 Thread Mike Rushton
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 UI for commissioning and installation.

sudo apt-cache policy maas
maas:
  Installed: 1.5.1+bzr2269-0ubuntu0.1
  Candidate: 1.5.1+bzr2269-0ubuntu0.1
  Version table:
 *** 1.5.1+bzr2269-0ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1.5+bzr2252-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300476

Title:
  Unable to setup BMC/UCS user on Cisco B200 M3

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1300476/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs