Proxmox console and New version of Java for OSX

[Guy]

I've just upgraded my OSX desktop to the latest version of Java that Apple released last night. It now seems that I'm no longer able to run the Java console on my proxmox systems!

I just get the read "!" in the middle of the screen.

--Guy

 

[Algon]

I see the same here, pls. find a solution asap, as I need access to the virtual machines

mvh
Niels

 

[rugby]

I just connected to my PVE install with a Macbook pro running 10.6.4 and the java update using Safari and I can open the VM remote VNC windows.

 

[Guy]

really?

can you confirm the version of JAVA that your Mac is running? I wonder if you've also installed a different version of Java and some other point?

I've updated several Macs today to the New version of Java and none of them are able to get to the consoles of proxmox VMs now.

---Guy

 

[rugby]

 

[Guy]

Ok well I'm stumpted... Why does it work for you but not for me on my 6 macs..all running snow leopard and had the java update from apple!!

 

[rugby]

There was another java issue that came up with Macs that I applied a patch on PVE for. I'm trying to search on it but can't find it in the forum for some reason. Maybe that's the difference?

 

[Algon]

hello,
the automatic update did not work for me, but by getting the update from Apple homepage and apply it maunally it works
mvh
Niels

 

[Guy]

Doh!!!... simple solution...quit and restart Safari after you've installed the update!

 

[Lokytech]

Java Version: 1.6.0_22 x86_64

VNC Console :
- SAFARI : OK
- CHROME / CHROMIUM : OK with modifications

Edit : /usr/share/pve-manager/root/qemu/vnc-direct.htm
and just after :

Line 36 :  function wresize() {

Add this :

try {
        var domain1:String = LoaderInfo(this.root.loaderInfo).parameters["allow"];
        if ( domain1.length > 0 ) {
                Security.allowDomain(domain1);
        }
} catch (error:Error) { }
try {
        var domain2:String = LoaderInfo(this.root.loaderInfo).parameters["allowhttps"];
        if ( domain2.length > 0 ) {
                Security.allowInsecureDomain(domain2);
        }
} catch (error:Error) { }

And to correct the Safari size bug, in the same file, change :

$out .= "<APPLET id=vncapp CODE='VncViewer.class' ARCHIVE='/vncterm/VncViewer.jar' width=640 height=480 vspace=0 hspace=0>\n";

to :

$out .= "<APPLET id=vncapp CODE='VncViewer.class' ARCHIVE='/vncterm/VncViewer.jar' width=800 height=600 vspace=0 hspace=0>\n";

Enjoy

 

[Guy]

ok how do we get those changes into the product for others to benefit?!

 

[tom]

we will take a look on it but we cannot test as we got no apple hardware here.

I am always asking if someone sponsors a macbook pro to our testlab - but till now no one contacted me.

 

[Guy]

plenty of us in the field will help with the testing

 

[tom]

plenty of us in the field will help with the testing

yes, I appreciate that. but you asked how to improve the mac support and I give the quite simple answer

 

[Lokytech]

I see you coming tom

You gave a simple self-interested answer

I would also like my boss to buy me a Macbook pro but ... the only one i have is mine

Btw tom, feel free to ask me if you need a tester.

 

[jlribeirof]

Hi,

any news about the Java and VNC console problem?
I´m no longer able to use the VNC console from Explorer or Chrome since the last Java update.
I tried with Windows XP and Vista as well.

 

[tom]

you talk about which problem? we have no issues with IE or firefox here.

 

[Lokytech]

Apply again the same modifications as my last post. The problem comes from the cross-domain calls.