Re: [Fedora-xen] Update of dom0 posible?
Maximilian Freisinger [EMAIL PROTECTED] writes: Hello, as there is no dom0 support in FC9, i am about to use FC8 as dom0 with FC9 as domU. My question now is: If there should be an update for dom0 support in FC9, will it be possible to install a FC9 dom0 system and move all domUs to that system, on the same machine? My idea was to setup a functional dom0 and move all configs to that system, but as FC8 is xen 3.1.2 and anything else would at least be 3.2.x it would be interesting to know if a port is possible. dc The domU interface is supposed to be stable, so you should be able to do that. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] xen booting problem
swethu bandaru [EMAIL PROTECTED] writes: While booting XEN I amgetting an eror saying Kernel panic - not syncing:attempted to kill init! I am not getting what is the problem Most likely, the interesting error message is further up. Try giving us more context. I am using FC6 OS Can any one please suggest me Thank you FC-6 is no longer supported. You might be better off upgrading to something that is. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Serial console as well as serial access for apps
bcrawfo2 [EMAIL PROTECTED] writes: I have 2.6.18-53.1.14.el5xen on a box with an on-board serial port I want to use for console access to my dom0. I also have a 4 port serial card I want to use on the dom0 as well. I can configure one or the other...access to the console, or access to the 4 port serials. I can't figure out how to do both. When I get console to work, dmesg | grep ttyS only shows it binding to the virtual console...no others. You didn't tell us what exactly you did and how exactly it went wrong. [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Re: Fedora9 and HP ML350
[Quoting fixed] Alroger L. Gomes F. [EMAIL PROTECTED] writes: Daniel P. Berrange [EMAIL PROTECTED] writes: Xen Dom0 host is *NOT* supported in Fedora 9. Only DomU guest is supported. If you need dom0 host, stay on Fedora 8. Dan. Dan, what do you mean? You mean in this beta stage, or what? What about all the talks of bringing kernel-xen uptodate with the latest kernels and P2V tools? [...] F9 will not support Xen Dom0 when released. Whether we will be able to provide that support in a later update I can't say. Old kernels are unsupportable in F9, and splitting resources between more forward porting of the Xen kernel patches and the pvops kernel makes no sense; we'd get neither done. So we opted for getting pvops done, because when that's done it's *done*. Unfortunately, we couldn't get there in time for F9. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Newby Help
Walter Coole [EMAIL PROTECTED] writes: Thanks for the hint; sorry it took so long for me to try several different approaches. I hadn't tried virt-install; I had assumed that virt-manager's Create Wizard did the equivalent job. Uh, I must have somehow missed that you used virt-manager, not virt-install. Telling us exactly how you interact with either is fine. Telling us how you run virt-install is easier, though. Trying virt-install, this is what my session looked like: sudo virt-install -n hockey -r 256 -f /xen/fedora/hockey.img -s 4 --nographics --noautoconsole -l http://192.168.1.117/mirror/pub/fedora/linux/core/6/x86_64/os/ Password: This is an unusual image location. Is SELinux enabled? Does /var/lib/xen/images/hockey.img work? [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Problem with XEN
swethu bandaru [EMAIL PROTECTED] writes: Respected Sir, When we are trying to install a guest os by using xen in fedora6 I am using virt-install command and i have specified the following What is the name of the VM ?guest1 How much RAM should be allocated in MB ? 200 What would you like to use as the diskpath ? /home/xenbox.img This is an unusual location. Is SELinux enabled? Does /var/lib/xen/images/xenbox.img work? [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] After upgrade F7 to F8 vnc console no longer accessible {Scanned}
Christian Exner [EMAIL PROTECTED] writes: Hey list, after i upgraded my f7 xen host to f8 there is no way to access my vm's by vnc protocol (from Win workstation with UltraVNC Viewer). Something pops up and hide so quickly there is no chance to see what it is. virt-viewer also does not work. Have you filed a proper bug report for that? Steps to reproduce, actual results, expected results, ... [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Xen : virsh error
Quick sanity check: you are running the xen kernel, aren't you? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Guest Image File Size
Sadique Puthen [EMAIL PROTECTED] writes: Aaron Metzger wrote: virt-install has a checkbox which suggests that you can avoid preallocating the entire guest image size -- that the guest image file will grow on demand. Does this work for Xen or is it only supported for KVM and the QEMU COW files? yes, this works fine on xen. Until you run out of space in the filesystem containing the image file! Then the guest can't write any blocks that were previously left out of the image file, which leads to massive guest filesystem corruption and data loss. I use sparse image files all the time. But only for the throw-away domains I create for testing. [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] recompile for using sdl and vnc
mathieu rohon [EMAIL PROTECTED] writes: Hello, I'm using fedora 7 with xen 3.1 from binaries rpm. I try to use the sdl display, but when i configure my VM with *graphics type='sdl'/ * no window pops up. Thanks to goolgle, I've found someone how got the same issue, and it seems that qemu-dm was not compile whith sdl support. What is the best way to recompile qemu-dm whith sdl support? In fact, I'd like to have sdl for local display of my VM, and vnc for remote access to it. What configuration should I use to do so? Thanks Support for the SDL display in libvirt is incomplete[*]. You'd have to bypass libvirt to use it. Are you sure you really need SDL? It has a serious usability problem: if you close its window, the PV framebuffer backend terminates, and you have to reboot the guest to get another one[**]. Why can't you stick to VNC? It works fine locally. Sorry, I can't answer you question on qemu-dm. [*] https://bugzilla.redhat.com/show_bug.cgi?id=240233 [**] Actually, you can restart the backend by hand, if you know what you're doing. Cheesy hacks in the backend make this work. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Slightly off-topic question about Xen+LVM
Aaron Metzger [EMAIL PROTECTED] writes: Sam Folk-Williams wrote: Alternatively, is there any other reliable way to make a self-consistent copy of a running Xen virtual machine image for the case where the Xen virtual machine is held in a regular file system file? Is LVM my only option? For a single file you can just copy the file... with, say, cp or dd. Thanks for the reply, but I thought that this is not a valid thing to do for a RUNNING guest. I think that the file will be changing too rapidly (guest machine swap etc) to get a self-consistent copy using just cp or dd. Right? Right. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] multiple CD ISO image files with qemu-kvm and virt-manager on F7
Chris Young [EMAIL PROTECTED] writes: I can't seem to get access to the qemu monitor console to change the location of the cdrom and point it to the next iso image file using virt-manager. Ctrl-Alt-2 sends me to the serial0 console and Ctrl-Alt-3 sends me to the parallel0 console, both of which don't respond to keyboard events as far as I can tell. Is there any other way of connecting to the qemu monitor console? You might find this thread helpful: http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00437.html -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Making Xen Guest Console Bigger
Robert L Cochran [EMAIL PROTECTED] writes: I'm brand new to using Xen. I've just successfully installed Fedora 7 as a guest system named F7guest with 618 Mb of memory and approximately 35 Gb of disk space. How do I make the console bigger so that I can actually work on applications? The default console is way too small -- the whole desktop window is about 6X6 inches. I need the actual desktop and application windows to fill my 19 monitor and be resizeable for them to be any good to me. Assuming your talking about the graphical console (a.k.a. para-virtual framebuffer): sorry, that one isn't resizable, yet. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU
Brian McDonald [EMAIL PROTECTED] writes: I am having problems getting a fedora7 domu running under my Centos5 Dom0 (this is a centos5 server no graphical interface) I followed the same steps to created the fedora 7 domu as I have for creating the cenots5 domu that I have on the same box. I downloaded the vmlinux and initrd from here ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ images/xen/ Xm config: kernel = /boot/vmlinuz-f7xeninstall ramdisk = /boot/initrd-f7xeninstall extra = text ks=http://www.mcdees-specialties.com/fed7/minimal-ks.cf; name = fed7 memory = 230 disk = [ 'tap:aio:/var/lib/xen/images/fed7.img,xvda,w', ] #vif = [ '', ] vif = [ 'bridge=xenbr0', ] ip = 192.168.1.202 netmask = 255.255.255.0 gateway = 192.168.1.1 vcpus=1 on_reboot = 'destroy' on_crash = 'destroy' When I run xm create -c fed7inst it gets to here and stops . Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Any and all ideas are welcome How exactly do you start your guest? What does starting your guest write to /var/log/xen/ and xm dmesg ? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU
Brian McDonald [EMAIL PROTECTED] writes: I am having problems getting a fedora7 domu running under my Centos5 Dom0 (this is a centos5 server no graphical interface) I followed the same steps to created the fedora 7 domu as I have for creating the cenots5 domu that I have on the same box. I downloaded the vmlinux and initrd from here ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ images/xen/ Wait a sec! You simply plunked kernel initrd into your /boot? That bypasses the scripts in the rpms, and you know, those are there for a reason. Can you try installing kernel-xen with yum? [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU
Brian McDonald [EMAIL PROTECTED] writes: -Original Message- From: Markus Armbruster [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 06, 2007 1:51 PM To: Brian McDonald Cc: fedora-xen@redhat.com Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU Brian McDonald [EMAIL PROTECTED] writes: I am having problems getting a fedora7 domu running under my Centos5 Dom0 (this is a centos5 server no graphical interface) I followed the same steps to created the fedora 7 domu as I have for creating the cenots5 domu that I have on the same box. I downloaded the vmlinux and initrd from here ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ images/xen/ Wait a sec! You simply plunked kernel initrd into your /boot? That bypasses the scripts in the rpms, and you know, those are there for a reason. Can you try installing kernel-xen with yum? You can not use yum if the operating system is not installed in the domU This is a centos5 server that I am trying to load a fedora7 domU Why can't you simply create the guest with virt-install? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Why I can't save and restore domU.
Àü»óÀÏ [EMAIL PROTECTED] writes: I successed save/restore and migrate the virtual machine of gui. Do you mean that migration worked, but the framebuffer didn't come up correctly? Migration and save/restore worked. Again: what does migration write to your dom0's /var/log/xen/? Attach [...] Your logs show more than just the save/restore, which makes it a bit difficult to find the relevant bits. I believe you saved domid 3, and it became domid 4 on restore. Output of xenstore-ls before save and after restore? Any xen-vncfb processes running before save and after restore? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] fc5 domU on rhel5 dom0
Paul Wouters [EMAIL PROTECTED] writes: On Sat, 21 Apr 2007, Markus Armbruster wrote: So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great.. I update my domUs by running rpm (actually yum) in the domU. Works fine for me. That only works for xen aware OS'es. It won't work to run FC/RHEL 3/4. I'm confused. We're talking about para-virtual guests, aren't we? How can you use an OS that is not `xen aware' in a para-virtual guest? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] fc5 domU on rhel5 dom0
Robert Story [EMAIL PROTECTED] writes: Hi, Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been Doesn't virt-install just work? struggling with it all morning. I'm stuck at: --- config --- memory = 1024 disk = [ 'phy:/dev/x/aaa,xvda,w' ] vif = [ 'mac=00:aa:bb:cc:dd:ee' ] uuid = ---- bootloader=/usr/bin/pygrub --- end --- --- domU grub --- title Fedora Core (2.6.20-1.2307.fc5xen) root (hd0,0) kernel /vmlinuz-2.6.20-1.2307.fc5xen ro root=/dev/gui/r rhgb quiet initrd /initrd-2.6.20-1.2307.fc5xen-blk.img --- end --- (Original domU was using fc5xenU kernel/initrd, but google told me I needed this PAE kernel. It fixed the PAE errors I was getting in xend-debug initially.) --- stdout --- Going to boot Fedora Core (2.6.20-1.2307.fc5xen) kernel: /vmlinuz-2.6.20-1.2307.fc5xen initrd: /initrd-2.6.20-1.2307.fc5xen-rs.img Started domain gui PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. i8042.c: No controller found. Red Hat nash version 5.0.32 starting mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! --- end --- --- xend-debug.log --- DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' --- end --- Based on some googling, I made a custom initrd image with '--with xenblk --preload xenblk', but it didn't help any.. Any hints greatly appreciated... How did you install the PAE kernel? With rpm in the domU? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] fc5 domU on rhel5 dom0
Robert Story [EMAIL PROTECTED] writes: On Fri, 20 Apr 2007 17:28:42 +0200 Markus wrote: MA Robert Story [EMAIL PROTECTED] writes: MA Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been MA MA Doesn't virt-install just work? I'm trying to get an existing domU from fc5 to load on rhel, not create a new one. MA Based on some googling, I made a custom initrd image with '--with xenblk MA --preload xenblk', but it didn't help any.. Any hints greatly appreciated... MA MA How did you install the PAE kernel? With rpm in the domU? I mounted the domU fs in the dom0, copied in the rpm, did a chroot, and rpm -i. I finally got it working... turns out that the chroot was the problem.. once I did the mkinitrd w/out the chroot (pointed at the domU fstab), things started going a lot more smoothly... So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great.. I update my domUs by running rpm (actually yum) in the domU. Works fine for me. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Problem about guest virtual machine creation
[EMAIL PROTECTED] writes: [...] Or currently we are not allowed to create a virtual machine inside another VM. The only possible way to create guest VM is to create it inside a physical machine, not VM? Correct. [...] -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Running Xen on low spec single CPU
Adrian Revill [EMAIL PROTECTED] writes: I know a lot of people just see Xen as a method to use over spec'd boxes more efficiently, but im interested in using its virtulisation capabilities on low spec systems. Has any one had any luck with getting a DomU running on a single CPU. I seem to get stuck during the install, as far as i can see it seems that the DomU is not being allocated CPU time. Using Fedora 6, i can get through the anaconda stage in about 1/2 hr but when the X window starts the CPU use drops to near 0% and i never get past a black screen with the X cursor. Shot from the hip: how much physical RAM? How much memory allocated to the domU? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] Re: gui console unavailable after upgrade
Robert Thiem [EMAIL PROTECTED] writes: I am just learning how to use xen. I installed a fc6 virtual machine and everything went okay. After the install I was able to start the virtual machine and use the gui console to log in. ... I don't see any new entries in the xend-debug.log I had a similar problem that's mysteriously rectified itself today. Anyway, when you have a guest running you should see (on the host, Dom0): [EMAIL PROTECTED] ~]# netstat -antp | grep xen tcp0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4350/xen-vncfb tcp0 0 127.0.0.1:5900 127.0.0.1:36614 ESTABLISHED 4350/xen-vncfb [EMAIL PROTECTED] ~]# netstat -antp | grep python tcp0 0 127.0.0.1:36614 127.0.0.1:5900 ESTABLISHED 4555/python This is (I believe) the xen virtual framebuffer serving on port 5900 and the client python console connecting to it (if a console is running). Correct. Checking that this xen-vncfb is running on the host is a good start. I'm pretty sure that it wasn't when my console wasn't working, but you might not be having the same issue. In case my checking today actually did something here's what I can remember doing since it wasn't working. yum update Reboot with SELinux in permissive mode (which didn't show up anything obviously wrong audit wise, but the console was working) Reboot with SELinux in enforcing mode (console still working) Robert Thiem I figure restarting xend did the trick. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Re: [Fedora-xen] gui console unavailable after upgrade
Daryl Daly [EMAIL PROTECTED] writes: On Fri, February 23, 2007 1:47 pm, Markus Armbruster wrote: Fully virtual or paravirtual? paravirtual Did you upgrade dom0 as well? Hmmm... I am not sure of the terminology here. I assume that dom0 is the host OS (the host that the virtual machine was created and is running on). If that assumption is correct then yes it was updated as well. Good. The virtual framebuffer protocol recently changed from a preliminary version to the final version. The new backend (running in dom0, what you call host) is backward compatible: it can cope with new and old domU (what you may call guest). Old backend with new frontend doesn't work, though. Your update of dom0 should have gotten you the new backend. Weird. Does restarting xend help? If not, what's new in /var/log/xen/* ? -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
