Search results

Re: help needed: legacy linux and virtio block - howto to map vdX to target sdX for g OK, I solved it for my legacy App. My solution might be specific to my situation. The general approach could be creating symlinks named sdX for each vdX device. If your Application can address it, the virtio...

Re: help needed: legacy linux and virtio block - howto to map vdX to target sdX for g Yes, I tried that but it did not work....thought it was caused by different major-minor numbers from vdX in comparison to that of sdX in the devices. But thinking of it, I might have done something wrong or...

Hi Folks, sorry if this has been asked before but I couldn't find a solution as of today. For a legacy app, based on slackware linux, I was able to produce a custom kernel with kvm & virtio support, to be used in a guest-VM. However the legacy Application to be run requires the namespace for...

...not sure if I understand correctly...installing Proxmox on a KVM based VPS will still create a nested VM environment. AFAIK nested KVM support is planned for future KVM releases and still far from a "production use" state. ...so, if you can wait until nested KVM is ready...and then find...

...I'd try that route: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny. AFAIK, if you succeed, you'd be limited to use OpenVZ containers only, because KVM cannot be run in a nested VM environment.

....the Realease.txt in the root of the proxmox-ve_1.8-5754-4.iso is still that of pve-v1.7 ?!?

...just curious. Anyone tried this: http://www.howtoforge.com/how-to-set-up-a-usb-over-ip-server-and-client-with-debian-lenny ?

...you did not update the e1000e driver in kernel 2.6.35 ?? Another remark: ....gave it a try on a fresh base squeeze install where I wanted to tryout ext4 and support for LSI Megaraid 9240-8i and IBM ServeRaid M1015 respectively. The RAID controller is not propperly recognised if there are...

I folks, for some research I'd like to setup several vz containers and forward different subset of devices to them. However, in order to make the devices visible, the pve kernel needs to be build with the required drivers. I know that pve kernel sources are provided, but what is the...

Hi Dietmar, I gave it a quick test with a fresh setup of pve-1.7, where I can confirm that the problem still persist with stock kernel. Your newly uploaded kernel with updated e1000e driver solved the problem! ...tested it by uploading a couple GBs of ISOs to the storage. Normally the...

...I've seen this on my supermicro X8SIL-F mobo. It comes with Dual Intel® 82574L Gigabit Ethernet Controllers Apparently there are some problems with all major distros with these, see here: https://bugzilla.redhat.com/show_bug.cgi?id=632650 I am currently not using pve on this mobo...

...cannot comment on this, since I am using KVM only. Regarding the performance issues, I can confirm that OF will run with virtio-net and virtio-block drivers on Proxmox VE If you're using a HW-Raid controller, this might be the only option to make use of it, i'd think. (passing on the PCI...

OK, see my remarks in your simplified thread...here

1) if you stick with your service level, then... - in that case you cannot set PVE eth0 to acquire via DHCP, since it will acquire a lease first (because VMs eth0 starts later). - you should NOT try and assign any IP out of your ISPs range to PVE eth0 AND to one of your VMs connected to the...

...normally this should work fine, but cable setups are tricky. Are you sure you have some leases left (sometimes no. of leases are limited by the cable modem. You need to reset the MAC/leases cache in order to allow a new MAC to receive a lease) if more than one is possible at all. ..can you...

..in a cable setup, some providers limit the number of leases available Are you sure you have some left? ...IPs are assigned to the bridge only...eth0 will follow ...so you expect eth1 on SME and PVE to be on the same network? - of course you cannot have PVE and a VM NIC share an IP (two NICs...

When you started from a debian install, you will miss the basic disk / filesystem layout of a standard PVE install. ...to start with, you should place your "/var/lib/vz" on a separate LVM group (which in your case should be created on a different physical volume of course) ...and probably read...

...oups...forgot...this is for OF with e1000 net:

OK, this is for TCP client to OF (with virtio-net) ...and client to PVE host:

Yes I had the very same problem. Install from ISO went fine, but it simply would not boot (not even into grub). My host has a HDD/SDD on IDE (used for proxmox host (/boot and /root) and three SATA drives (for storage). Proxmox is numbering them as follows: sda: sata-disk 1 sdb: sata-disk 2...