[Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit

2014-09-26 Thread joh...@servergy.com
I am no longer working on this project, -- 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/1317603 Title: qemu-system-ppc does not terminate on VM exit To manage notifications about this

[Bug 1324640] [NEW] vm-builder fails on creating ppc images

2014-05-29 Thread joh...@servergy.com
Public bug reported: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS (trusty)root@jade-rev4:/etc# uname -a Linux jade-rev4 3.13.0-24-powerpc-e500mc #46-Ubuntu SMP Thu Apr 10 19:52:34 UTC 2014 ppc ppc ppc GNU/Linux (trusty)root@jade-

[Bug 1317651] Re: ppc: VM hangs on first boot after network install

2014-05-28 Thread joh...@servergy.com
The root of this is the image is missing /etc/init/ttyS0.conf This file needs added to the distro ; ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu

[Bug 1317651] Re: ppc: VM hangs on first boot after network install

2014-05-28 Thread joh...@servergy.com
It appears /etc/init/ttyS0.conf needs added to the package upstart (trusty)root@jade-rev4:/etc/init# dpkg -S tty1.conf upstart: /etc/init/tty1.conf There is no tty0.conf either. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu

[Bug 1317651] Re: ppc: VM hangs on first boot after network install

2014-05-28 Thread joh...@servergy.com
Looking more at this, it appears the device should be automatically configured: [root@ab763 init]# cat serial.conf # Automatically start a configured serial console # # How this works: # # On boot, a udev helper examines /dev/console. If a serial console is the # primary console (last console on

Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit

2014-05-24 Thread joh...@servergy.com
qemu-system-ppc never terminates. Regards, John. -- o Energy-efficiency is #1 reason data centers look to expand. -- Digital Realty Trust o Green Data Centers spending to increase 300% worldwide by 2016. -- Pike Research o Data Centers have become as vital to the functioning of society as

Re: [Bug 1317603] Re: qemu-system-ppc does not terminate on VM exit

2014-05-24 Thread joh...@servergy.com
Research o Data Centers have become as vital to the functioning of society as power stations. -- The Economist On Sat, May 24, 2014 at 7:12 PM, Serge Hallyn 1317...@bugs.launchpad.net wrote: Quoting joh...@servergy.com (joh...@servergy.com): qemu-system-ppc never terminates. Assuming you

[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean

2014-05-21 Thread joh...@servergy.com
1. ssgyboot-break has no effect in the VM kernel; It is only used by jade-initrd-2.0.bin ; kernel cmdline: [0.00] pcpu-alloc: s28800 r8192 d16256 u53248 alloc=13*4096 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pag es:

[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean

2014-05-21 Thread joh...@servergy.com
/var/log/syslog attached as syslog.onboot when file system is dirty ; Since the VM terminated ; the device should have been umounted ; ** Attachment added: syslog.onboot https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1321028/+attachment/4116987/+files/syslog.onboot -- You received

[Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean

2014-05-21 Thread joh...@servergy.com
I am thinking since the VM hasn't terminated due to defect 1317603 , qemu-system-ppc has to be terminated with kill pid which is not kill -9 ; I could see some inconsistencies with virtio device file not being sync'ed ; but the VM did unmount it; -- You received this bug notification because

[Bug 1321362] [NEW] virsh fails to launch : missing /proc/device-tree/cpu

2014-05-20 Thread joh...@servergy.com
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1:

[Bug 1321362] Re: virsh fails to launch : missing /proc/device-tree/cpu

2014-05-20 Thread joh...@servergy.com
refiled under: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1321365 ** Changed in: qemu (Ubuntu) Status: New = Invalid ** Description changed: - - - virsh # define vm01.xml + virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01

[Bug 1321365] [NEW] virsh (ppc) fails with missing /proc/device-tree/cpu

2014-05-20 Thread joh...@servergy.com
Public bug reported: virsh # define vm01.xml virsh # start Ubuntu-VM01 error: Failed to start domain Ubuntu-VM01 error: internal error: early end of file from monitor: possible problem: Can't open directory /proc/device-tree/cpus/ qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1:

[Bug 1321028] [NEW] qemu-system-ppc : file systems are not shutting down clean

2014-05-19 Thread joh...@servergy.com
Public bug reported: Launching a VM that has been shutdown gracefully ( via init 0) typically requires fsck to run when it is started ; This indications data integrity issues; The symptom can be seen by observing the fsck running when the VM restarted. Install 14-04-LTS to a VM and the

[Bug 1319923] Re: Console stdin ignored using -nographic mode

2014-05-18 Thread joh...@servergy.com
It appears that running qemu in the background causes this. ** Changed in: qemu (Ubuntu) Status: New = Incomplete ** Changed in: qemu (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 1319923] [NEW] Console stdin ignored using -nographic mode

2014-05-15 Thread joh...@servergy.com
Public bug reported: (trusty)root@jade-rev4:/home2/qemu/vm2# lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 dpkg -l | grep qemu | grep ppc qemu-system-ppc 2.0.0~rc1+dfsg- 0ubuntu3.1 Launching VM's from qemu-system-ppc frequently

[Bug 1317987] [NEW] error: Cannot check QEMU binary qemu-system-ppc: No such file or directory

2014-05-09 Thread joh...@servergy.com
Public bug reported: trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # define vm01.xml error: Failed to define domain from vm01.xml error: Cannot check QEMU

[Bug 1317603] [NEW] qemu-system-ppc does not terminate on VM exit

2014-05-08 Thread joh...@servergy.com
Public bug reported: When a VM is created for a p4080-e500mc ; the VM can not be rebooted or terminated. The qemu-system-ppc process must be killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu

[Bug 1317651] [NEW] ppc: VM hangs on first boot after network install

2014-05-08 Thread joh...@servergy.com
Public bug reported: 1. perform a direct install to a new file by obtaining the network install components from http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer-powerpc/current/images/e500mc/netboot/ qemu-system-ppc -M ppce500 -nographic -kernel vmlinux \ -initrd