kvm guest problem

[natxo]

hi,

yesterday I installed your system on a proliant ml110 g5 (no hardware raid) and I am liking it a lot. Installing from iso or template works as expected. Now I want to install a xp pro vm. I have a cdrom and that's when my problems begin

I create a vm choosing:

1. type: fully virtualized kvm
2. installation media: cdrom
3. guest type: windows xp
4. netwok type: bridged ethernet (tap)
5. network card: rtl8139

I see this confirming the action:
/usr/bin/pvectl qmcreate 102 --mem 512 --disk 10 --onboot yes --name vmxp2 --cdrom cdrom --network model=rtl8139,tap --disktype ide --ostype wxp
Formatting '/var/lib/vz/images/vm-102-default.qcow2', fmt=qcow2, size=10485760 kB
VM 102 created
Then I go back to the list of virtual machines and boot it. I see the cpu pike to 99%; I try logging in the console but I get an start applet not initialized message (I can use java applicaties without problems in my browser, jre is installed and works);

in the host I get this in syslog:

May 17 15:05:18 hpxen pvedaemon[3923]: creating new VM 102 on node 0 (localhost)
May 17 15:05:18 hpxen pvedaemon[3923]: VM 102 created
May 17 15:06:24 hpxen pvedaemon[3937]: starting VM 102 on node 0 (localhost)
May 17 15:06:24 hpxen qemuserver[2429]: Starting VM 102
May 17 15:06:24 hpxen kernel: device tap0 entered promiscuous mode
May 17 15:06:24 hpxen kernel: audit(1211029584.860:5): dev=tap0 prom=256 old_prom=0 auid=4294967295
May 17 15:06:24 hpxen kernel: vmbr0: port 2(tap0) entering learning state
May 17 15:06:25 hpxen pvedaemon[3937]: VM 102 started
May 17 15:06:35 hpxen kernel: tap0: no IPv6 routers present
May 17 15:06:39 hpxen kernel: vmbr0: topology change detected, propagating
May 17 15:06:39 hpxen kernel: vmbr0: port 2(tap0) entering forwarding state
May 17 15:06:57 hpxen kernel: apic write: bad size=1 fee00030
May 17 15:06:57 hpxen kernel: Ignoring de-assert INIT to vcpu 0
May 17 15:06:57 hpxen kernel: Ignoring de-assert INIT to vcpu 0
May 17 15:07:41 hpxen pvedaemon[3969]: starting vnc proxy UPID:3969:1211029661:vncproxy:0:102:root:5900:97GkHuuPfO15C4L4A2PgkvzO2mI
May 17 15:07:41 hpxen pvedaemon[3969]: CMD: /bin/nc -l -p 5900 -w 30 -c /usr/sbin/qm vncproxy 102 97GkHuuPfO15C4L4A2PgkvzO2mI
May 17 15:08:11 hpxen pvedaemon[3969]: VM 102 vnc proxy failed - 256

If I shutdown the vm i cannot boot it again. This is reproducible.

Any ideas?

 

[natxo]

wtf???

I tried with another pc and another jre and now it works ...

So do not try this with a stock fedora9 install, the vnc applet will not work then.

 

[tom]

I tried with another pc and another jre and now it works ...

So do not try this with a stock fedora9 install, the vnc applet will not work then.

hi,

please note: ONLY the sun-java browser plugin works with Proxmox VE web interface.

currently there is NO sun-java browser plugin available for amd64 but I hope this will change soon.

there are some ways to install a 32-bit browser on a 64-bit system in order to run 32-bit browser plugins, but this is not an easy way. For desktop systems, I suggest using 32-bit to avoid this (and many other) browser plugin issues.

 

[alphadog]

Is this still an issue?

I have installed PVE v1.0 on a server and fired off my first KVM VM to install Windows 2008 Server.

When I try to get a VNC console off the web interface, it fails when I use my main workstation, which is JRE 1.6.0_07 on Vista 64.

Can I use an alternate VNC client, such as RealVNC? If so, how?

 

[alphadog]

Nevermind. While it didn't work the first time around, a restart of FF3 seems to have allowed the VncViewer applet to start properly this time.