January 2014 - openSUSE Virtual - openSUSE Mailing Lists

[opensuse-virtual] xen - anyone using pypxeboot as bootloader?
by Per Jessen 31 Jan '14

31 Jan '14

I'm trying to set up a DomU with pypxeboot with the following: bootloader= "/usr/lib64/xen/bin/pypxeboot" bootloader_args= ['mac=11:22:33:00:01:0f'] When I do "xl create config", all I get is the usage() output from pypxeboot :-( All hints appreciated. -- Per Jessen, Zürich (-0.1°C) http://www.dns24.ch/ - your free DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

[opensuse-virtual] Issues building Xen on ARM
by Andrew Wafaa 24 Jan '14

24 Jan '14

Hi, I'm trying to package Xen for both armv7l and aarch64 architectures, and have managed to fix a couple of issues (max_cpu differes on ARM to x86 and xenalyze is x86 specific). Problem is I'm now stuck at the install stage. The current error I'm getting is: [ 597s] install -m0644 -p /home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen/xen-syms /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/boot/xen-syms-4.4.0_02-0 [ 598s] if [ -r /home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen/xen.efi -a -n '' ]; then \ [ 598s] [ -d /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm ] || install -d -m0755 -p /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm; \ [ 598s] install -m0644 -p /home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen/xen.efi /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/xen-4.4.0_02-0.efi; \ [ 598s] ln -sf xen-4.4.0_02-0.efi /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/xen-4.4.efi; \ [ 598s] ln -sf xen-4.4.0_02-0.efi /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/xen-4.efi; \ [ 598s] ln -sf xen-4.4.0_02-0.efi /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/xen.efi; \ [ 598s] if [ -n '/boot/efi' -a -n '' ]; then \ [ 598s] install -m0644 -p /home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen/xen.efi /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/boot/efi/efi//xen-4.4.0_02-0.efi; \ [ 598s] elif [ "/home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm" = "/home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm" ]; then \ [ 598s] echo 'EFI installation only partially done (EFI_VENDOR not set)' >&2; \ [ 598s] fi; \ [ 598s] fi [ 598s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen' [ 598s] make: Leaving directory '/home/abuild/rpmbuild/BUILD/xen-4.4.0-testing/xen' [ 598s] + install_xen [ 598s] + local ext= [ 598s] + '[' -n '' ']' [ 598s] + rm /home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/boot/xen-4.4.gz [ 598s] rm: cannot remove '/home/abuild/rpmbuild/BUILDROOT/xen-4.4.0_02-0.arm/boot/xen-4.4.gz': No such file or directory Looking at the spec file, the section in question has: %ifarch x86_64 %arm aarch64 make -C xen install \ %if %{?with_gcc46}0 CC=gcc-4.6 \ %endif max_phys_cpus=%{max_cpus} debug=n crash_debug=n DESTDIR=$RPM_BUILD_ROOT %{?_smp_mflags} make -C xen clean install_xen() { local ext="" if [ -n "$1" ]; then ext="-$1" mv $RPM_BUILD_ROOT/boot/xen-%{version}-%{release}.gz \ $RPM_BUILD_ROOT/boot/xen${ext}-%{version}-%{release}.gz mv $RPM_BUILD_ROOT/boot/xen-syms-%{version}-%{release} \ $RPM_BUILD_ROOT/boot/xen-syms${ext}-%{version}-%{release} fi rm $RPM_BUILD_ROOT/boot/xen-%{xvers}.gz rm $RPM_BUILD_ROOT/boot/xen-%{xvermaj}.gz rm $RPM_BUILD_ROOT/boot/xen.gz # Do not link to links; grub cannot follow. ln -s xen${ext}-%{version}-%{release}.gz $RPM_BUILD_ROOT/boot/xen${ext}-%{xvers}.gz ln -s xen${ext}-%{version}-%{release}.gz $RPM_BUILD_ROOT/boot/xen${ext}-%{xvermaj}.gz ln -s xen${ext}-%{version}-%{release}.gz $RPM_BUILD_ROOT/boot/xen${ext}.gz ln -sf xen-syms${ext}-%{version}-%{release} $RPM_BUILD_ROOT/boot/xen-syms${ext} } So the architectures are being specified, but the files don't exist. Anyone got any pointers as to what I need to do? For the full build log and to see my spec file, see my branch[0]. Many thanks, Andy 0 - https://build.opensuse.org/package/show/home:FunkyPenguin:branches:Virtuali… -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

Re: [opensuse-virtual] XEN on a 13.1 system
by Jim Fehlig 22 Jan '14

22 Jan '14

Charles Arnold wrote: >>>> On 1/20/2014 at 07:29 PM, in message <52DDDBA2.5000908(a)suse.com>, Jim Fehlig >>>> > <jfehlig(a)suse.com> wrote: > >> Hans Witvliet wrote: >> >>> Yes, i forgotten that xm/xend is depreceated. >>> Heard that a couple of times at several fosdems from Ian, >>> and when you mention "xm" at the xen-lists you are considered a relic >>> from a distant past.... >>> >>> >>> How ever: >>> When you do a fresh instalation of the xen-stuff in 13.1, and you try to >>> create a VM like one is used to do in previous versions, i still got a >>> warning that i had to check because "xend was not running" >>> >>> >> Charles, is there a check in {vm,virt}-install for xend running? I >> vaguely recall something along those lines, but suppose it was fixed >> long ago. >> > > Yes. vm-install does check for a running xend. This is how it knows > whether to use 'xm' to start VMs or if xend is not running it uses a > libvirt connection to start VMs. The only time vm-install uses 'xl' for > starting VMs is if xend is not running and it fails to connect to libvirt. > Failure to connect could mean libvirtd was not running or some other > error occurred when connecting to libvirtd. > BTW, I don't think we should support xl in vm-install. If vm-install cannot connect to libvirt, then it should just fail IMO. That seems to be the behavior on KVM # systemctl stop libvirtd.service # vm-install libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Otherwise users might be able to create VM's, which they are then unable to see or manage with virt-manager. Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] XEN on a 13.1 system
by Hans Witvliet 22 Jan '14

