Bug 477258
Summary: | Block attach-detach operations fail for rhel 4.7 and rhel 3.9 HVM guests. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Gurhan Ozen <gozen> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.3 | CC: | bdonahue, benl, clalance, jburke |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-22 16:45:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gurhan Ozen
2008-12-19 22:27:23 UTC
Well, here's the thing. In all of the above commands, you are trying to attach a PV-on-HVM disk. In order for this to work, you have to have installed the PV-on-HVM drivers inside the guest (that's already the default in 4.7, but you need the external kmod-xenpv drivers on 3.9), *and* have done modprobe xen-vbd inside the guest. If you do that, does the blkattach work? Also note that blkattach of SCSI or IDE disks emphatically will not work, so it's not even worth testing. The detach problem is exactly the same as that other bug you opened, so we don't need to track that separately. Chris Lalancette (In reply to comment #3) > Well, here's the thing. In all of the above commands, you are trying to attach > a PV-on-HVM disk. In order for this to work, you have to have installed the > PV-on-HVM drivers inside the guest (that's already the default in 4.7, but you > need the external kmod-xenpv drivers on 3.9), *and* have done modprobe xen-vbd > inside the guest. If you do that, does the blkattach work? Also note that > blkattach of SCSI or IDE disks emphatically will not work, so it's not even > worth testing. > The detach problem is exactly the same as that other bug you opened, so we > don't need to track that separately. > > Chris Lalancette Well, here's the thing... I was thinking that only tap:aio would invoke pv-on-hvm, that file and phy drivers would not be pv-on-hvm. However, from your comments it sounds like anything /dev/xvd?? is pv-on-hvm regardless of what driver is being used. Is this correct? If that's the case, then does only pv-on-hvm work on hvm guests, since scsi and ide emulation doesn't work on hvm guest, according to #476746, right? Also, I was told that 4.7 would automatically just work out of box for pv-on-hvm, but according to this comment, i still need to manually insert xen-vbd :( For rhel3.9 guests, i didn't even bother testing this because, as I said earlier, i thought phy and file drivers wouldn't invoke pv-on-hvm . I'll go back and make sure all pv-on-hvm settings are in place and retest. Sorry about this bug noise , looks like this is all -EUSER error:( (I know this has been closed now, but just in response to Comment #4...) tap:aio vs phy vs. file has nothing to do with whether it is PV-on-HVM or not. What you have to realize with virtualization is that there is always a backend driver and a frontend driver. The backend driver is how the host is accessing the disk file; in the Xen case, the three methods to do that are tap:aio, phy, and file. The frontend driver is how the host is presenting the device to the guest (and, also, which driver the guest needs). In Xen, the available methods are either xvd (a PV device), or IDE (for HVM guests only). An xvd device is *always* a paravirtualized device, which means that the guest has to have PV drivers to access it (this includes both pure paravirtualized domains and HVM domains with PV-on-HVM drivers). An IDE device can only be presented to an HVM guest, but since there is no generic IDE hotplug facility, you can attach these on the fly. I hope that clears things up a little bit. Chris Lalancette |