Thanks for the Detail Robin!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
TL;DR: pass '-vga none' with -nographic, or redirect the screen
somewhere!
I ended up digging into this after it was mentioned by smoser. The bug
is invalid because of a bad assumption in the QEMU inputs. smoser's
workaround of usb=off removes USB as a workaround.
The kernel, OpenFirmware, and
As noted, Xenial kernel is not supporting POWER7 cpu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
** Changed in: qemu
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifications
Build target was changed to P8 starting with Xenial. Previously it had
been a P7 target. I would expect Xenial kernel to have problems booting
on a P7 model. IMO this kernel bug is invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I should also mention that the original command used will work if we
specify which cpu type to use:
qemu-system-ppc64 -m 256 \
-cpu POWER8 \
-display none -nographic \
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 \
-machine pseries \
-drive
Here's an update.
The Xenial kernel doesn;t like the emulated POWER7 cpu that the command
line being used generates by default.
processor : 0
cpu : POWER7 (raw), altivec supported
clock : 1000.00MHz
revision: 2.3 (pvr 003f 0203)
timebase:
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage
@leftyfb - what exactly is IBM asking to verify? Whether kvm works
under powervm? Did smoser's info help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on
ok. so after playing some, this all comes down to needing 'usb=off' on
the qemu command line.
works:
qemu-system-ppc64 -enable-kvm -machine usb=off -device
virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive
if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive
Note, that Michael Roth's comments are probably valid. I suspect that
if leftyfb ever saw this working on powerVM host, then it was through
the kvm_pr module. In my experience, that works generally pretty well
(buit my testing has only ever been done powerNV host).
--
You received this bug
ok. so after playing some, this all comes down to needing 'usb=off' on
the qemu command line.
works:
qemu-system-ppc64 -enable-kvm -machine usb=off -device
virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive
if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive
Note, that Michael Roth's comments are probably valid. I suspect that
if leftyfb ever saw this working on powerVM host, then it was through
the kvm_pr module. In my experience, that works generally pretty well
(buit my testing has only ever been done powerNV host).
--
You received this bug
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
PowerVM mode is an LPAR. It is not a kvm instance trying to run an KVM
within. This was also working in 14.04 without issue and is being asked
of us from IBM to certify
2. the xenial cloud images
I have also shown that this issue has the exact same results on PowerNV
above.
** Changed in: qemu
Status: Invalid => Confirmed
** Changed in: qemu (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu
Status: New => Invalid
--
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
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifications about
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do
The PowerVM machine I've been using for these tests has the following
output:
ubuntu@alpine01:~/kvm$ cat /proc/cpuinfo | grep platform
platform: pSeries
The PowerNV server has the following output:
ubuntu@binacle:~$ cat /etc/issue; uname -a ; ppc64_cpu --smt ; cat
/proc/cpuinfo |grep
Quoting Mike Rushton (2016-04-05 17:22:24)
> Sorry, I copied the wrong thing:
>
> sudo qemu-system-ppc64 -enable-kvm -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
Sorry, I copied the wrong thing:
sudo qemu-system-ppc64 -enable-kvm -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
Quoting Mike Rushton (2016-04-05 16:47:29)
> @mdroth
>
> I don't think PPC supports kvm the same way as x86:
>
> ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -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
>
@serge-hallyn
ubuntu@alpine01:~/kvm$ cat /etc/issue; uname -a ; ppc64_cpu --smt
Ubuntu Xenial Xerus (development branch) \n \l
Linux alpine01 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256
@mdroth
I don't think PPC supports kvm the same way as x86:
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -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
Quoting Mike Rushton (2016-04-05 13:10:17)
> ubuntu@alpine01:~$ sudo ppc64_cpu --smt=1
> ubuntu@alpine01:~$ ppc64_cpu --info
> Core 0:0*1 2 3 4 5 6 7
> Core 1:8*9101112131415
> Core 2: 16* 1718192021
If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know. Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ubuntu@alpine01:~$ sudo ppc64_cpu --smt=1
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1 2 3 4 5 6 7
Core 1:8*9101112131415
Core 2: 16* 17181920212223
Core 3: 24* 25262728
Quoting Mike Rushton (2016-04-04 09:49:29)
> ubuntu@alpine01:~$ ppc64_cpu --info
> Core 0:0*1*2*3*4*5*6*7*
> Core 1:8*9* 10* 11* 12* 13* 14* 15*
> Core 2: 16* 17* 18* 19* 20* 21* 22* 23*
> Core 3: 24* 25* 26*
4.4.0-16 also works.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on
Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I
can boot the installed image (with same kernel) just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1*2*3*4*5*6*7*
Core 1:8*9* 10* 11* 12* 13* 14* 15*
Core 2: 16* 17* 18* 19* 20* 21* 22* 23*
Core 3: 24* 25* 26* 27* 28* 29* 30* 31*
Core 4: 32* 33*
Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -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=my-seed.img,if=virtio
** Attachment added: "crash.png"
Hm - I can boot a wily cloud image, just not a xenial one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage
Quoting Serge Hallyn (2016-04-01 11:56:29)
> Hi,
>
> I've redeployed my test box with 14.04 with kilo-staging archive, but i
> get a core dump when i try to run kvm the same way you did.
What does `ppc64_cpu --info` report? The original bug had some output
that suggested SMT was enabled:
>
Hi,
I've redeployed my test box with 14.04 with kilo-staging archive, but i
get a core dump when i try to run kvm the same way you did.
Can you show your /etc/apt/sources.list and /etc/apt/sources.list.d, as
well as output for
uname -a
dpkg -l | egrep -e '(qemu|linux|bios)'
--
You received
Hi,
I've redeployed my test box with 14.04 with kilo-staging archive, but i
get a core dump when i try to run kvm the same way you did.
Can you show your /etc/apt/sources.list and /etc/apt/sources.list.d, as
well as output for
uname -a
dpkg -l | egrep -e '(qemu|linux|bios)'
--
You received
Indeed building the kilo package from source gives me the same hang. So
something else (seabios maybe)
--
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
Indeed building the kilo package from source gives me the same hang. So
something else (seabios maybe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on
I'll try building the package source from kilo on the xenial host and
see if that succeeds. I'm having doubts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64
I'll try building the package source from kilo on the xenial host and
see if that succeeds. I'm having doubts.
--
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:
Hm, building 2.2.0 (close to what is in the kilo cloud archive) doesn't
help.
--
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
Hm, building 2.2.0 (close to what is in the kilo cloud archive) doesn't
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To
Thanks very much for testing.
I think I have a system I can use to try and bisect tonight/tomorrow.
--
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
Thanks very much for testing.
I think I have a system I can use to try and bisect tonight/tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on
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
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
Failing any brighter ideas, this should be pretty bisectable to figure
out what happened. Hardware availability is the main problem. Would
you be able to use your system to bisect to the commit introducing the
bug?
Actually before we get to that, could you try installing the 14.04 slof
package
Failing any brighter ideas, this should be pretty bisectable to figure
out what happened. Hardware availability is the main problem. Would
you be able to use your system to bisect to the commit introducing the
bug?
Actually before we get to that, could you try installing the 14.04 slof
package
Same issue with -m 2048
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
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
Just to be sure before I mark this as affecting upstream, could you
try adding more memory, maybe -m 1024?
--
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:
Just to be sure before I mark this as affecting upstream, could you
try adding more memory, maybe -m 1024?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on
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
Same issue. Stopped on the exact same spot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifications about this
Could you try this using upstream qemu?
git clone http://git.qemu.org/git/qemu.git
cd qemu
sudo apt-get -y build-dep qemu
./configure --target-list=ppc64-softmmu
make
cd ppc64-softmmu
./qemu-system-ppc64 [...]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Could you try this using upstream qemu?
git clone http://git.qemu.org/git/qemu.git
cd qemu
sudo apt-get -y build-dep qemu
./configure --target-list=ppc64-softmmu
make
cd ppc64-softmmu
./qemu-system-ppc64 [...]
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Hi,
looking at the information in the Description, it looks like you still
have /dev/nbd0 attached to the file you're using in qemu. Just to be
sure, does this still happen when you disconnect that first?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Hi,
looking at the information in the Description, it looks like you still
have /dev/nbd0 attached to the file you're using in qemu. Just to be
sure, does this still happen when you disconnect that first?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
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.
** 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. There is no
error output.
- ubuntu@alpine01:~$
** 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. There is no
error output.
- ubuntu@alpine01:~$
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
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
66 matches
Mail list logo
