a way of redoing a vm configured with libvirt on proxmox

[gcalliet]

Hello,

I tested a "bizare" OS (OpenVMS) on Proxmox and it hangs in the first boot. I tested it on a fedora environment, using libvirt configurator, and it works. Apparently the configurations are the same.

Is there a way to "export" the libvirt configuration, and "import" it on proxmox?

Thanks

 

[dcsapak]

no there is no libvirt import, but if you post both the libvirt xml and the qemu vm config, maybe we can see what's wrong

also you can get the qemu commandline from the pve vm config with

qm showcmd ID --pretty

so you could get the running commandline from libvirt and compare

 

[gcalliet]

no there is no libvirt import, but if you post both the libvirt xml and the qemu vm config, maybe we can see what's wrong

also you can get the qemu commandline from the pve vm config with

qm showcmd ID --pretty

so you could get the running commandline from libvirt and compare

Hello,

I join the libvirt configuration (xml), the proxmox configuration, and the command for proxmox.

There are more disks on libvirt, I can use all, and install the os from the iso. On proxmox it begins a boot from the cd and hangs when it tries to associate a ram disk copied before that on memory (the support for OpenVMS speaks about DIMM1 usage).

Any idea welcomed.

 

[gcalliet]

Hello,

I join the libvirt configuration (xml), the proxmox configuration, and the command for proxmox.

There are more disks on libvirt, I can use all, and install the os from the iso. On proxmox it begins a boot from the cd and hangs when it tries to associate a ram disk copied before that on memory (the support for OpenVMS speaks about DIMM1 usage).

Any idea welcomed.

Hello,

Do you think I can submit this issue as a "ticket" of support? I choose ProxMox to develop my use of OpenVMS virtualised, because it seems more robust than libvirt... and for now I can use libvirt and not ProxMox.

 

[dcsapak]

i looked a bit over the configs (i really dislike xml though ) and a few things stood out:

* in libvirt you have 4 cores, but in the pve config you configured 4 sockets, try using 4 cores instead
* the machine type is 7.0 in libvirt, but 7.1 in the pve conf, you might want to set that manually to 7.0?)
also trying to use i440fx instead of q35 could also help (thats not what libvirt here uses, but worth atry)
* the display type in libvirt ist set to spice/qxl, so thats also what you can try to set in pve
* in libvirt also the hpet is disabled, you can try to add '-no-hpet' to the 'args' of the pve config

Do you think I can submit this issue as a "ticket" of support? I choose ProxMox to develop my use of OpenVMS virtualised, because it seems more robust than libvirt... and for now I can use libvirt and not ProxMox.

if you have a basic subscription or higher, you can try, but AFAIU getting "unknown" guest os to run is not really covered by the subscription agreement