From: Eric Blake <eblake@redhat.com>
To: Bug 1882350 <1882350@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Bug 1882350] [NEW] it always create sdx device when I configure ide device with hdx name
Date: Mon, 8 Jun 2020 10:23:10 -0500 [thread overview]
Message-ID: <c04b7074-85f5-d0c7-818c-69019d513192@redhat.com> (raw)
In-Reply-To: <159144063074.3735.15991486640962003601.malonedeb@soybean.canonical.com>
On 6/6/20 5:50 AM, marshell wrote:
> Public bug reported:
>
> I have configured 2 ide disks with name starting with hd, but when the
> vm boots up, it shows disks whose name starting with sd.
This looks more like a libvirt question than a qemu one.
>
> 1. ide disks in vm xml:
>
> <disk type='file' device='disk'>
> <driver name='qemu' type='raw'/>
> <source file='/data3_raw.qcow2'/>
> <target dev='hdc' bus='ide'/>
> </disk>
> <disk type='file' device='disk'>
> <driver name='qemu' type='qcow2'/>
> <source file='/data2.qcow2'/>
> <target dev='hdb' bus='ide'/>
> </disk>
The name that libvirt chooses to identify disks from the host
perspective is independent...
>
>
> 2. in VM:
>
> sda 8:0 0 2G 0 disk
> sdb 8:16 0 1G 0 disk
...from what the guest OS chooses to use. Although there are many
situations where a Linux guest will pick the same names as libvirt chose
on the host side based on the transport (such as SCSI or virtio), there
is no guarantee that this is always the case, nor that your guest is
always running Linux as its OS.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <1882350@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1882350] [NEW] it always create sdx device when I configure ide device with hdx name
Date: Mon, 08 Jun 2020 15:23:10 -0000 [thread overview]
Message-ID: <c04b7074-85f5-d0c7-818c-69019d513192@redhat.com> (raw)
Message-ID: <20200608152310.jkC0aGFcMnyeDMN7Z6QXbr74jFdQatZ-nAMgvoqgHHg@z> (raw)
In-Reply-To: 159144063074.3735.15991486640962003601.malonedeb@soybean.canonical.com
On 6/6/20 5:50 AM, marshell wrote:
> Public bug reported:
>
> I have configured 2 ide disks with name starting with hd, but when the
> vm boots up, it shows disks whose name starting with sd.
This looks more like a libvirt question than a qemu one.
>
> 1. ide disks in vm xml:
>
> <disk type='file' device='disk'>
> <driver name='qemu' type='raw'/>
> <source file='/data3_raw.qcow2'/>
> <target dev='hdc' bus='ide'/>
> </disk>
> <disk type='file' device='disk'>
> <driver name='qemu' type='qcow2'/>
> <source file='/data2.qcow2'/>
> <target dev='hdb' bus='ide'/>
> </disk>
The name that libvirt chooses to identify disks from the host
perspective is independent...
>
>
> 2. in VM:
>
> sda 8:0 0 2G 0 disk
> sdb 8:16 0 1G 0 disk
...from what the guest OS chooses to use. Although there are many
situations where a Linux guest will pick the same names as libvirt chose
on the host side based on the transport (such as SCSI or virtio), there
is no guarantee that this is always the case, nor that your guest is
always running Linux as its OS.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882350
Title:
it always create sdx device when I configure ide device with hdx name
Status in QEMU:
New
Bug description:
I have configured 2 ide disks with name starting with hd, but when the
vm boots up, it shows disks whose name starting with sd.
1. ide disks in vm xml:
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/data3_raw.qcow2'/>
<target dev='hdc' bus='ide'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/data2.qcow2'/>
<target dev='hdb' bus='ide'/>
</disk>
2. in VM:
sda 8:0 0 2G 0 disk
sdb 8:16 0 1G 0 disk
3. from vm.log:
le=/data2.qcow2,format=qcow2,if=none,id=drive-ide0-0-1 -device ide-
hd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive
file=/data3_raw.qcow2,format=raw,if=none,id=drive-ide0-1-0 -device
ide-hd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev t
4. rpm info: (I got the same issue on 2 diff envs)
(1) env1
qemu-kvm-1.5.3-105
libvirt-3.2.0-14.el7
(2) env2
libvirt-5.9.0-1.el8
qemu-4.1.0-1.el8
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1882350/+subscriptions
next prev parent reply other threads:[~2020-06-08 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 10:50 [Bug 1882350] [NEW] it always create sdx device when I configure ide device with hdx name marshell
2020-06-08 15:23 ` Eric Blake [this message]
2020-06-08 15:23 ` Eric Blake
2020-06-09 0:55 ` [Bug 1882350] " marshell
2021-05-06 16:08 ` Thomas Huth
2021-07-06 4:17 ` Launchpad Bug Tracker
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=c04b7074-85f5-d0c7-818c-69019d513192@redhat.com \
--to=eblake@redhat.com \
--cc=1882350@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).