*** This bug is a duplicate of bug 1317603 ***
https://bugs.launchpad.net/bugs/1317603
** This bug has been marked a duplicate of bug 1317603
qemu-system-ppc does not terminate on VM exit
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1317603 ***
https://bugs.launchpad.net/bugs/1317603
** This bug has been marked a duplicate of bug 1317603
qemu-system-ppc does not terminate on VM exit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
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/1321028
Title:
qemu-system-ppc : file systems are not shutting down clean
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321028
Title:
qemu-system-ppc : file systems are not shutting down clean
To manage
Can you explain what ssgyboot=break tells the kernel to do?
Could you upload the guest's /var/log/syslog after reboot?
Please show
echo $?
immediately after the qemu-system-ppc command has exited?
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
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:
/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
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
Can you explain what ssgyboot=break tells the kernel to do?
Could you upload the guest's /var/log/syslog after reboot?
Please show
echo $?
immediately after the qemu-system-ppc command has exited?
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
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:
/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
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
12 matches
Mail list logo
