Search results

I just fixed this for myself. You can fix it by editing /etc/hosts and correcting the line about your local host (usually the 2nd line).

I know; it was totally separate but more pressing issue, that's why I didn't come back to reply quickly :)

Sorry for the late reply... I tried it, and one of my VM decided to not come back after reboot (stuck after Loading initramfs goes away, and then "Loading, please wait..." message just blinks forever. Turns out I had to turn off ACPI support on it for some reason. Anyways, side adventure aside...

Sorry, I must've referred to it incorrectly. I meant the terminal / console after grub menu, where kernel takes over and start spewing status messages before dropping you at the login prompt, and there after, on the host OS. The screen resolution up to grub menu is okay, after that the vkvm...

I use DRAC's remote console (vkvm) to manage my server, as it is thousands of KM away in a datacenter. Before installing Proxmox, the resolution of this was handled by X11's configuration on the OS. After installing Proxmox, it made the window too high for my monitor (macbook, 1280x800, but top...

Re: pve1 kernel: EXT4-fs (dm-1): Unaligned AIO/DIO on inode 36831235 by kvm; performa Ah, okay, thanks! Then I guess we need to report to Proxmox / KVM, and hope they fix it, then?

Re: pve1 kernel: EXT4-fs (dm-1): Unaligned AIO/DIO on inode 36831235 by kvm; performa I also noticed this on my machine. Does anyone have any recommendations on how to work around this problem?

After tanking my way through the physical to virtual conversion, I'm down to the final stretch of getting the VMs connected properly. However, banging my head at it for almost an entire day now made me realized how utterly useless I am when it comes to virtual networking without the pretty GUI's...

Sorry! User stupidity! Been up all night and totally blanked out. I realized my system was using 2.2-24 instead of the latest, so I did an apt-get update && apt-get upgrade between copying disk to raw, and raw to qcow2, but forgot to reboot the system. So all the kernel modules were in a broken...

I've been fighting with this for almost 12 hours now, and the server is still not accessible. Much of the time is lost from dd'ing from the backup disk to a .raw image (even with bs=16M, I was only getting 32MB/s on a 150G device), as well as converting the said .raw image to a compressed qcow2...

Ah, I didn't think of rsync. Yes, I think rsync will work much better than dd. Live system is Debian 6.0.6, so rsync should work as long as I skip /sys, /dev, /proc, /media, and /mnt... Though, I need to look up how to keep the boot menu working after rsync, so if things go south, I can rsync...

First post, not even sure where to start :confused: I have 5 drives in hardware RAID 6 right now. I ordered a 6th drive today, of same capacity, with intention to do a P2V conversion. Here are the steps I am planning to take for the process, can you guys please point stuff out if I am messing...