From: Cole Robinson <crobinso@redhat.com>
To: James Brackinshaw <jbrackinshaw@gmail.com>
Cc: kvm@vger.kernel.org, virt-tools-list <virt-tools-list@redhat.com>
Subject: Re: virt-install: hda disks?
Date: Wed, 30 Sep 2009 11:14:51 -0400 [thread overview]
Message-ID: <4AC375EB.1060707@redhat.com> (raw)
In-Reply-To: <abc54bf00909300811p3d18a8a0x9496d980a3b8bf80@mail.gmail.com>
On 09/30/2009 11:11 AM, James Brackinshaw wrote:
> On Wed, Sep 30, 2009 at 4:51 PM, Cole Robinson <crobinso@redhat.com> wrote:
>> On 09/30/2009 10:28 AM, James Brackinshaw wrote:
>>> Hi,
>>>
>>> Not sure if this is the right place to ask this.
>>>
>>
>> virt-install questions should be directed to virt-tools-list@redhat.com
>
> Thanks.
>
>>> I'm getting hda disks by default with kvm under RHEL5.4 using
>>> virt-install. This seems an odd default. Is there a reason for hda
>>> disks over sda disks? Can I change this?
>>>
>>
>> virt-install/libvirt defaults to IDE for disk devices (as does directly
>> launching qemu or kvm). These disks will show up in a RHEL5 guest as
>> /dev/hda, etc. In newer distros, these disks show up as /dev/sda, etc.
>> It's just a matter of the RHEL5 stack being older than the hdX -> sdX
>> change.
>>
>> If you want to use scsi disks via virt-install, you can use:
>>
>> virt-install --disk ...,bus=scsi
>>
>> Though AIUI it's generally considered buggy at the qemu level, and may
>> even be disabled in RHEL5.4
>>
>> - Cole
>
> Is virtio stable and recommended?
Sorry, forgot about that. If you are installing a RHEL5.4 guest, use
virt-install --disk ...,model=virtio
or
virt-install --os-variant virtio26
which will take care of disk and networking defaults.
- Cole
next prev parent reply other threads:[~2009-09-30 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 14:28 virt-install: hda disks? James Brackinshaw
2009-09-30 14:51 ` Cole Robinson
2009-09-30 15:11 ` James Brackinshaw
2009-09-30 15:14 ` Cole Robinson [this message]
2009-09-30 15:18 ` James Brackinshaw
2009-09-30 15:23 ` Cole Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AC375EB.1060707@redhat.com \
--to=crobinso@redhat.com \
--cc=jbrackinshaw@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=virt-tools-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).