[cstanley]

It doesn't work with my custom Windows installations either. I know you're not going to support my custom win installations, that's fair enough but you can't "hide" behind the "oh, it's for Windows servers anyway" argument.

Anyone get this to work still?

Mine is outputting:

Option 'ipv4': Use 'on' or 'off'
Failed to parse "yes" for "dummy.ipv4"

I know the port is open from nmap command:

Host is up (0.034s latency).
PORT     STATE SERVICE
5900/tcp open  vnc
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: general purpose
Running: Linux 3.X
OS CPE: cpe:/o:linux:linux_kernel:3
OS details: Linux 3.11 - 3.14
Network Distance: 20 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 2.26 seconds

But when I try to connect with VNC it doesn't connect.

[everwicked]

I just read your ticket, vKVM mode is for Windows systems

It doesn't work with my custom Windows installations either. I know you're not going to support my custom win installations, that's fair enough but you can't "hide" behind the "oh, it's for Windows servers anyway" argument.

[IainK]

I did figure that one but it didn't seem to work. No matter what options I tried; it still ended the same:

Aborted

[Myatu]

Use the option "-no-kvm"

[IainK]

So this doesn't seem to work on servers that don't support virtualisation (VT) extensions... whereas vKVM does.
A bit of a shame for the older servers in the block.

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
Aborted
root@rescue:/tmp#

[Myatu]

[ snip! ]

[stalks]

echo -e "change vnc password\nmoo"|./kvm -drive file=/dev/sda -vnc 0.0.0.0:0 -monitor stdio -boot d -cdrom mycdrom.iso

[IainK]

Nice, that's cool. Shame we can't pass the password in on the command line as that would be scriptable. I'll look in to that.

[stalks]

I've just come accross how to add a vnc password:

Add '-monitor stdio' to the end of the command-line and you can interact with the QEMU daemon after its loaded and run a command to set the password:

# ./kvm -drive file=/dev/sda,if=scsi -drive file=/dev/sdb,if=scsi -cdrom mycdrom.iso -monitor stdio -vnc 0.0.0.0:0    
QEMU 0.12.2 monitor - type 'help' for more information
(qemu) change vnc password
Password: ******
(qemu)

[IainK]

It took me 5-10 minutes to install Linux over VNC... If anyone had taken that over I would have noticed... Fair enough it could be more secure using a tunnel but I'd rather just get the job done quick.

I'm sure there's a way to add a vnc password if you really care.

[stalks]

Change the XXX.XXX.XXX.XXX to reflect your servers IP address.

I suggest using localhost and forwarding SSH ports like OVH suggested. Leaving the machine open for use and unprotected is asking for trouble.

You could add an iptables rule to block all but your IP if you don't like the hassle of ssh port forwarding.

Also if you use the -drive parameters you can install the new OS using the intended device names of /dev/sda etc. Instead of the IDE interface of /dev/hda that QEMU defaults to.

./qemu-system-x86_64 -drive file=/dev/sda,if=scsi [...etc]

[OVHelp]

Does anyone know if one can install Windows through vKVM - legit .iso obviously? Trying to bypass OVH's gay non-raid0 or 20GB limit on C: etc??

Cheers

[darkfyre]

OVH - You guys mentioned that your target was to have the vKVM working this week .. any update ?

[IainK]

I've got Ubuntu 9.10 installation working through rescue mode. Not had a chance to try it out yet but here's how to get it started. Login to rescue mode ssh and issue the following commands:

cd /tmp
wget http://87.98.218.102/kvm.tgz
tar xf kvm.tgz
wget http://mirror.xn3.co.uk/ftp.ubuntu.com/releases/9.10/ubuntu-9.10-server-amd64.iso
/tmp/bin/qemu-system-x86_64 /dev/sda -m 1024 -cdrom /tmp/ubuntu-9.10-server-amd64.iso -boot d -vnc XXX.XXX.XXX.XXX:0

Now open VNC and connect to XXX:XXX:XXX:XXX (Display:0, Port: 5900)

Change the XXX.XXX.XXX.XXX to reflect your servers IP address.

Hopefully you should see this:


Update: Tried, tested, delivered. Works well.

[Myatu]

