Search results

This is completely wrong.

Weird, I could have sworn I replied to this yesterday :( Anyway, I tried several times, including bare seconds after seeing ceph reporting "HEALTH_OK". I pretty much gave up at that point...

Maybe I was not clear. I did all of that. Per the HOWTO. Yet when I create a VM, and am moving through the wizard, when I get to the storage part, there is nothing to choose from.

PCI passthrough is kind of arcane. Some controllers work, some don't. Some builtin on the motherboard have issues due to PCI bridge or whatever. I've seen things where an HBA in slot X doesn't pass through properly, but if moved to slot Y, it does. I was proposing a simple test to see if it...

Maybe something about the motherboard that doesn't like passthrough for the SATA controller? Can you swap them? e.g. pass through the 3ware and use the mobo sata for the promox install?

I don't have 3 spare boxes. I'm not interested in performance, just learning how this works, and virt should work for that. Regardless of that, I understand now there is no mount point, but this doesn't explain why when I tried creating a VM, no storage is presented to use?

Deafening silence. Off to look for other solutions, I guess...

I think I might have seen a hint on a different thread. Since I am testing these virtualized, there is no kvm support (I can set the vmware servers to support a nested hypervisor but hadn't done so...) The thread implied that kvm supports the rdb storage directly - so if there is no kvm, would...

I must be missing something basic. I created 3 proxmox virtual machines under vmware (for testing). The cluster looks good, the ceph status tab on any given host says health_ok. Each host has an OSD showing for a total of 3X the space of each disk. It all claims to be okay (and I have...

sheepdog seems to just use the same interface as corosync. So I am wondering if I can change *that* address (well subnet) to use the dedicated interface. My main concern is I still need to be able to get to the management interface, but it looks like that is listening on the wildcard address...

I ran into this same quandary while playing with sheepdog the last couple of days. I had a thought on this: my motivation is to remove sheepdog replication traffic from the nics the guests on my 2-node proxmox cluster use for their network traffic. So, given that, instead of a dedicated link...

Based on a couple of articles I read, I decided to dabble with this. It was certainly simpler than setting up drbd, I'll say that much! Took about 5 minutes and I had a centos guest up and running. Write performance (two nodes with --copies=2) was about wire speed (110MB/sec). A large...

Semantics. Obviously the layout on storage has a format. e.g. vm disk metadata that qcow2 has to support snapshots etc. That has nothing to do with the file itself, but data inside it. That said, like I said, I understand why it works this way - it's just a nuisance that I can't use LVM...

No, in both cases it was the standard file format (e.g. no choice between qcow2 or raw.) I would use qcow2 here if I could but I understand why it has to be raw format stored on an LV.

Let me clarify. I am using the replicated local storage in shared mode. This is documented and present in your own GUI. So it sounds like until some future enhancement, whether I continue with drbd or switch to rbd or somesuch, snapshots of running VMs will not work...

So I am running two PE2.3 hosts in a cluster using drbd as shared local storage. Works perfectly. My only complaint is that I can't snapshot any of the guests, since the storage is not snappable (lvs on the vg on top of the drbd devices.) What is frustrating is that since the storage is...

Nothing useful, I'm afraid. I ended up deleting the "sick" VM. Very odd... Be nice to know where (if anywhere) useful reason(s) for the failure were logged or some kind of verbose migration mode. Oh well...

On proxmox2: root@proxmox2:~# qm config 100 boot: c bootdisk: virtio0 cores: 1 memory: 4096 name: hyper1 net0: virtio=AE:5B:11:94:32:F2,bridge=vmbr0 ostype: l26 sockets: 1 virtio0: San:100/vm-100-disk-1.raw,size=32G root@proxmox2:~# pveversion -v pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)...

I have a running ubuntu 12.04 guest on proxmox2. I am trying to migrate it to proxmox1. It has no local resources or anything. I fire up the migrate (same results from cli as gui) and see this: root@proxmox2:/var/log# qm migrate 100 proxmox1 --online Apr 04 09:49:12 starting migration of VM...

Both servers are fully up to date, but I think the failure occurred before that. I will try restoring from a previous copy of the raw file and see...