search for: vncconnect

Hi. I can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource...

...things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a reverse connection (the way the `vncviewer'' config option currently works) Signed-off-by: Don Dugger <donald.d.dugger@intel.com> -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Donal...

On 02/03/2015 11:19 AM, Jay Leafey wrote: > The documentation says that you can just put "vnc" (or > "vncconnect={host}") in the kickstart file in the command section and > proceed from there. Here's a link to an article in Red Hat Magazine > that has a pretty good overview: > >> http://www.redhat.com/magazine/024oct06/features/kickstart/ > > As usual, YMMV! OK, not QUITE that...

Is there a way to use kickstart to boot a machine into a manual setup process? Basically what I'm getting to is this, the machine doesn't not have a CD drive in it (nor can I add one), but I can boot it via kickstart. The install media is on the network. What I'd like to do is boot this machine up and rather than have kickstart do everything for me as far as installing the OS and

...e first one is the vnc connection. I''ve set everything up, but if i try to do a xm console XX, it says something about xenconsole tty file not found, and if i look up the qemu-dm-XXXX.log there is just one line that says : "/path/to/xen/bin/qemu-dm invalid option -- ''- vncconnect'' ". But vncconnect is installed, ive also installed all the dependencies. I am running Xen 3.0 on a debian system. I''ve just managed to run it by using SDL. But it seems to be a bit slow in transmitting the mouse movements. By earlier use of VNC, ive noticed its quite f...

Hi Folks, I'm interested in "headless" installation. If I use GRUB, then I provide arguments to the kernel of things like "headless vnc vncpassword=whoopie ip=dhcp" GRUB passes this on to ISOLinux, which manages the CD and subsequently the installation. Shouldn't I be able to do exactly the same thing with EXTLinux? I ask, because, as you might suspect, I

...into ioemu and the enable-ioemu-new patch changes the tools/Makefile to build ioemu-new instead of old ioemu. The enable-ioemu-new patch also includes changes to the tools to adjust the arguments passed to qemu (network device selection and vnc port selection). Known limitations: - No support for vncconnect - No support for summagraphics - SDL support not tested - No support for ia64 Major changes: - Doesn''t use libvncserver but uses the vnc support from qemu 0.8.1 - Includes usb support (same as backported to old ioemu recently) - Doesn''t include pcnet network driver but rtl8139 T...

...ll. There is a write-up in the RHEL installation guide on doing just that. You can either have the installer accept incoming VNC connections for the session or have it connect to a listening VNC client via boot arguments. The documentation says that you can just put "vnc" (or "vncconnect={host}") in the kickstart file in the command section and proceed from there. Here's a link to an article in Red Hat Magazine that has a pretty good overview: > http://www.redhat.com/magazine/024oct06/features/kickstart/ As usual, YMMV! -- Jay Leafey - jay.leafey at mindless.com M...

Proposed new page for comment: http://wiki.centos.org/TipsAndTricks/InstallFromGRUB Phil

...ts and a monitor of sorts so I can get to my menu select for remote vnc install. The install then proceeds and gets to setting up eth0, but fails. It seems like dhcp is not succeeding. If I boot from the standard FC10 CD, hdcp does work. Here is my append line: append initrd=initrd.img vnc vncconnect=10.8.6.15 headless ip=dhcp ksdevice=eth0 meth od=http://server.foo.com/fedora/10/os/i386 lang=en_US keymap=us All these commands are listed at: http://fedoraforum.org/forum/showthread.php?t=25826 Any pointers to where to get help on this?

Ben- I like the idea but I don''t understand how this patch can work: 1) You never put a name into `serial_devices[]'' for the summa port. The loop in `main'' that initializes the serial devices only calls `qemu_chr_open'' if there''s a string name in `serial_devices''. How did you get this to work? 2) Minor point, I don''t see the need