Closed sirtoobii closed 1 year ago
So the VM doesn't book off of an iso?
What does "lxc info
What does "lxc info --show-log" show when its running?
/var/snap/lxd/common/lxd/logs/lxd.log
:
time="2023-07-13T18:05:39Z" level=warning msg=" - Couldn't find the CGroup network priority controller, network priority will be ignored
lxc monitor
: Nothing suspicious, mostly communication logs with our remote lxc controller. So the VM doesn't book off of an iso?
I just know about this specific redhat version. But an ubuntu iso works fine
Will it boot off other isos?
Also sorry, I meant
lxc info (instance) --show-log
lxc info (instance) --show-log
The log:
sections stays empty
Will it boot off other isos?
Yes, the latest ubuntu-server iso boots perfectly fine
Interesting. Something different about the redhat iso. Are you able to reproduce with an iso we can try (maybe a centos iso?)
@tomponline Just tested centOS 7.9, netinst iso - same behaviour.
Ah good so we should he able to reproduce
Between 5.15-002fa0f
and 5.14-7072c7b
UEFI firmware was updated and CSM support was added.
I think it worth trying to check if it works with security.csm
set to true
.
Certainly worth a try. Although that will disable UEFI which shouldn't be needed in this case AFAIK and seems undesirable.
Can you try using the latest/edge
channel (keeping in mind you likely won't be able to downgrade, so using a fresh/throwaway system for this would be good) and then also I noticed you've not set your boot.priority
, which we normally need to do to ensure it boots from the iso.
But I've just successfully booted from and installed centos 7.9 from the iso using latest/edge
:
lxc config show vtest --expanded
architecture: x86_64
config:
volatile.cloud-init.instance-id: d2d513de-be55-4d46-8459-1f78d95036d8
volatile.eth0.host_name: tapca911747
volatile.eth0.hwaddr: 00:16:3e:cc:4c:d2
volatile.last_state.power: RUNNING
volatile.last_state.ready: "false"
volatile.uuid: 0b43fd4f-aee8-4787-9a95-a1840f199b5e
volatile.uuid.generation: 0b43fd4f-aee8-4787-9a95-a1840f199b5e
volatile.vsock_id: "4075497721"
devices:
eth0:
name: eth0
network: lxdbr1
type: nic
iso:
boot.priority: "10"
source: /home/user/Downloads/CentOS-7-x86_64-DVD-2009.iso
type: disk
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""
If this works, then LXD 5.16 is being released next week and will be cut from latest/edge.
I tried latest/stable too for good measure and it worked fine.
and then also I noticed you've not set your boot.priority, which we normally need to do to ensure it boots from the iso.
Yes i thought there must be such an option -> I always booted with the graphical boot menu.
I tried latest/stable too for good measure and it worked fine.
You managed to boot with 5.15
? If yes, did you change anything?
And at this point also thank you for looking into this so quickly!
Yes I did manage to boot.
Yes I did manage to boot.
@tomponline Just for clarification: You booted the centOS 7.9 iso with the 5.15-002fa0f
lxd snap and without any modifications?
Yes indeed. I only needed to set boot.priority, which is a normal requirement.
What storage pool type is vm-disks
?
I tried on a dir
pool.
Did you try latest/edge yet?
Yes indeed. I only needed to set boot.priority, which is a normal requirement.
Hmm, I suspect this has nothing to do with the success of the booting itself (I mean I should make no difference if manually chose the ISO in the boot menu?)
What storage pool type is vm-disks?
Also dir
Did you try latest/edge yet?
Not yet, I probably won´t have time until this evening
Hmm, I suspect this has nothing to do with the success of the booting itself (I mean I should make no difference if manually chose the ISO in the boot menu?)
Worth trying though right? In case somehow you are selecting a different item (perhaps a non-uefi enabled one).
Seems like we've seen a similar issue here https://discourse.ubuntu.com/t/ubuntu-18-04-vm-doesnt-start-on-ubuntu-20-04-on-lxd-5-15
Does lxc config set NAME raw.qemu='-cpu qemu64'
fix it?
In addition to the workaround above, we intend to address this issue via a patch to our edk build in the snap package.
For more details on the issue see
Issue description
After an update to the snap package
5.15-002fa0f
our Redhat 7.9 VMs fail to boot because they cannot see any disks:Downgrading to
5.14-7072c7b
resolves the issue.Steps to reproduce
The issue is easily reproducible by booting directly from an official redhat iso (or centOS 7.9):
Create a fresh vm:
Information to attach
Container configuration
```yaml architecture: x86_64 config: limits.cpu: "4" limits.memory: 16384MiB volatile.cloud-init.instance-id: 020a77f6-d05b-42fb-8a8d-3c19134b3204 volatile.eth0.hwaddr: 00:16:3e:53:83:ba volatile.last_state.power: STOPPED volatile.last_state.ready: "false" volatile.uuid: 85e7bb4e-0c6f-4c34-b0b9-ea371c746558 volatile.uuid.generation: 85e7bb4e-0c6f-4c34-b0b9-ea371c746558 volatile.vsock_id: "7" devices: eth0: name: eth0 nictype: bridged parent: br-lxd type: nic rhl7iso: source: /VM/iso/rhel-server-7.9-x86_64-dvd.iso type: disk root: path: / pool: vm-disks size: 250GB type: disk ephemeral: false profiles: - default stateful: false description: "" ```