http://permalink.gmane.org/gmane.comp.emulators.xen.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.emulators.xen.user/74288 <pre>Hi, I've made some draft for helping distro packagers with knowing if they made something that actually works. I wonder if we (xen.org...?) could offer a xen host that does regression testing for domU distros. Odd idea? The doc: http://confluence.wartungsfenster.de/display/Adminspace/Xen+domU+functions+checklist Just typed it in my own wiki for lazyness. I'll try to be around on monday and pull it over to Xen wiki. It's a holiday here, too, but I admit I asked for a doc day that is not on a working day. :) Greetings, and happy celebrations Florian </pre> Florian Heigl 2012-05-25T21:58:28 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74287 <pre> Keep in mind that in US that is Memorial day so pretty much everybody in US is going BBQ-ing and such. </pre> Konrad Rzeszutek Wilk 2012-05-25T21:12:35 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74286 <pre>Hi, everybody. A quick reminder that the next Xen DocumentDayis happening next Monday. More info on document days at http://wiki.xen.org/wiki/Xen_Document_Days Hope to see you on IRC! Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. Best Regards Lars ********************* * Xen Document Days * ********************* We have another Xen document day come up next Monday. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO &lt;http://wiki.xen.org/wiki/Xen_Document_Days/TODO&gt;). Of course, you can work on anything you like: the list just provides s</pre> Lars Kurth 2012-05-25T21:13:23 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74285 <pre> I mean exactly - connect directly to the guest machine. Run whatever software your (unspecified) guest OS needs in order to provide it's own GUI via &lt;your choice of remote viewer&gt;. For Linux, you can setup an X server to provide a VNC connection. For Windows you'd be better with Remote Desktop than VNC - it passes display primitives (eg "draw a rectangle") rather than passing a bitmap of the result, and works very well with less bandwidth. In both cases you'll have remote access to the machine once it has booted. Getting access to a booting machine will require you to use the VNC (or text) console provided by the host. Personally, for a Linux guest I'd not run a graphical console. I'd use a text based console. </pre> Simon Hobson 2012-05-25T20:06:48 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74284 <pre>OS X uses "ScreenSharing" for VNC connections, pretty sure it's closed source, so I can't really open it up to find out how they make it work. If anyone has any ideas I'd be willing to look into them. On Fri, May 25, 2012 at 3:55 PM, Andrew Bobulsky &lt;rulerof&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Casey DeLorme 2012-05-25T20:25:49 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74283 <pre>Yes i agree with you as well, that however it is setup on a Mac OS X is quite puzzling and can't imagine how they have it implanted. I am pretty much looking for what Casey has setup using Mac OS X, but as i don't have such a computer, i am relying on a different set of programs. That is why i was thinking it was some settings somewhere that is resetting the connection to the VNC client each time you do certain things on the VM and yes it has disconnected on me a few times for resolution changes, but mostly during reboots. My next trial session was to try different VNC programs, such as UltraVNC, RealVNC, and many others out there and see if they all share the same behavior and since UltraVNC does the same thing, i guess i can skip that one...lol. I have even tried "gvncviewer" on Debian running on the same Dom0 that is running Xen as loopback, AND even that one resets a lot. </pre> cyberhawk001< at >gmail.com 2012-05-25T20:23:39 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74282 <pre>Hello, Just thought I'd chime in. I use UltraVNC on Windows to connect to the DomU, and it doesn't have any issues with resolution changes. I got into UltraVNC because it's open source and supports AD authentication and various encryption methods. It does, however, require a reconnect after DomU reboots. I had thought that this was a side effect of the DomU ID changing upon reboot, something with Xen stopping the VNC server and then bringing up a new one.... but Casey's note here about the OS X VNC viewer seems to indicate otherwise :) Cheers, Andrew Bobulsy On Fri, May 25, 2012 at 2:27 PM, Shane Johnson &lt;sdj&lt; at &gt;rasmussenequipment.com&gt; wrote: </pre> Andrew Bobulsky 2012-05-25T19:55:58 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74281 <pre>I use the VNC option on all my HVM DomU's but I still have to do xm vncviewer {host} everytime the resolution changes. which is a pain but I can still see the entire boot process.I will usually have 3-5 run command windows open so once it crashes, I can immediately open the new connection to the DomU.  I have only use the console option on a PV domain for boot debugging because once the DomU is fully booted, the console stops responding - I don't know if this is the way it's supposed to work, but it's how mine does. Shane On Fri, May 25, 2012 at 11:49 AM, &lt;cyberhawk001&lt; at &gt;gmail.com&gt; wrote: -- Shane D. Johnson IT Administrator Rasmussen Equipment </pre> Shane Johnson 2012-05-25T18:27:14 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74280 <pre>------------- ------------- ------------- What do you mean by "connect to the guest machine itself"? By guest machine you mean the Guest VM (aka DomU), or you mean the Host Machine (aka host server or Dom0)? I was really hoping not have to try things like trying to write my own proxy server and etc. But, I have also heard about a "reverse vnc" and i think it could be what TightVNC calls a "listening" mode that you can select when you run the VNC Client. I guess most VNC clients have this option, BUT not figured out how it even works or how to use it yet. I guess one option would be something like what is written here http://www.realvnc.com/products/viewerplus/index.html This VNC client uses the Intel Active Management Technology (AMT 6.0+) that is located on some Intel motherboards that, as the article states, "...enabling permanent remote access and control...". But, that is just one option if you have that type of motherboard. I was also looking in the "*xl*" command man page, and under in</pre> cyberhawk001< at >gmail.com 2012-05-25T17:49:03 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74279 <pre>Dear all, I have a PCIe device driver that I have been using on various Linux distributions and Kernel versions (2.6.x - 3.x.y) successfully all along. I recently set up a Xen environment with Linux Mint 12 and Xen Hypervisor 4.1. When I boot to Linux Mint, my driver still load (via insmod manually) successfully at Dom0 without any issue. I can do reads and write to the hardware device. But once booted to Xen, the driver failed to complete the driver load (via insmod manually) at Dom 0 and the console just hangs. From my debug messages, it appears it hangs because the driver doesn't receive any interrupt after a command is sent to the hardware device by writing a parameter to the mapped register. Once that register is written, the device is expected to DMA the command from the buffer allocated by the driver. The things that I can only think of that might have caused the problem are 1) IRQ mapping issue, or 2) DMA mapping issue, which I am not sure. What the driver does: Set up a command buffer: Bu</pre> Kenneth Wong 2012-05-23T23:40:08 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74278 <pre> Yes. HVM Linux for most workloads is actualy faster than PV one. I've done benchmarks a while ago on a decent hardware (Xeon 56xx, EPT, lots of optimizaton for VMENTRY / VMEXIT, etc). Look for what VMware has been doing from a long time - it has switched every x86_64/AMD64 guest to hardware virtualization (there's a paper about that that shows what they use for which kind of guest). PV still has its place in some specific workloads, but the tendency is now reversed. </pre> Michał Purzyński 2012-05-24T09:09:46 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74277 <pre>Cool. Stay tuned fo FC17 (still with Xen support, of course), which is coming! They are, indeed. Well, the one with 'syms' in it should be related to the possibility of booting with a version of the hypervisor compiled with debugging symbols, so better to avoid it, although it would still work like all the others. The fact that they are so much it's an actual bug, which has been worked out (IIRC) for Fedora 17. Nothing that is worth worrying about. I guess it's something related to packaging or, in general, not compiling from an actual hg tree. In virt-manager you mean, right? I'm seeing this too, but I'm not sure what "copying host CPU" is (and if it means something at all), so I never cared. Thanks and Regards, Dario </pre> Dario Faggioli 2012-05-25T14:15:06 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74276 <pre> Hi, I installed xen using yum in fedora 16. When I boot grub shows me a lot xen botting options. Are the all same or have different funtionality? also in xl info I have xen_changeset : unavailable, what does it mean? I also can not copy host CPU configuration in guest, it gives Error copying host CPU: No host CPU reported in capabilities Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 1779, in config_cpu_copy_host CPU.copy_host_cpu() File "/usr/lib/python2.7/site-packages/virtinst/CPU.py", line 185, in copy_host_cpu raise ValueError(_("No host CPU reported in capabilities")) ValueError: No host CPU reported in capabilities Regards, Arindam _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Arindam Choudhury 2012-05-25T11:06:08 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74275 <pre> ... Would it be better to connect to the guest machine itself ? Ie set up the machine to run a shared virtual desktop rather than the virtual console display ? That way, you never need to know where the guest is (ie which host it's on, or which port it's console is on), you just connect to it's IP address and it'll just work (as long as it's actually up at the time). </pre> Simon Hobson 2012-05-25T07:05:20 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74274 <pre>Hello James, On Thu, May 24, 2012 at 6:25 PM, James Harper &lt;james.harper&lt; at &gt;bendigoit.com.au&gt; wrote: Heh, I remember I tried the Citrix drivers on Xen a while back... that didn't go well :D While GPLPV seemed to work pretty well with my Xen guests, it invariably caused a BSOD on atimkpag.sys (I think that's the spelling) when I passed my Radeon 5850 through with IOMMU. I really wish I knew why, especially because it seems to work very well for Casey, albeit on an Intel setup with a Radeon 6XXX model card. If you'd like, I can offer my time and/or access to my hardware to help debug the issue, but would definitely need some direction on exactly what to do :P Cheers, Andrew Bobulsky </pre> Andrew Bobulsky 2012-05-25T00:14:35 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74273 <pre> And if you run more than one set of firewall rules on a per-VM basis, iptables -I FORWARD -m physdev --physdev-in $IF_IN --dst $VM_IP -j $RULENAME --Andy _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Andrew Finkenstadt 2012-05-24T23:23:12 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74272 <pre> If they were running the Citrix branded Xen product then Citrix's own drivers would be the obvious choice. In what way is GPLPV letting you down? You asked about USB a while back... I've made some progress there but it's still very much a work in progress. Thanks James </pre> James Harper 2012-05-24T22:25:44 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74271 <pre> I was actually looking into this a little while back. One thing I decided though was that qemu would need to make a 'reverse vnc' connection so that it connects to the proxy as the server, which would remove the need for the proxy to poll the server (or even know which physical server IP the client was running on). For some reason though, qemu has its own implementation of vnc rather than using libvnc (or whatever it is called), so this change is more than a one-liner, although maybe still not that difficult. I also can't remember how the password authentication works in the reverse connection mode... ideally the client and server would have to authenticate with each other but having the server authenticate to the proxy would be sufficient. Anything else would be a security hole. The other advantage of this for me is that in a cluster of physical machines where the VM's float around depending on load etc, they all still just connect to the same proxy. James </pre> James Harper 2012-05-24T22:22:40 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74270 <pre>From my experiences it has nothing to do with the Server side of the connection. Gnome VNC Viewer (gvncviewer) and OS X ScreenSharing do not crash on window resize, the built in and xtightvncviewer seem to however. Also, OS X Screen Sharing (launched from terminal "open vnc://ip:display") requires the server to be up to establish the first connection, but afterwards I can reboot the virtual machine as many times as I want and the VNC Client Window remains open throughout the entire process. To me this either means many of the VNC Clients lack in functionality, or haven't well documented these features. ~Casey On Thu, May 24, 2012 at 5:02 PM, John Sherwood &lt;jrs&lt; at &gt;vt.edu&gt; wrote: _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Casey DeLorme 2012-05-24T21:42:21 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74269 <pre>I think your best bet would be to write a proxy server that keeps the VNC client's connection open and periodically attempts to reconnect to the VNC server when the server goes down. The VNC protocol is actually really simple, so you could probably implement one without that much difficulty. On Thu, May 24, 2012 at 4:54 PM, &lt;cyberhawk001&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> John Sherwood 2012-05-24T21:02:45 http://permalink.gmane.org/gmane.comp.emulators.xen.user/74268 <pre>From what I have seen - it's a limitation of VNC with resolution changes. I see the same behavior if I resize a Windows desktop. I've never found a way to circumvent it. Shane On Thu, May 24, 2012 at 2:54 PM, &lt;cyberhawk001&lt; at &gt;gmail.com&gt; wrote: </pre> Shane Johnson 2012-05-24T20:58:55 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.emulators.xen.user