Marked the bug as invalid (I am the original reporter). I can't
reproduce the problem again. After a day, the system rebooted fine. I am
performing different tests (smartctl tests) on the hard drive.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
latest grub2 renders gpt based sy
On Fri, May 7, 2010 at 2:44 AM, Colin Watson wrote:
> If the message you are seeing is "This GPT partition label has no BIOS
> Boot Partition; embedding won't be possible!", then see
> http://grub.enbug.org/BIOS_Boot_Partition
During the upgrade, I also read "When GRUB can't be embedded, its only
What strikes me here is the clear warning message about the
unreliability of grub related to the gpt partition, that could be seen
on the aptitude console. As if the pre or post install scripts had
detected something fishy. What happened there?
If boot from a usb drive, how can I redo this test be
Public bug reported:
Binary package hint: grub2
system version : upgraded form Karmic to beta Lucid then regurlarly updated
package version: unknown (system unbootable at this time ...)
The hardware is an Apple Macbook computer with gpt partitions instead of
a bios boot partitions (all the recen
Public bug reported:
ubuntu release : jaunty alpha6
kvm : 1:84+dfsg-0ubuntu8
libgtk-vnc-1.0-0 : 0.3.8-2ubuntu2
virt-viewer: 0.0.3-6ubuntu7
To reproduce the problem on a rfesh install of jaunty alpha6 host with host
keyboard configured as french :
1. virt-install -n jaunty -f jaunty.img -s 1 -r
I can confirm the attach-device command does not work. When attaching a
file as a disk to the guest when the guest is active, virsh answers an
error message 'cannot be hotplugged'. When attaching a file when thee
guest is inactive, virsh answers 'cannot attach device on inactive
domain'.
Here is
The default network is set to be autostarted but the start fails. The
libvirt-bin package tries to install a NAT network, is it desirable
considering the fact that many users will use a physical shared device
in a bridged configuration and will have to deconfigure this default
network?
The default