Recent content by draak

++1

I've sent a feature request, than you for your suggestion. It would be nice to have this functionality, as migration over live production network is not desirable.

Hello, Is there any way that this can be achieved? Because it is not very elegant or efficient to do migrations over the production network. Thanks!

Hello, Could you please advise on setting up a dedicated network for live migration? I've got two networks, client and storage. I could possibly use storage network for that, but I'd prefer having both servers directly interconnected by a cross-over cable. Thank you.

Hello, I pulled this together from various Debian/Ubuntu sources as information from the official wiki didn't work for me for some reason. Changes to /etc/iproute2/rt_tables weren't required and post-up/down "ip route add table..." didn't work. This config is for two networks, default...

Hello mo_, I've exported NFS share on NAS, and set NFS storage in GUI. Nodes mount it fine. I then restricted NFS share to storage network only and nodes then can't mount the share. Normally I'd add static route for the new interface, which in my case is vmbr<vlan number>. Is there any...

Thanks mo_, I'll give it a go tomorrow.

Hello, I've got an upcoming project where I need the following setup. I would appreciate your thoughts on this and what would be the "best practice". Requirement: I have 4 interfaces divided in 2 bonds. There will be a mixture of KVM and CT. Each virtual server will need access to both client...

This is currently on the system. # dpkg -l | grep qemu ii etherboot-qemu 5.4.4-9 Bootstrapping for various network adapters (qemu) ii pve-qemu-kvm 1.0-5 Full virtualization on x86 hardware ii...

Sorry! I only tried to work it out myself. That was just a temporary workaround, not a fix! (virtio disk and NIC both work fine though)... :-)

With qemu-server removed, here's the output when trying to boot from the command line. # qm start 100 qemu: could not load PC BIOS 'bios.bin' start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait' -mon...

When tried to start the VM after I removed qemu-system, syslog entries are as follows. Mar 5 13:09:48 XXXXXXXXX pvedaemon[985973]: start VM 100: UPID:XXXXXXXXX:000F0B75:021EAF2A:4F54BB1C:qmstart:100:root@pam: Mar 5 13:09:48 XXXXXXXXX pvedaemon[985139]: <root@pam> starting task...

It seems that without qemu-system, VM wouldn't even start. I had to install it back to be able to boot this VM. It looks to me that SeaBIOS just can't see the disk... I even tried to remove the VM and re-create it, but the issues stays the same, Virtio disks won't boot.

open("/etc/ld.so.cache", O_RDONLY) = 3 open("/usr/lib/libnss3.so.1d", O_RDONLY) = 3 open("/usr/lib/libnssutil3.so.1d", O_RDONLY) = 3 open("/usr/lib/libsmime3.so.1d", O_RDONLY) = 3 open("/usr/lib/libssl3.so.1d", O_RDONLY) = 3 open("/usr/lib/libplds4.so.0d", O_RDONLY) = 3...

I've installed ProXmoX 2 beta and then on top of it I installed Gnome for dev purposes. kvm --version QEMU emulator version 1.0.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard md5 sums are as follows 9649e5d3cebac9106af3d6555dbf4ae7 /usr/share/kvm/bios.bin md5sum...