Search results

And way too fast to capture a kernel OOPS, panic etc. when it scrolls through your screen ;) I summarized all this info in this FAQ: http://pve.proxmox.com/wiki/FAQ Feel free to correct it and/or move to a separate page.

After playing for ~2 weeks with Proxmox VE, I must say - I'm impressed. It's probably the best virtualization solution available for Linux. Of course, improvements are always good - here is my wishlist for future releases. Points 1 and 2 can be theoretically made by everybody even now, given a...

Just run: update-pciids as root. "Unknown hardware" in lspci just means that lspci tools doesn't have it in its "database".

I see 82576 support first appears in kernel 2.6.25. Debian Etch uses 2.6.24, so no luck for you. Either compile a newer kernel (which might be tricky if you want to use OpenVZ; if you only want to use KVM, it should be fine) or, backport the driver.

BTW, your cards should be supported by the igb driver. If you do: modprobe igb ifconfig -a Do you see your cards?

First two lines of "lspci -v" for a network card with what is written *excactly*.

Looks like 2.6.24 does not have network drivers for your hardware. Please, post "lspci" as I asked you before (for network cards, please post "lspci -v" output).

Check ifconfig -a if you have any cards detected? Did you replace or move network cards in different slots? Check the contents of /etc/udev/rules.d/z25_persistent-net.rules What does lspci -v show?

And how is "IO delays" value calculated? Is it the same as "wa" (iowait) shown by top?

It is not true. Of course you can run 32 bit guests on 64 bit hosts. I corrected Debian wiki. See also: http://kvm.qumranet.com/kvmwiki/Guest_Support_Status

So download speed is OK, only it takes long until it actually starts to download? Can you confirm your DNS is OK, i.e. do for every entry from /etc/resolv.conf: dig google.com @192.168.1.4 dig google.com @<another entry from /etc/resolv.conf> and see if it returns your queries instantly.

If you use NFS or iSCSI, you don't copy anything, obviously, but configure the hosts to access the same paths. I didn't use live migration with Proxmox VE yet, but are you sure this is what is done? - pausing the guest - copying i.e. 20 GB guest's disk (file) image to another host -...

Do both hosts have access to guest's file image / block device? It is required, otherwise, after migration, guest will not be able to access its drive.

How fast can you download big files (i.e., kernel sources from kernel.org with wget)? Are you sure you don't have DNS servers misconfigured (i.e. resolv.conf on your client etc.)? Your symptoms seem to be typical for it.

I see, and there are KVM patches there as well. Two of the fail to apply cleanly; I didn't check if it's just some code differences that need to be re-edited, or something more serious.

What options do you normally use to compile kvm? Do you apply any patches to qemu/kvm? I tried to compile kvm-84, as it potentially solves one issue I have. Unfortunately, it doesn't seem to work with Proxmox VE interface - when I want to start a guest, it fails with: /usr/bin/kvm: invalid...

Thanks for the hint. Power button was not configured on this system in /etc/acpi/*. It works now.

Good, that does the trick, thanks!

I see it uses system_powerdown in the "monitor". I have acpid running: # ps aux|grep acpi root 49 0.0 0.0 0 0 ? S< 11:49 0:00 [kacpid] root 50 0.0 0.0 0 0 ? S< 11:49 0:00 [kacpi_notify]...

In the web interface for a given guest, there is a "Shutdown" button which is supposed to cleanly shutdown the guest. What is needed on guest for this to work? I tried it with a KVM Linux guest and it worked. Now when I use it with another Linux guest (uses virtio_pci and other virtio_*...