@gangsta: You can't use "-cdrom ftp://FTP_SERVER_IP/bootcd.iso".

Standard options:
-h or -help     display this help and exit
-version        display version information and exit
...
-cdrom file     use 'file' as IDE cdrom image (cdrom is ide1 master)

So use "wget" to grab the ISO first, then point to it with something like "-cdrom /iso_file.iso".

Example:

ssh root@SERVER_IP -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C /tmp && wget ftp://FTP_SERVER_IP/bootcd.iso -O /tmp && /tmp/bin/qemu-system-x86_64 /dev/sda -m 1024 -cdrom /tmp/bootcd.iso -boot d -vnc 127.0.0.1:0'

[gangsta]

Well, Neil's method doesn't work for me.
I'm trying to boot from ISO file placed on my second OVH server, but no luck.

server ip address was replaced with SERVER_IP string in code below

login as: root
Using keyboard-interactive authentication.
Password:
Linux rescue.ovh.net 2.6.32.2-xxxx-std-ipv4-32 #1 SMP Tue Dec 29 14:40:32 UTC 2009 i686
root@rescue:~# ssh root@SERVER_IP -L 5900:localhost:5900 'cd /tmp | wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C /tmp && /tmp/bin/qemu-system-x86_64 /dev/sda -m 1024 -cdrom ftp://FTP_SERVER_IP/bootcd.iso -boot d -vnc 127.0.0.1:0'
The authenticity of host 'SERVER_IP (SERVER_IP)' can't be established.
RSA key fingerprint is 02:11:f2:db:ad:42:86:de:f3:10:9a:fa:41:2d:09:77.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'SERVER_IP' (RSA) to the list of known hosts.
Password:
--2010-03-14 12:27:06--  http://87.98.218.102/kvm.tgz
Connecting to 87.98.218.102:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4270825 (4.1M) [application/x-gzip]
Saving to: `STDOUT'

     0K .......... .......... .......... .......... ..........  1% 5.36M 1s
    50K .......... .......... .......... .......... ..........  2% 13.1M 1s
   100K .......... .......... .......... .......... ..........  3% 13.4M 0s
   150K .......... .......... .......... .......... ..........  4% 14.9M 0s
   200K .......... .......... .......... .......... ..........  5% 10.3M 0s
   250K .......... .......... .......... .......... ..........  7% 7.24M 0s
   300K .......... .......... .......... .......... ..........  8% 12.2M 0s
   350K .......... .......... .......... .......... ..........  9% 7.09M 0s
   400K .......... .......... .......... .......... .......... 10% 12.7M 0s
   450K .......... .......... .......... .......... .......... 11% 8.14M 0s
   500K .......... .......... .......... .......... .......... 13% 6.11M 0s
   550K .......... .......... .......... .......... .......... 14% 13.6M 0s
   600K .......... .......... .......... .......... .......... 15% 13.8M 0s
   650K .......... .......... .......... .......... .......... 16% 7.11M 0s
   700K .......... .......... .......... .......... .......... 17% 7.21M 0s
   750K .......... .......... .......... .......... .......... 19% 14.9M 0s
   800K .......... .......... .......... .......... .......... 20% 7.14M 0s
   850K .......... .......... .......... .......... .......... 21% 13.6M 0s
   900K .......... .......... .......... .......... .......... 22% 6.41M 0s
   950K .......... .......... .......... .......... .......... 23% 12.6M 0s
  1000K .......... .......... .......... .......... .......... 25% 7.46M 0s
  1050K .......... .......... .......... .......... .......... 26% 13.8M 0s
  1100K .......... .......... .......... .......... .......... 27% 6.92M 0s
  1150K .......... .......... .......... .......... .......... 28% 7.21M 0s
  1200K .......... .......... .......... .......... .......... 29% 14.3M 0s
  1250K .......... .......... .......... .......... .......... 31% 7.12M 0s
  1300K .......... .......... .......... .......... .......... 32% 11.6M 0s
  1350K .......... .......... .......... .......... .......... 33% 6.86M 0s
  1400K .......... .......... .......... .......... .......... 34% 13.5M 0s
  1450K .......... .......... .......... .......... .......... 35% 6.37M 0s
  1500K .......... .......... .......... .......... .......... 37% 7.60M 0s
  1550K .......... .......... .......... .......... .......... 38% 13.6M 0s
  1600K .......... .......... .......... .......... .......... 39% 7.15M 0s
  1650K .......... .......... .......... .......... .......... 40% 13.2M 0s
  1700K .......... .......... .......... .......... .......... 41% 7.08M 0s
  1750K .......... .......... .......... .......... .......... 43% 11.0M 0s
  1800K .......... .......... .......... .......... .......... 44% 5.36M 0s
  1850K .......... .......... .......... .......... .......... 45% 11.8M 0s
  1900K .......... .......... .......... .......... .......... 46% 6.21M 0s
  1950K .......... .......... .......... .......... .......... 47% 6.98M 0s
  2000K .......... .......... .......... .......... .......... 49% 13.3M 0s
  2050K .......... .......... .......... .......... .......... 50% 7.35M 0s
  2100K .......... .......... .......... .......... .......... 51% 13.8M 0s
  2150K .......... .......... .......... .......... .......... 52% 7.02M 0s
  2200K .......... .......... .......... .......... .......... 53% 13.6M 0s
  2250K .......... .......... .......... .......... .......... 55% 7.02M 0s
  2300K .......... .......... .......... .......... .......... 56% 5.67M 0s
  2350K .......... .......... .......... .......... .......... 57% 10.9M 0s
  2400K .......... .......... .......... .......... .......... 58% 5.71M 0s
  2450K .......... .......... .......... .......... .......... 59% 13.0M 0s
  2500K .......... .......... .......... .......... .......... 61% 7.02M 0s
  2550K .......... .......... .......... .......... .......... 62% 14.0M 0s
  2600K .......... .......... .......... .......... .......... 63% 6.86M 0s
  2650K .......... .......... .......... .......... .......... 64% 13.5M 0s
  2700K .......... .......... .......... .......... .......... 65% 7.01M 0s
  2750K .......... .......... .......... .......... .......... 67% 7.06M 0s
  2800K .......... .......... .......... .......... .......... 68% 13.6M 0s
  2850K .......... .......... .......... .......... .......... 69% 6.57M 0s
  2900K .......... .......... .......... .......... .......... 70% 11.0M 0s
  2950K .......... .......... .......... .......... .......... 71% 6.26M 0s
  3000K .......... .......... .......... .......... .......... 73% 14.4M 0s
  3050K .......... .......... .......... .......... .......... 74% 7.13M 0s
  3100K .......... .......... .......... .......... .......... 75% 7.02M 0s
  3150K .......... .......... .......... .......... .......... 76% 13.4M 0s
  3200K .......... .......... .......... .......... .......... 77% 7.34M 0s
  3250K .......... .......... .......... .......... .......... 79% 12.9M 0s
  3300K .......... .......... .......... .......... .......... 80% 7.47M 0s
  3350K .......... .......... .......... .......... .......... 81% 13.2M 0s
  3400K .......... .......... .......... .......... .......... 82% 5.11M 0s
  3450K .......... .......... .......... .......... .......... 83% 14.9M 0s
  3500K .......... .......... .......... .......... .......... 85% 5.25M 0s
  3550K .......... .......... .......... .......... .......... 86% 6.46M 0s
  3600K .......... .......... .......... .......... .......... 87% 14.0M 0s
  3650K .......... .......... .......... .......... .......... 88% 4.01M 0s
  3700K .......... .......... .......... .......... .......... 89% 12.9M 0s
  3750K .......... .......... .......... .......... .......... 91% 6.20M 0s
  3800K .......... .......... .......... .......... .......... 92% 5.34M 0s
  3850K .......... .......... .......... .......... .......... 93% 4.02M 0s
  3900K .......... .......... .......... .......... .......... 94% 6.20M 0s
  3950K .......... .......... .......... .......... .......... 95% 17.7M 0s
  4000K .......... .......... .......... .......... .......... 97% 12.4M 0s
  4050K .......... .......... .......... .......... .......... 98% 21.2M 0s
  4100K .......... .......... .......... .......... .......... 99% 14.1M 0s
  4150K .......... ..........                                 100%  171M=0.5s

2010-03-14 12:27:07 (8.52 MB/s) - `-' saved [4270825/4270825]

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
qemu: could not open disk image ftp://FTP_SERVER_IP/bootcd.iso: No such file or directory
root@rescue:~#

