Yeah, can also confirm that this is fixed. Having the same problem with
bug #281492 as Dustin.
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
The current bug, as described is fixed.
Using today's server ISO, I was able to perform multiple installations,
to completion on virtio devices.
I'm marking this bug as "fix released".
That is not the end of the story, though. I have opened a new bug, Bug
#281492, as the grub installer seems to
** Changed in: kvm (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Dustin Kirkland (kirkland)
Status: Confirmed => Triaged
Target: None => ubuntu-8.10
** Changed in: kvm (Ubuntu)
Importance: Medium => High
--
Intrepid fails to install onto virtio block
Also tried latest (67aca2a9b4186ec7d2a506f508ca6433) but I get stuck
when the installer is "Retrieving libc6-udeb" under the process "Loading
additional components".
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received this bug notification bec
I just downloaded the latest daily iso, including Colin's fix.
67aca2a9b4186ec7d2a506f508ca6433 intrepid-server-amd64.iso
The virtio disk is once again detected by the installer. That's good.
The installation proceeds without incident, and completes successfully.
However, the installed system
** Changed in: kvm (Ubuntu)
Status: New => Confirmed
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Okay, thanks for the instructions. I have reproduced the problem.
I'm posting the syslog here.
:-Dustin
** Attachment added: "syslog"
http://launchpadlibrarian.net/18348693/syslog
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received thi
> Can you give me step-by-step instructions?
Sure. I should have done it from the beginning of this bug report. Sorry about
that.
-- Steps to reproduce --
* Create a new image file with "qemu-img create myfile.img 5G". Default should
be "raw". You can check it with "qemu-img info myfile.img".
*
On Tue, Oct 07, 2008 at 10:12:41PM -, Dustin Kirkland wrote:
> On Tue, Oct 7, 2008 at 4:15 PM, Blinkiz <[EMAIL PROTECTED]> wrote:
> > Using a simple image file as block device and the installation will also
> > fail. No need for LVM to reproduce this. I used the default "raw" as
> > file forma
On Tue, Oct 7, 2008 at 4:15 PM, Blinkiz <[EMAIL PROTECTED]> wrote:
> Using a simple image file as block device and the installation will also
> fail. No need for LVM to reproduce this. I used the default "raw" as
> file format for the image file.
Can you give me step-by-step instructions?
I'm sta
Using a simple image file as block device and the installation will also
fail. No need for LVM to reproduce this. I used the default "raw" as
file format for the image file.
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received this bug notifica
Temporary solution for this is to install intrepid without having the
virtual hard drive accessed the virtio way. Just plain simple /dev/hda
type. After installation is finish, I shutdown the machine and switch to
virtio block device. The change to /dev/vda is not a problem because
UUID is used.
H
** Attachment added: "Syslog from intrepid installer"
http://launchpadlibrarian.net/18298386/syslog
--
Intrepid fails to install onto virtio block device
https://bugs.launchpad.net/bugs/279754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
13 matches
Mail list logo