22 Jan '14

Hi all, Are there any known issues with 13.1 as a DOM0 ? @work, i installed+updated a new system, added XEN-tools + XEN-kernel, enabled bridging, verified with "xm list" that all was up-and-running. But when trying to create a domU (with the yast2-module) no show. First issue was that an ubuntu-client needed hw-virtualisation (which was disabled in the bios), but after tweaking that, still no show. Next i tried sles11sp3 (thus using paravirt.) but same problem. Disabled graphic-emulation, still fails. (sorry for the briefness, no access to those systems here athome) Is there anything i should tweak on 13.1? On 12.1 and 12.2 it worked out-of-the-box... Hans -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

4 7

Re: [opensuse-virtual] XEN on a 13.1 system
by Jim Fehlig 21 Jan '14

21 Jan '14

Charles Arnold wrote: >>>> On 1/20/2014 at 07:29 PM, in message <52DDDBA2.5000908(a)suse.com>, Jim Fehlig >>>> > <jfehlig(a)suse.com> wrote: > >> Hans Witvliet wrote: >> >>> Yes, i forgotten that xm/xend is depreceated. >>> Heard that a couple of times at several fosdems from Ian, >>> and when you mention "xm" at the xen-lists you are considered a relic >>> from a distant past.... >>> >>> >>> How ever: >>> When you do a fresh instalation of the xen-stuff in 13.1, and you try to >>> create a VM like one is used to do in previous versions, i still got a >>> warning that i had to check because "xend was not running" >>> >>> >> Charles, is there a check in {vm,virt}-install for xend running? I >> vaguely recall something along those lines, but suppose it was fixed >> long ago. >> > > Yes. vm-install does check for a running xend. This is how it knows > whether to use 'xm' to start VMs or if xend is not running it uses a > libvirt connection to start VMs. The only time vm-install uses 'xl' for > starting VMs is if xend is not running and it fails to connect to libvirt. > Failure to connect could mean libvirtd was not running or some other > error occurred when connecting to libvirtd. > > For virt-install, it only uses libvirt for starting VMs. It will try to default > to a xen connection if '/var/lib/xend' and '/proc/xen' exist otherwise it > It shouldn't look for /var/lib/xend, since that directory wont exist on a system without xend. Jim > looks to see if qemu/kvm is present and connects to that. With > virt-manager, and the command line virt-install you can specify the > connection you want and that is what virt-install will use assuming the > appropriate libvirt driver was loaded. > > - Charles > > -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 2

[opensuse-virtual] Xen compat
by Wolfgang Rosenauer 17 Jan '14

17 Jan '14

Hi, I've noticed a few days ago that openSUSE 13.1 cannot be installed on openSUSE 11.4 Xen host. All the virtualization stuff with Xen is starting to annoy me if I need to update the host all the time. Therefore I want to look into providing my own kernel for 13.1 and try to get it run. There is a Xen compatibility setting in the kernel which apparently says in 13.1 that it should be backwards compatible down to xen 4.2. Can I simply change that value or are problems expected already before I'm going to try it? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 4

[opensuse-virtual] Static IP and internet access in a VM
by Sankar P 13 Jan '14

13 Jan '14

Hi, I am not sure if this is the right list but this seemed the most suitable. I am using openSUSE 13.1 and using virt-manager I created a SLES virtual machine. One of the applications that I am going to install in the VM requires static ip address and so my VM must have static ip address. In the VM Details, I have set the NIC card to be "Virtual network 'default': NAT" and inside the VM I have given a static i.p. in the yast. However, I am not able to access the internet from my VM. So, what should I do to get: 1) a static i.p. for my VM 2) with the ability to access the internet in the VM (using the host's internet connection) ? 3) Ability to ssh into the VM directly without coming into the host machine, will be good to have but not at all needed if it will complicate the setup (due to the static ip requirement) In VirtualBox, I have achieved the above by creating two network cards one with hostonly and another with Bridged networking. One will be DHCP (bridged) and will give me access to the internet and the hostonly will give me a static i.p. address for the VM. (IIRC) Is there a way to satisfy this requirement ? Google does not seem to return any helpful results for this. Any help will be appreciated. Thanks. -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

4 6

[opensuse-virtual] BUG: unable to handle kernel NULL pointer dereference
by Jeroen Groenewegen van der Weyden 13 Jan '14

13 Jan '14

Hi All, Yesterday my xen machine stopped working, after a kernel panic. To me it seems to problem started at something called xen_spin_kick, I attached a screenshot of the console of the xen machine. Is this email-list the right one to address this bug? disto: openSuse 13.1 kernel 3.11.6-4-xen xen : 4.3.1_02-4.4 mfg, Jeroen

2 3