with putty running I'm starting RealVNC Viewer, trying to connect via:

localhost:5900

and getting:

failde to connect: COnnection refused (10061)

FTP is set to anonymous, ISO is downloadable through webbrowser.

[darkfyre]

It does not affect all servers, however those it does here is a temporary solution that should work:

1) run server in rescue-pro

2)
ssh YOUR-SERVER -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu /dev/sda -boot c -vnc 127.0.0.1:0'

or if host sys is 64bit

ssh YOUR-SERVER -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'

3) now use any vnc client and connect to localhost eg.

vncviewer localhost:5900

Also remember to keep the SSH Connection open.

Can confirm that this will not work if your rescue system is FreeBSD. however if you install any version of Linux (not unix) from the managerv3 then boot to rescue, this works fine.

[darkfyre]

never mind - sorted it now i think

home# ssh root@188.165.199.148 -L 5900:localhost:5900 'cd /tmp | wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C /tmp && /tmp/bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'


I had to change tar xzf - -C / to tar xzf - -C /tmp

[darkfyre]

What is the error if you just do:

ssh root@188.165.199.148 -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'

Length: 4,270,825 (4.1M) [application/x-gzip]

0K .......... .......... .......... .......... .......... 1% 7.48 MB/s
50K .......... ......bin/: Can't set user=0/group=0 for bin: Read-only file systemCan't update time for bin: Read-only file system
bin/qemu-nbd: Can't create 'bin/qemu-nbd': Read-only file system


