Mailinglist Archive: opensuse-bugs (4068 mails)

< Previous Next >
[Bug 714183] New: Since last update Xen VM's don't start if the name contains dots (as in 'example.mydomain.com')
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 25 Aug 2011 12:24:28 +0000
  • Message-id: <bug-714183-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=714183

https://bugzilla.novell.com/show_bug.cgi?id=714183#c0


Summary: Since last update Xen VM's don't start if the name
contains dots (as in 'example.mydomain.com')
Classification: openSUSE
Product: openSUSE 11.4
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.4
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Xen
AssignedTo: jdouglas@xxxxxxxx
ReportedBy: podpora@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101
Firefox/5.0

After installing the latest Xen update (version 4.0.2_52-0.2.1) our VM's didn't
start anymore - xm create reported "Error: (22, 'Invalid argument'".

Changing the name inside VM config file to a shorter name or replacing dots
with underscores (as in example_mdomain_com) helps - the VM can be started as
normal.


Reproducible: Always

Steps to Reproduce:
1. Change the VM name in config file to include dots
2. Start / create the domain with 'xm create'
3. Observe the Error: (22, 'Invalid argument' error
Actual Results:
xm create example.mydomain.com
Using config file "./example.mydomain.com".
Error: (22, 'Invalid argument')

Expected Results:
The VM should start as it did before the update.

I know it is relatively easy to change VM names in configuration, but we like
to name our VM's according to their FQDN and if there is no strong reason
against it, we'd like to continue doing so.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >