This worked of course. Thank you very much! > On Saturday, Dec 10, 2022 at 5:59 PM, Jeremy Hansen <jer...@skidrow.la > (mailto:jer...@skidrow.la)> wrote: > Thank you! > > > > > On Saturday, Dec 10, 2022 at 4:56 PM, Wei ZHOU <ustcweiz...@gmail.com > > (mailto:ustcweiz...@gmail.com)> wrote: > > Hi, > > > > You can configure guest cpu model. > > > > Please refer to > > https://docs.cloudstack.apache.org/en/4.17.1.0/installguide/hypervisor/kvm.html#configure-cpu-model-for-kvm-guest-optional > > > > > > > > On Saturday, 10 December 2022, Jeremy Hansen <jer...@skidrow.la.invalid> > > wrote: > > > > > Looks like it’s supported by the host hardware on my CS hosts: > > > > > > [root@netman ~]# cexecs cs: "/lib64/ld-linux-x86-64.so.2 --help | grep > > > x86-64-v2" > > > ************************ cs ************************ > > > --------- cm01--------- > > > x86-64-v2 (supported, searched) > > > --------- cm02--------- > > > x86-64-v2 (supported, searched) > > > --------- cn04--------- > > > x86-64-v2 (supported, searched) > > > --------- cn05--------- > > > x86-64-v2 (supported, searched) > > > --------- cn06--------- > > > x86-64-v2 (supported, searched) > > > --------- cn07--------- > > > x86-64-v2 (supported, searched) > > > > > > I am running KVM. Any idea how to incorporate using the ‘—cpu host’ > > > option in a Cloudstack environment? > > > > > > Thanks! > > > > > > > > > > > > On Saturday, Dec 10, 2022 at 3:26 PM, Jeremy Hansen <jer...@skidrow.la> > > > wrote: > > > In an effort to troubleshoot this, I decided to launch a Rocky 8 vm and do > > > a manual upgrade to Rocky 9. While I understand this isn’t recommended, I > > > thought perhaps it would reveal what the issue are. After I started doing > > > package upgrade, I noticed this: > > > > > > Fatal glibc error: CPU does not support x86-64-v2 > > > > > > I suspect this is the root of my issues. Can anyone explain this > > > further? Is there something I can change in Cloudstack to allow this v2 > > > capability? > > > > > > Thanks > > > -jeremy > > > > > > > > > > > > On Friday, Dec 09, 2022 at 2:32 PM, Jeremy Hansen <jer...@skidrow.la> > > > wrote: > > > Sorry for the late response. Got covid. Mild. Anyway. > > > > > > I have plenty of Rocky 8 vm’s running with no issue and I can launch news > > > Rocky 8 vm with no issue. Here’s lspci from one of my running rocky 8.7 > > > instances: > > > > > > [root@cmx01 ~]# lspci > > > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev > > > 02) > > > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] > > > 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton > > > II] > > > 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton > > > II] (rev 01) > > > 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) > > > 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 > > > 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device > > > 00:04.0 Communication controller: Red Hat, Inc. Virtio console > > > 00:05.0 SCSI storage controller: Red Hat, Inc. Virtio block device > > > 00:06.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon > > > 00:07.0 System peripheral: Intel Corporation 6300ESB Watchdog Timer > > > > > > Thanks > > > -jeremy > > > > > > > > > > > > On Tuesday, Dec 06, 2022 at 5:10 PM, Nux <n...@li.nux.ro> wrote: > > > What hardware profile are you using? If you boot a system rescue cd or a > > > rocky 8 one, what is the output of "lspci"? > > > > > > On 6 December 2022 18:41:25 GMT, Jeremy Hansen <jer...@skidrow.la.INVALID> > > > wrote: > > > > > > Unfortunately I’m getting a kernel panic upon boot. I tried both the > > > production grub option and the rescue and I get the same result. Maybe > > > something with the size of the root disk? I have it just at 8 gig right > > > now? Something with the initrd perhaps? > > > > > > Thanks! > > > -jeremy > > > > > > On Tuesday, Dec 06, 2022 at 12:53 PM, Jeremy Hansen <jer...@skidrow.la > > > (mailto:jer...@skidrow.la)> wrote: > > > Wow. Thank you! I appreciate this. I’ll report back after trying. > > > > > > -jeremy > > > > > > > > > > > > On Tuesday, Dec 06, 2022 at 11:39 AM, Nux <n...@li.nux.ro (mailto: > > > n...@li.nux.ro)> wrote: > > > > > > > > > God knows, I've built you one with the Cloudstack bits enabled, you can > > > grab it from below. It's got the root login enabled, so that's your > > > default user. Let me know if it works. > > > > > > http://dl.openvm.eu/cloudstack/rockylinux/9/rockylinux-9-kvm-rootuser. > > > qcow2.bz2 > > > > > > I'll build more later on with non-priviliged users. > > > > > > --- > > > Nux > > > www.nux.ro [1] > > > > > > On 2022-12-06 15:26, Jeremy Hansen wrote: > > > > > > Unfortunately I think it gets stuck before ever reaching grub. I tried > > > to catch it on the console after a reboot and this is all I see. I > > > never get to the grub menu. > > > > > > Is there a way I can alter the qcow2 image before I create a template? > > > > > > I thought perhaps I could see the IP it obtains via dhcp, but I see > > > nothing coming from that VM which tells me it's not getting to the > > > point of bringing up its interface. > > > > > > Thanks > > > -jeremy > > > > > > On Tuesday, Dec 06, 2022 at 4:59 AM, Nux <n...@li.nux.ro> wrote: > > > > > > You can't alter the kernel parameters from libvirt as the image loads > > > its own kernel, but you can alter the parameters at their grub screen. > > > Try to open the console proxy as soon as possible and hit up or down > > > arrow so grub doesn't proceed, then hit "e" key (I think) to edit the > > > appropriate vmlinuz entry. > > > > > > My hunch is that this being a generic image (made mostly with EC2 and > > > possibly Openstack in mind) they send all output to a serial console > > > instead of vga, so you would need to remove any parameters such as > > > console=ttyS0 and then boot it. > > > > > > --- > > > Nux > > > www.nux.ro [1] > > > > > > On 2022-12-06 04:26, Jeremy Hansen wrote: > > > > > > I'm trying to boot a Rocky cloud image for Rocky 9.1 using their qcow2 > > > image. > > > > > > As soon as I start the VM, I get: > > > > > > "Probing EDD (edd=off to disable)... ok" > > > > > > and then nothing. I don't see a DHCP lease being pulled, so I assume > > > the VM isn't actually proceeding with boot. > > > > > > Anyone else see this? This is on Cloudstack 4.17.1.0. I posted a > > > similar message on the Rocky mail list. Is there an easy way via virsh > > > or cloudstack to alter the kernel command line parameters in an > > > existing image before it boots? > > > > > > Thanks > > > -jeremy > > > > > > Links: > > > ------ > > > [1] http://www.nux.ro > > > > > > > > > > > > Links: > > > ------ > > > [1] http://www.nux.ro > > > > > >
signature.asc
Description: PGP signature