and more errors like that, all complain about a read only file system.

[darkfyre]

thanks will test - I think i crashed my rescue system, it stopped responding, so I done a reboot via the managerv3 , still waiting on it coming back online :P

and thanks again for taking the time to come up with a temp fix for this, your time is appreciated

[Neil]

now that I think about it , none of this will allow an ISO to be mounted ? doh!

You can change '/dev/sda' to '-cdrom path/to/distro.iso' and '-boot c' to '-boot d'

Should be something like:
qemu-system-x86_64 /dev/sda -m 1024 -cdrom path/to/distro.iso -boot d -vnc 127.0.0.1:0

[darkfyre]

now that I think about it , none of this will allow an ISO to be mounted ? doh!

[darkfyre]

Will test just now,

"On iso image

An image will be loaded. You could use this option to carry out your own installation of the server"

sourced from http://help.ovh.co.uk/KvmWinSimple

Im just trying to carry out my own installation of the server as you suggest the vKVM can be used for. I know you say its not supported, but its a function of the vKVM and ive done it many times.. I dont need support, just for the vKVM to work so I can mount an ISO.

[Neil]

home# ssh root@188.165.199.148 -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | cd /tmp | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'
Password:
--11:21:51-- http://87.98.218.102/kvm.tgz
=> `-'
Connecting to 87.98.218.102:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4,270,825 (4.1M) [application/x-gzip]

0K 0% 0.00 B/s


Cannot write to `kvm.tgz' (Broken pipe).
home#



If I leave the cd /tmp part out .. i get this error:

share/qemu/keymaps/nl-be: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/nl-be': No such file or directory
share/qemu/keymaps/pt: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/pt': No such file or directory
share/qemu/keymaps/sl: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/sl': No such file or directory
share/qemu/keymaps/tr: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/tr': No such file or directory
tar: Error exit delayed from previous errors.

What is the error if you just do:

ssh root@188.165.199.148 -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'


Also I am unsure what you are trying to achieve with vKVM on FreeBSD?

[darkfyre]

home# ssh root@188.165.199.148 -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | cd /tmp | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'
Password:
--11:21:51-- http://87.98.218.102/kvm.tgz
=> `-'
Connecting to 87.98.218.102:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4,270,825 (4.1M) [application/x-gzip]

0K 0% 0.00 B/s


Cannot write to `kvm.tgz' (Broken pipe).
home#



If I leave the cd /tmp part out .. i get this error:

