July 2013 - openSUSE Virtual - openSUSE Mailing Lists

Re: [opensuse-virtual] Issues with virt-manager 0.9.5
by Michael Hill 01 Aug '13

01 Aug '13

Thanks, Tony. On Tue, Jul 16, 2013 at 6:34 PM, Tony Su <tonysu(a)su-networking.com> wrote: > - What version openSUSE are you running, and what Desktop? 13.1/Factory with GNOME Factory desktop (mostly 3.9.4). > - Is there a reason why you choose to run virt-manager 0.9.5? It's just the version I get with Factory, I guess. > - Exactly what do you mean by "import?" - Are you trying to create a > new Guest using an existing virtual disk, or something else? I'm importing the GNOME OSTree qcow2 image from here: http://build.gnome.org/ostree/buildmaster/images/z/current/ ...as described here: https://wiki.gnome.org/GnomeOSTree > - If you're trying to create a new VM, are you doing it by clicking > the "Create a new virtual machine" button top left and directly under > the "File" menu? Yes. > - Are you trying to change the disk format or just use a disk "as is?" As is, using "Import existing disk image" and "Customize configuration before install." Clicking on "Disk 1" in the customization dialogue gives the error. > Also, you should know that if you're trying to create a new VM, there > are <two> different programs, one can be launched from vm manager and > has a "pretty chrome" appearance. The other can be launched a couple > ways, one is from the Desktop, eg 'virt-manager --no-fork -c qemu:///session' to access QEMU Usermode. I imported the daily image a number of times until about a month ago (when I messed up my laptop). It can then be launched from virt-manager or GNOME Boxes. > App Launch button > System > Virtualization > Create Virtual Machines > for Xen and KVM I'll take a look at this, thanks. Mike -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 1

Re: [opensuse-virtual] Issues with virt-manager 0.9.5
by Michael Hill 17 Jul '13

17 Jul '13

On Wed, Jul 17, 2013 at 10:00 AM, Tony Su <tonysu(a)su-networking.com> wrote: > Factory is Beta code. Yes, I've been running it for a couple of years now, with the occasional crushing setback. I work on upstream GNOME docs, so it's good to be able to use beta versions. > If you run into problems like what you describe, you should submit a > bug to bugzilla (http://bugzilla.novell.com). I'll try to gather more information and maybe file a bug. I have 0.10.0 running well on Fedora. Thanks, Mike -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] Issues with virt-manager 0.9.5
by Michael Hill 16 Jul '13

16 Jul '13

I'm trying to import the GNOME OSTree current qcow2 image using virt-manager 0.9.5 on GNOME Factory. I get these messages on launch... mike@himon:~> virt-manager --no-fork -c qemu:///session /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+CellRendererSparkline::data-array after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+CellRendererSparkline::reversed after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+Sparkline::data-array after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+Sparkline::num-sets after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+Sparkline::reversed after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+Sparkline::rgb after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property virtManager+graphwidgets+Sparkline::filled after class was initialised type_register(cls, namespace.get('__gtype_name__')) During the import operation, when I try to specify the disk format in the interface, I get this instead of the usual list of disk formats... Error message: Error refreshing hardware page: unsupported operand type(s) for /: 'NoneType' and 'int' Details: Error refreshing hardware page: unsupported operand type(s) for /: 'NoneType' and 'int' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 1307, in hw_selected self.refresh_disk_page() File "/usr/share/virt-manager/virtManager/details.py", line 2921, in refresh_disk_page iotune_read_bytes_sec = disk.iotune_read_bytes_sec / 1024 TypeError: unsupported operand type(s) for /: 'NoneType' and 'int' Any suggestions where to look for a solution? I've posted this to opensuse-gnome as well. Thanks, Mike -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

Fwd: [opensuse-virtual] Best Practices / Details for Serial Console debug-level logging when using Xen + systemd ?
by Tony Su 05 Jul '13

05 Jul '13

---------- Forwarded message ---------- 1. Wondering if you have considered the method described at Freedesktop.org(one of my primary sources of info on systemd) http://freedesktop.org/wiki/Software/systemd/Debugging/ 2. Is this for a special purpose? If not and if you're just setting up a regular maintenance system, have you considered extracting and aggregating logs remotely using IP instead of serial using something like Logstash? Tony -- 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] Best Practices / Details for Serial Console debug-level logging when using Xen + systemd ?
by ar16 02 Jul '13

02 Jul '13

I boot Opensuse 12.3 + Xen 4.3 using Grub1. Reading http://en.opensuse.org/SDB:Systemd#Getting_debug_from_systemd There's a note to ln -s /usr/lib/systemd/system/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty(a)ttyS0.service On my system, I have just: find /usr/lib/systemd/system/ -name *serial-getty* /usr/lib/systemd/system/serial-getty@.service i.e., I do NOT have the symlink for startup in place. I currently have serial console(s) enabled using the config below. It seems to work, but it's evolved to this over time, tweaked as kernel- and xen-versions have changed. I suspect it needs some clean up. My goal is to have grub, early boot, Xen and detailed, debug-level, complete boot logged to both a serial console & video out. What, if anything, SHOULD be changed in the config below for correctness? Specifically, what's recommended for getting the 'right info' form boot process for informative reporting on bugs? cat /boot/grub/menu.lst ... serial --unit=0 --speed=57600 --word=8 --parity=no --stop=1 terminal --timeout=6 serial console ... title Xen root (hd0,0) kernel /xen.gz vga=gfx-1280x1024x16 ... systemd.log_level=debug systemd.log_target=syslog-or-kmsg loglvl=debug guest_loglvl=debug com1=57600,8n1,pci console=vga,com1 console_timestamps ... apic_verbosity=verbose iommu=verbose ... module /vmlinuz-xen log_buf_len=4M console=tty0 console=xvc0,57600n8 xencons=tty earlyprintk=xen vga=0x31a ... showopts noquiet module /initrd-xen ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 3