Brian Jackson wrote:
On Friday 24 April 2009 09:35:52 Gerd v. Egidy wrote:
Hi Bernhard,
On Friday 24 April 2009 14:56:15 Bernhard Held wrote:
does not boot, BIOS complains "Boot failed: could not read the boot
disk":
-drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
P
On Friday 24 April 2009 09:35:52 Gerd v. Egidy wrote:
> Hi Bernhard,
>
> On Friday 24 April 2009 14:56:15 Bernhard Held wrote:
> > > does not boot, BIOS complains "Boot failed: could not read the boot
> > > disk":
> > >
> > > -drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
> >
> > Please t
Hi Bernhard,
On Friday 24 April 2009 14:56:15 Bernhard Held wrote:
> > does not boot, BIOS complains "Boot failed: could not read the boot
> > disk":
> >
> > -drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
>
> Please try with:
> -drive file=/dev/VolGroup00/testpart,if=virtio,index=0,boot=
does not boot, BIOS complains "Boot failed: could not read the boot disk":
-drive file=/dev/VolGroup00/testpart,if=virtio,index=0 \
O.k., this doesn't work on my box too.
Please try with:
-drive file=/dev/VolGroup00/testpart,if=virtio,index=0,boot=on \
Anthony wrote "index doesn't have meaning
Hi Andreas,
On Thursday 23 April 2009 19:34:31 Andreas Plesner Jacobsen wrote:
> On Thu, Apr 23, 2009 at 06:57:45PM +0200, Gerd v. Egidy wrote:
> > sorry, I'm not getting that far to make this a problem. I just added the
> > second disk (the virtio one) to test if virtio is working when the guest
Daniel P. Berrange wrote:
On Thu, Apr 23, 2009 at 11:13:50AM -0500, Anthony Liguori wrote:
Brian Jackson wrote:
Your problem is that index's are per interface type, so both of your
drives should be index=0 since they are different interface types.
More specifically, with virtio
On Thu, Apr 23, 2009 at 06:57:45PM +0200, Gerd v. Egidy wrote:
>
> sorry, I'm not getting that far to make this a problem. I just added the
> second disk (the virtio one) to test if virtio is working when the guest is
> running.
>
> I first tried it with just one virtio disk and no ide ones:
Hi Andreas,
> > I am (or better libvirt is) starting the guest like this:
> >
> > -drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
> > -drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
>
> Both should have index=0 (or no index at all), since the index is
> internal to the driver.
sorr
On Thu, Apr 23, 2009 at 11:13:50AM -0500, Anthony Liguori wrote:
> Brian Jackson wrote:
> >Your problem is that index's are per interface type, so both of your
> >drives should be index=0 since they are different interface types.
> >
>
> More specifically, with virtio-blk, you cannot have disco
On Thu, Apr 23, 2009 at 10:43:03AM +0200, Gerd v. Egidy wrote:
>
> I am (or better libvirt is) starting the guest like this:
>
> -drive file=/dev/VolGroup00/testboot,if=ide,index=0 \
> -drive file=/dev/VolGroup00/testvirt,if=virtio,index=1 \
Both should have index=0 (or no index at all), since t
Brian Jackson wrote:
Your problem is that index's are per interface type, so both of your drives
should be index=0 since they are different interface types.
More specifically, with virtio-blk, you cannot have discontinuous
indexes. In other words, having index=0, index=1, index=2 is valid
Your problem is that index's are per interface type, so both of your drives
should be index=0 since they are different interface types.
On Thursday 23 April 2009 03:43:03 Gerd v. Egidy wrote:
> Hi,
>
> I just tried to upgrade my kvm (from 79) to the new 85. I'm using qemu-kvm-
> devel with the
Hi,
I just tried to upgrade my kvm (from 79) to the new 85. I'm using qemu-kvm-
devel with the kvm-modules (and kernel-includes) that came with 2.6.29.1.
Qemu-blockdevices and virtio-net work well. But virtio blockdevices are not
accessible from within the guest system. Neither can the BIOS boot
13 matches
Mail list logo
