Recent content by dhcolesj

I tried the "convert" command, qemu-disk convert I think it was, that got all the disks for running VMs, and I think if I had looked for where the storage was primarily controlled (sorry forget the term, been testing too many platforms) I probably could have from there. But, no worries, I was...

Yea, I was concerned about the specifics, and found that RHV does raw, so I'm trying just using the raw disk without conversion. my other question was about exporting the disk with the VM powered off, and it doesn't look like that's possible. which is interesting. Unless there's another...

I've found a few threads about exporting, but some are old, and others never mention the correct (or what seems like correct) commands to export a VM (disk, settings etc). I need to export 1 VM back into Red Hat Virtualization as it's the only one I'm concerned with in our POC setup. I need to...

Cool. Gives me an excuse to play with the LXC parts. :D

Anyone here used this? My question is do I need a separate server to run this on, or can it be installed on a Proxmox Host?

Does this need a separate "management" server or can it be installed on a Proxmox Node? Looks like exactly what we need.

Well, as it turns out the cp command doesn't work when exporting from RHV. the qemu-img convert -O raw command works flawlessly as seen on the ProxMox side. Not sure why it wouldn't since the format didn't change, but it did. I haven't tested using qemu-img dd yet.

So, to keep it as raw just run a cp command from the RHV hypervisor and place it where the Hypervisor can see it? I may have to try that.

We use RAW format in RHV. (KVM based). my question is would "qemu-img dd" work faster (or at all) than "qemu-img convert" and has anyone done such a migration? I've seen where you can import raw format disk images into ProxMox instead of Qcow2, and was hoping just exporting the disk as raw...

OK, well, right after posting this, I edited the definition of the VMs to remove disks on local-vm storage, and for odd reasons, the WARNING messages above are gone. Very weird, and still has me puzzled. NOTE: None of the vm disks shown above were on local storage. The cloudinit (which I...

Not sure this is in the right place, but I have installed and setup ProxMox, and using 8.3, and Multpath with LVM for shared storaage. I have created 2 templates and used the last to deploy a VM and when I run "pvs" from the console I see this: # pvs WARNING: Device mismatch detected for...

You may not have done anything wrong, it just may have taken a couple of reboots to get it back into the fold. I'd like to know if it all worked myself. :D We might rename some nodes to take 'em from POC to test/build and if those are the right steps we'll be in good shape.

Your Hypervisor shouldn't route the traffic, let the router (default) do that. The bridges don't route anyway. Since I don't do containers on ProxMox I can only speak from VM machine perspective. So, from ProxMox point of view, your VM's should have a network device that looks like this...

Your VMs need to have their networks assigned to the switches, not the VLAN interfaces. Then the networking inside the container/VM is the same as a regular (physical) box. you assign an IP and set mask and default route.

I'm not against CEPH (just not a FAN unless you have a lot of local storage you want to use for low end workloads/iso storage/backups), but if you have Fibre attached SAN and you want to use Shared storage LVM is the way to go. It'll provide the best performance and keep your IP network from...