share/qemu/keymaps/nl-be: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/nl-be': No such file or directory
share/qemu/keymaps/pt: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/pt': No such file or directory
share/qemu/keymaps/sl: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/sl': No such file or directory
share/qemu/keymaps/tr: Failed to create dir 'share': No such file or directoryCan't create 'share/qemu/keymaps/tr': No such file or directory
tar: Error exit delayed from previous errors.

[Neil]

Thanks, however as its a read only file system I cant untar the kvm as the command suggests.

I tried to sort this by adding cd /tmp before the tar command, but the new error is:

Cannot write to `kvm.tgz' (Broken pipe).


Perhaps im missing something ?

Remember to do:

ssh root@YOUR-SERVER

The only error you should get is at the end:

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
Option 'ipv4': Use 'on' or 'off'
Failed to parse "yes" for "dummy.ipv4"

Then just leave it like this and open up VNC.

[darkfyre]

Thanks, however as its a read only file system I cant untar the kvm as the command suggests.

I tried to sort this by adding cd /tmp before the tar command, but the new error is:

Cannot write to `kvm.tgz' (Broken pipe).


Perhaps im missing something ?

[Neil]

It does not affect all servers, however those it does here is a temporary solution that should work:

1) run server in rescue-pro

2)
ssh YOUR-SERVER -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu /dev/sda -boot c -vnc 127.0.0.1:0'

or if host sys is 64bit

ssh YOUR-SERVER -L 5900:localhost:5900 'wget -O- http://87.98.218.102/kvm.tgz | tar xzf - -C / && /bin/qemu-system-x86_64 /dev/sda -boot c -vnc 127.0.0.1:0'

3) now use any vnc client and connect to localhost eg.

vncviewer localhost:5900

Also remember to keep the SSH Connection open.

[darkfyre]

Yup , I know .. so my question is valid ..

"why will OVH not look into it until 1 week" as Fozle said in this thread - its been offline for 7 days and OVH said they cant even look into whats causing the problem until next week - this is unacceptable, its a massive outage affecting all clients, so it should be a critical issue, not a look into in 1 weeks time issue.

[gangsta]

darkfyre read my first post about how vKVM is actually working... something goes wrong on their base server and your system can not be virtualized anymore. Moreover users on entire network are submitting problems with vKVM - not only here in UK, other countries as well - check forums.

[stalks]

The guy who designed the vKVM is probably on holiday =]

[darkfyre]

Im just going to repeat my question as you may have missed it due to the amount of posts in this thread:

If this is a problem affecting EVERY dedicated server customer and your entire network, plus it has already been broken for 6 (now 7) days .. why is it not a high priority fix ? Why is the delay 1 week before it can even be looked into ?

And - surly, based on these facts you can have it looked into now rather than a week later ?? after all its basically an outage of a paid service which will cost you reputation damage and compensation claims.


also - you say on the vKVM manual page that it can be used to install our own distro on our server - so its a documented feature of a service we pay for .. really guys, this should be a critical issue and something which you get fixed ASAP, not in 1 weeks time before you will even look into the problem .. how can you honestly justify that to us.

"On iso image

An image will be loaded. You could use this option to carry out your own installation of the server"

sourced from http://help.ovh.co.uk/KvmWinSimple

[Neil]

I can confirm that Kimsufi is affected as well.

Please, don't go offtopic anymore, but I'd like to tell you that real KVM on demand is nothing unusual. Plenty of datacenters (here in EU as well as US) offer this service free of charge e.g. for couple of hours. The point is that you actually don't need KVM for a whole month and pay really big fee like OVH wants. Most often you need it to quickly solve the problem or sth which may be done within hours, not days.

OK, let's back to the topic. The obvious thing wasn't answered:

Any compensation for a downtime of the included sevice?

We are aware other companies offer kvm for limited period but the idea of vkvm is that you can boot into it at anytime without the need to contact us, although it is designed accessing Windows Server and not 'really' designed for installation of Linux or using it to access Linux - which is what Rescue Mode is for.

Regarding compensation for vKVM, it is not covered in the SLA and its main feature is for Windows servers so it is something we can look at but first we must fix the issue with it.

[gangsta]

I can confirm that Kimsufi is affected as well.

