Bug 1908421
| Summary: | [v2v] [VM import RHV to CNV] Windows imported VM boot failed: INACCESSIBLE BOOT DEVICE error | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Khaoula Ben Sghaier <ksghaier> | ||||||||||||||
| Component: | V2V | Assignee: | Fabien Dupont <fdupont> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Daniel Gur <dagur> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | high | ||||||||||||||||
| Version: | 2.5.2 | CC: | amastbau, cnv-qe-bugs, fdupont, istein, ksghaier, pousley, pvauter | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | 2.6.0 | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2021-03-10 11:22:41 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 1739700 [details]
importer pod
Created attachment 1739702 [details]
Windows VM
Created attachment 1739703 [details]
VM instance
Created attachment 1739705 [details]
dv and pvc
@ksghaier This is assigned to the wrong component, it seems like it should be under the CNV project. This component deals with running Windows container workloads with https://github.com/openshift/windows-machine-config-operator/ (In reply to Sebastian Soto from comment #5) > @ksghaier > This is assigned to the wrong component, it seems like it should be under > the CNV project. > This component deals with running Windows container workloads with > https://github.com/openshift/windows-machine-config-operator/ I could not pick the CNV project, it says that I'm not authorized to submit a bug for it, how can I get this fixed? @ksghaier I have moved the bug for you. Please ensure details like version and component are accurate. @ @aravindh Thank you, much appreciated. I also tried with adding VirtIO container to windows VM and I had the same issue:
[root@ocp4-bastion ~l]# oc get vm win2k19 -o yaml
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
annotations:
comment: ""
kubevirt.io/latest-observed-api-version: v1alpha3
kubevirt.io/storage-observed-api-version: v1alpha3
sso: guest_agent
creationTimestamp: "2020-12-16T22:26:39Z"
generation: 15
labels:
app: win2k19
flavor.template.kubevirt.io/medium: "true"
origin: rhev
os.template.kubevirt.io/win2k19: "true"
tags: ""
vm.kubevirt.io/template: windows2k19-server-medium-v0.12.3
vm.kubevirt.io/template.namespace: openshift
vm.kubevirt.io/template.revision: "1"
vm.kubevirt.io/template.version: v0.12.4
workload.template.kubevirt.io/server: "true"
managedFields:
- apiVersion: kubevirt.io/v1alpha3
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:comment: {}
f:sso: {}
f:labels:
.: {}
f:app: {}
f:flavor.template.kubevirt.io/medium: {}
f:origin: {}
f:os.template.kubevirt.io/win2k19: {}
f:tags: {}
f:vm.kubevirt.io/template: {}
f:vm.kubevirt.io/template.namespace: {}
f:vm.kubevirt.io/template.revision: {}
f:vm.kubevirt.io/template.version: {}
f:workload.template.kubevirt.io/server: {}
f:spec:
.: {}
f:template:
.: {}
f:metadata:
.: {}
f:creationTimestamp: {}
f:labels:
.: {}
f:flavor.template.kubevirt.io/medium: {}
f:kubevirt.io/domain: {}
f:kubevirt.io/size: {}
f:os.template.kubevirt.io/win2k19: {}
f:vm.kubevirt.io/name: {}
f:workload.template.kubevirt.io/server: {}
f:spec:
.: {}
f:domain:
.: {}
f:clock:
.: {}
f:timer: {}
f:utc: {}
f:cpu:
.: {}
f:cores: {}
f:sockets: {}
f:threads: {}
f:devices:
.: {}
f:autoattachGraphicsDevice: {}
f:autoattachSerialConsole: {}
f:inputs: {}
f:features:
.: {}
f:acpi: {}
f:firmware:
.: {}
f:bootloader:
.: {}
f:bios: {}
f:machine:
.: {}
f:type: {}
f:memory: {}
f:resources:
.: {}
f:limits:
.: {}
f:memory: {}
f:requests:
.: {}
f:memory: {}
f:evictionStrategy: {}
f:networks: {}
f:terminationGracePeriodSeconds: {}
manager: vm-import-controller
operation: Update
time: "2020-12-16T22:26:47Z"
- apiVersion: kubevirt.io/v1alpha3
fieldsType: FieldsV1
fieldsV1:
f:spec:
f:template:
f:spec:
f:domain:
f:devices:
f:disks: {}
f:interfaces: {}
f:volumes: {}
manager: Mozilla
operation: Update
time: "2020-12-16T23:20:12Z"
- apiVersion: kubevirt.io/v1alpha3
fieldsType: FieldsV1
fieldsV1:
f:spec:
f:running: {}
manager: virt-api
operation: Update
time: "2020-12-16T23:20:47Z"
- apiVersion: kubevirt.io/v1alpha3
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:kubevirt.io/latest-observed-api-version: {}
f:kubevirt.io/storage-observed-api-version: {}
f:spec:
f:template:
f:spec:
f:domain:
f:firmware:
f:uuid: {}
f:status:
.: {}
f:conditions: {}
f:created: {}
f:ready: {}
manager: virt-controller
operation: Update
time: "2020-12-16T23:21:11Z"
name: win2k19
namespace: default
resourceVersion: "3901753"
selfLink: /apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachines/win2k19
uid: 39a989a8-8408-4096-be52-84681ddb45a4
spec:
running: true
template:
metadata:
creationTimestamp: null
labels:
flavor.template.kubevirt.io/medium: "true"
kubevirt.io/domain: win2k19
kubevirt.io/size: medium
os.template.kubevirt.io/win2k19: "true"
vm.kubevirt.io/name: win2k19
workload.template.kubevirt.io/server: "true"
spec:
domain:
clock:
timer: {}
utc: {}
cpu:
cores: 1
sockets: 1
threads: 1
devices:
autoattachGraphicsDevice: true
autoattachSerialConsole: false
disks:
- bootOrder: 1
disk:
bus: virtio
name: dv-win2k19-062b5bfe-c048-4cfa-8159-3c1674db1c30
- bootOrder: 2
cdrom:
bus: sata
name: windows-virtio
inputs:
- bus: usb
name: tablet
type: tablet
interfaces:
- macAddress: 56:6f:2c:d0:00:01
masquerade: {}
model: virtio
name: nic1
features:
acpi: {}
firmware:
bootloader:
bios: {}
machine:
type: q35
memory: {}
resources:
limits:
memory: 2Gi
requests:
memory: 2Gi
evictionStrategy: LiveMigrate
networks:
- name: nic1
pod: {}
terminationGracePeriodSeconds: 3600
volumes:
- dataVolume:
name: win2k19-062b5bfe-c048-4cfa-8159-3c1674db1c30
name: dv-win2k19-062b5bfe-c048-4cfa-8159-3c1674db1c30
- containerDisk:
image: registry.redhat.io/container-native-virtualization/virtio-win
name: windows-virtio
status:
conditions:
- lastProbeTime: null
lastTransitionTime: "2020-12-16T23:21:06Z"
status: "True"
type: Ready
created: true
ready: true
Isn't it a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1903585 ? I reproduced this bug by importing a Windows2019 with virtio-scsi to CNV. After a successful import, start the VM on CNV, and got Stop code: INACCESSIBLE BOOT DEVICE. See attached "Screenshot". Once bug 1903585 will be fixed, it will be possible to verify if it solves the issue. Created attachment 1741367 [details]
Screenshot
Verification is Blocked by a vmimport crashloopback issue: [amastbau@amastbau totp2]$ oc logs pods/importer-win20191-9de75658-e59b-48db-b7ac-06e79087e98c --follow I0121 10:06:22.930567 1 importer.go:52] Starting importer I0121 10:06:22.931242 1 importer.go:121] begin import process E0121 10:06:24.833751 1 importer.go:137] Fault reason is "Operation Failed". Fault detail is "[Cannot transfer Virtual Disk. The relevant Storage Domain's status is Unknown.]". HTTP response code is "409". HTTP response message is "409 Conflict". Error sending transfer image request kubevirt.io/containerized-data-importer/pkg/importer.getTransfer /remote-source/app/pkg/importer/imageio-datasource.go:272 kubevirt.io/containerized-data-importer/pkg/importer.createImageioReader /remote-source/app/pkg/importer/imageio-datasource.go:184 kubevirt.io/containerized-data-importer/pkg/importer.NewImageioDataSource /remote-source/app/pkg/importer/imageio-datasource.go:60 main.main /remote-source/app/cmd/cdi-importer/importer.go:135 runtime.main /usr/lib/golang/src/runtime/proc.go:203 runtime.goexit /usr/lib/golang/src/runtime/asm_amd64.s:1373 [amastbau@amastbau totp2] will link to BZ once opened Fabian, does this bug need to be documented in the CNV 2.6 release notes? It came up in my search due to the requires_doc_text? flag. Thanks! Pan, I don't think it requires documentation. It's very likely that it's a duplicate of BZ#1903585 and the fix is part of 2.6.0. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 2.6.0 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:0799 |
Created attachment 1739699 [details] Importer pod logs Description of problem: When I try to import a Windows VM (Win Server 2019) from RHV (works fine on RHV) on CNV, the import is successful and the VM powers on but starts with a blue screen with error "INACCESSIBLE_BOOT_DEVICE" Version-Release number of selected component (if applicable): Openshift 4.6.6 and RHV 4.4 (Self-hosted engine), with OpenShift Virtualization 2.5.2 How reproducible: Always Steps to Reproduce: 1. Import Windows VM from RHV to CNV with default template values 2. 3. Actual results: Blue screen with error "INACCESSIBLE_BOOT_DEVICE" Expected results: VM boots successfully Additional info: