Search results

Sadly one problem left: root@basis01:~# apt-get install -f Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 1 nicht vollständig installiert...

5 more minutes and my Debian based setup is up an running. I think the first information about the setup I gave to you was wrong. The initial setup was a Debina setup too due to the VGA problems. I do not use OpenVZ and if I want to I can create a addition store with LVM and format it with ext3.

I've to do a debian install because my PCIeX16 slot is used by my RAID Controller and I've only old PCI VGA cards not supported by the ISO-Installier - my wish sice my first contact with proxmox: pleas switch to a cures installer ... really no one needs a graphical installer ... with the ability...

Thanks any way - and I will NOT use ext3 :-)

Yes it is a ISO install. I've installed a few things: bind, dhcpd and SEP Sesam Server, then I've changed the default mounts to: /dev/mapper/pve01-root on / type xfs (rw,noatime) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on...

Hi, I've tried to upgrade my system from 1.9 to 2.1. The script failed with: apt-get --purge -y --force-yes install rsyslog Reading package lists... Building dependency tree... Reading state information... rsyslog is already the newest version. The following packages were automatically...

This will not work as if I can see the boot scree, I see it for less than a second ...

I've tried this ... but the machine rebooted before I was able to do so ... perhaps due to the slow connection to the remote site. Is there an other way?

Thanks. It's a remote site ... perhaps I will try vmware converter. If I'm lucky I can find some one who boots if into a rescue CD for me and set a password ... I've applied mergeide.reg. But: How can I make the VM stop after the bluescreen ?

Hi, I've tried to virtualize a Windows XP using "selfimage" as described here: http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Physical_.28running.29_server_to_Proxmox_VE_.28KVM.29_using_SelfImage Every thing worked as expected but XP does not boot. It imediately shows a...

OK, changed to 2.6.32 ... lets see - but one strange things happened: The HP P410 devices usually name like this /dev/cciss/c0d0p1 got normal "sd" devices. In my case the server didn't boot because /dev/cciss/c0d0p1 was "renamed" to /dev/sda1. Can some one please point me to some background...

Again a bluescreen with BAD_POOL_HEADER as usual. @e100: Why 2.6.32 kernel. Can you give reasons? @holgihero: Hardware: - IDE - rtl8139 @tom: Updates done: pve-manager: 1.9-26 (pve-manager/1.9/6567) running kernel: 2.6.35-2-pve proxmox-ve-2.6.35: 1.8-13 pve-kernel-2.6.32-4-pve: 2.6.32-33...

I'm on 2.6.35-2-pve, not 32

This is the blue screen.

I know the devic. dm-8 is - or better was - /dev/vg0/vzsnap-bs01-0 :-) What I need is to know why this happens and how to get rid of this problem ...

Thanks for your reply. Next time I will do a screen shot. Oh, ok, thanks, I will do the update.

Hi, I've a KVM-VM with Windows 2008 sp2. Mainly this VM works but on a irregular base (2 to 8 weeks) it bluescreens with no visible reason. Other Linux and Windows XP VMs on this system work flawlessly. What can I do to solve this problem? VM: name: MS-Exchange2008 vlan0...