Please, don't go offtopic anymore, but I'd like to tell you that real KVM on demand is nothing unusual. Plenty of datacenters (here in EU as well as US) offer this service free of charge e.g. for couple of hours. The point is that you actually don't need KVM for a whole month and pay really big fee like OVH wants. Most often you need it to quickly solve the problem or sth which may be done within hours, not days.

OK, let's back to the topic. The obvious thing wasn't answered:

Any compensation for a downtime of the included sevice?

[Razakel]

Im wondering something - is there anyone with a kimsufi who can test their vKVM ? Im wondering if its just ovh servers.

I had this problem yesterday evening with my Q-1T.

[YouWhat]

Im in middle of a OS reinstall at moment, but will do when it finished installing if nobody else has done so in mean time

[darkfyre]

Im wondering something - is there anyone with a kimsufi who can test their vKVM ? Im wondering if its just ovh servers.

[darkfyre]

Well, there is going to be some waiting with this issue afterall. The problem lies either in the kernel that is booted in vkvm mode or the applet configuration, but I can't get this addressed until next week at the earliest.

Hi

Out of interest, and this is a question I have been asked by my client.

If this is a problem affecting EVERY dedicated server customer and your entire network, plus it has already been broken for 6 days .. why is it not a high priority fix ? Why is the delay 1 week before it can even be looked into ?

[fozl]

sure, we will provide KVM for first installation free of charge.

Sounds like they're offering what the Manager v3 or MoM offers, except with Mv3/MoM you install as often as you want for no charge. But you must do what you beleive is right for you.

[darkfyre]

This issue annoyed me also - so i started looking for another provider for my client who needs a kvm.

Below is a reply from a company who will go the extra mile to provide customer service - a free KVM to install the OS of my choice.

I wont be renewing my clients dedicated server, I will be moving hosts because of this very important issue.


-------- Original Message --------
Subject: Re: Pre Sales Question
Date: Tue, 9 Mar 2010 14:15:52 +0100
From: info@netdirekt.de
Reply-To:
Organisation: netdirekt e.K.
To: Daniel Grant


Hello,

sure, we will provide KVM for first installation free of charge.

Mit freundlichen Grüßen / Best regards,
Wiethold Wagner

[gangsta]

Forget about free real KVM... that simply won't happen.
I doubt that any compensation will be given for inaccessibility of the service you're actually buying with your dedicated server and which is listed as INCLUDED on their website.
How may you refer to this?

Problem was submited on Thursday... so almost a week of downtime for me, and I'm saying it once again, downtime of the included sevice.

[fozl]

I just read your ticket, vKVM mode is for Windows systems, for linux and FreeBSD stuff you should use rescue mode: http://help.ovh.co.uk/RescueMode (the first part reffers to running hardware checks which can be used for all systems).

We don't offer support or compensation for the creative use of vKVM to do things like install other distros or operating systems etc, so trying to do that kind of thing is at your own risk.

When it is applied, compensation usually takes the form of an extended expirey date, but in some cases may be in Loyalty Points that can be applied to any order you want. There is currently an issue with using vKVM for it's intended use though, and that's what needs to be fixed.

[darkfyre]

Thanks for your reply.

Ive had an open ticket - 387460 since Friday .. its been marked as critical but ive got more information from you on this forum than in that ticket.

regarding access to a KVM for free or reduced price, is that something I can discuss with you or should I put it in the ticket (I dont like to put it in the ticket - because as you can see, they dont reply to me)

[fozl]

A good place to start would be to open a ticket so that there is a record of how long the issue has affected you. I offer no grounds for assumption on this thread, as I am pretty sure any compensation requests will be handled on a case by case basis.

[darkfyre]

I assume we will have credits added to our account due to the unavailability of services which we pay for ?

PS - Literally 2 minutes before you posted your reply, I sent an email to oles saying I would be informing our French business sales manager about the problem .. interesting that we now get a reply.

But as I understand it ..

downtime so far = 6 days
downtime before you can look into problem = 5 days

11 days minimum downtime. I simply cannot justify this to a client ... I dont know how anyone can.

Would it be possible to have a free KVM added to our servers while you correct this problem ?

[fozl]

Well, there is going to be some waiting with this issue afterall. The problem lies either in the kernel that is booted in vkvm mode or the applet configuration, but I can't get this addressed until next week at the earliest.

[stalks]

This is still yet to be fixed. What is going on?

[stalks]

Even attempting to boot from an ISO via FTP doesn't work. Its truly screwed.

Until this is fixed all our operations are on hold, most frustrating!

[gangsta]

Same issue on my end...
vKVM throws out "Network error: Connection reset"
It was tested on: Debian 5 and Ubuntu Desktop 8.04 - both installed from OVH manager.
I contacted support and at first they've been trying to persuade me that this is software problem and I need to solve this myself, but at least they believed me that this is not my fault and said that they're investigating this issue right now.

As far as I know vKVM working this way that at first the system is started on their base server and then your OS is virtualized.
So, most probably something has been changed/broken on the main server and that's why vKVM isn't working for all of us.

Waiting impatiently for a fix.

[darkfyre]

Thank you for saying your looking into it - i was under the impression that no one was and i still had to prove there was an issue .. i guess its a communication problem between myself and the support people.

ps - as you mentioned the back door - i sent an email to customerservice and opened a support ticket asking for a list of all changes, neither department could answer me.

the site you linked doesnt mention how you have installed a file to delete our files on every boot .. (if i write to /etc/motd) your scripts delete it and replace my data with your own .. other unauthorized cron jobs, changes to the kernel (ive made a thread about htis before), would be much better IMO if you just had a list of all changes, would allow myself to trust the OS you install. I give a full list of my findings to the customersupport@ovh email about a month ago. But the support staff simply replied in ticket that they could not find the patch which made these changes.. lol.

apologies for going OT, but the vKVM issue has been driving me mad, its the main attraction to OVh for me and i cant even get started on building a clean server. As I already said, I was under the impression that you didnt realise there was a problem .. but Fozle - thank you for saying what the french support team should have said last week :-)

[stalks]

Can you let us know when this is resolved?

[fozl]

Personally I use the vKVM for building fresh operating systems for my clients (due to the root back door and other undocumented software which is installed in your default versions).

You mean this undocumented back-door?
http://help.ovh.co.uk/InstallOvhKey

We're looking into this issue.

[darkfyre]

Hi

I have tried with both windows and UNIX.

But - i didnt think the OS mattered as the vKVM is just a version of VNC on a seperate kernel 'emulating a real kvm/ip'?

Thing is, its the java applet which wont load - you know when you click start server now, well the error I get is 'receive failed'.

Personally I use the vKVM for building fresh operating systems for my clients (due to the root back door and other undocumented software which is installed in your default versions).

Ive give the support staff a user/pass for my current vKVM so they can check - but no reply .. you are more than welcome to have a look also ?

But the fact that other customers have replied in this thread with the same problem - my simple reasoning says its a problem with the OVH network.

[fozl]

Are you all trying with Windows 2k8?

[darkfyre]

meh, vKVM still not working today

I really just wish the support staff would talk to me like a human being - I got a reply late last night and they asked me for more details about the problem and and error message.

All of that information was in my very first ticket :-S

[freshwire]

If you were wanting to install Ubuntu I just posted the remote install guide and need someone to test it out

http://forum.ovh.co.uk/showthread.php?p=28633

[IainK]

vKVM is broken for me too. Has been for days.

[yonatan]

some problems with netboot , i had a major issue with this also.
had to reformat my server to fix the issue i had :\

[freshwire]

It wasn't working last night.

[slacker]

vKVM isn't working for me either at the moment, same error as yours.
It used to work last time I tried.

[darkfyre]

Hi

Could I possibly ask for anyone with an OVH or Kimsufi server to test their vKVM.

When I reboot my server into vKVM mode and access the java applet, It just says connection failed to receive after I click 'boot from hard disk' - the exact same thing when I load an ISO. I have tested on 3 different PC's, so I know its not a java issue at my end.

When it worked fine (a week ago) - I would usually get a security warning, then access to a java applet which let me see the server etc etc ... now it just fails and wont let me use it.

Ive had a support ticket open as 'hardware unavailable' - but have yet to receive a reply.

Simply put - im wondering if its just my server which the vKVM isnt working for .. or is it a network thing ...

Anyone who wouldnt mind testing real quick and replying to this thread would be greatly appreciated